Annoyances caused by sporting events

[greg in kansas]

Wiki looks good. Also looks like I might want this all the time "--postgame time to add on for postgame chat" to get all the post game shows.

Greg

[mvallevand]

The default is to add 10 minutes for --postgame only use it if you want more or less time

Martin

[dlowe]

Hi Martin,

I love the concept of your add-on but it does not seem to be working as I have expected it too.

In my ParallelProcessing.bat, I have:

"C:\Program Files (x86)\NPVR\NextEnd.exe" --oid %3

In my PostUpdateEPG.bat, i have:

"C:\Program Files (x86)\NPVR\imageGrabLite.exe" --updateepg
"C:\Program Files (x86)\NPVR\NextEnd.exe" --sunday

Now, there are two shows that would have been affected by Sunday's football game:

- Madam Secretary
- Good Wife

Now, when I checked my records on CBS, both started on the regular schedule, and both ended 60 minutes later. As a result I don't have a full episode of the shows. I was expecting that both those shows would either have a delayed start time or be extended by the Football time overage. Neither seems to have happened.

Now, to complicate matters a little, I am in Toronto, Canada. So I can pickup the show from both a local Toronto station and from Buffalo. Based upon my previous experience with Football ruining the post game shows, I now actually record both the US and Canadian channels. Luckily the local channel does not have football running before hand, so it records as expected, it is the CBS feed that does not work as expected. So overall I have not missed my expected content.

I guess the question is, is the intention of your tool to support auto extending of the sporting event that has gone long, extending the recording of the shows that occur after sporting events that have gone long, or both? Could the fact that I was recording the show on two different channels, one affected by the game, and the others not be the cause?

Attached are my logs. Please let me know if I can be of any additional help.

Thanks
<david />

[mvallevand]

Hi Martin,

I love the concept of your add-on but it does not seem to be working as I have expected it too.

I worked well for my on CBS for Madam Secretary (although I record Global too). Do you recall what you did on your machine yesterday morning In the --sunday log I see it was waiting fine until 10:21

It was monitoring 3 events even an NHL game.

Code:

2014-10-19 06:21:26.647    [DEBUG][1]    NFL Football New York Giants at Dallas Cowboys 2014-10-19 16:25:00-2014-10-19 19:30:00
2014-10-19 06:21:26.656    [DEBUG][1]    Requesting wake up for 'SP002981380000' at 10/19/2014 7:26 PM
2014-10-19 06:21:26.663    [DEBUG][1]    NFL Football Kansas City Chiefs at San Diego Chargers 2014-10-19 16:00:00-2014-10-19 19:00:00
2014-10-19 06:21:26.663    [DEBUG][1]    Requesting wake up for 'SP002981360000' at 10/19/2014 6:56 PM
2014-10-19 06:21:26.663    [DEBUG][1]    NHL Hockey Calgary Flames at Winnipeg Jets 2014-10-19 19:00:00-2014-10-19 22:01:00
2014-10-19 06:21:26.663    [DEBUG][1]    Requesting wake up for 'SP003008320000' at 10/19/2014 9:57 PM


But at 10:21 it was all killed.

2014-10-19 10:19:27.567    [DEBUG][1]    Waiting
2014-10-19 10:21:27.577    [DEBUG][1]    CancelAllWakeupRequests

Martin

[dlowe]

Actually no one was home yesterday between 9:00 am and 10:00pm. Based upon the log entries, I believe that you are referring to 10:21 am, so there is no way the computer was touched.

I think that part of the challenge is that i have 9 different things recording on Sunday, and the NextEnd logs only go back three. Is there a way to prevent rotation?

It should be noted that the same-thing has been happening for the past 3 weeks or so (since you released the tool), with the same shows, but as I did not get a chance to collect the logs, I did not raise this problem before.

I can be more diligent with the logs next Sunday, if that helps. The sports issue is normally only a problem for me on Sundays.

[mvallevand]

Actually no one was home yesterday between 9:00 am and 10:00pm. Based upon the log entries, I believe that you are referring to 10:21 am, so there is no way the computer was touched.

Yes AM it was still in wait mode. You didn't include the NRecord.log for yesterday and I can't see anything to indicate why the NextEnd task was killed, but I was interested because it was exactly four hours after it started.

Martin

[dlowe]

I archived the logs directory, so it should have been there, but it seems that it was a locked file and could not be added. I made a copy and was able to archive that, see attached.

Looking at the 6:21 time stamp, i see process to kick off PostUpdateEPG.bat. 4 hours and 11 seconds layer, it reports as complete.

2014-10-19 06:21:21.547 [DEBUG][9] Running PostUpdateEPG.bat
2014-10-19 06:21:21.547 [DEBUG][9] About to run C:\Users\Public\NPVR\Scripts\PostUpdateEPG.bat
2014-10-19 10:21:32.372 [DEBUG][9] C:\Users\Public\NPVR\Scripts\PostUpdateEPG.bat has completed
2014-10-19 10:21:32.372 [DEBUG][9] EPG_UPDATED

Is that expected? When i manually executed the batch today, I get:


C:\Users\Public\NPVR\Scripts>PostUpdateEPG.bat
C:\Users\Public\NPVR\Scripts>"C:\Program Files (x86)\NPVR\imageGrabLite.exe" --updateepg
C:\Users\Public\NPVR\Scripts>"C:\Program Files (x86)\NPVR\NextEnd.exe" --sunday

2014-10-26 18:35 -0400
10/26/2014 6:35:00 PM
6149521
6151873
6151873
6150522
6151567
NFL Football
Indianapolis Colts at Pittsburgh Steelers
SP002981530000
10/26/2014 4:25:00 PM
Madam Secretary
10/26/2014 8:30:00 PM
6150523
6151304
6149522
6151568
10/26/2014 8:25:00 PM
6149523
6150226
NHL Hockey
Ottawa Senators at Chicago Blackhawks
SP003008750000
10/26/2014 7:00:00 PM
Revenge
10/26/2014 10:01:00 PM
Leaving


Where the script execution ends after a second or so. If I execute this on a Sunday, is the task meant to stay active, polling for status changes?

If so, I wonder if NextPVR monitors PostUpdateEPG and kills it if it is executing for to long. Do you think that changing my In my PostUpdateEPG.bat to be:

"C:\Program Files (x86)\NPVR\imageGrabLite.exe" --updateepg
start cmd /c "C:\Program Files (x86)\NPVR\NextEnd.exe" --sunday

might help?

[mvallevand]

Thanks looking at the logs does seem to indicate that it isn't really post update, and NRecord might be killing it.

2014-10-19 06:21:21.547 [DEBUG][9] Running PostUpdateEPG.bat
2014-10-19 06:21:21.547 [DEBUG][9] About to run C:\Users\Public\NPVR\Scripts\PostUpdateEPG.bat
2014-10-19 10:21:32.372 [DEBUG][9] C:\Users\Public\NPVR\Scripts\PostUpdateEPG.bat has completed

Instead of running a second command shell start cmd /c ... I use

start /b "" ... as shown here

http://forums.nextpvr.com/showthread.php...post479655

Running on other days will just give you the log for what's coming.

Martin

[mvallevand]

Oops, it was my code, I have a hard coded limit to stop after fours of monitoring in case the web site I read got stuck. I would have noticed this yesterday as a bug on the NASCAR race but it didn't run the full 4 hours. Using the start command is a good idea for both batch files so when I update the wiki I will add that change too.

Martin

[greg in kansas]

Worked on all 3 shows after the game for me.

Greg