Bug 215964
| Summary: | iPad: Audio streams received by WebRTC and fed to Web Audio are killed when switching to another app | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Justin Uberti <juberti> |
| Component: | WebRTC | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | darin, electroteque, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 13 | ||
Justin Uberti
Observed on iPadOS14b6, but occurred in earlier iPadOS revs as well.
When receiving an audio stream in WebRTC, and then feeding that stream into createMediaStreamSource, and then connecting that source to AudioContext.destination, this graph gets broken when switching to another app. The context continues as 'running', and the stream is not muted, but all playout stops, and stays stopped even when switching back to Safari.
This does not happen when:
1) WebRTC is fed into an <audio/> element (i.e., no Web Audio)
2) A Web Audio oscillator node is connected to a destination (i.e., no WebRTC)
JSFiddle demonstrating this issue: https://jsfiddle.net/juberti/sr078wyj/
1) Load it up and hit the play button. A tone will start to play out (using WebRTC and Web Audio).
2) Switch to another app. Audio will stop.
3) Switch back to Safari. As seen in the console, the context is still running, but no audio plays out.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/68000812>
Daniel Rossi
Sound is being disabled when creating another createMediaStreamSource when changing to a new stream. Its not related to stopping the audio track. Is there a work around ? Another painful time consuming time to find a work around. Really awful.
https://jsfiddle.net/danrossi303/gsLy96hc/2/