All, Just a heads up that the IETF codec working group has issued a last call on the draft Opus specification. This means we think the draft adequately documents the format, and that we're willing to live with whatever bugs are present in the reference implementation, if they can't be fixed without breaking decodes. In turn, this means we could really use some feedback from implementers. If you've been using celt, or are considering using opus, please download the latest source release: http://downloads.xiph.org/releases/opus/opus-0.9.8.tar.gz Give it a try, and let us know if you run into any issues. In particular, the API hasn't had a lot of usability testing. If you have editorial or codec development experience, please review the draft specification and report any issues you find: http://tools.ietf.org/id/draft-ietf-codec-opus-10.txt Bonus points for actually trying to implement the spec! The deadline for feedback on this (hopefully final!) draft is November 19. Reports are welcome on the IETF mailing list (https://www.ietf.org/mailman/listinfo/codec), here, or to any of the primary developers personally: Jean-Marc, Tim, Greg, or myself. Cheers, -r -- Ralph Giles Xiph.org Foundation for open multimedia
On 11/8/11 12:30 PM, Ralph Giles wrote:> Give it a try, and let us know if you run into any issues. In > particular, the API hasn't had a lot of usability testing.The CELT API was particularly bad about not have a full set of queries about capabilities (frame size, sample rate, etc.) *AND* not returning intelligent errors that could tell what was wrong. Has this been fixed for Opus? -a
On 11/08/2011 03:30 PM, Ralph Giles wrote:> All, > > Just a heads up that the IETF codec working group has issued a last > call on the draft Opus specification. This means we think the draft > adequately documents the format, and that we're willing to live with > whatever bugs are present in the reference implementation, if they > can't be fixed without breaking decodes. > > In turn, this means we could really use some feedback from > implementers. If you've been using celt, or are considering using > opus, please download the latest source release: > > http://downloads.xiph.org/releases/opus/opus-0.9.8.tar.gz > > Give it a try, and let us know if you run into any issues. In > particular, the API hasn't had a lot of usability testing.It would be nice to have a couple things added: 1) repacketizer API documentation 2) document what the multistream channel mapping data is supposed to look like or provide a simple way to create it Thanks, Justin
On 8 November 2011 12:46, Andrew Lentvorski <bsder at allcaps.org> wrote:> Has this been fixed for Opus?You can check the API documentation at http://opus-codec.org/docs/html_api/ In particular, see http://opus-codec.org/docs/html_api/group__genericctls.html, http://opus-codec.org/docs/html_api/group__encoderctls.html, and -r -- Ralph Giles Xiph.org Foundation for open multimedia
Justin Ruggles wrote:> 2) document what the multistream channel mapping data is supposed to > look like or provide a simple way to create itWe should probably have better documentation in the code, agreed, however for now please see Section 5.1.1 of http://tools.ietf.org/html/draft-terriberry-oggopus-01