[FFmpeg-devel] [PATCH 1/2] lavf/avienc: Simplify palette handling

Reimar Döffinger Reimar.Doeffinger at gmx.de
Sat Feb 27 19:18:29 CET 2016


On Sat, Feb 27, 2016 at 06:05:20PM +0100, Mats Peterson wrote:
> On 02/27/2016 05:45 PM, Reimar Döffinger wrote:
> >>Not that it couldn't be done with side data packets, though.
> >
> >If it doesn't support side data then the muxers are plain broken.
> 
> The muxers should support side data, I agree on that. The thing is the
> packets come in to the AVI, QuickTime and nut muxers with the palette data
> appended to the video data in the packets.

You never answered that actually...
How do the come in that way?!?
That's not what e.g. the matroska demuxer produces, so stream
copying with some generic remuxing example I am really sure that is
NOT how the packets come in.

> That's a choice Michael have
> made, I think. Possibly someone else, I don't know. Anyway, Michael once
> told me that he would like to view palettized frames as "self-contained",
> where the palette is part of the video data in an atomic way.

I'd be fine with that.
Except that is simply not the way it is currently as far as I can tell.

> Anyway, things work OK right now, and even if the situation is slightly
> confusing, it's probably not a good idea to start messing around with things
> until a clearly defined way of storing the palette for the muxers and
> demuxers has been presented.

I can't see HOW they even COULD work right now?!
Otherwise I wouldn't really care, but as far as I can
tell I don't see how it could work at all but for
some lucky exceptions.
What cases have we actually tested to work?


More information about the ffmpeg-devel mailing list