Recording NOT stopping at finishing time (logs attached)

[mixedup]

Hi,

Here's an interesting one. Just got most of the GB-PVR functions running now on my new dual core AMD PC, however when I schedule a recording the GB-PVR recording service keeps thinking it is recording even after the timeslot has finished. So in point form:

- Schedule a recording
- Come back after recording normally should have finished to check
- GB-PVR recording status indicator indicates recording is still occuring
- Look at the recording file and note that the recording size seems to indicate the actual recording did stop on time (i.e. the file is not huge as one would expect if the recording truely hadn't stopped)
- The pending recordings that should have been recorded did NOT get recorded, no doubt because the recording service still thought it was recording
- Manually tried to stop recording but no response
- Had to force a Recording Service Restart to recover

Logs:
3/08/2006 10:59:00 AM.140 INFO [6] Found new programme requiring recording: National Nine Morning News
3/08/2006 10:59:00 AM.187 VERBOSE [6] Changing to channel (GBPVR.Backend.Common.NullTunerController): 1
3/08/2006 10:59:00 AM.187 VERBOSE [6] Requesting IRecordingSource to start recording: E:\GB-PVR\recordings\National Nine Morning News\National Nine Morning News_20060803_11001130.mpg
3/08/2006 10:59:00 AM.234 VERBOSE [6] BDARecordingSource about to start recording oid:1 channel:T:C8,191500,0,0,7~P:1025~V:513~A:660~L:eng ~PMT:257~LCN:9~TXT:577~N:>Nine Digital
3/08/2006 10:59:01 AM.000 VERBOSE [6] Programme is now recording
3/08/2006 10:59:01 AM.000 VERBOSE [6] RecordingFactory.save()
3/08/2006 10:59:01 AM.000 VERBOSE [6] Save(): Updated existing scheduled recording
3/08/2006 10:59:01 AM.031 VERBOSE [6] Adding E:\GB-PVR\recordings\National Nine Morning News\National Nine Morning News_20060803_11001130.mpg to parallel processing queue
3/08/2006 11:32:00 AM.171 VERBOSE [6] Recording has passed endtime+padding. Stopping.
3/08/2006 11:32:00 AM.171 VERBOSE [6] Stopping recording oid:1
3/08/2006 6:33:27 PM.312 INFO [4] GB-PVR Recording Service stopping
3/08/2006 6:33:28 PM.312 INFO [4] GB-PVR Recording Service shutdown complete
3/08/2006 6:33:28 PM.343 INFO [2] Finalize called


Any ideas?

Thanks


PS. Some sundry errors which I see which I'm pretty sure have nothing to do with the above

3/08/2006 6:32:44 PM.656 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="MenuType"]
3/08/2006 6:32:44 PM.718 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="CloseButton"]
3/08/2006 6:32:47 PM.187 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="ForegroundTransparency"]
3/08/2006 6:36:38 PM.187 ERROR [1] Unable to find named image pos: /settings/CompositeImages/CompositeImage[@name="ItemListBackground"]/Element[@name="NoItemsFound"]
3/08/2006 6:36:38 PM.187 ERROR [1] Unable to find named image size: /settings/CompositeImages/CompositeImage[@name="ItemListBackground"]/Element[@name="NoItemsFound"]

[sub]

Zip and attach a complete set of logs and I'll take a look.

PS. Some sundry errors which I see which I'm pretty sure have nothing to do with the above

3/08/2006 6:32:44 PM.656 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="MenuType"]
3/08/2006 6:32:44 PM.718 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="CloseButton"]
3/08/2006 6:32:47 PM.187 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="ForegroundTransparency"]
3/08/2006 6:36:38 PM.187 ERROR [1] Unable to find named image pos: /settings/CompositeImages/CompositeImage[@name="ItemListBackground"]/Element[@name="NoItemsFound"]
3/08/2006 6:36:38 PM.187 ERROR [1] Unable to find named image size: /settings/CompositeImages/CompositeImage[@name="ItemListBackground"]/Element[@name="NoItemsFound"]

Those can be ignored. They just indicate an option setting was not found.

[mixedup]

thanks Sub - much appreciated - logs attached - Let me know if you need more info

Thanks

[sub]

Unfortunately those logs dont seem to cover the period of that error you posted above.

[mixedup]

woops - here is the earlier set of logs Sub

tks in advance

[mixedup]

Sub - here is another sample of logs. I just did a manual recording from 7.00pm to 7.10pm. When I checked at around 7.20pm it was still indicating it was recording. Interestingly when I played back the record file (e.g. click on the pending recording and push play) the remaining time was showing at just over 5 minutes (not sure why this wasn't up around 9 minutes+ and whether this indicated that not the entire 10 minutes itself was recorded then)

Logs attached.

[sub]

According to those logs, its started the recording a 7.00PM and stopped it at 7.10PM. If it stopped in between, then it sounds like the device or the mux had stopped producing data. This may be an indication of marginal DVB signal strength.

It may be worth trying the DVR-MS mux. This has proven to be a little more tolerant of interuptions to the DVB stream.

[mixedup]

thanks Sub - I'll try this plus perhaps some different muxes then - couple of quick questions:

- any recommendation re a good way to independantly check signal strength? (e.g. perhaps an independant piece of software?)

- are there any issues with having multiple muxes registered (once I fix the problem)? I thought I read channel switching times could be affected by having too many muxes or decoders or something installed

Tks again

[mixedup]

PS. Also Sub can I ask the following. The setup I'm using on the new PC is the same as on my previous system (i.e. indoor antenna + tuner card), so I've just migrated this into the new PC (dual core). Given this it would be reasonable to assume there should be no real problems with signal strength.

If the issue wasn't signal strength what would you recommend? Reinstalling GB-PVR again perhaps? Is there additional trace I could enable? If the recording service thinks it has correctly ended the recording does this imply the issue is some in the BDA driver layer? (i.e. is it this layer that then has the responsibility to actually stop the recording? - I'm not sure how the recording service asks for the recording to stop + ensures that the GB-PVR client itself picks up on this I guess)


Tks

[sub]

PS. Also Sub can I ask the following. The setup I'm using on the new PC is the same as on my previous system (i.e. indoor antenna + tuner card), so I've just migrated this into the new PC (dual core). Given this it would be reasonable to assume there should be no real problems with signal strength.

The symptoms sounds like those experienced by users with signal problems, so I'd wouldnt rule it out.

If the issue wasn't signal strength what would you recommend?

I'm not really sure.

Make sure you're running the latest drivers for your capture device.

Maybe update the motherboard chipset drivers. You might be having PCI problems. This has caused problems for users in the past, particularly when the device was sharing an IRQ with another device.

Might be worth checking the capture device with exactly the same driver version as your old machine. Most user also upgrade to the latest and greatest driver during this type of machine move. The new drivers may not work as well as the ones?

Reinstalling GB-PVR again perhaps?

No, I doubt that would help. GB-PVR basically tells the device and mux to start recording, then steps out of the way until its time to stop the recording. If the recording is stopping in between these two points, then its either the device has stopped producing data or the mux has stopped producing data.