rjmorris at nc
May 27, 2012, 6:33 AM
Post #6 of 11
"Michael T. Dean" <mtdean [at] thirdcontact> wrote on Sun, May 27, 2012 at 07:52:58AM -0400:
Re: RFE: Put part-watched recordings at the top of the Watch List
[In reply to]
> On 05/27/2012 07:45 AM, Simon Waldman wrote:
> >From: "Michael T. Dean"
> >>You guys do know about:
> >>TV Playback/JUMPPREV -> Jump to previously played recording
> >>(defaults to unbound) which will always take you back to the last-played
> >>recording, or
> >>TV PLAYBACK/PREVCHAN -> Switch to the previous channel
> >>(defaults to 'H'), which will take you to the previously-played
> >>recording when in recording (non-Live-TV) playback? It doesn't work in
> >>TV Frontend context (i.e. Watch Recordings), but you can start playing
> >>any recording and use the key to go back to the one you were watching
> >I didn't know about those. Do they work across sessions?
> They will work across playback sessions, but not
> > (ie will it
> >work two days later when the combined FE/BE has been shut down and
> >booted a few times)
> across frontend restarts
> >While they would offer a slight convenience boost if so, they don't
> >help with "I've forgotten that I was half way through this programme".
> However, I would like to extend the feature to actually store the
> previous recording information in the database so that they will
> work even after shutdown, as well as supporting the use of these
> bindings in Watch Recordings to take me to the last-watched show.
> (I also often forget what I was watching.)
> >>Or, if you don't want to bind a key, MENU|Source|Jumpt to Program|<title
> >>of show you were previously watching>.
> >That's exactly the same as just selecting it from Watch Recordings, isn't it?
> Yes. I just mentioned this approach because some people don't have
> a lot of extra buttons to devote to the functionality.
> >>As far as the changes/requests, I have some thoughts on how to
> >>accomplish this type of thing more easily, using tags and some
> >>improvements for filtering/sorting in Watch Recordings, and plan to
> >>begin working on that functionality soon.
> >Interesting - good to hear!
> Now I just need to make the time to work on it. :)
I have three primary use cases for this:
1) Start watching a show in one room and finish it in another. I did a
quick test, and it looks like PREVCHAN is specific to the current
frontend, so that wouldn't work for this use case. Is JUMPPREV also
specific to the current frontend?
2) Start watching a show one day and finish it the next.
PREVCHAN/JUMPPREV should work for this use case as long as I stick to
the same frontend. (I put my frontends to sleep instead of shutting
them down, so that shouldn't be a problem.)
3) Start watching a show, exit it to watch something else, then finish
the original show after watching an arbitrary number of other shows.
The time between starting and finishing the original show could be
several days. To complicate matters, those shows in between may fall
into use cases (1) or (2) themselves. I don't think PREVCHAN/JUMPPREV
would work in this use case, because they go back just one show, but
I'd want to go back 2+ shows.
I'm looking forward to your tagging and filtering/sorting
functionality, Mike. I'd seen some of your previous emails mentioning
it and thought it could potentially address these use cases.
mythtv-users mailing list
mythtv-users [at] mythtv