Jump to content

Can't get XMLTV to work


HumanPanda
Go to solution Solved by Luke,

Recommended Posts

HumanPanda

Hi Guys,

 

I am using zap2xml against tvguide.com to create xmltv data. However when trying to import it to Emby it is not working. In between I even get an error saying that it couldn't add my lineup to my Schedules Direct account and I am not using Schedules Direct. Anyone else seeing this?

 

Environment:

Unraid Server w/ Latest Docker

Emby Version Version 3.0.6300.0

 

I have Emby Premiere so it shouldn't be because I am importing more than 24 hours of data I think.

 

This happened in the previous version too but, waited until the new Docker was released to make sure it was still broken in the new version.

Link to comment
Share on other sites

HumanPanda

I have set up a new Docker and the issue still occurs. I have also put only 2 days worth of XMLTV data. I am not seeing the error message about schedules direct however. The logs aren't very useful. I am going to do this with debug logging on and send it to you after it is done. I have also attached my XMLTV data. But, all I see in the logs right now is:
 
2016-08-28 19:59:42.3742 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:42.9892 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:43.5992 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:44.2095 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:44.8237 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:45.4319 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:46.0332 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:46.6474 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:47.2554 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:47.8715 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:48.4815 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:49.0909 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:49.6921 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:50.3028 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml
2016-08-28 19:59:50.9120 Info App: xmltv path: /unraid/appdata/zap2xml/xmltv.xml

 

 

Edit: Debug logging didn't anything so not attaching it.

embylogs.txt

xmltv.zip

Edited by phiyuku
Link to comment
Share on other sites

HumanPanda

Those were the full logs and the debug logging showed nothing. I am guessing the xmltv data is bad but, have no way to verify that.

Link to comment
Share on other sites

If it failed to parse there definitely would have been an exception logged. So it's just empty?

Link to comment
Share on other sites

HumanPanda

Yeah it is just completely empty. I'm going to try and manually map a couple channels. Maybe that could be the reason.

Link to comment
Share on other sites

  • Solution

Does the guide show channels with no programs or nothing at all? if it's at least showing channels then mapping should do it. 

  • Like 1
Link to comment
Share on other sites

HumanPanda

Yeah... that did it. Manually mapping them. Is there a way to automate that? As the numbers are the same. Or perhaps a faster way?

Link to comment
Share on other sites

If there was a way to automate it, then you wouldn't have to do it :) the only reason you have to do it is because the channel numbers in the guide data don't match the channel numbers from your tuner.

Link to comment
Share on other sites

HumanPanda

That's weird cause it is definitely the same number. Does it go by channel id?

 

For instance my channel 2

 

    <channel id="I2.102.tvguide.com">
        <display-name>2 WCBS</display-name>
        <display-name>2</display-name>
        <display-name>WCBS</display-name>
    </channel>

 

Emby shows it as 2 WCBS which is one of the display-names.

Link to comment
Share on other sites

HumanPanda

OK so as a test, I changed all references of "I2.102.tvguide.com" to "2" and it mapped it automatically. So it looks like the Channel ID has to be the actual channel number in Emby and the display-names are ignored.

 

Wonder if it is feasible to use the display-name if the channel id doesn't match anything since most xmltv data will probably have one of the display names be the actual channel number. Only issue is that the channel-id is used for the actual timeslots so there will need to be some mapping done but, this might be a gateway to automatic mapping perhaps?

Edited by phiyuku
Link to comment
Share on other sites

So Luke will this be fixed in the coming versions where Emby will read the actual displayname part of the xml tag to get the Channel ID as opposed to phiyuku's hack?

Link to comment
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...