RE: FW: [xine-devel] mpeg2 decoder and GOP timecode

[Deas, J. <Jam...@wa...>]

I noticed that the mpeg decoder already reads the header and gets the
GOP timecode from the stream. I have failed to find a subroutine I can
call to extract that data when this is used as a plugin. I ran the
decoder with a simple printf around the timecode detect and confirmed
that the information is there.
 Am I missing a call that would allow me to get data from the decoders
data structure. If not, what are the ramifications of extending the
decoder plugin functionality? It seems to me that the decoder would be a
logical place to extract time information from most streams. It would
already have access to the decoded GOP and would be in a position to be
called by the post plugin as the first step when supplying a new frame
of data.

JD


-----Original Message-----
From: Michael Roitzsch [mailto:mr...@us...]=20
Sent: Friday, May 14, 2004 2:01 PM
To: xin...@li...
Cc: Deas, Jim
Subject: Re: FW: [xine-devel] mpeg2 decoder and GOP timecode

Hi,

> Would a better fit be to write a spu decoder plugin vs a post plugin?
> Looking at the graphic layout I would assume this is closer to what I
> want (frame accurate timecode burn-in window).

A SPU decoder is different. It takes subpicture information from the
stream,=20
like subtitles and converts them into an overlay. You don't want that,
since=20
you are not decoding any subpicture, you are post-processing the video=20
frames. The SPU decoder does not even receive the timestamps of the
video=20
frames.

> Is it even possible for the OSD to change every field or frame?

It should be.

Michael

--=20
"Premature optimization is the root of all evil."   =20
	-Donald E. Knuth