[MPlayer-dev-eng] Re: [PATCH] dvr-ms fixes for pts, key frame detection and seeking
johnfdonaghy at gmail.com
Fri Feb 16 19:48:53 CET 2007
> Yes sh_video->fps is set based on the distance between frames. However
> that does not mean it works "on the bases you can't get fps from the
> container" - if the container gives constant-distance timestamps that
> will produce the same fps. The value of sh_video->fps doesn't matter all
> that much anyway. Video timing is done based on the timestamps.
You're right, I didn't explain it very well but my issue comes down to
I can set a correct fps value at the start and then I could start producing
pts values that were evenly spaced (0.033, 0.066 etc) until I read a real
pts value form the container, which will typically be a much larger number.
I cant then pass this on because the fps will get messed up and mplayer will
start complaining. But if I dont use the pts values in the container for
both audio and video then AV dosnt sync. I'm thinking that if
video.cdoesn't adjust the fps when it gets the new much larger pts
container then it might be possible to play the files.
Most dvr-ms files have non-cronological pts values most of the time -
correct-pts works to some extent with these but so far I havent been able to
get seeking working at all with it. Also, the dvr-ms files that have
intermittent i-frame pts values only wont play at all with correct-pts.
I know I'm not explaining this very well, I just dont have the time to spare
to do it properly. Sorry.
> MPlayer-dev-eng mailing list
> MPlayer-dev-eng at mplayerhq.hu
More information about the MPlayer-dev-eng