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

[ACTCMS]

If you guys had used live tv any time near those recordings, the scenario I described to ACTCMS may have been the cause. There is a fix for this in 1.2.9.

Tested this out tonight - two 30 minute back to back recordings each with 5 mins pre and post padding - live TV running - first recording shows pre padding and no post - second recording shows post padding and no pre - live TV uninterrupted...

Thanks for that sub...

[AlanC]

Perhaps my system just has an aversion to ER

are you using the Microsoft Mux? There is a long standing problem, that certainly applies to Hauppauge DVB, where the picture freezes and the sound continues. Most common on freeview Channel 4 and More 4. Most frequently triggered by a fade to black.

[Bobins]

No. I'm using the ATI mux but now you mention it, I have seen that behaviour as well.

For the second of my two problems, I'm just wondering if this particular issue is something in the CH4 signal that isn't getting handled properly. It does seem confined to a restricted number of channels and particularily CH4!

I'll try a series of recordings on CH4 to see if it's repeatable.

[AlanC]

An example from me. I've got a Hauppauge 500 and a Cinergy 2400.
At 22.35 the recording status showed a Coronation Street, a Deep Space Nine and a Battle for Haditha all in progress.
Coronation Street file was the correct 34 minute length.
Deep Space Nine was 2 hours and 36 minutes (ran on into Terminator and Blade)
Battle for Haditha was only 2 minutes long.
The last entry in the '-native' was at 21:03, nothing else was added even after a 'restart recording service'.

[sub]

2008-03-17 20:59:00.203 VERBOSE [5] Requesting IRecordingSource to start recording: C:\Documents and Settings\Alan\My Documents\My Videos\Recorded TV\Battle for Haditha\Battle for Haditha_20080317_21002250.mpg
2008-03-17 20:59:00.203 VERBOSE [5] BDARecordingSource about to start recording oid:3 channel:T:C45,665834,0,0,8~NID:12290~ONID:9018~TSID:8194~P:8384~V:560~A:561~L:eng~PMT:300~LCN:4~PCR:2307~N:>Channel 4
2008-03-17 20:59:04.484 VERBOSE [5] Programme is now recording
2008-03-17 20:59:04.484 VERBOSE [5] RecordingFactory.save()
2008-03-17 20:59:04.593 VERBOSE [5] Save(): Updated existing scheduled recording
2008-03-17 20:59:04.593 VERBOSE [5] Adding C:\Documents and Settings\Alan\My Documents\My Videos\Recorded TV\Battle for Haditha\Battle for Haditha_20080317_21002250.mpg to parallel processing queue
2008-03-17 20:59:04.796 VERBOSE [5] Checking signal status on TerraTec Cinergy 2400i DT #1 DVB-T:1
2008-03-17 20:59:08.265 VERBOSE [5] Checking signal status on Hauppauge Nova-T-500 DVB-T (1):1
2008-03-17 21:01:04.671 VERBOSE [5] Checking signal status on Hauppauge Nova-T-500 DVB-T (2):1
2008-03-17 21:01:04.937 VERBOSE [5] Checking signal status on TerraTec Cinergy 2400i DT #1 DVB-T:1
2008-03-17 21:01:08.406 VERBOSE [5] Checking signal status on Hauppauge Nova-T-500 DVB-T (1):1
2008-03-17 21:03:00.000 VERBOSE [5] Recording has passed endtime+padding. Stopping.
2008-03-17 21:03:00.000 VERBOSE [5] Stopping recording oid:2
2008-03-17 21:20:25.468 VERBOSE [14] RecordingFactory.LoadNext24HourEvents()
2008-03-17 21:20:25.468 VERBOSE [14] forcing refresh of next 24 hour events for capture source:4
2008-03-17 21:20:25.468 VERBOSE [14] Starting LiveTV for captureSource: 4 channel oid: 32 filename:
2008-03-17 21:20:26.796 VERBOSE [14] RenewLease 4
2008-03-17 21:20:26.796 VERBOSE [14] forcing refresh of next 2 hour events for all capture sources
2008-03-17 21:20:26.796 VERBOSE [14] Checking for other recordings using device: DEVICE:TerraTec Cinergy 2400i DT #2 DVB-T:1
2008-03-17 21:20:26.796 VERBOSE [14] RenewLease finished (accepted - preview mode)

This error seems to have occurred when someone started live tv at 21:20, which caused the recording to stop. The app should have denied the request to start live tv instead, so definitely something funky happening with live tv. Unfortunately I'm a bit to busy with the day job today to look into it in any more detail just now.

[Bobins]

Have now done a series of recordings on CH4. I find they regularily truncate at a seemingly random time into the recording. The resulting file is playable but the time sync is always out (e.g. skip forward 60 secs and it'll jump 5 minutes) plus the OSD says the recording is say 5 hours long (which it is not)

This only seems to be happenning on CH4 and the logs show no errors. Indeed the logs think the recording continued and finished ok at the programmed time.

The signal strength is always 60+ and the quality 100% (which is the same for other channels).

This does seem restricted to CH4.

With nothing showing up in the current logs, is there any other way to work out where this is going wrong?

[gEd]

This original post was all about a recording terminating at the precise time that another recording started on the second tuner.

The problem that you are describing sounds like a weak signal that results in the recording aborting and/or having screwed up timestamps. If it only appears to happens on C4 then perhaps your C4 signal is weak.

[off topic but it's a small world] My mum grew up in a cottage on the chase when she was young (1930's) and many men from her family worked down the pit in Hednesford. My nan worked in the pit canteen.

[Bobins]

Yes I've been looking at the signal strength but it's a few points stronger than some of the other muxes and logs at 100% quality. The strength is in a range considered "good" for the Nova-T 500. There's no sign of image/sound breakup in the part of the recording that does get saved.

What puzzles me is that GBPVR thinks everything is fine and carries on logging right until the normal time the recording should end. It shows a normal completion of the recording in the log even though it terminated some time earlier. On some occasions the recording service hangs and you get a file that's hours long (with no sound/video after the point of the hang). In this state, other later programmed recordings don't happen until the service is re-started.

I've seen another post reporting this too.

Just to confuse matters, I had an ITV1 recording terminate prematurely last night at exactly the same time as a BBC2 recording stopped normally. As I said earlier in the thread, I think these are two different problems.

(off topic) That probably means your mother/relatives were only a few hundred yards from where I live. My house is built just down the road from where the old Hednesford mines used to be.

[sub]

If a recording stops somewhere between the GB-PVR log messages indicating the recording is being started, and the recording is being stopped, then its either because the device stopped delivering data or the mux locked up for some reason.

[macgyver]

Hi All,

There seem to be a few threads about this issue with Nova-T 500s truncating recordings but can't see a fix. I've just built a machine with one and am experiencing the same truncated recordings with no errors, simply small file sizes with correct timestamps. Again it seems to be linked to the second tuner being given a command to start recording.
I'm running 1.4.7 and the only suggested solution I can find is to buy a different tuner card. Can anyone come up with any other options?
Having said that, I'm happy to buy a new card (got the 500 cheap on ebay and can still use it as single tuner) but what dual tuner card do people recommend?
Thanks in advance for any info.