-
Notifications
You must be signed in to change notification settings - Fork 165
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
Obtain an AudioBuffer from a MediaElementAudioSourceNode #1872
Comments
For context, I'm trying to precisely schedule audio that comes from EME https://developers.google.com/web/fundamentals/media/eme. e.g. Using https://developer.spotify.com/documentation/web-playback-sdk/ or Apple's Player |
I think the third answer on the stackoverflow question will do what you want: connect a Not sure how useful that will be since you don't have a whole lot of control over when you get the data so the captured data won't be sample accurate, even if the |
Thank you. Yes I'm not sure if this would work in my case. Perhaps EME support for an AudioBuffer could be considered? Or some implementation of |
There is work on a new decoding API and that would presumably include support for EME. The shape of the API or even all the capabilities aren't known yet; we're still in the early stages. But I think it will be handled by the media API and not WebAudio. But certainly the needs of WebAudio should influence the decoding API. |
This needs to be reviewed by the group. |
Teleconf: Too late to do anything in v1. Punting to the next version. |
This will not be considered for V2, as it is better placed in webcodecs. |
Describe the feature
The ability to obtain a buffer source from an audio element. Even when an audio element is fully loaded, it's not possible to schedule samples of audio using a MediaElementAudioSourceNode.
https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-html5/HkX1sP8ONKs
https://stackoverflow.com/questions/11292076/load-audiodata-into-audiobuffersourcenode-from-audio-element-via-createmediae
The text was updated successfully, but these errors were encountered: