Qam.ini Manager

zehd · 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...

whurlston · 2008-12-11, 10:25 PM

zehd Wrote:OK. And if I don't need the offsets, I might only use this to limit the channels/Frequencies in the scan...

Yup. That's it. You can actually post the zip directly on the wiki if you like. There won't be very many changes to it and it will be easier to find that way. I can give you the source to put there too but it's really just a simple list of frequencies and a text writer.

zehd · 2008-12-11, 11:15 PM

whurlston Wrote:Yup. That's it. You can actually post the zip directly on the wiki if you like. There won't be very many changes to it and it will be easier to find that way. I can give you the source to put there too but it's really just a simple list of frequencies and a text writer.

Nothing's that simple, now is it? (Don't let anyone know...)

whurlston · 2008-12-11, 11:33 PM

zehd Wrote:Nothing's that simple, now is it? (Don't let anyone know...)

This one actually is. Big Grin

There is some added code to check the registry for the GBPVR install folder but even that is trivial. I could have made it more involved like parsing the current qam.ini to get the current settings etc but I used the K.I.S.S. method on this one.

zehd · 2008-12-12, 06:31 AM

According to my TV, I have a few channels that are lower than 70...

56.9
56.11
57.13
64.14

I like how you prog makes for a smaller list to scan. Am I right in thinking that the program checks 70-138 (when chosen) and therfore would miss those channels?

whurlston · 2008-12-12, 06:36 AM

Not necessarily. Are those the real physical channels or just the virtual channels reported in the PSIP data? It would only miss them if they were the actual physical channel.

zehd · 2008-12-12, 06:42 AM

whurlston Wrote:Not necessarily. Are those the real physical channels or just the virtual channels reported in the PSIP data? It would only miss them if they were the actual physical channel.

All I know is I get a few digital channels on the TV with those channel numbers. I believe they are the physical channels...

It's considered CADTV with my LG TV

zehd · 2008-12-12, 06:25 PM

Bad news for testing. My provider killed all of my clear QAM (except for a HD Yule Log)

whurlston · 2008-12-12, 06:27 PM

Ouch. That sux.

pcostanza · 2008-12-12, 06:30 PM

zehd Wrote:Bad news for testing. My provider killed all of my clear QAM (except for a HD Yule Log)

I fear the same for me in the near future. What happens to the Yule log after Christmas? Live Bingo? Smile