[mythtv-users] seek past a cut

[Joey Morris]

Jim Stichnoth <stichnot at gmail.com> wrote on Thu, Feb 24, 2011 at 06:42:18PM -0800:
> On Thu, Feb 24, 2011 at 5:17 PM, Joey Morris <rjmorris at nc.rr.com> wrote:
> > Suppose my cutlist includes a cut from the 6 minute mark to the 9
> > minute mark of a recording. If Myth has just skipped the cut during
> > playback, and now I'm at 9:03, for example, what should I do if I want
> > to seek back a few seconds to what I just saw before the cut? Using
> > SEEKRWND (bound to my left arrow and set to a 10 second jump) takes me
> > back to the most recent cutpoint, i.e., the 9 minute mark.
> >
> > I understand that Myth is interpreting this as "OK, you want to jump
> > back 10 seconds from 9:03, so that takes you to 8:53. But that's
> > inside a cut, so I'll move you forward to the end of the cut at 9:00."
> > It seems more natural to me that the cut would be excluded from the 10
> > second jump, and therefore it would take me back to 5:53. Was this an
> > intentional design decision, is this a bug, or is this just something
> > that doesn't come up much so no one has really considered it?
> 
> I would guess the latter.  My sense is that most people who even use
> cutlists follow through with lossless transcoding (except for h.264
> recordings) so the issue rarely comes up.
> 
> Ticket #8631 (http://code.mythtv.org/trac/ticket/8631) fixes this
> behavior for relative seeking, absolute jumping, and time display
> (e.g., if the first minute of the recording is cut, it might display
> 8:03 instead of 9:03).  Of course, that's only helpful if you do your
> own builds, since it's unlikely to be incorporated any time soon.

Thanks, Jim. It looks like that patch does exactly what I'm looking
for. Thanks also for the hint about transcoding, as that's probably
the real solution for me long term. I'm slowly working my way through
all Myth has to offer, and while I haven't gotten to transcoding yet,
it's definitely on the list.