search for: decodeaudiodata

...ne has connections with browser vendor engineers, it would be worth considering a direct way for JavaScript to access browsers' baked-in Opus decoding library, which would avoid the ~140-220K Wasm binaries currently needed to do this. Only complete files can be downloaded with BaseAudioContext.decodeAudioData(): https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/decodeAudioData -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20181102/33bd013f/attachment.html>

...ssues/1 You may also be interested in <https://github.com/brion/ogv.js/> (if you're not already aware of it). There might be some useful collaboration possible. > ~140-220K Wasm binaries currently needed to do this.  Only complete > files can be downloaded with BaseAudioContext.decodeAudioData(): > https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/decodeAudioData Maybe I'm confused, but I thought this was the purpose of the Media Source Extensions? If you can parse page boundaries with JS/WebAssembly, it is pretty simple to assemble a "complete" file...

...be interested in <https://github.com/brion/ogv.js/> (if > you're not already aware of it). There might be some useful > collaboration possible. > > > ~140-220K Wasm binaries currently needed to do this. Only complete > > files can be downloaded with BaseAudioContext.decodeAudioData(): > > > https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/decodeAudioData > > Maybe I'm confused, but I thought this was the purpose of the Media > Source Extensions? > > If you can parse page boundaries with JS/WebAssembly, it is pretty > simple to a...