[mythtv] Jumping around. was: Re: 0.19 dvb-t recording: bytepos-offset does not match keyframe in recordedmarkup

[Stanley Merkx]

Hi,

More in general something seems wrong with frame/bytepos calculations.
If I jump back while watching a recording the distance of the jump is far
more than configured. Also, the distance seems to get more the further I
am into the recording.

Cutpoints detected by mythcommflag are also way off when jumping to them.

Almost as if a wrong fps setting is used in a calculation somewhere...
This is with 0.19-fixes (9349) in a PAL country.

Anyone else seen something similar?

Regards,
Stanley.


> Hi,
>
> while I was preparing some movies to burn it on DVD (recorded->cutlist
> via
> recordmarkup->offset to bytepos cuts) I found out that the offset (Type:9)
> in
> recordedmarkup not longer match the keyframe. I compare the offset
> (bytepos)
> infomation with ProjectX and the offset is something between 10000-3000
> bytes
> behind the real keyframe position.
> I rebuild the seektable with "mythcommflag -c xxxx -s 'yyyyyyyyyy'
> --rebuild"
> and get a new seek information (Type: 6) matched perfectly.
>
> Looks like something is goes wrong with the offset calculation while
> recording
> dvb(-t).
>
> The is happend since Version 0.19. Version 0.18.x works fine.
>
> Cheers Jan
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>