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

Introduce optional default sink id #20

Closed
o1ka opened this issue Sep 27, 2024 · 1 comment
Closed

Introduce optional default sink id #20

o1ka opened this issue Sep 27, 2024 · 1 comment

Comments

@o1ka
Copy link

o1ka commented Sep 27, 2024

AudioSession API seems to be focused on mobile platforms, where the web application usually cannot control which output device audio is rendering to.

On the other hand, on desktop various audio tags and AudioContext entities can play to different output devices (setSinkId API). And in general applications do want to control to which device audio is rendered.

The output audio device is a shared system resource, and audio session/audio focus seem to be meaningful in the context of a shared usage of a specific resource.

There is also Set Default Audio Output Device proposal https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/SetDefaultSinkId/explainer.md#set-default-audio-output-device for an application to centralize the control over where its various audio elements are playing audio to.

Maybe we can align this all by extending AudioSessionState with optional sink id which would act as a default audio output device, in the meaning proposed by "Set Default Audio Output Device"?

@o1ka
Copy link
Author

o1ka commented Sep 29, 2024

duplicate of #6

@o1ka o1ka closed this as completed Sep 29, 2024
@tidoust tidoust transferred this issue from w3c/audio-session-fork Oct 14, 2024
tidoust pushed a commit that referenced this issue Oct 14, 2024
tidoust pushed a commit that referenced this issue Oct 14, 2024
SHA: 10c81d3
Reason: push, by marcoscaceres

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant