Nova-t 500 recording issue (short or missing time)

[Bobins]

Should add for me that when my recordings truncate, the status indicator also stays showing it's still recording both programmes (but of course it's lying )

[Bobins]

Well I thought I'd got a handle on this with the "dispose" error bring a trigger but I was wrong. Saturday night again and ER cut off after 45 minutes when it was the only thing recording and nothing else was happening. This time it was after a clean re-start with no generation of the error before the recordings.

The logs show it recorded for 1 hour with good signal strength and 100% quality but the recording is 15 minutes short and the time markers imply it recorded for over 13 hours :eek: ! (but it didn't)

There are no errors in the logs and other later recordings worked fine.

There's definitely something weird going on here.

[gEd]

that's the problem. the logs suggest gbpvr is behaving as expected. The tray thinks the show is still recording and the recording service continues to check signal strength for a recording that it still thinks is in progress.

The common theme here is that we are all using nova-t 500's and a nova-t stick that i guess uses the same driver set. Either gbpvr is somehow accidentally telling both tuners to finish on a multi-tuner device or there is a bug in the nova-t driver.

it would be interesting to reproduce the problem using the win2k software rather than gbpvr. this might confirm where the problem lies. I'll have to see if I can find some time to do this.

[nj2112]

The Nova-t stick uses a different driver from the Nova-t-500.

Incidentally there is a newer (than CD4.0 version) driver for the stick available from Hauppauge UK site.

http://www.hauppauge.co.uk/pages/support...sonly.html

I tried installing XP SP3 RC2 just to see if there might be something in there that helped but no joy.

[sub]

Well I thought I'd got a handle on this with the "dispose" error bring a trigger but I was wrong. Saturday night again and ER cut off after 45 minutes when it was the only thing recording and nothing else was happening. This time it was after a clean re-start with no generation of the error before the recordings.

The logs show it recorded for 1 hour with good signal strength and 100% quality but the recording is 15 minutes short and the time markers imply it recorded for over 13 hours :eek: ! (but it didn't)

There are no errors in the logs and other later recordings worked fine.

There's definitely something weird going on here.

GB-PVR isnt in the chain of components that has an impact on recording. Data flows from the device, through the demultiplexer, through the mux filter, to disk. None of these are components written by me. If it stops mid stream, I'd guess either the device stopped delivering data (device or driver problem) or the mux stopped writing data.

[nj2112]

Well I tried WinTV, did around 100 start stop cycles on one tuner while the other was doing a background recording and monitored the I/O while doing this. The backgroung recording was unaffected.

So I'd say WinTV doesn't seem to produce this issue.

[gEd]

Thanks for spending time testing out WinTV nj2112. So this suggests that the are not the problem.

Sub: Any thoughts on how we can find the root cause of this problem (as detailed in posts #1, #13 & #30)?

I wonder if it might be worth appealing to anyone else with a Dual DVB tuner that is NOT a Nova-T 500 to spent a little time trying to reproduce this problem?

[ACTCMS]

Thanks for spending time testing out WinTV nj2112. So this suggests that the are not the problem.

Sub: Any thoughts on how we can find the root cause of this problem (as detailed in posts #1, #13 & #30)?

I wonder if it might be worth appealing to anyone else with a Dual DVB tuner that is NOT a Nova-T 500 to spent a little time trying to reproduce this problem?

Appologies for not having had time to do some testing on this...

re sub:

I'd guess either the device stopped delivering data (device or driver problem) or the mux stopped writing data.

Has anyone tried using a different mux?

I use Cyberlink - what are the rest of you guys using?

[martint123]

I have a nova-t-500 and pvr150 and not noticed the problem which appears to need a stick as well??. I have an unused kworld tuner (bit bigger than a stick) that I'm willing to configure if someone can suggest the quickest way to try and break things (I've not read this thread in depth).

Martin

[gEd]

I can reproduce the problem with just the Nova-T 500, no stick necessary.

I use cyberlink Mux.

When Sub said
I'd guess either the device stopped delivering data (device or driver problem) or the mux stopped writing data.

This was in response to Bobins post #32 but this is an aborted recording problem rather than the OP's issue of recording x prematurely ending when recording y finishes.

I confess I'm struggling to think where the mux would fit into this problem unlesss....... how about when recording y finishes, the nova-t has a "blip" and stops sending a signal for recording x, which the mux then can't handle, causing the recording service to barf..I'll see if I can repro the problem again and then test with the ati mux that i still have installed.