Issue with playing same sound/video repeatedly in a trial

Support
1

Hi Chris,

I tried to make a little script that pings the visual or auditory system with a flashing stimulus or sound. Works fine for the image but not for the movie/sound.

  • In the first trial, if I have eg 8 presentations but only 3 stimuli, it will display the first 3 stimuli and then only the photodiode after. It has correct indexing into the group of sound files though.
  • with (and only with) Load or unload stimulus commands, a single stimulus is then played for the following trials instead of the desired e.g. 8. Otherwise no stimulus at all is played after the initial trials.
  • I am assuming this is related to some caching issues since the code is still happily displaying the photodiode image stimulus and a similar code with a visual stimulus works.
  • I tried deferred yes no and explicit, and loading/unloading at hopefully the right locations, to no avail.
  • If I turn alpha_multiplier to 1, I can see that the visual part of the (static) movie is still shown, there’s just no tone. Is it not reset? Setting the repeats variable to some higher value doesn’t change anything either. Does it lose the volume setting and set it back to default off perhaps?
  • I attached the code, set eye_in_window to true to run.
  • Yoon mentioned he remembers he ran into a similar issue before

Thanks

Alina

2

Hi Alina,

I’m not seeing this issue. When I run your audio_only protocol with eye_in_window set to true, I consistently hear eight sounds per trial. If I remove the load/unload actions, the behavior remains the same. I tried throwing in some simulated broken fixations, in case there was an error in the failure-handling states, but everything seems to work correctly.

Can I ask what version of MWorks you’re running? I tested on the current nightly build.

Thanks,
Chris

3

I’m running on 0.11dev. It occurs both with laptop and headphone audio btw. I guess I should try the nightly build then.

Random thought: do the mwork behavioral files that are written always have information on the version it was ran on?

4

I’m running on 0.11dev. It occurs both with laptop and headphone audio btw. I guess I should try the nightly build then.

You are running a nightly, but maybe not a recent one. What is the date stamp? For example, the latest nightly would have today’s date (“Version 0.11.dev (2021.11.23)”).

Also, what version of macOS are you running on?

Random thought: do the mwork behavioral files that are written always have information on the version it was ran on?

Yes, the version is announced in a message, and all messages are recorded to the event file. The message looks like this:

Running MWorks 0.11.dev (2021.11.23)

Chris

5

Problem is indeed resolved with the latest nightly build 

6

Great! Thanks for letting me know.

Chris