Scheduling issue with program that starts one minute early

[johnsonx42]

I think that Johnsonx42 got scJohn confused with the OP--johnsta.

yep

[johnsonx42]

by the way, for those following along, there are some problems with the idea of processing recurring recordings in channel order; I of course imagined it as a simple change, which is always easy for me because I'm not the one who actually has to implement it. at the time my npvr server was sleeping, so I couldn't have a look at the database without getting out of my chair and walking 20 feet to wake it up, and I was feeling lazy.

having now had a reminder look at the database, it's not in fact a simple change at all. it'll probably require adding a column to the database, and a variety of code changes to populate the new column and handle the alternate processing order without breaking anything. additionally, I was completely neglecting the recordings that don't specify a channel (I have a good handful). the channel_oid is 0 for those; where do you process them? first? last? since those recordings are going to cross channels, they'll defeat some of the tuner allocation efficiency that was supposed to be gained by processing the recordings by channel.

honestly I'm not sure it's worth advocating for at this point.

[sub]

Yeah, I'm not doing it. Too many changes required to even try it.

[johnsonx42]

if I find myself continuing to be curious about this idea, I might write a SQL script that would re-prioritize the recurring recordings by channel_oid+recurrence_oid (to make sure they're all unique). of course at the moment I don't know how to do that, since the channel_oid is buried in XML in the match_rules column. I know just enough SQL to imagine doing things that I won't actually do.