Recordings cut-off due to improper use of multiple tuners

[Handy.Man]

Just happenned to me:

Nature of Things was recording on channel 6 20h-21h00 with post-pre padding of 1 min

Doc Zone was scheduled to start 1 min pre padding at 22h00 on channel 6
Bazzo.tv was scheduled to start 1 min pre padding at 22h00 on channel 17
Enquete was scheduled to start 1 min pre padding at 22h00 on channel 2

Instead of rolling over on Tuner 1 from Nature of Things to Doc Zone for channel 6
It started Doc Zone on Tuner 2
Bazzo.TV was started on Tuner3

but it started Enquete on Tuner 1 while 'keeping' recording Nature of Things ... basically terminating the recording.

Hauppauge PVR-2250 Tuner 1 and 2
Usb ATI Wonder 750 Tuner 3
Order of Priority is Tuner 2 , Tuner 1, Tuner 3
Win7 x64

[sub]

Give that patch go. Post #30, which I posted at the same time as your post. I'm pretty sure it'll fix it.

[Handy.Man]

Give that patch go. Post #30, which I posted at the same time as your post. I'm pretty sure it'll fix it.

Yes I saw your post, I will do this later tonight NextPVR is still recording ;-) !

[johnsonx42]

I will try it later tonight or tomorrow. Woe be to the man who installs a software update on the PVR minutes before all the wife's favorite shows begin recording (The Vampire Diaries, The Big Bang Theory, Grey's Anatomy, Beauty and the Beast).

[johnsonx42]

No change. Test scenario was the same, 2 recordings (Friends and American Dad) started at about 23:26 on different physical channels, 3rd recording scheduled for 23:30 on a 3rd physical channel (TMZ) with 1-minute pre-padding. At 23:29, it moved the TMZ recording to the same tuner as American Dad, which cut off that recording.

Also, with these last two NShared updates, the startup time for NRecord has become very long - over 20 seconds, so long that the NPVRServiceControl program throws an error believing that the service has hung on starting. Not really a big problem, but surprising.

[sub]

Also, with these last two NShared updates, the startup time for NRecord has become very long - over 20 seconds, so long that the NPVRServiceControl program throws an error believing that the service has hung on starting. Not really a big problem, but surprising.

I can't see any reason why it would have made the startup slower. I only changed stuff in the code that moves recordings, which won't happen when you start the recording service. Can you see any extra activity happening in the log to account for this 20 seconds?

[johnsonx42]

I can't see any reason why it would have made the startup slower. I only changed stuff in the code that moves recordings, which won't happen when you start the recording service. Can you see any extra activity happening in the log to account for this 20 seconds?

No, no extra activity. You can see it in the nrecord.log, a 20+ second delay between the line where it says it's starting the client listener, and the next line where it says the startup is complete. I'm not completely sure the delay is new with these 2 nshared updates, but it certainly isn't any older than the latest pre-release.

I'll try rebooting...

after rebooting the initial NRecord startup took 12 seconds between the "client listener" and "OnStart() Complete" lines, and restarting it with NPVRServiceControl took 10 seconds between those lines. This still seems longer than expected, but not quite so bad. I attached the two nrecord logs for your review, but I'm happy to shelve this issue for now...

[johnsonx42]

ok, here's a scenario where it worked like it's supposed to:

I started two recordings on two different physical channels as before, but this time I made it so the recording on the second tuner was an hour long, and not just about to end when the third recording was to start. This time it moved the third recording to the next available tuner (analog 1532).

[TVHelp]

Also, with these last two NShared updates, the startup time for NRecord has become very long - over 20 seconds, so long that the NPVRServiceControl program throws an error believing that the service has hung on starting.

I was going to try and create a scenario to help generate logging as well, but when I installed this patch and tried looking at the logs it crashed my win7 x64 computer...repeatedly. First the windows explorer stopped responding, then black screen of death for a few minutes, then a message stating that windows logon could not respond and I needed to hard boot my computer....rolling back to old .dll has fixed this problem. Definitely seems like something is locking up the logs!!! Sorry I will not be able to test or generate extended logs for you

attached logs for 2-22-2013 that resulted in crash (don't think they will show anything, but... - no tuner cut-off info included.

[sub]

No change. Test scenario was the same, 2 recordings (Friends and American Dad) started at about 23:26 on different physical channels, 3rd recording scheduled for 23:30 on a 3rd physical channel (TMZ) with 1-minute pre-padding. At 23:29, it moved the TMZ recording to the same tuner as American Dad, which cut off that recording.

Sorry, can you repeat the test again with this patch and repost the logs? I've added more logging.