I didn't think about event triggers... that would work far better than monitoring the logs... good call.<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 29, 2012 at 2:30 PM, Jim Stichnoth <span dir="ltr"><<a href="mailto:stichnot@gmail.com" target="_blank">stichnot@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Nov 29, 2012 at 5:41 AM, Brian Long <<a href="mailto:briandlong@gmail.com">briandlong@gmail.com</a>> wrote:<br>
</div><div><div class="h5">> I was wondering if there is some way I can query MySQL to determine which<br>
> recordings (not videos) have been recently watched and at what time they<br>
> were viewed. I use a similar feature on NetFlix to ensure my kids aren't<br>
> watching things they're not supposed to be watching. It would be nice to<br>
> know this information from MythTV.<br>
<br>
</div></div>My wife has asked for this feature -- not for spying on the kids, but<br>
to help navigate large sets of recordings. The idea would be to offer<br>
a Previously Watched screen, similar to Watch Recordings but<br>
sorted/grouped by timestamp of playback. (This probably makes it more<br>
similar to the Previously Recorded screen.) The screen could be<br>
filtered by recordings watched on a particular frontend, versus all<br>
recordings watched on any frontend. After finding the desired<br>
recording, you could start watching it immediately, or switch to the<br>
Watch Recordings context that was active when it was previously<br>
watched (see example 3 below for more detail).<br>
<br>
Example 1: You painstakingly find just the recording you want, start<br>
watching, then accidentally hit a jump point key. You can easily<br>
resume watching by navigating the Previously Watched screen.<br>
<br>
Example 2: You painstakingly find your recording, start watching, and<br>
then decide to resume watching on a different frontend. The<br>
Previously Watched screen makes this much easier.<br>
<br>
Example 3: You finally start watching your backlog of episodes from<br>
some series. For whatever reason, you don't delete or move into a<br>
different recording group after watching. If you go away and come<br>
back after watching an episode, it could be painful to find the next<br>
episode, so you find the last watched episode in the Previously<br>
Watched screen, switch to its Watch Recordings context, and then<br>
easily locate the next episode in the list.<br>
<br>
This of course makes it (too) easy to spy on other people's viewing<br>
habits, so options for selectively deleting viewing history would also<br>
be in order.<br>
<br>
Now, cool as that may be, it's probably overkill for the readonly<br>
spying application. I would suggest setting up a System Event<br>
(<a href="http://www.mythtv.org/wiki/MythTV_System_Events" target="_blank">http://www.mythtv.org/wiki/MythTV_System_Events</a>) to log something<br>
when the Playback Started event triggers.<br>
<span class="HOEnZb"><font color="#888888"><br>
Jim<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div>