SchedulesDirect: request that a Jellyfin developer contact me

[asilvera4]

To add to snowinrv2's post and maybe save some others some time. If you find the tv_grab_na_dd on GitHub, before you run it, you need to go to on or around line 719 and modify the fqdn within the url of two lines containing "$dd_service='http://docs.tms.tribune.com/tech...". Change docs.tms.tribune.com to dd.schedulesdirect.org in both URLs. Then run the script with --configure to build the config file. I found it easy to then run it again with --output </path/file.xml> to make an XMLTV file that JF loaded happily. The default is 7 days of data. YMMV, but this was how a non-techie got LiveTV working again for now. Oh, and don't forget to make sure you've built an SD-DD lineup on SD first if you've only ever used the JSON side. Obviously, both downsides snowinrv2 mentions still apply, which is a big ol' bummer, but it's better than nothing.

[rmeden]

To add to snowinrv2's post and maybe save some others some time. If you find the tv_grab_na_dd on GitHub, before you run it, you need to go to on or around line 719 and modify the fqdn within the url of two lines containing "$dd_service='http://docs.tms.tribune.com/tech...". Change docs.tms.tribune.com to dd.schedulesdirect.org in both URLs.

You must be using a *very* old version of tv_grab_na_dd!  That change was probably made 15 years ago!

Here's the XMLTV github

I'm not sure how Jellyfin schedules programs.. the program-id in the XMLTV file probably matches the SD-JSON program id.

RobertE
XMLTV/Schedules Direct

[asilvera4]

You must be using a *very* old version of tv_grab_na_dd!  That change was probably made 15 years ago!

I believe it read "14 years ago" hah. This is what happens when an amateur googles how to make an XMLTV file from SD. I didn't realize the newer grabbers were within xmltv itself. The stand-alone on git is ancient. Thanks for clearing that up and for the helpful info over on the git thread (greyspace07 on there).

[robo45h]

PRs are welcome

What is a PR?

[asilvera4]

PR is a Pull Request. I understand it to be an open invite for other developers to review, modify, test, and submit changes to a branch of a project. Makes me wish my skillset was more than "20 goto 10"

[robo45h]

PR is a Pull Request. I understand it to be an open invite for other developers to review, modify, test, and submit changes to a branch of a project. Makes me wish my skillset was more than "20 goto 10"

Oh, a pull request. That generally means that there is a code fix already proposed. I certainly hope so. I can't believe how long this outage has gone on.

[Sam Harbaugh]

Does anyone have a temporary work-around for this problem?

I am trying an XML file, as a workaround.  But the guide is not populating.
Did you have to sort the DD XML file?
Command I used.  tv_grab_na_dd --days 7 --output test.txt
No errors in the JF log
I am in fact getting data in the file

Thanks

[TheDreadPirate]

If you are using an XML, you have to map the guide to a source if you have not done so already.

   

[Sam Harbaugh]

If you are using an XML, you have to map the guide to a source if you have not done so already.

Thank you!  That did the trick

[finicky6457]

I have configured my TV Guide Data Providers for XMLTV to use an XML file with listings data that I generate once a day from SchedulesDirect using tv_grab_na_dd.  There's 2 downsides to this approach:
1 - my generated listings file does not contain season and episode numbers so ignore duplicate recordings setting does not work.
2 - any recordings previously scheduled under the Schedules Direct configuration are ignored.  I had to set up new recording schedules.
It's much cleaner to use the SchedulesDirect listing provider directly.

Thank you! I've also been able to get this method to work. I also observed the downsides you mentioned. Additionally (and it may be related to the first) some shows now are not available to record as a "Series" while others are.