Jump to content
BrianG

ANSWERED Help With Guide Mapping

Recommended Posts

BrianG

Provider: MediaCom

ZIP code: 50317

 

I'm having a little trouble mapping the channel line-up from my HDHomeRun unit in Emby. I selected the Emby Guide Data as the provider and it kinda works; a few channels seem to be ok, but most aren't. I think it's something to do with how my provider (mediacom) does things.

 

When setting up the lineup, among a whole bunch of choices I see two MediaCom options. I have tried both MediaCom selection options and they seem to be no different.

 

post-1359-0-34858400-1567466361_thumb.png

 

After doing that, I refreshed the guide and saw there were a bunch of channels not showing any guide info.

 

post-1359-0-95298400-1567466653_thumb.png

 

So, I went to map the channels hoping to fix this, but I get a list that doesn't really match up.

 

post-1359-0-95012400-1567466368_thumb.png

 

Here is my provider's guide info from their own website:

 

post-1359-0-68615000-1567466375_thumb.png

 

post-1359-0-69746100-1567466380_thumb.png

 

Any help would be appreciated. As of right now, I have to open MediaCom's own channel guide while selecting channels in Emby to know what to expect.

 

I do remember a couple years ago having similar mapping issues with Schedules Direct, and they were able to fix it fairly quickly. I stopped using them a few months ago (even though the sub is fairly cheap, it's an expense I didn't want at the time).

Edited by BrianG

Share this post


Link to post
Share on other sites
BrianG

A little extra info:

 

