Howdy, Stranger!

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

Supported by

Audio error with newest Chrome update?

I was just about to relaunch an osweb study using JATOS/prolific and went to run a final check - only to find that the audio now cuts out after only a few correct responses (each followed by a correct! audio ping). The console error message is:

[Intervention] Blocked attempt to create a WebMediaPlayer as there are too many WebMediaPlayers already in existence. See crbug.com/1144736#c27

It works fine in other browsers but seems to be related to maximum number of audio output streams being reached? Which i guess explains why it happens partway through the experiment...but this is pretty over my head. Is there a way to set the opensesame audio player to only open a single stream or to close it after each time?

Thanks!

The game can be played here: https://onlinestudies.eva.mpg.de/publix/75/75/start?srid=221 (Instructions are in German but just touch the cross in the middle when its available and then try to click the yellow beads when they are there).


Sarah Pope

Comments

  • Also - there's a terminal work around that works for a single computer but not something I can ask recruited participants to do beforehand:

    /Applications/'Google Chrome.app'/Contents/MacOS/'Google Chrome' --max-web-media-player-count=5000

  • Hi @popely ,

    Thanks for reporting this. I can replicate this as well, and I'm going to look into it. For now, maybe you can use a simple inline_javascript to play the sample? Say that your sound file is called my_sound.ogg and is in the file pool, then you can play it like this:

    let sample = runner._pool['my_sound.ogg'].data
    sample.play()
    

    This method of sound playback doesn't appear to suffer from the issue.

    — Sebastiaan

  • This workaround works perfectly, thank you!

    (And thanks for this platform and all the forum updates - they're always so helpful!)

Sign In or Register to comment.