[mythtv] [PATCH] position map using frame numbers, rev 2

[Bruce Markey]

Doug Larrick wrote:
> On 12/14/03 14:51:08, Isaac Richards wrote:
> 
>> Seems to work pretty well, aside from if you go into edit mode,  
>> switch to single frame, then seek forward, it looks like it's
>> forgetting where it is.  Only happens for the very first single frame
>> seek, though.  I'll see about fixing it later today if you don't get  
>> to it before then =)
> 
> 
> I'm not seeing this.  You're either gonna have to be more descriptive,  
> or fix it yourself :-D

It's always been like this. Play back something with obvious
motion where you can easily identify where frames are in time.
Press "M" to freeze frame and go into edit mode. Press down
arrow twice so that the scale is set to "1 frame". Press left
arrow intending to go back one frame. What happens is that
instead of going back one frame it goes forward about 20 frames.
The next left does go back one to just 19 frames ahead.

I believe this is because FramesPlayed is something more like
frames decoded and doesn't account for the frames in the
vbuffers. In other words, when FramesPlayed is 100 the frame
shown from normal playback is 980. Left arrow decodes and
displays 99 which is nearly a second later than the pause
when entering edit mode.

I tried to fix this a long time ago but I couldn't figure out
how to pass around the number of frames in the vbuffer. It's
changed a lot since then and may be easier now.

--  bjm