-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add Opus decoding support #4
Comments
local chunk-based decoding tests succeed using |
👍 |
@haywirez I dropped this a few months ago and would be happy to pick up again. Also, decoding would be the easy part, but seeking/queuing would be more difficult. I got as far as branch https://github.com/AnthumChris/fetch-stream-audio/tree/opus-stream-decoder. I'll be busy for a couple weeks and apologize I can't clean this up and give you a proper handoff before then. Now that someone else is interested, it's on my to-do list. |
Am interested too |
@haywirez @lavvy https://github.com/anthumchris/opus-stream-decoder If you could, please test the build and file any issues you notice in |
Chunk-based Opus file decoding should be supported. Emscripten can be used to build WebAssembly modules for decoding the data. The opusfile decoder library could be used if it supports chunk-based byte array decoding. Initial research shows that a complete file may be needed for
OggOpusFile
objects. Otherwise, libogg may be needed to interface directly to parse/assemble the chunks into decodable packets.The preference is to use WebAssembly for all decoding functions and limit use of JS to parse Ogg file structure. mohayonao/libogg.js could be used if JS is needed.
The text was updated successfully, but these errors were encountered: