Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Editing a script file with a text editor and then using it with the mac version of OpenSesame

Editing a experiment is becoming very slow with OpenSesame.
I have just tried to open the .osexp file with TextWrangler and found much easier to edit the script and make changes.
The problem then, is how to insert the edited script into an .osexp file (i.e. including also the "pool" file) and to run it on a mac.

Any ideas?
Thank you,


  • Sorry, completely stupid question, solved by just copying and pasting into the general script editor...
    I don't know how to close (and delete) this forum. I would have done it by now otherwise!

  • Hi Javi,

    Glad you figured it out. You could even just save the script with a .osexp extension and open it.

    But of course OpenSesame is not supposed to be unworkably slow. Are you using the latest version? There have been substantial performance improvements lately. If you already are using the latest version, could you upload the experiment here, or another experiment that in your experience is unworkably slow?


    There's much bigger issues in the world, I know. But I first have to take care of the world I know.

  • Yes, I am using the lastest portable version (3.1.7 Jazzy James).
    This experiment is trying to replicate the "color vesion" in Conway et al (2017) Contribution of Implicit Sequence Learning to Spoken Language Processing.
    I am using a keyboard instead of ipads.
    It works fine (although slow) in my imac, but it crashes in a pc with the message "Out of memory"

    Any ideas?

    Thank you for your kind help!

  • Hi Javi,

    Well the problem is clear: You have dozens of sketchpads in a sequence, and no less than 345 items in total! Don't do that to yourself—you deserve better!

    But it explains the memory error: All those sketchpads are loaded into memory at the same time, which can easily lead to an out-of-memory error. I assume that this error occurs when running the experiment, not when editing the experiment?

    So my main recommendation would be to avoid this kind of hyper-serial implementation, and use loops. That will make life easier, and will make OpenSesame faster.

    In the meanwhile, I'll see if I can use your experiment as testcase to find ways to optimize things further. Is there one specific operation that makes OpenSesame extremely slow? (If I edit your experiment on my laptop, it's indeed pretty slow, but not excessively so.)


    There's much bigger issues in the world, I know. But I first have to take care of the world I know.

Sign In or Register to comment.