Symptons:
Channel selection from TV guide works fine with the channel changer (usbuirt) run correctly; pvrx2.exe.log @ 2008-03-28 19:15:21.750 & 2008-03-28 19:15:54.031
However, when recording from the tv guide, or a scheduled recording, although the channel changer is called according to the logs, the usbuirt does not 'flicker' and the 'current' (i.e. more than likely wrong) channel is recorded; GBPVRRecordingService.exe-native.log @ 2008-03-28 19:10:44.343
Could it be that some compute-intensive record start operation is running concurrently with the channel changer call?
There seems to be 'less' happening, err 'less' happening which is logged, immediately after the channel change call in pvrx2.exe.log as opposed to the recording channel change in GBPVRRecordingService.exe-native.log.
Note that I am using a custom channel changer but the usbuirt still fails to flicker using the standard hipsend and 400 mS between characters ( {channel} 400 4 )
There are several verbose errors ( :-) ) in the GBPVRRecordingService.exe-native.log around the time of the recording but these seem to have been discounted in previous posts http://forums.nextpvr.com/showthread.php?t=34231
The other card, a Nova T-500, works fine in all respects but obv this does not require the channel changer.
First upgrade to 1.2.9 was over 1.1.5 . Second attempt was an uninstall and a fresh install to an empty gbvr directory; same difference.
All the above work(s|ed) fine in 1.1.5
Tips, howls of derisive laughter, requests for further info welcome. I can always revert to 1.1.5 but would miss the 1.2.9 shiny goodness.
Oh, great product btw, but I guess we already know that ;-)
David
Channel selection from TV guide works fine with the channel changer (usbuirt) run correctly; pvrx2.exe.log @ 2008-03-28 19:15:21.750 & 2008-03-28 19:15:54.031
However, when recording from the tv guide, or a scheduled recording, although the channel changer is called according to the logs, the usbuirt does not 'flicker' and the 'current' (i.e. more than likely wrong) channel is recorded; GBPVRRecordingService.exe-native.log @ 2008-03-28 19:10:44.343
Could it be that some compute-intensive record start operation is running concurrently with the channel changer call?
There seems to be 'less' happening, err 'less' happening which is logged, immediately after the channel change call in pvrx2.exe.log as opposed to the recording channel change in GBPVRRecordingService.exe-native.log.
Note that I am using a custom channel changer but the usbuirt still fails to flicker using the standard hipsend and 400 mS between characters ( {channel} 400 4 )
There are several verbose errors ( :-) ) in the GBPVRRecordingService.exe-native.log around the time of the recording but these seem to have been discounted in previous posts http://forums.nextpvr.com/showthread.php?t=34231
The other card, a Nova T-500, works fine in all respects but obv this does not require the channel changer.
First upgrade to 1.2.9 was over 1.1.5 . Second attempt was an uninstall and a fresh install to an empty gbvr directory; same difference.
All the above work(s|ed) fine in 1.1.5
Tips, howls of derisive laughter, requests for further info welcome. I can always revert to 1.1.5 but would miss the 1.2.9 shiny goodness.
Oh, great product btw, but I guess we already know that ;-)
David
1.2.13, XP SP3, C2Duo E6550,2GB, 2600XT, 500GB + 750GB raid 1, 2 * MVP (wired)
Nova-T 500 ; PVR150 << Manhattan st550 << 90cm motorised dish
USB-UIRT + HIP + custom 'HipSend' to change channels and coordinate dish
Nova-T 500 ; PVR150 << Manhattan st550 << 90cm motorised dish
USB-UIRT + HIP + custom 'HipSend' to change channels and coordinate dish