Recording Logic

[danorum]

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.

I was just planning to start writing an app that could do exactly this. My plan was for it to be a Windows EXE that you could put in scheduled tasks and run it once a day (maybe 4:00am). It would send an email to you that there are conflicts (and maybe even with the details of them) so you know to go look/resolve them.

Is this something people would want to try out?

Dan

[jrockow]

Personally, I'd rather wait for Sub's input.
It might not be that difficult for him to add?

[danorum]

Personally, I'd rather wait for Sub's input.
It might not be that difficult for him to add?

OK. Now that I have NPVR all set up, I am not sure how much I will go into the recording screen (and I shouldn't have many conflicts), so the email will work better for me.

[MarkHotchkiss]

. . . I am not sure how much I will go into the recording screen (and I shouldn't have many conflicts), so the email will work better for me.

An email would work better for me, as well, as I get emails for most other things that occur on my network, like backup status. Now that my recurring recordings are all programmed, I almost never log into the NextPVR computer. We watch all of our recordings using a Dune as the client, so I don't know what Sub might add that we would be able to see.

Here's a suggestion: Rather then scheduling your program to run autonomously, put it in a batch file named "PostUpdateEPG.bat" in NextPVR's \scripts directory, and it will be run automagically after each program-guide update.

[danorum]

An email would work better for me, as well, as I get emails for most other things that occur on my network, like backup status. Now that my recurring recordings are all programmed, I almost never log into the NextPVR computer. We watch all of our recordings using a Dune as the client, so I don't know what Sub might add that we would be able to see.

Here's a suggestion: Rather then scheduling your program to run autonomously, put it in a batch file named "PostUpdateEPG.bat" in NextPVR's \scripts directory, and it will be run automagically after each program-guide update.

Great suggestion, and the utility has been uploaded to a thread in the add-ons forum - http://forums.nextpvr.com/showthread.php...-conflicts

[jrockow]

I would love to have this new feature work for me as described, but so far no go.

I have a conflict with a program (Fast N' Loud) I'm trying to record, (as expected) but it just doesn't seem to want to automatically schedule the next showing.

The original showing is 9/14 at 9:00 PM.
The same episode runs 2 hours later, then 5 days later, then again another day after that.
None of them ever get scheduled.

The "look for conflict" checkbox is checked in Settings.

What am I missing?

I have attached the log and the EPG snippet file.

As always, thanx to you guys for your support.

[johnsonx42]

the new logic is not firing during your EPG update, as if it's not enabled. I'd verify in config.xml that you have <LookForConflictAlternatives>true</LookForConflictAlternatives> in the <Recording> section of config.xml (nevermind the checkbox for the moment), then exit npvr, restart the recording service and then run another epg update. You surely know this, but as a reminder if you run the EPG update from the Settings->Channels screen, the log of it will be in NPVR.log.

[jrockow]

I had already checked the config statement; it was set to "true".

I have attached the log file.



Just a thought; does it matter that I'm not using Schedules Direct?

[johnsonx42]

Just a thought; does it matter that I'm not using Schedules Direct?

yeah, that's probably the trouble. I didn't look carefully enough at the episode-num provided by your EPG data; that "ms_progid" may not be loaded by the EPG update process as the internal "unique_id" that everything depends on. I don't have your database, but I see nothing in your log indicating any unique_id's are being processed at all. I see almost all of your recordings are set for "new only" or a specific day/time which I'm guessing you do because you have no unique_id support so you can't just say "record 'em all but no dupes" like I do.

easy answer: use schedules direct.
harder answer: convince sub that he should add processing for your particular EPG source's episode-num system. he may not care to, supporting the various rogue epg sources for the US is kind of a pain when schedules direct is supported and reliable (another way to read that answer: he should spend his time doing that in order to save you $2 a month?).
hardest answer: find a way to pre-process your EPG data and convert the "ms_progid" episode number into something supported by npvr. this will have unintended consequences unless you do it right. (another way to read that answer: you should spend your time doing that in order to save yourself $2 a month?).

[jrockow]

johnson42,

Thanx for taking the time to check this out and respond with suggestions.

I realize the cost of SD isn't much, but right now I keep bouncing back and forth between NPVR and SAGE.
I was a SAGE user for many years and it's hard to let go.

Right now I'm using mc2xml for my EPG.

I agree that it's not worth Sub's time to look into this.

Thanx again!