Hi all,
I've just switched from v4 to v5 and everything is running great except for one small issue. Historically, I've only used the ATSC source for the guide data but with the upgrade I thought it was time to revisit the xml route via EPG Buddy (using TVGuide.com data). My use case is very simple, just one tuner and 8 OTA channels. The XML file EPG Buddy generates adds a local GMT offset (presently -7hrs) to every data entry, so when it gets imported into the NextPVR TV Guide everything is (predictably) off by 7 hours. I can manually find/replace the -0700 entry in the xml file and then of course, everything lines up.
It appears that in Media Portal 2 there is a setting (Plugins/XmlTv) "Apply time compensation when loading tvguide.xml" to account for this. Is there something like this that could be added to NextPVR? Or, am I missing something that functions similarly that's already there? Any help/suggestions are appreciated.
I've attached a log zip if that's of any help.
Thanks!
I've just switched from v4 to v5 and everything is running great except for one small issue. Historically, I've only used the ATSC source for the guide data but with the upgrade I thought it was time to revisit the xml route via EPG Buddy (using TVGuide.com data). My use case is very simple, just one tuner and 8 OTA channels. The XML file EPG Buddy generates adds a local GMT offset (presently -7hrs) to every data entry, so when it gets imported into the NextPVR TV Guide everything is (predictably) off by 7 hours. I can manually find/replace the -0700 entry in the xml file and then of course, everything lines up.
It appears that in Media Portal 2 there is a setting (Plugins/XmlTv) "Apply time compensation when loading tvguide.xml" to account for this. Is there something like this that could be added to NextPVR? Or, am I missing something that functions similarly that's already there? Any help/suggestions are appreciated.
I've attached a log zip if that's of any help.
Thanks!