Re: [xine-devel] BUF_FLAG_PALETTE

[Mike M. <mel...@pc...>]

On Mon, 3 Jun 2002, Siggi Langauf wrote:

> Just one comment: You don't really have to care about plugin API versions=
,
> currently: G=FCnter is reworking the plugin system, so we will have to
> increase all of the plugin API versions.
> So if there's a way to simplify things at the expense of an API change: g=
o
> for it! (Not that I could really imagine any such simplification, but you
> sounded like you took great care not to touch the decoder API...)

=09No big deal: I thought about it a little more and I do not see why
I even need to bump the demuxer API version. I will just add the new flag
type and demuxers will use it if they need it. The same goes for the
video decoders. And audio decoders will never care.

> Btw: this _should_ be our last big API change before 1.0, so if there are
>      any other suggestions about any (input/{a,v}output/{a,v}decoder/demu=
xer)=20
>      APIs: make them now or remain silent for a long time!

=09Since you asked, I know of a few other file types that transport
important codec data in the header. Notably, MJPEG-encoded QT files have
header atoms that contain Huffman and quantization tables ('mjht' and
'mjqt'). Any good ideas on how to get that information from the demuxer to
the decoder without making it look like a total hack? More special
flags?...:)

=09Thanks...
--
=09-Mike Melanson