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

Should AudioSession be able to specifiy the output speaker and/or route options (a la sinkId)? #6

Open
youennf opened this issue Nov 8, 2022 · 3 comments
Labels

Comments

@youennf
Copy link
Contributor

youennf commented Nov 8, 2022

It might be handy for an application to specify the audio route on the audio session instead of each individual media element.

@chrisn chrisn added the TPAC2024 label Aug 1, 2024
@youennf
Copy link
Contributor Author

youennf commented Sep 19, 2024

TPAC 2024 proposal: add API to set speaker route in AudioSession.

@youennf youennf changed the title Should AudioSession be the one used to specifiy the output speaker and/or the route (a la sinkId)? Should AudioSession be able to specifiy the output speaker and/or route options (a la sinkId)? Sep 23, 2024
@SteveBeckerMSFT
Copy link

SteveBeckerMSFT commented Sep 27, 2024

Microsoft is proposing and prototyping a similar API on MediaDevices:

partial interface MediaDevices {
  Promise<void> setDefaultSinkId(DOMString deviceId);
};

Explainer
Chrome Status
GitHub Issue

@youennf
Copy link
Contributor Author

youennf commented Sep 28, 2024

Thanks for the links.
A few things have been discussed at TPAC:

  • This is worth fixing
  • This is essentially the same proposal as Microsoft proposal
  • Having this API within AudioSession can be better if/when we allow AudioSession objects being created from JS (to support two groups of audio in the same document, each group having a different speaker route for instance).

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

No branches or pull requests

3 participants