[mythtv] Trying to debug seek problems
dave at boost-consulting.com
Mon Jan 30 11:10:43 UTC 2006
Isaac Richards <ijr at case.edu> writes:
> On Sunday 29 January 2006 09:08, David Abrahams wrote:
>> Isaac Richards <ijr at case.edu> writes:
>> > On Saturday 28 January 2006 22:11, David Abrahams wrote:
>> >> Isaac Richards <ijr at case.edu> writes:
>> >> > The problem is that VideoOutputQuartz::UpdatePauseFrame() isn't
>> >> > updating the scratch frame's frame number like it should, since it's
>> >> > using that style of pausing.
>> >> Okay, so how should it update the scratch frame's frame number? And
>> >> why, if it's supposed to work that way, is it apparently perfect with
>> >> my change? What is broken that I'm not seeing?
>> I'd still like to know what's broken by the change I proposed. It
>> would help me to understand the code and not waste as much of your
>> time the next time around.
> Your fix never updates the scratch frame's frame number - it could get out of
> sync with reality. Putting it in UpdatePauseFrame copies the video data and
> the frame number at the same time, so that can't possibly happen..
And if you never read the scratch frame's frame number, it doesn't
have a chance to screw anything else up. I made a patch based on your
advice and entered it in Trac (Ticket #1151), but as it turns out, it
doesn't fix the problem. I still get the unpredictable jumping back
to zero while skipping forward. Did I misunderstand what you were
More information about the mythtv-dev