Schedules Direct EPG (integrated BETA)

[EnterNoEscape]

Schedules Direct EPG support is now integrated into the SageTV core.

This feature is currently considered beta. I encourage people who are curious to try this new feature out and post their impressions, suggestions or issues they experience. Before reporting an issue with this EPG solution, make sure you have the same problems on the latest version of SageTV.

Because this is a core feature, you can actually use the original EPG solution (WarlockRipper) alongside Schedules Direct if desired. Just know that if there is any overlap, the Schedules Direct solution will yield to WarlockRipper in all foreseen cases. That means that if you use the exact same lineup from both sources and they download the exact same stations, all of your guide data will come from WarlockRipper.

Check the wiki page on GitHub for details on how to use the new EPG data source.

Extra Features:

• Series Info
• Channel Logos
• Series Images
• Episode/Movie/Sports Images

[tmiranda]

Excellent. Sage needed this.

[pukka]

Working so far

[trk2]

Great news! Thanks for all your hard work!

[nyplayer]

Great Job works right out of the box.

[EnterNoEscape]

Thanks everyone. It's good to see some people have already tried to use it and so far have had success. I really hope this integrated solution will help draw in new users and maybe even some new developers.

[rickgillyon]

Thanks for this, perfect timing 24 hours after I subscribed another year with my old provider...

I tried it the other night, then removed the new tuner because I didn't have time to sort out the mappings. So all my tuners are with old lineups using XML, not Sage EPG (I'm in UK). Today I have 7 system messages saying "Invalid EPG Server License Key Specified." I'm not using Sage EPG or SD at the moment, but it may be that Sage is doing a pull of my SD data anyway.

Any ideas?

[nyplayer]

Originally Posted by EnterNoEscape

Thanks everyone. It's good to see some people have already tried to use it and so far have had success. I really hope this integrated solution will help draw in new users and maybe even some new developers.

What I had to do on Windows was download the windows Installer ...Installed it then went to the Linux files and download SageJar-9.0.8.423.zip and replaced the files. Is this the correct way to Install in Windows for now?

[EnterNoEscape]

Originally Posted by rickgillyon

Thanks for this, perfect timing 24 hours after I subscribed another year with my old provider...

I tried it the other night, then removed the new tuner because I didn't have time to sort out the mappings. So all my tuners are with old lineups using XML, not Sage EPG (I'm in UK). Today I have 7 system messages saying "Invalid EPG Server License Key Specified." I'm not using Sage EPG or SD at the moment, but it may be that Sage is doing a pull of my SD data anyway.

Any ideas?

That error message is more likely coming from WarlockRipper (you might have something using it), but if you can post your sagetv_0.txt log, we can be more positive about that. I made sure that the Schedules Direct oriented messages actually say Schedules Direct in them for clarity.

Edit: Check to make sure you have the XML plugin set up correctly. If the plugin isn't loading correctly, I could see you getting that message too since SageTV might be trying to use WarlockRipper since the plugin failed to load.

[EnterNoEscape]

Originally Posted by nyplayer

What I had to do on Windows was download the windows Installer ...Installed it then went to the Linux files and download SageJar-9.0.8.423.zip and replaced the files. Is this the correct way to Install in Windows for now?

That should be ok for now; the wiki comments on the one issue you will have in Windows involving channel logos. An updated Windows installer will be forthcoming from another developer, but I don't have an ETA on that.

[rickgillyon]

Originally Posted by EnterNoEscape

That error message is more likely coming from WarlockRipper (you might have something using it), but if you can post your sagetv_0.txt log, we can be more positive about that. I made sure that the Schedules Direct oriented messages actually say Schedules Direct in them for clarity.

Edit: Check to make sure you have the XML plugin set up correctly. If the plugin isn't loading correctly, I could see you getting that message too since SageTV might be trying to use WarlockRipper since the plugin failed to load.

