Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review mute/unmute/ended and constraints on track in audioContext.createMediaStreamDestination().stream #2571

Open
jan-ivar opened this issue Feb 20, 2024 · 1 comment

Comments

@jan-ivar
Copy link

As per w3c/mediacapture-main#984, please review mute/unmute/ended and constraints on the track in MediaStreamAudioDestinationNode's stream.

This is a spec cleanup to remove any implicitly inherited behaviors, requiring each spec that defines a source of new MediaStreamTracks to follow these extension guidelines, specifically:

image

A quick perusal revealed no mention of muted, ended or constraints related to MediaStreamAudioDestinationNode's track.

If a MediaStreamAudioDestinationNode's track is never muted or ended, and cannot be constrained (with applyConstraints), this is now the default behavior, but it might be good to call it out if it is intentional. E.g. something like "The MediaStreamAudioDestinationNode's stream's track is never muted or ended, and has no constraints."

@jan-ivar jan-ivar changed the title Review mute/unmute/ended and constraints on track in ac.createMediaStreamDestination().stream Review mute/unmute/ended and constraints on track in audioContext.createMediaStreamDestination().stream Feb 20, 2024
@mjwilson-google
Copy link
Contributor

2024-04-04 Audio WG teleconference conclusion:

If a MediaStreamAudioDestinationNode's track is never muted or ended, and cannot be constrained (with applyConstraints), this is now the default behavior, but it might be good to call it out if it is intentional. E.g. something like "The MediaStreamAudioDestinationNode's stream's track is never muted or ended, and has no constraints."

We will make the default behavior explicit as suggested above. Thank you for bringing this up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants