Bug 203435 – REGRESSION(iOS 13): createMediaElementSource not working

• Status: RESOLVED
• Resolution: FIXED
• Component: Media

[Steven V.]

Audio elements connected to the Web Audio API using the `createMediaElementSource` function don't seem to work anymore on iOS 13.

Tested using this MDN example: https://mdn.github.io/webaudio-examples/media-source-buffer/
Last tested on iOS version: 13.1.3

[Radar WebKit Bug Importer]

<rdar://problem/56647240>

[Greg Fodor]

We use this API in Mozilla Hubs (https://hubs.mozilla.com) and noticed that iOS 13 users no longer can play videos. We traced it back to the videos being paused (and unable to play further) once we called createMediaElementSource.

Videos without audio continue to work fine, and if we do not call that API, videos with audio play through the main audio output. For us, it's important we wire the sound into the WebAudio API for proper attenuation, so playing through the normal method is not something we can switch to.

[Jordy van Dortmont]

Unfortunately we're running into the same issue at DialogueTrainer. We use this API animate the speech of 3D characters for our iOS 13 users. This completely ruins their user experience.

[Adam McAmis]

I’m running into this same issue with an audio visualization app that worked fine in iOS12. Interesting that it’s not broken completely, the audio element will still show up on the lock screen widget for “Now Playing” albeit with no audio actually playing.

[Eugene M. Joseph]

I'm having the same issue with an audio visualization web app that doesn't work anymore in iOS13. Any progress or fixes for this?

[Abe Shakim]

Seconding all these comments. Please fix ASAP.

I've also been having the same issue since the release of iOS 13.  This functionality is needed because iOS doesn't support volume control on the audio element itself, so you need to create an element source and pipe it through a gain node.

[Per Arne Vollan]

Created attachment 387721 [details]
Patch

[David Kilzer (:ddkilzer)]

<rdar://problem/57257358>

[David Kilzer (:ddkilzer)]

*** Bug 204261 has been marked as a duplicate of this bug. ***

[Per Arne Vollan]

Comment on attachment 387721 [details]
Patch

Thanks for reviewing!

[WebKit Commit Bot]

Comment on attachment 387721 [details]
Patch

Clearing flags on attachment: 387721

Committed r254550: <https://trac.webkit.org/changeset/254550>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Maxim Balyaba]

What iOS version has this fix ?
and what about https://bugs.webkit.org/show_bug.cgi?id=203293 ?
Thanks

[dataexcess]

When will this bug-fix be shipped? with which version?
Thnx

[Eugene M. Joseph]

createMediaElementSource is still not working for me in iOS 13.4.1. Do we know which version will include the patch?

[Alexey Proskuryakov]

This issue was supposed to have been fixed in iOS 13.4. Could you please a new report with diagnostics specific to your case?

[dataexcess]

I just tested with 13.4.

The issue is still there... No Audio

[Luigi Pulcini]

I asked all my friends on Facebook to test the following player on their iOS 13.4.1 device. None of them managed to make it work. The playback is stuck.

https://www.staging2.waveplayer.info/

The player uses the `createMediaElementSource` WebAudio function to analyze the audio file and animate the waveform using the Frequency Data coming from the source.
So, my only alternative is falling back to a regular Audio Element (with no waveform animations) for all the iOS 13 visitors.

This has been working just fine on any other known versions since iOS 9.

Please update this bug as NOT FIXED and provide us with an estimated date for the final fix.

[Alexey Proskuryakov]

Sorry for the delay. Could you please file a new bug report? This issue was fixed with a patch, and although the fix appears to have been insufficient, continuing the discussion here increases the risk of confusion and mistakes.

[Luigi Pulcini]

I will do.

Could you please link the new bug report here as well?  I have been patiently waiting for a resolution for months now.

[Alexey Proskuryakov]

The new report is bug 211394.