I dug up some emails from 2015 between me and someone at SchedulesDirect when I was experiencing a channel mapping issue (similar to what I'm seeing now), and mention was made of the fact that MediaCom uses QAM. Not sure if that helps?

 

Also, here is my lineup.json from the HDHomeRun device in case that helps too.

[

   {  
      "GuideNumber":"5.1",
      "GuideName":"WOI-HD",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v5.1"
   },
   {  
      "GuideNumber":"5.2",
      "GuideName":"Laff",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v5.2"
   },
   {  
      "GuideNumber":"5.3",
      "GuideName":"Grit",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v5.3"
   },
   {  
      "GuideNumber":"5.4",
      "GuideName":"Cozi",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v5.4"
   },
   {  
      "GuideNumber":"7.2",
      "GuideName":"UNKNOWN",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v7.2"
   },
   {  
      "GuideNumber":"8.1",
      "GuideName":"KCCI-HD",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v8.1"
   },
   {  
      "GuideNumber":"8.2",
      "GuideName":"KCCI-SD",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v8.2"
   },
   {  
      "GuideNumber":"8.3",
      "GuideName":"KCCI-MY",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v8.3"
   },
   {  
      "GuideNumber":"11.1",
      "GuideName":"IPTV1",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v11.1"
   },
   {  
      "GuideNumber":"11.2",
      "GuideName":"IPTV2",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v11.2"
   },
   {  
      "GuideNumber":"11.3",
      "GuideName":"IPTV3",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v11.3"
   },
   {  
      "GuideNumber":"11.4",
      "GuideName":"IPTV4",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v11.4"
   },
   {  
      "GuideNumber":"12.1",
      "GuideName":"UNKNOWN",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v12.1"
   },
   {  
      "GuideNumber":"12.2",
      "GuideName":"UNKNOWN",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v12.2"
   },
   {  
      "GuideNumber":"13.1",
      "GuideName":"WHO-HD",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v13.1"
   },
   {  
      "GuideNumber":"13.2",
      "GuideName":"WHO-DT",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v13.2"
   },
   {  
      "GuideNumber":"13.3",
      "GuideName":"WHO-DT",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v13.3"
   },
   {  
      "GuideNumber":"13.4",
      "GuideName":"WHO-DT4",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v13.4"
   },
   {  
      "GuideNumber":"17.1",
      "GuideName":"FOX",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v17.1"
   },
   {  
      "GuideNumber":"17.2",
      "GuideName":"Comet",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v17.2"
   },
   {  
      "GuideNumber":"17.3",
      "GuideName":"Charge!",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v17.3"
   },
   {  
      "GuideNumber":"17.4",
      "GuideName":"TBD",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v17.4"
   },
   {  
      "GuideNumber":"23.1",
      "GuideName":"KCWI-HD",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v23.1"
   },
   {  
      "GuideNumber":"23.2",
      "GuideName":"Escape",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v23.2"
   },
   {  
      "GuideNumber":"23.3",
      "GuideName":"Bounce",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v23.3"
   },
   {  
      "GuideNumber":"23.4",
      "GuideName":"Quest",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v23.4"
   },
   {  
      "GuideNumber":"39.1",
      "GuideName":"ION",
      "HD":1,
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v39.1"
   },
   {  
      "GuideNumber":"97.1",
      "GuideName":"UNKNOWN",
      "Favorite":1,
      "URL":"http://192.168.1.107:5004/auto/v97.1"
   },
   {  
      "GuideNumber":"5000",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5000"
   },
   {  
      "GuideNumber":"5001",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5001"
   },
   {  
      "GuideNumber":"5002",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5002"
   },
   {  
      "GuideNumber":"5003",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5003"
   },
   {  
      "GuideNumber":"5004",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5004"
   },
   {  
      "GuideNumber":"5005",
      "GuideName":"Unknown",
      "HD":1,
      "URL":"http://192.168.1.107:5004/auto/v5005"
   },
   {  
      "GuideNumber":"5006",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5006"
   },
   {  
      "GuideNumber":"5007",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5007"
   },
   {  
      "GuideNumber":"5008",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5008"
   },
   {  
      "GuideNumber":"5009",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5009"
   },
   {  
      "GuideNumber":"5010",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5010"
   },
   {  
      "GuideNumber":"5011",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5011"
   },
   {  
      "GuideNumber":"5012",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5012"
   },
   {  
      "GuideNumber":"5013",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5013"
   },
   {  
      "GuideNumber":"5014",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5014"
   },
   {  
      "GuideNumber":"5015",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5015"
   },
   {  
      "GuideNumber":"5016",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5016"
   },
   {  
      "GuideNumber":"5017",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5017"
   },
   {  
      "GuideNumber":"5018",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5018"
   },
   {  
      "GuideNumber":"5019",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5019"
   },
   {  
      "GuideNumber":"5020",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5020"
   },
   {  
      "GuideNumber":"5021",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5021"
   },
   {  
      "GuideNumber":"5022",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5022"
   },
   {  
      "GuideNumber":"5023",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5023"
   },
   {  
      "GuideNumber":"5024",
      "GuideName":"Unknown",
      "URL":"http://192.168.1.107:5004/auto/v5024"
   }
]
Edited by BrianG

Share this post


Link to post
Share on other sites
Luke

Hi, in your screenshot of the mapping tool, the channels you see on the left are the channels reported by your tuner device. The channels  you see in the popup are the channels reported by the guide data. 

 

So for each tuner channel that isn't showing guide data, you need to manually select the guide channel for it. Yes they look different, that's why you have to map them manually. If they looked exactly the same, the server probably would have automatically found the right mappings.

 

Please let us know if this helps. Thanks.

  • Like 1

Share this post


Link to post
Share on other sites
BrianG

Arrg. I was afraid of that. I started going with mapping that made some logcal sense, but quickly found it was off. So then I started watching a channel and seeing how that matched up in the guide and mapping accordingly, but this is a TEDIOUS process!

 

I think I'm just going to disconnect TV service and get rid of the HDHomeRun tuner box. It's just not worth the hassle. The only time we've used it recently is when the wife wanted to watch this year's superbowl

 

I think if my provider was even close to being consistent in their web guide vs their guide data, this would be a whole lot easier. So I fully blame them.

 

Thanks for the explanation though. I guess I was hoping for some magic setting or something lol.

Share this post


Link to post
Share on other sites
Luke

But you have a small channel list of what, 24 channels? Shouldn't that only take a couple minutes? I can already see some of them right now just by eyeballing the two lists. Notice how the channel names are close enough that it's probably the right one.

Share this post


Link to post
Share on other sites
BrianG

That's the problem, they just look like they match up, but don't when you physically watch a channel and compare it to what MediaCom's TV listing says it should be. And being cable TV, I have to watch around 10 minutes of commercials before I get to the actual program and see if it matches. It really is easy, just very tedious - makes me want to take a nap just thinking about it. lol.

 

Dealing with all this really makes me understand why people don't bother paying for TV anymore. It's just not worth it.

Share this post


Link to post
Share on other sites
Spaceboy

That's the problem, they just look like they match up, but don't when you physically watch a channel and compare it to what MediaCom's TV listing says it should be. And being cable TV, I have to watch around 10 minutes of commercials before I get to the actual program and see if it matches. It really is easy, just very tedious - makes me want to take a nap just thinking about it. lol.

 

Dealing with all this really makes me understand why people don't bother paying for TV anymore. It's just not worth it.

embys implementation of this is awful. We must assume that Luke has never had to deal with more than 5 channels as part of a test process. Consider mapping hundreds of channels which is what most emby users have

 

Xteve is the way forwards

Share this post


Link to post
Share on other sites
BrianG

embys implementation of this is awful. We must assume that Luke has never had to deal with more than 5 channels as part of a test process. Consider mapping hundreds of channels which is what most emby users have

 

Xteve is the way forwards

 

It actually appears Emby implements its automatic mapping fairly well. It just sucks when the provider's data is inconsistent and such a mess, like in my case. So, I really blame the provider. I'm not really sure how Emby could make the process of manually re-mapping hundreds of channels any easier tbh. I remember the dev(s) at SchedulesDirect having to work with me quite a bit when I started using them, so I don't think the problem is isolated to Emby. The problem really is the presence of thousands of different providers and the seemingly non-standard way of reporting their channels vs what they advertise.

Share this post


Link to post
Share on other sites
Spaceboy

It actually appears Emby implements its automatic mapping fairly well. It just sucks when the provider's data is inconsistent and such a mess, like in my case. So, I really blame the provider. I'm not really sure how Emby could make the process of manually re-mapping hundreds of channels any easier tbh. I remember the dev(s) at SchedulesDirect having to work with me quite a bit when I started using them, so I don't think the problem is isolated to Emby. The problem really is the presence of thousands of different providers and the seemingly non-standard way of reporting their channels vs what they advertise.

i worked with software in wmc that had far more sophisticated mapping tech. Nothing to do with providers. The list of channels they provide you to match against is completely randomly ordered for starters. That’s just brain dead

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...