[FFmpeg-trac] #3545(avformat:closed): Unsupported pix_fmts in avi rawvideo are written without any warning
FFmpeg
trac at avcodec.org
Sat Apr 12 14:59:41 CEST 2014
#3545: Unsupported pix_fmts in avi rawvideo are written without any warning
------------------------------------+------------------------------------
Reporter: peter_b | Owner:
Type: defect | Status: closed
Priority: minor | Component: avformat
Version: git-master | Resolution: fixed
Keywords: avi mov | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 0 |
------------------------------------+------------------------------------
Comment (by peter_b):
I'm using out-of-the-box working ffv1+pcm_s16le+avi for everything
(including >8bit) at the moment. Works perfectly :)
More than 8bits-per-component is generally not well supported, varying
from application to application, in different containers as well as
codecs. Uncompressed >8bit seems to be even more of a "stepchild" ;)
Thanks for pointing out that I'd be creating invalid/unreadable files
using the rawvideo approach in AVI.
Is there any way of creating >8bit uncompressed (doesn't have to be
rawvideo) AVIs? For yuv422p10le, V210 does just that, but what about e.g.
16bit?
According to the MSDN article, it sounds like it should technically be
possible. Even if WMP wouldn't play them, they'd have a defined standards-
compliant bitstream, so it'd be the fault of WMP, not ffmpeg.
I'm just trying to understand this.
If this is not the right place to discuss this, should I post it on the
ffmpeg-user ML?
Thanks.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3545#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list