Recording Logic
|
2015-08-11, 02:01 AM
mvallevand Wrote:I have a particular problem that I have articulated several times that happens mainly on Sundays on AMC. At 10pm and 11pm they air the same new show and I want to record the 11pm show. I always end up with a conflict for the 10pm because NextPVR tries to record it and then then 11pm show is usually recorded. I think NextPVR should respect the time and only fall back to the 90 minute window when it fails.Ok, I'm sure I can take a look at this too.
2015-08-11, 02:11 AM
Thanks I like to preserve primetime 8-11 for unique shows whenever possible.
Martin
2015-08-28, 04:34 PM
(This post was last modified: 2015-08-28, 04:40 PM by johnsonx42.)
@TRiddle -
just so you know you've not been forgotten, sub has added additional logic to the scheduler to deal with your situation and I've recently completed testing it. In short, when it completes all scheduling operations for a particular recurring recording request, if any conflicts remain it will go hunt for other showings of the same unique_id first on the same channel as the original conflict (on the assumption that the original channel is preferred), and then on any channel. This is done without regard for any other criteria of the original recurring request, whether it was limited to certain days, times, new episodes only, or specific channel; the assumption is that once an episode is identified as a valid episode to be recorded, any showing of that episode is fair game. If no replacement showing is found and scheduled (the replacement could also be in conflict), the original conflict is left and will show in the Conflicts list. for logistical reasons, any showing of an episode scheduled by this logic will be a single recording not subject to further management as part of the recurring recording group, though it will still be grouped by title in the Ready Recordings list. "red text" will be set on the recording indicating why it was created, thus giving a clue to this special status. this feature will be on by default (unless the testing group's opinion changes between now and release), but there will be a checkbox for it in Settings->Recording. For a small subset of users, this feature will not be desired so they can turn it off.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
2015-09-01, 12:44 PM
Excellent. One follow-up question if I may: is this priority based? I'm assuming it is by the way I understand how the scheduling operations worked, I just wanted to make sure. That's the other way to "game" the intelligent recordings system on everything else I've used over the years. If you have a show that has limited showings and is always not recording due to conflicts, just move it to top priority and "usually" the conflicts go away.
The functionality you listed is exactly what I'm after, I guess I just need reinforcement on if the scheduling operations schedule based on priority (as I'm assuming they do). Thanks!
2015-09-01, 05:24 PM
(This post was last modified: 2015-09-01, 05:28 PM by johnsonx42.)
The new logic fires at the end of the scheduling for each recurring recording, so it's based on the priority of the recurring recording that resulted in the conflict. Once created though, these special replacement recordings become single recordings unaffected by the priority system (exactly the same as any single recording you might schedule yourself).
Here's a log snippet from my testing last week: Code: 2015-08-26 15:28:17.327 [DEBUG][8] - Potential episode at: 9/1/2015 8:00:00 PMAfter concluding scheduling for AGT, and before moving on to the next program to be scheduled, it checks if any conflicts remain for this program and begins looking for another airing of the specific unique_id. In this early version of the code it checks all channels right away; in the release version it first looks only on the original channel, and then tries a second time on all channels. It does end up trying to schedule the 9/1 airing again, which is redundant but harmless; not worth the bother to add code to avoid it when it only takes 15ms to do it. It then finds the 9/4 showing, and now unconcerned with the "new only" flag it triumphantly ("Yes!") schedules it. Then it moves on to the next program to be scheduled, 20/20 in my case.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
2015-09-02, 03:57 PM
Excellent. Thanks for the log snippet, that helps me understand the logic quite a bit. And once again, a huuuuuge thanks for this feature.
2015-09-07, 12:00 AM
Spent the long weekend putting the new recording logic through the paces. It is working absolutely perfect. Thanks again for making this happen!
2015-09-11, 12:59 PM
Is there any way to automatically notify the user there is a conflict, or must I always go to the Conflict screen to find out?
I was thinking of some type of popup flag. Thanx.
2015-09-11, 04:33 PM
nothing I'm aware of, certainly nothing within the program. i think maybe the system plugin will display something about conflicts, but you'd still have to access the system plugin screen.
it would be nice if there were some sort of flag in the corner of the recordings screen (regardless of which particular recording screen you're on) that conflicts are present. I go for many months, even years, without getting a conflict, so on the extremely rare occasion that I do, I usually don't find out until I go looking to find out why some show didn't record.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV |
|
|
