LKO wrote:Ok, so evidently at some time Zap2it suddenly added the "I" and "labs.zap2it" stuff to the 4DTV data, which broke mythTV (because a couple years ago everything worked). Should SD modify the data, or mythfilldatabase get modified to handle the problem, or -- since there are so few 4DTV folk left -- should I just be happy with the workaround?
Nope.. I'm the guilty party when I wrote tv_grab_na_dd for Zap2IT labs. (4+ years ago)
The XMLTV spec strongly encourages a RFC2838 style channel-id. I wanted to base it on the TMS channel-id, so added a "I" (not sure why that letter, but it couldn't start with a number) and the "labs.zap2it.com" domain. The old Zap2IT.com scraper used a channel-id based on the callsign and channel number, which --old-chan-id provides for compatability.
When the conversion to SchedulesDirect was done, there was no reason to change the channel id (and it would cause grief), so the labs.zap2it.com part was left in.
I don't think anyone suddenly changed the channel-id... tv_grab_na_dd has always done that. Maybe you used to use a native MythTV grabber (which didn't mangle the TMS-id), but now you're using XMLTV to avoid upgrading?
If we (SD) does self-host the data, I don't see us changing the channel-id.
Robert