| |||||||||||||
The Opus codec becomes an IETF standardThe Opus codec becomes an IETF standardPosted Sep 11, 2012 21:03 UTC (Tue) by jmspeex (subscriber, #51639)In reply to: The Opus codec becomes an IETF standard by cyanit Parent article: The Opus codec becomes an IETF standard
When you get to bitrates like 128 kb/s, it's so close to transparent that it's nearly impossible to test which codec is best with any kind of statistical significance. If you encoded all your music collection with Vorbis at 160 kb/s, I don't think you'd be gaining much from using Opus instead. Opus, Vorbis and AAC are so close to transparent at those rates that it's becomes mostly an encoder issue. In the end, there are bit-rates where Opus clearly outperforms Vorbis, but we're not aware of Vorbis really outperforming Opus at any point.
(Log in to post comments)
The Opus codec becomes an IETF standard Posted Sep 11, 2012 21:25 UTC (Tue) by drag (subscriber, #31333) [Link]
Web based Voice over IP and super-high-compressed video/music is were Opus should shine.
Can it usefully be embedded in webm?
The Opus codec becomes an IETF standard Posted Sep 11, 2012 21:59 UTC (Tue) by bjencks (subscriber, #80303) [Link]
Not webm, since webm is specifically the matroska/vp8/vorbis combination, with some extra restrictions on what matroska features are available.
There's work on putting it into matroska, though it looks like there are some incompatibilities with seek timestamps: http://wiki.xiph.org/MatroskaOpus
|
|||||||||||||