Etienne Gaudrain

Seems like a very old issue but still happening with v4.2.0: seeking by clicking on the waveform pauses playback. This is perhaps intentional, but that was an issue for me....

To clarify, I am guessing that the difference between Safari and Chrome is that Chrome accepts any user interaction since context initialisation to unlock the audio context, while Safari only...

For __`use_webaudio=false`__, one has to use the play/pause trick on one sound... To do that, I exposed the list of ids of preloaded sounds in jsPsych.js by adding, before `return...

I made a minimalistic case trial here: https://dbsplab.fun/test/jspsych/test_jspsych-audio-safari-init.html. Doing so I think it is a bit clearer which cases this concerns, but I am still not 100% certain. It looks...

Thanks for your feedback, @jodeleeuw and @becky-gilbert! I had a look at the `preload` plugin. Is there a discussion item somewhere that outlines the rationale? But I also agree with...

Ahah, of course! I modified it such that you can just wait 2s before the sound is played (I had put the spacebar trial just to check that pressing a...

As far as I understand it, as @becky-gilbert noted, the AudioContext is always created suspended. On macOS, hat happens with Firefox, Chrome and Safari. However, it is only suspended until...

Thanks @qbunt, after some research, we had indeed figured out that much. The issue boiled down to the fact that there is no clear documented definition of what Safari considers...

Also happening on Windows 11, Pulsar 1.114.2024021608.