[PATCH]Decode broken v210 samples
Hi! QuickTime specification states for v210 that: Each line of video data in an image buffer is padded out to the nearest 128 byte boundary. Ticket 743 contains some evidence that not all applications are following this recommendation. Unfortunately, I cannot play (any) v210 samples with QuickTime, so I cannot test if our interpretation of the specification is correct. Please review, Carl Eugen
Hi Carl, On Dec 16, 2011, at 5:37 PM, Carl Eugen Hoyos wrote:
Hi!
QuickTime specification states for v210 that: Each line of video data in an image buffer is padded out to the nearest 128 byte boundary.
Ticket 743 contains some evidence that not all applications are following this recommendation.
Unfortunately, I cannot play (any) v210 samples with QuickTime, so I cannot test if our interpretation of the specification is correct.
I am able to play back the output of "ffmpeg -i input.mov -s 356x236 -vcodec v210 -an out.mov" in QuickTime. However, if I remove "/Library/QuickTime/FCP Uncompressed 422.component" and restart QuickTime then I can not. The "FCP Uncompressed 422.component" file was installed as part of Final Cut installation. Hope this helps, Dave Rice
Please review, Carl Eugen <patchv210avi.diff>_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 17/12/2011 9:48 AM, David Rice wrote:
I am able to play back the output of "ffmpeg -i input.mov -s 356x236 -vcodec v210 -an out.mov" in QuickTime. However, if I remove "/Library/QuickTime/FCP Uncompressed 422.component" and restart QuickTime then I can not. The "FCP Uncompressed 422.component" file was installed as part of Final Cut installation. Hope this helps, Dave Rice
Alternatively, on Windows, you can use BlackMagic's uncompressed component. Adobe software also support v210 natively. - Derek
Derek Buitenhuis <derek.buitenhuis <at> gmail.com> writes:
Alternatively, on Windows, you can use BlackMagic's uncompressed component. Adobe software also support v210 natively.
Do they play the sample from ticket 743? Do they play (correctly!) the output of: ffmpeg -i input -s 356x236 -vcodec v210 -an out.avi ? Carl Euge
On 19/12/2011 5:14 AM, Carl Eugen Hoyos wrote:
Do they play the sample from ticket 743? Do they play (correctly!) the output of: ffmpeg -i input -s 356x236 -vcodec v210 -an out.avi ?
Carl Euge
It plays fine in QuickTime using BlackMagic's component, in VirtualDub via BlackMagic's VFW component, and in Adobe software via their native support for v210. As for the output of that ffmpeg line, I output to both mov and avi and tested: Original Picture: http://i.imgur.com/FXC52.png v210/avi in VirtualDub via VFW Codec: http://i.imgur.com/YSWDG.png v210/avi and v210/mov in QuickTime: http://i.imgur.com/YNRbx.png v210/avi in Adobe Software with its native support: http://i.imgur.com/YNRbx.png (Same link cause they're the same output.) v210/mov was declared an invalid mov by Adobe Software. - Derek
Hi Carl Eugen, On 12/16/11 2:37 PM, Carl Eugen Hoyos wrote:
Hi!
QuickTime specification states for v210 that: Each line of video data in an image buffer is padded out to the nearest 128 byte boundary.
Ticket 743 contains some evidence that not all applications are following this recommendation.
Unfortunately, I cannot play (any) v210 samples with QuickTime, so I cannot test if our interpretation of the specification is correct.
Quicktime doesn't pay this file. It plays other files though. -- Baptiste COUDURIER Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA FFmpeg maintainer http://www.ffmpeg.org
Baptiste Coudurier <baptiste.coudurier <at> gmail.com> writes:
Ticket 743 contains some evidence that not all applications are following this recommendation.
Unfortunately, I cannot play (any) v210 samples with QuickTime, so I cannot test if our interpretation of the specification is correct.
Quicktime doesn't pay this file. It plays other files though.
I didn't realize that v210 is installed with FCP. Is the patch ok? Thank you, Carl Eugen
On 12/16/11, Carl Eugen Hoyos <cehoyos@ag.or.at> wrote:
Hi!
QuickTime specification states for v210 that: Each line of video data in an image buffer is padded out to the nearest 128 byte boundary.
Ticket 743 contains some evidence that not all applications are following this recommendation.
Unfortunately, I cannot play (any) v210 samples with QuickTime, so I cannot test if our interpretation of the specification is correct.
Please review, Carl Eugen
lgtm
On 12/16/11, Carl Eugen Hoyos <cehoyos@ag.or.at> wrote:
Hi!
QuickTime specification states for v210 that: Each line of video data in an image buffer is padded out to the nearest 128 byte boundary.
Ticket 743 contains some evidence that not all applications are following this recommendation.
Unfortunately, I cannot play (any) v210 samples with QuickTime, so I cannot test if our interpretation of the specification is correct.
Please review, Carl Eugen
What's status of this?
participants (5)
-
Baptiste Coudurier -
Carl Eugen Hoyos -
David Rice -
Derek Buitenhuis -
Paul B Mahol