Mangled SD Channel Maps

[bisongde]

Any tips for making SchedulesDirect lineups not be so garbled (this very well may be a problem with Sage and not this plugin or SD)? We've been using this solution back as far as the Slugger plugin and we've always gotten malformed channel listings when using SD + channel scan. Mostly a ton of "Unknown" channels in the SD/local range. It starts to clear up as you get into basic cable and HD/premiums. This is on Fios in the NYC metro area.

The HDHomeRuns will provide .xml and json listings as well from the head-end, and the HDHomeRun app seems to be pretty accurate in terms of what channels are actually there and what they're supposed to be called. That may be because HDHomeRun uses Gracenote EPG though.

Is the inability to manually define .xml or json sources for EPG down to a certain formatting Sage expects to be able to parse guide data?

Would love to know if there's a workflow available to get correctly named channels with the right mappings in terms of frequencies without having to manually prune/rename the search results.

[Fuzzy]

Would need better information on what your problems are. Sage's scan simply compares what it gets from the broadcast itself (the ID encoded in the transport stream) and compares it to the list of channels in the lineup, and matches them up. Usually, things like locals are the most reliable, because they have very defined ID's (the callsign).

[bisongde]

Originally Posted by Fuzzy

Would need better information on what your problems are. Sage's scan simply compares what it gets from the broadcast itself (the ID encoded in the transport stream) and compares it to the list of channels in the lineup, and matches them up. Usually, things like locals are the most reliable, because they have very defined ID's (the callsign).

I'll post back with an example channel scan. We see the same thing between Cetons and HDHRs.