[FFmpeg-trac] #3545(avformat:closed): Unsupported pix_fmts in avi rawvideo are written without any warning
FFmpeg
trac at avcodec.org
Sat Apr 12 18:04:27 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 cehoyos):
Replying to [comment:9 peter_b]:
> Uncompressed >8bit seems to be even more of a "stepchild" ;)
If anything does not work with nut, please tell us!
> Is there any way of creating >8bit uncompressed (doesn't have to be
rawvideo) AVIs?
I believe I explained two possibilities:
You can either patch FFmpeg to read the files that you (already) created
or you can teach FFmpeg's avi muxer to write nut fourccs.
> For yuv422p10le, V210 does just that, but what about e.g. 16bit?
From libavformat pov (and as said, this is the only relevant pov for this
discussion) v210 is exactly as compressed (or uncompressed) as ffv1 (or
huffyuv) or any other intra-only codec.
> 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.
How would you know that if you cannot test?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3545#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list