[mythtv] Ticket #8631: Treat cutlists like lossless transcoding
stichnot at gmail.com
Tue Jul 6 21:47:13 UTC 2010
On Mon, Jul 5, 2010 at 10:55 AM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> Jim, I like the idea of making the information available, but I think it
> should be available as just another piece of data in the map, so that
> themers can choose to display it or not--or, more likely, to decide where to
> display each piece of data. It would also be nice to factor in the flag
> list, even if a cut list isn't specified (once it becomes an
> alternative/additional/optional display element).
I like that. I originally thought to have the status say something
like "13:00 of 42:43 (15:00 of 60:00 without cutlist)", but stopped
short after realizing I would have to dig into themes.
> As far as the jumping and seeking goes, though, I'm not sure if that's a
> good thing. I know that 3/4 of the way through a 1-hr TV show is the 45-min
> mark. If I have a cutlist applied and the 1-hr show is now 38min of
> content, I have no clue what 3/4 is--let alone the fact that I have no idea
> how long various programs are after cutting commercials. Therefore, I'd
> like to make this "optional" by the use of different key bindings (i.e.
> LEFT/RIGHT/UP/DOWN work as they always have, but LEFTIGNORECUTS (or
> whatever--better name appreciated) seeks while factoring in the cutlist.
> (And, of course, the other key binding wouldn't factor in the flag list for
> seeking/jumping since you may need to seek to find parts of the show that
> the flagger mistakenly removed.)
More keybindings? How about more settings pages? Just kidding. My
observation is that *every* 1-hour show with commercials ends up being
43 minutes after removing commercials, so I bet you would very quickly
train your fingers that 33 minutes is the 3/4 point.
> The biggest problem with the alternative keybindings approach is that doing
> it elegantly requires some changes to keybindings I have planned to unroll
> the overloaded bindings into separate bindings. Until then, though, just
> adding another case(s) to the TV::SeekHandleAction() function would be fine.
While this is all in progress, the new code to translate between
with-cutlist and without-cutlist frame numbers is there in DeleteMap,
and the intercept points for displaying and seeking based on the
cutlist, are identified in the patch, waiting for the dust to settle.
More information about the mythtv-dev