- for me the important thing is that the SD JSON data gives me the Season "Number" and the other data sources only provide the Season "Year".
I'm not sure what the other data differences are.
So I'm looking into switching from PercData to the SD JSON source so I can get season and episode #'s again (it turns out that I have a SD subscription through 2021 thanks to having worked on an app that uses it a while back). Am I correct in assuming that I should select the MC2XML option in MC and choose the SD JSON option when the MC2XML configuration opens up? I've tried doing that running my standalone copy of MC2XML (version 1.5, I donated to get the version that includes the new Rovi feed). I selected "schedules direct json" as the service, entered my SD username and password, entered my zip code, left the country code set to US, and hit ok (no options checked) and see the following in the command window:
Connecting .. : schedulesdirect.org
Error: Did not receive User-Agent in header. See
https://github.com/SchedulesDirect/JSON-Service/wiki/API-20141201#tasks-your-client-must-performNo mc2xml.dat file gets created and no xmltv.xml file gets created (obviously because it isn't getting to the point of downloading the data).
Before I clear my EPG data in MC, I want to make sure that MC2XML is going to get the data correctly.
If I choose the regular SD option in MC2XML and enter my same username and password (no zip code is requested - is it using the lineups I created on the SD site?), it downloads the data just fine and I end up with the mc2xml.dat and xmltv.xml files as expected.
I did a bit more reading on the MC2XML site and it sounds like I need to set an environment variable (USERAGENT) to my email address before running MC2XML. But it also mentions something about some complications in downloading multiple lineups and using multiple dat files - is this something MC will take care of for me? I need an OTA lineup and a digital cable lineup.