Safari not playing audio file

lahomann

Hey! So I've tested using the sampler in both chrome and safari, and only chrome works. According to the console it says "Unhandled Promise Rejection: NotSupportedError: The operation is not supported". I used Safari 13.1.1 and Chrome 83.0.4103.61.

I did a little googling and I think the issue is autoplay content blockers on safari. Even with turning them off for every site, it still doesn't work! I think for some reason the user needs to interact with the page for it to work (that's what I read on stack overflow), but they have to press the space bar past a welcome screen so I'm not really sure why it's not working.

I know it's the audio because all I have is a Welcome screen that says 'hi', 1 loop for playing 5 different .wav files, and then the sampler item and a bland sketchpad in between them. I know it takes the time to 'play' them as the end screen also comes up after the right amount of time and you're able to complete the experiment.

Also, I think Safari doesn't support .ogg files so I didn't try that.

Thank you in advance!

sebastiaan

Hi,

Thanks for bringing this to our attention! @Daniel, does this look familiar?

Cheers,

Sebastiaan

Daniel

Hi all,

It doesn't sound familiar, but I can look into it. I think Safari should be able to play ogg files. Which version of osweb are you using? I know that Safari support has improved a lot as of 1.3.8 due to a better build process that creates the osweb library.

 I think for some reason the user needs to interact with the page for it to work (that's what I read on stack overflow), but they have to press the space bar past a welcome screen so I'm not really sure why it's not working.

That's actually what the initial click screen is for. Only after a user clicks on the canvas in which te experiment is shown, we have the ability to play audio and do other stuff like fullscreen presentation. In fact, the whole experiment sort of runs in the scope of this click action. Unless Safari has become stricter in this regard, this shouldn't be the cause of this problem.

sebastiaan

This should be fixed as of OSWeb 1.4.11.

It was a tricky issue, which (as @Daniel_513@Daniel already suspected) did not have to do with lack of user interaction. Rather (if anyone cares 😉) it was due to Safari not being able to read audio from blob URLs.