Device failed to start

[leaded1]

Got a good analog recording on my PVR2-USB2 this evening without crashing NRecord by using the latest Unmanaged.dll from above.
Thanks sub!

[sub]

Got a good analog recording on my PVR2-USB2 this evening without crashing NRecord by using the latest Unmanaged.dll from above.
Thanks sub!

Great.

[sub]

After reboot, it looks like it's all good. Cranked up all tuners without error (4 analog tuners plus 4 recordings on 2 digital tuners). I'll give it another workout tomorrow, but it looks like you've done it again! Now I have some champagne to drink and a girl to kiss! Cheers to all.

Good - hopefully it stays that way. Let me know how your further testing goes tomorrow.

[mulletback]

Happy New Year, sub! My analog problems are fixed - the PVR-500 is back in the game.

[sub]

Great.

[roy]

Good - hopefully it stays that way. Let me know how your further testing goes tomorrow.

Testing went well. I set up a full schedule of recordings to use all tuners, back to back, all recorded properly with no problems.

Thank you again.

[sub]

Phew.

[Misko5]

Basically I set up everything how I wanted to with the first qam device listed, then I chose the copy device settings option or whatever it is called for the second one. I only need to record two channels so I only enabled the two I needed and mapped them. There are no error messages when I choose quick record on either channel, and both files are created in my recordings directory. However, only the first channel I chose quick record with gets recorded. Doesn't matter which order, it's always the first one I choose that gets recorded. The second one I choose just creates the file in the directory but doesn't record anything. The only error message I ever get is when I go to my device setup and click "scan", sometimes one or both will say "Unable to start device: device failed to start". As far as

Use that LogTSFlow=2 tip mentioned on the last page, and post the mon-*.txt files so I can take a look.

goes, I do not know how to do this.

[roy]

Today I scheduled several recordings for 10am, and watched as they all started properly. Came back a couple hours later and they were all still recording, past the end time. I could play the recordings, which were still increasing, but couldn't cancel them and Device Status would not open. After reboot, all recordings showed as failed with "Recording service not running at recording time". Removed each failed recording, and all files were deleted except the actual .ts file.

Should be in the logs.

I've scheduled some more now, to start during the Patriots game recording.

[sub]

Today I scheduled several recordings for 10am, and watched as they all started properly. Came back a couple hours later and they were all still recording, past the end time. I could play the recordings, which were still increasing, but couldn't cancel them and Device Status would not open. After reboot, all recordings showed as failed with "Recording service not running at recording time".

This wasnt related to your analog problem fixed earlier in the thread.

Its an occurrence of a years old problem we occasionally see in both NPVR and GBPVR where the app askes a device to stop, but that call never returns, effectively leaving the recording service frozen. I've no idea what causes it, and I've never been able to reproduce it myself.