The XML plugin has been in use for years, and I believe it does use warlockripper. Never produced these errors until I used SD. Maybe it's failed every time since I used SD...

Log here: http://www.gillyon.com/downloads/sagetv_0.txt

Edit: last error 14:39.

[jusjoken]

Originally Posted by nyplayer

What I had to do on Windows was download the windows Installer ...Installed it then went to the Linux files and download SageJar-9.0.8.423.zip and replaced the files. Is this the correct way to Install in Windows for now?

I would think that the SageTV7.xml STV file would be needed as well for this.

I am currently uploading to BinTray the Windows installers for 9.0.8.423 so when that completes then I will post that the update is available.

k

[jusjoken]

New Windows installer posted.... see my signature.

Note: the issue mentioned on the Wiki for "Grey-scale channel logos are green and half-width" is NOT fixed in this installer.

k

[EnterNoEscape]

Originally Posted by jusjoken

I would think that the SageTV7.xml STV file would be needed as well for this.

I am currently uploading to BinTray the Windows installers for 9.0.8.423 so when that completes then I will post that the update is available.

k

You are correct and that file is included in the archive he downloaded.

[EnterNoEscape]

Originally Posted by rickgillyon

The XML plugin has been in use for years, and I believe it does use warlockripper. Never produced these errors until I used SD. Maybe it's failed every time since I used SD...

Log here: http://www.gillyon.com/downloads/sagetv_0.txt

Edit: last error 14:39.

You are definitely using WarlockRipper whether you know it or not. In your Sage.properties, make sure you actually have the XML plugin defined. epg/epg_import_plugin= should be set to something other than the Schedules Direct plugin and you will likely need to delete your lineups and add them again to use the XML plugin. I don't know the details of what you're using, so that's about about as far as I can take you.

[rickgillyon]

epg/epg_import_plugin=xmltv.XMLTVImportPlugin

This plugin has, I believe, always used WarlockRipper:

epg_data_sources/6835103/epg_class=WarlockRipper

That from last month's backup, been using the same same system for a number of years. We'll see if it's still a problem once I dump the old lineups.

[rickgillyon]

More examples popping up:
https://forums.sagetv.com/forums/showthread.php?t=63536

[EnterNoEscape]

Originally Posted by rickgillyon

More examples popping up:
https://forums.sagetv.com/forums/showthread.php?t=63536

It is unlikely that the Schedules Direct addition is causing this problem. The logic for WarlockRipper to load a plugin in place of it's normal routine was also changed slightly recently to provide more helpful error messages, but I don't actually know the full details on those changes. Are you having the same issues with 9.0.7? That version should have those changes, but not the Schedules Direct changes. That should help narrow things down.

[rickgillyon]

Originally Posted by EnterNoEscape

It is unlikely that the Schedules Direct addition is causing this problem. The logic for WarlockRipper to load a plugin in place of it's normal routine was also changed slightly recently to provide more helpful error messages, but I don't actually know the full details on those changes. Are you having the same issues with 9.0.7? That version should have those changes, but not the Schedules Direct changes. That should help narrow things down.

I think they did also appear in 9.0.7, unfortunately I won't have a chance to check that out until the weekend.

[EnterNoEscape]

Originally Posted by rickgillyon

epg/epg_import_plugin=xmltv.XMLTVImportPlugin

This plugin has, I believe, always used WarlockRipper:

epg_data_sources/6835103/epg_class=WarlockRipper

That from last month's backup, been using the same same system for a number of years. We'll see if it's still a problem once I dump the old lineups.

If I'm reading the code correctly, this will result in WarlockRipper being loaded. There's a line just before it will load the plugin that checks if in your case, the property epg_data_sources/6835103/epg_class= contains a period (.) and in your case, that would fail and end up loading WarlockRipper instead.

I'll dig a little more and see what I can find.

Edit: What is epg/custom_data_source_class= set to in Sage.properties?