mythedoff, I really appreciate your supplying the code for both the zap2it and silicon dust scenarios. After looking at this some more I'm realizing I've already been down this path, so I thought I'd share my experience:

1. Silicon Dust. Many (most?) zip codes have multiple line ups associated with them. This is because the cable company typically has more than 1 "head end" covering any given zip code and the head ends don't all assign the same channels to the same frequency. To use the silicon dust data successfully, you need to figure out which of the line ups listed on the Silicon Dust page corresponds to your neighborhood. It's also not a 1-time process -- the line ups list change on a regular basis as SD is continuously harvesting data from users of their HDHOMERUN tuners. In addition, SD does not provide XMLTV ID's.

2. Zap2it -- I may be mistaken but I don't think they have useful frequency data. They do have useful XMLTV ID data.

So to make it all work one would need to do this:

1. Select the correct lineup from SD to get the frequency data.

2. Get the XMLTVID's from Zap2it and merge that with the SD data. Not to hard -- just line it up using the virtual channel number.

Once this is done the following (untested) SQL should do the trick:

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.

OK -- I dusted off an old script I wrote sometime back that attempted to automate the clear QAM channel mapping process and made some enhancements to it. I probably spent more time on the script than it would have taken to do everything manually, but what the heck -- scripting is fun!

In some situations it is able to map channels without any human input; in other situations it requires you to to choose which of 2 or 3 different channels might be the right answer; and there are still some situations that require you to figure out the correct channel number on your own, although on my last pass all of these turned out to be frequencies that didn't work anyway. In any event, it does make the job easier.

The script uses the data generated by scte65scanand the Silicon Dust clear QAM tuning data. It looks like scte65scan only supports comcast; the Silicon Dust tables provide data for areas where HDHOMERUN tuners are deployed. If either data source is available in your situation it will help; if both data sources are available, it will help even more.

It would take some work to make this script work outside my environment. If there is interest in using it, I will take the time to make those changes. Let me know...

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.

I don't need this now but am mulling a switch to comcast at some point in my future. I would certainly love your script if and when I make that switch. If I wait six months to ask for it it will all be gone from your head I'm sure

Surely other folks would like this??

_________________
Paul O'Flynn