HVR-2250 QAM Records wrong channel sometimes

[Jetlag]

GB-PVR v. 1.4.7, Vista Ultimate with TV Pack, UAC turned off, HVR-2250 driver version 7.6.27.27223

I have set up both digital tuners as QAM on my HVR-2250. Sometimes it records the wrong channel and sometimes I get a blank file, and other times it records the right channel. If I stop the recording and start it again I will generally get the right channel then. When I get a wrong channel it will be one of the other channels in the TS. And I seem to get the same wrong channel every time.

I made sure my channels were set up correctly. And I confirmed it happens on both tuners. It also happened with multi-record on or off.

I will try to upload the logs later when I get home.

ETA: I've attached the logs from recording two small videos. The first time I got the wrong channel, "T:415250,0,0~P:12~TSID:9450~V:2624~A:2625~PMT:58~PCR:2624~N:>415250.12 Unknown9* (000)" to be specific. The second recording captured the correct channel.

[dennit]

I have set up both digital tuners as QAM on my HVR-2250. Sometimes it records the wrong channel and sometimes I get a blank file, and other times it records the right channel. If I stop the recording and start it again I will generally get the right channel then. When I get a wrong channel it will be one of the other channels in the TS. And I seem to get the same wrong channel every time.

I can't be sure, but this sounds to me like the mapping is wrong for one tuner on one or more channels. If you have one tuner correctly mapped and one incorrectly mapped, you'll get the right channel recorded sometimes, but when the correctly mapped tuner is in use, you'll get the incorrectly mapped tuner recording at the wrong frequency. I'd look at the live preview in config for both tuners on a channel that has shown this problem.

[johnsonx42]

fwiw, in absence of logs saying otherwise, I second dennit's diagnosis. there's really no other mechanism that could cause this behavior.

[Jetlag]

I've attached logs to the first post.

[dennit]

I've attached logs to the first post.

You're getting errors in the RecordingService log:

Code:

2009-10-17 01:44:27.901 VERBOSE [5] processing request to reload schedule 2009-10-17 01:44:28.401 VERBOSE [5] RecordingFactory.loadSchedule() 2009-10-17 01:44:28.401 VERBOSE [5] getValue cached value: /settings/AutoRemoveMissingRecordings : false 2009-10-17 01:44:28.401 VERBOSE [5] getValue cached value: /settings/CheckForRenamedRecordings : true 2009-10-17 01:44:28.636 VERBOSE [5] checking recordings 2009-10-17 01:44:28.636 VERBOSE [5] - checking [...] 2009-10-17 01:44:29.137 ERROR [5] Unexpected error checking tuning on back-to-back multirecords 2009-10-17 01:44:29.151 VERBOSE [5] Changing to channel (GBPVR.Backend.Common.NullTunerController): 75 2009-10-17 01:44:29.162 VERBOSE [5] Requesting IRecordingSource to start recording: C:\Users\Public\Videos\GBPVR\Manual Recordings\manual_113_20091017014400.mpg 2009-10-17 01:44:29.162 VERBOSE [5] start recording @1 2009-10-17 01:44:29.163 VERBOSE [5] start recording @2 2009-10-17 01:44:29.173 VERBOSE [5] BDARecordingSource about to start recording oid:2 channel:T:415250,0,0~P:1~TSID:9450~V:1984~A:1985~PMT:48~PCR:1984~N:>415250.1 Unknown6* (000(AC3)) file:C:\Users\Public\Videos\GBPVR\Manual Recordings\manual_113_20091017014400.mpg 2009-10-17 01:44:30.553 VERBOSE [5] getValue() loading new key/value into cache: /settings/BDASubmitTuningRequestTwiceOnRecord 2009-10-17 01:44:30.553 VERBOSE [5] getValue: /settings/BDASubmitTuningRequestTwiceOnRecord : true

Code:

2009-10-17 01:46:48.476 VERBOSE [5] processing request to reload schedule 2009-10-17 01:46:48.976 VERBOSE [5] RecordingFactory.loadSchedule() 2009-10-17 01:46:48.976 VERBOSE [5] getValue cached value: /settings/AutoRemoveMissingRecordings : false 2009-10-17 01:46:48.976 VERBOSE [5] getValue cached value: /settings/CheckForRenamedRecordings : true 2009-10-17 01:46:49.173 VERBOSE [5] checking recordings 2009-10-17 01:46:49.173 VERBOSE [5] - checking [...] 2009-10-17 01:46:49.672 VERBOSE [5] Found new Pending recording needed wakeup request: (10/17/2009 1:47:00 AM) 2009-10-17 01:46:49.673 ERROR [5] Unexpected error checking tuning on back-to-back multirecords 2009-10-17 01:46:49.677 VERBOSE [5] Changing to channel (GBPVR.Backend.Common.NullTunerController): 75 2009-10-17 01:46:49.679 VERBOSE [5] Requesting IRecordingSource to start recording: C:\Users\Public\Videos\GBPVR\Manual Recordings\manual_113_20091017014700.mpg 2009-10-17 01:46:49.679 VERBOSE [5] start recording @1 2009-10-17 01:46:49.680 VERBOSE [5] start recording @2

They're showing up moments later in the RecordingService-native log:

Code:

2009-10-17 01:44:29.976 INFO Tuning by frequency (415250) 2009-10-17 01:44:29.976 VERBOSE Setting BDA_MOD_256QAM 2009-10-17 01:44:29.976 VERBOSE atsc@8 2009-10-17 01:44:29.976 VERBOSE atsc@9 2009-10-17 01:44:29.981 VERBOSE KSPROPSETID_BdaDigitalDemodulator is NOT supported!!! 2009-10-17 01:44:29.982 ERROR PropSet->Set() failed... hr=80070492 2009-10-17 01:44:29.982 VERBOSE About to put ATSC/QAM tuning request

It refers to back-to-back, multirecord, manual recording and tuning by frequency (415250). I can't figure it out - maybe sub or someone else can. Can you be more explicit on what channel/program you were trying to record, when, whether you have any back-to-back or manual recordings set up, etc.

[Jetlag]

These were just two small one minute manual recordings I made in a row to prove that I was getting a different channel with the same tuner and tuning. Here's the portions of the pending.log when I made the recordings.

Code:

---------SERVICE STARTUP--------- ---------10/17/2009 1:43:23 AM source: 2 name: PVR 2250 QAM 1 type: digital:Hauppauge HVR-2250 (QAM):1 source: 3 name: PVR 2250 QAM 2 type: digital:Hauppauge HVR-2250 (QAM):2 source: 1 name: PVR2 USB2 type: analog ----10/17/2009 1:44:28 AM 1355 10/17/2009 1:44:00 AM - 10/17/2009 1:45:00 AM capture-source:2 tuning:T:415250,0,0~P:1~TSID:9450~V:1984~A:1985~PMT:48~PCR:1984~N:>415250.1 Unknown6* (000(AC3)) ----10/17/2009 1:46:49 AM 1356 10/17/2009 1:47:00 AM - 10/17/2009 1:48:00 AM capture-source:2 tuning:T:415250,0,0~P:1~TSID:9450~V:1984~A:1985~PMT:48~PCR:1984~N:>415250.1 Unknown6* (000(AC3))

The channel I was trying to record was 75 (tuning above). But the first recording produced a capture of channel 64 ("T:415250,0,0~P:12~TSID:9450~V:2624~A:2625~PMT:58~ PCR:2624~N:>415250.12 Unknown9* (000)"), and the second recording produced a capture of channel 75.

I ended up tuning by frequency after playing with the qam.ini manager when I was trying to find a solution to this problem.