Do Not Use the Vorbis FFMPEG enecoder if you building WebM!, Monty mentions this in his blog post, but nobody is listening! Options

[HotshotGG]

A lot of open-source enthusiasts and advocates are very excited about Google latest announcement of VP8 / Vorbis combo in a new container called WebM. The entire HTML 5 enthusiasts are so excited that they went a ahead a little to prematurely are building suboptimal builds! Michael Niedermeyer of FFMPEG projects acknowledges that the FFMPEG Vorbis encoder is buggy! Monty has a work around on his blog if you plan on building the WebM encoder under Linux. I am also providing an explanation in the wiki as to why it's generally a good idea to use the mainline libvorbis with libavcodec instead due to the fact that is has 5.1 channel coupling implemented correctly! Please spread the word as this will turn into a disaster sooner or later before it's patched. If you thought the HTML 5 wars are not bad enough now!

Monty's Blog:
http://xiphmont.livejournal.com/51160.html

This post has been edited by HotshotGG: Jun 12 2010, 18:43

[Kohlrabi]

I don't get the point of this post, ffmpeg-people always suggested using libvorbis over their internal encoder, nothing new here. It's the same for ffmpeg's AAC encoder, for example. Noone should use software blindly without doing some (re)search on its functionality first. The easiest way is to drop by in #ffmepg on freenode and just ask. You'd be surprised as to how many "guides" on the net are bad or plain wrong.

If you use libvorbis you have to make sure it's the newest version to have correct multichannel coupling, as this was just introduced recently. AoTuV does not have the new coupling, yet.

This post has been edited by Kohlrabi: Jun 14 2010, 09:00