3 ms·
Given that Opus is built into the browser, is the format backwards compatible? Or will browsers need to update their Opus Libraries to get these changes?
by kernelsanderz 9y ago
Given that Opus is built into the browser, is the format backwards compatible? Or will browsers need to update their Opus Libraries to get these changes?
- jmvalin 9y agoAll Opus releases since 1.0 are fully compatible with the specification (RFC 6716) and all future releases will also be. That's why we have standards. If we ever decided to make something that's not compatible, it would be called a different name.
- kernelsanderz 9y agoThat's so awesome. I guess the webrtc audio encoding libraries would need to be updated in the browsers to take advantage of these improvements though?
- jmvalin 9y agoEven that should happen relatively quickly since so far we've also preserved API and ABI compatibility (since 1.0). Also, we're working closely with the Firefox and Chrome teams so they know what's going on with Opus.
- derf_ 9y agoIn fact, libopus 1.2 has already landed in Firefox (including for WebRTC) and will be available in the next Nightly: https://bugzilla.mozilla.org/show_bug.cgi?id=1374870 https://bugzilla.mozilla.org/show_bug.cgi?id=1374870