Originally Posted by Dave Brown
Did you determine if there is a work-around for this problem? I finally got around to fixing the Zap2it lineup information, but as you said recording doesn't work because of the apparent sub-channel issues with the guide information.
Sorry for the delay - I did figure out a fix over the weekend, but it required changes to the Zap2itDataDirect executable. I'm going to go out on a bit of a limb and assume that I can distribute that on my own as it doesn't contain any code that uses any of the proprietary accessDTV drivers or reference code, etc. that would be a concern under the distribution NDA agreements. A new version of Zap2itDataDirect.exe along with a sample ini file that contains the channel mappings for the Boston area can be found here
. Just overwrite your current copy of Zap2itDataDirect.exe and edit your channel mappings to suit your local channel listings and you should be back in business. If I had tested the channel mapping code before releasing it, this code change would have been done a while ago, but until now there was no need to use the feature with Zap2it.
In case it's not entirely clear what's going on, here are the mappings for the Boston area, followed by an explanation:
- 19|WGBHDT - This is the channel number and call sign that comes down from Zap2it for a given channel. Note that the channel number is currently the RF channel number, not the PSIP or familiar channel number that we're all used to. The relevant Zap2it XML looks like this:
This field is simply used as a lookup to match the Zap2it data to the mapping entry in the ini file.
- 19,2,1 - This is in the form RF Channel #, PSIP Channel #, subchannel # and is used so that you get the right data showing up in the right place in the guide.
I can't fathom why Zap2it changed the format of the channel data and haven't seen any explanation of it on their forums. Sure, the service is free, but it would be nice if they would let people know when they're going to make a change of this nature.