Richard Shaw wrote:
I verified the problem exists even when the AAC patch is not
applied.
Reported upstream. We'll see what they say.
Looks like they've broken the libavcodec encoder plugin entirely.
The fix (when they come up with one) should also fix AAC.
(And as I wrote in Bugzilla, the 2.6 branch has AAC enabled in the
libavcodec encoder plugin, so when 2.6.x will be released, we won't have to
maintain that AAC patch anymore.)
Kevin Kofler