2008-12-11, 10:21 PM
whurlston Wrote:Correct.
Yes. I could make registry changes to override the frequencies so that you can always use the default qam.ini but I figured this was better.
GBPVR just sends the tune request from the mapping in the qam.ini. It's the tuner's bda driver that translates that as a channel number or frequency and do the lookup if its a channel number. The drivers will either always apply the offset when tuning or not at all. So when Windows reports that channel 71 is 507000 to the bda driver, the tuner may actually try to tune 508750 (507000 + 1750) and then doesn't lock onto the signal properly.
My program just tells GBPVR wether to use channel numbers or frequencies for tuning requests. I just got tired of manually changing the qam.ini because I needed one setting for my Vistaview tuner and one for my HDHomeRuns. The default qam.ini worked fine for my Vistaview but the HDHomeRun kept applying the offset so I wrote this so I could easily switch out my qam.ini files as needed.
OK. And if I don't need the offsets, I might only use this to limit the channels/Frequencies in the scan...
I think I got it. Let me play with it, and I'll write something up, in conjuction with a general QAM page, a 1600 walkthough, and tweaking...
Frank Z
[COLOR="Gray"]
I used to ask 'why?' Now I just reinstall...
[SIZE="1"]______________________________________________
Author: ZTools: ZProcess, MVPServerChecker; UltraXMLTV Enhancer, Renamer, Manager; [/SIZE]
[/COLOR]
[COLOR="Gray"]
I used to ask 'why?' Now I just reinstall...
[SIZE="1"]______________________________________________
Author: ZTools: ZProcess, MVPServerChecker; UltraXMLTV Enhancer, Renamer, Manager; [/SIZE]
[/COLOR]