interaction between audio elements and the Web Audio API about web-audio-api-v2 HOT 2 CLOSED

Thanks for filing this, @chrisguttandin!

from web-audio-api-v2.

I learned today that the behavior should depend on the connection between an audio element and the Web Audio API.

context.createMediaElementSource(audioElement)

This should re-route the audio from the audio element into the Web Audio API which means the audio element does not produce any sound anymore on its own. This is defined here: https://webaudio.github.io/web-audio-api/#mediaelementaudiosourcenode

The HTMLMediaElement MUST behave in an identical fashion after the MediaElementAudioSourceNode has been created, except that the rendered audio will no longer be heard directly, but instead will be heard as a consequence of the MediaElementAudioSourceNode being connected through the routing graph. Thus pausing, seeking, volume, src attribute changes, and other aspects of the HTMLMediaElement MUST behave as they normally would if not used with a MediaElementAudioSourceNode.

context.createMediaStreamSource(audioElement.captureStream())

This should not affect the output of the audio element. It should be controllable independently. This is defined here: https://w3c.github.io/mediacapture-fromelement/#dom-htmlmediaelement-capturestream

Whether a media element is actively rendering content (e.g., to a screen or audio device) has no effect on the content of captured streams. Muting the audio on a media element does not cause the capture to produce silence, nor does hiding a media element cause captured video to stop. Similarly, the audio level or volume of the media element does not affect the volume of captured audio.

from web-audio-api-v2.