Theora YUV422 and 444 not supported

[Stuart Fisher]

The current version (0.26) assumes that Theora input clips are 420 encoded and subsequently things go wrong if they are not 420 (I discovered this trying to use ffmpeg2theora to re-size a 444 encoded clip). The latest version of ffmpeg seems to handle the pixel format properly, so perhaps you just need to do another build pulling in the latest verion of ffmpeg?

[j^ (j)]

does http://firefogg.org/nightly/ work already?

[Stuart Fisher (stuart-fisher)]

Unfortunately not. You don't even have to try converting anything to verify
the problem. Running ffmpeg2theora --info reports yuv420, even when the
input file is yuv422 or yuv444.

----- Original Message -----
From: "j^" <email address hidden>
To: <email address hidden>
Sent: Sunday, May 02, 2010 6:20 PM
Subject: [Bug 573798] Re: Theora YUV422 and 444 not supported

does http://firefogg.org/nightly/ work already?

--
Theora YUV422 and 444 not supported
https://bugs.launchpad.net/bugs/573798
You received this bug notification because you are a direct subscriber
of the bug.

Status in ffmpeg2theora: New

Bug description:
The current version (0.26) assumes that Theora input clips are 420 encoded
and subsequently things go wrong if they are not 420 (I discovered this
trying to use ffmpeg2theora to re-size a 444 encoded clip). The latest
version of ffmpeg seems to handle the pixel format properly, so perhaps you
just need to do another build pulling in the latest verion of ffmpeg?

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ffmpeg2theora/+bug/573798/+subscribe