@#$%^&*()!!! I spoke too soon. Tuner 0 (antenna) works. Tuner 1 (cable) gives me the same "unable to start the BDA device" message. Back to the drawing board.
Got it. I can confirm that the correct line for a cable tuner with the expanded tuning modification is "TUNING_SPECIAL=1". It works again. Have a great weekend Sub and Whurlston.
Sub, I ran a test. Tuning_special=1 does attempt to use the OnAir filters but it works anyway. Tuning_Special=2 crashes when attempting the tune request. Logs show that it cannot find the "IATSCTuningSpace". I've attached the logs for you:
-1.log is with tuning_space=1
I know you're busy and it's not an issue since =1 works for us. I just know that if you're like me, you might just have a need to know why things are the way they are.
Also as a note to HDHR users, the registry edits are no longer needed. The HDHR setup now has a GBPVR option. I'll update the linked thread accordingly.
Yup. That's what I say. Quick question for you though. Does GBPVR wait for the channel changer command to exit before submitting the tune request? I was thinking about writing a small app that will perform the pid filtering to cut down the network traffic. I could call it from the channel changer but it would have to be delayed until after the tune request was sent. If GBPVR is waiting for the channel change command, I would just be creating a catch 22 situation.