Re: [VCDImager Bugs/Devel] code to parse mpeg-2 down to frame level.

[Herbert Valerio Riedel]

a big thank you! :)

I've learned a lot (again) by this code of yours. I've merged it in, while
rewriting vcd_mpeg.c and related modules...

take a look at cvs, I'd like to know if I really have to fill that
search.dat with i-frame-points (if so, I'll make it quick'n'dirty by
estimating the scanpoints... only if this does not work I'll make the
right way -- well... and for version 1.0 I'll do it the right way anyway
:)

I'm estimating the playtime by looking at the timecode at the beginning
and the end of the mpeg1/2 stream, and then taking the difference of it...

...this should work most of the time for genuine mpeg streams, right?

btw, I've been looking at the dumped mpeg frame output... why does the
timecode offset to last GOP timestamp sometimes decrement from one frame
to the next one? :-/

On Fri, 24 Nov 2000, Mike Bernson wrote:
> The following code is parse the mpeg stream
> to find out starting address of each frame
> and store the timecode, packet and offset,
> frame type for each frame.
>
> I have then added a call to vcdimager to
> dump the frames out.
>
> Here is the new vcd_mpeg.* and
> vcdimager.c
>
> Please let me known if you need more info
> on parse mpeg stream for svcd. I think this
> gives you every thing you need.
>
> The frame rate is not read from the stream
> as I was keeping it simple. I do not known
> how you wanted to add this code any you already
> have something to read frame rate.

-- 
Herbert Valerio Riedel      /     Finger address@hidden for GnuPG Public Key
GnuPG Key Fingerprint: AC2A CD57 A5C8 A1CB 0A18  DA95 CB0B DB23 60B6 16F5