EPG123 Bug Reports

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
PricklyPear

Posts: 4
Joined: Sat Jul 08, 2017 2:40 pm
Location:

HTPC Specs: Show details

Re: EPG123 Bug Reports

#841

Post by PricklyPear » Mon Oct 15, 2018 10:00 pm

There is nothing in the XMLTV file to indicate the time zone or the SD lineup identifier, but all "programme" blocks are in UTC time.
An example of a <programme> entry for a local station. The entry for "news at noon":

<programme start="20181015190000" stop="20181015200000" channel="KVOADT">
<title>News 4 Tucson at Noon</title>
<desc>A comprehensive look at all of the latest local and national news provided by the News 4 Tucson team.</desc>
<date>20060109</date>
<category>News</category>
<language>en</language>
<icon src="https://s3.amazonaws.com/schedulesdirec ... _v5_aa.jpg" />
<episode-num system="dd_progid">SH00809370.0000</episode-num>
<episode-num system="original-air-date">2018-10-15 12:00:55</episode-num>
<video>
<quality>HDTV</quality>
</video>
<audio>
<stereo>stereo</stereo>
</audio>
<new />
<subtitles type="teletext" />
</programme>

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#842

Post by garyan2 » Mon Oct 15, 2018 10:22 pm

Correct, everything is in UTC. I would say NPVR is not interpreting the start and stop times correctly... it assumes the times are local.

Here is an excerpt from the xmltv.dtd which defines what the fields are and how to interpret.
All dates and times in this DTD follow the same format, loosely based
on ISO 8601. They can be 'YYYYMMDDhhmmss' or some initial
substring, for example if you only know the year and month you can
have 'YYYYMM'. You can also append a timezone to the end; if no
explicit timezone is given, UTC is assumed
. Examples:
'200007281733 BST', '200209', '19880523083000 +0300'. (BST == +0100.)
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#843

Post by garyan2 » Mon Oct 15, 2018 10:42 pm

PricklyPear wrote:
Mon Oct 15, 2018 10:00 pm
<programme start="20181015190000" stop="20181015200000" channel="KVOADT">
<title>News 4 Tucson at Noon</title>
BTW: Howdy neighbor! You a Tucsonan or nearby area?
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

PricklyPear

Posts: 4
Joined: Sat Jul 08, 2017 2:40 pm
Location:

HTPC Specs: Show details

#844

Post by PricklyPear » Mon Oct 15, 2018 11:29 pm

garyan2 wrote:
Mon Oct 15, 2018 10:22 pm
Correct, everything is in UTC. I would say NPVR is not interpreting the start and stop times correctly... it assumes the times are local.

Here is an excerpt from the xmltv.dtd which defines what the fields are and how to interpret.
All dates and times in this DTD follow the same format, loosely based
on ISO 8601. They can be 'YYYYMMDDhhmmss' or some initial
substring, for example if you only know the year and month you can
have 'YYYYMM'. You can also append a timezone to the end; if no
explicit timezone is given, UTC is assumed
. Examples:
'200007281733 BST', '200209', '19880523083000 +0300'. (BST == +0100.)
So, the dtd says that in the absence of a time zone identifier, the times are to be interpreted as UTC. OK. I don't read that as a spec that says "all times must be populated as UTC". In fact, your quote shows precisely how to specify a time other than UTC. In fact, I see no rationale for putting the times in UTC. The information in the guide is only relevant not only to a specific time zone, it is relevant only to a specific cable system operating in a very small area comprising a handful of zip codes in that time zone.

So, given the above, is it your position that the arithmetic required to populate the guide is strictly the responsibility of the consuming application? I can assure that the NPVR owner is about .00001% likely to do the coding to accommodate that.

I haven't bothered to look at the JSON output from SD, but always assumed it was in local time for the reasons I outline above.
garyan2 wrote:
Mon Oct 15, 2018 10:42 pm
PricklyPear wrote:
Mon Oct 15, 2018 10:00 pm
<programme start="20181015190000" stop="20181015200000" channel="KVOADT">
<title>News 4 Tucson at Noon</title>
BTW: Howdy neighbor! You a Tucsonan or nearby area?
Yup. I am in Tucson.

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#845

Post by garyan2 » Mon Oct 15, 2018 11:47 pm

PricklyPear wrote:
Mon Oct 15, 2018 11:29 pm
So, the dtd says that in the absence of a time zone identifier, the times are to be interpreted as UTC. OK. I don't read that as a spec that says "all times must be populated as UTC". In fact, your quote shows precisely how to specify a time other than UTC. In fact, I see no rationale for putting the times in UTC. The information in the guide is only relevant not only to a specific time zone, it is relevant only to a specific cable system operating in a very small area comprising a handful of zip codes in that time zone.
I disagree and would argue that all times should be in UTC... the only benefit of specifying the time zone is when a human tries to read the data. We don't add and/or subtract very well, especially when it comes to time. I also disagree with the notion that time is only relevant to a small geographic location. Take for example CNN... a person watching CNN on the east coast will be watching the exact same broadcast as on the west coast. Their local times may be different, but you are absolutely guaranteed that the UTC time is the same.
PricklyPear wrote:
Mon Oct 15, 2018 11:29 pm
So, given the above, is it your position that the arithmetic required to populate the guide is strictly the responsibility of the consuming application? I can assure that the NPVR owner is about .00001% likely to do the coding to accommodate that.

I haven't bothered to look at the JSON output from SD, but always assumed it was in local time for the reasons I outline above.
Yes and No. I don't know how NPVR coded it up, but basically all they needed to do was identify the time as UTC... the operating system would have then translated it automatically. NPVR doesn't have to do the math.

BTW: I have verified that that same XMLTV file will work in emby and Plex. NPVR should be no different. And, the SD-JSON data is in UTC as well.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Space

Posts: 1491
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#846

Post by Space » Tue Oct 16, 2018 1:17 am

Yes, I have to agree that standardizing on UTC is the best method. You can easily convert from UTC to other timezones. It is particularly nice when you have DST changes (which I grant, Arizona, for the most part, does not have), since the time in the XMLTV file does not all of a sudden change from MST to MDT, so you end up having two 2AMs or missing 2AM all together (depending on which way you are transitioning).
Not only that, you can use the same XMLTV file in whatever timezone you are in and it will be correct (as long as you properly convert the UTC time to your local time).

I am pretty sure that NextPVR supports conversion from UTC to the local timezone, so there must be some configuration setting that is not correct on your system (either in the XMLTV importer, NextPVR, or in the Windows timezone setting).

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#847

Post by garyan2 » Tue Oct 16, 2018 1:49 am

Okay, I just ran an experiment. I installed NPVR on my laptop and set it up for TV. I first used the generated XMLTV file from EPG123 and I duplicated what you were seeing. The start and stop times were being translated as local time and not UTC as it is supposed to be.

I then changed the time formats from "yyyyMMddHHmmss" to "yyyyMMddHHmmss +0000", giving a time offset of 0 hours. The results is the guide now had the correct time values. So this is again on NPVR in their implementation. However, there is no harm in me updating EPG123 to just add the "+0000" to the time entries and it will still be compatible with emby and Plex without issues... I'll have to verify that though. The biggest con is it will add quite a bit to the file size, but should be reasonable.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#848

Post by garyan2 » Tue Oct 16, 2018 2:57 am

Here is where NPVR went wrong in the parseToUTC() function. They needed to define the DateTimeStyle to assume universal time. The DateTime.ParseExact assumes local time otherwise.

Code: Select all

DateTime dateTime;
if (text.Length == 14)
{
	dateTime = DateTime.ParseExact(text, "yyyyMMddHHmmss", null);
}
else
{
	dateTime = DateTime.ParseExact(text, "yyyyMMddHHmm", null);
}

Code: Select all

DateTime dateTime;
if (text.Length == 14)
{
	dateTime = DateTime.ParseExact(text, "yyyyMMddHHmmss", null, System.Globalization.DateTimeStyles.AssumeUniversal);
}
else
{
	dateTime = DateTime.ParseExact(text, "yyyyMMddHHmm", null, System.Globalization.DateTimeStyles.AssumeUniversal);
}
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Space

Posts: 1491
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#849

Post by Space » Tue Oct 16, 2018 4:02 am

I'm guessing much of the XMLTV input is generated from screen scrapers which usually means the time is specified in the local time zone, so I figure that is why it defaults to that. Still doesn't make it right.

PricklyPear

Posts: 4
Joined: Sat Jul 08, 2017 2:40 pm
Location:

HTPC Specs: Show details

#850

Post by PricklyPear » Wed Oct 17, 2018 9:30 pm

garyan2 wrote:
Mon Oct 15, 2018 11:47 pm
...all they needed to do was identify the time as UTC... the operating system would have then translated it automatically. NPVR doesn't have to do the math.

BTW: I have verified that that same XMLTV file will work in emby and Plex. NPVR should be no different. And, the SD-JSON data is in UTC as well.
I stand corrected. After giving it some thought, it is obvious my position made no sense. Obviously a live show occurs at a specific point in time independent of any particular way of expressing it. So UTC is the obvious choice. Same reason I used Z time for several years in military. 1200Z is 1200Z no matter where you happen to be. LOL

(As an occasional Windows programmer, I should also have realized that conversion from UTC to local is trivial in Windows. I rarely have to drop to WinAPI level in the HLL I use.)

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#851

Post by garyan2 » Wed Oct 17, 2018 11:57 pm

PricklyPear wrote:
Wed Oct 17, 2018 9:30 pm
Same reason I used Z time for several years in military.
Same here.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

lostgreycells

Posts: 22
Joined: Wed Jan 13, 2016 6:11 am
Location:

HTPC Specs: Show details

#852

Post by lostgreycells » Fri Oct 19, 2018 5:49 pm

Cannot set up scheduled task without having the "automatically match stations to channels" greyed out. I need it checked to fully populate the guide. Without that option a few channels show up with "no data available". I then have to clear the cache and run manually to allow it to again fully populate my channels. All channels I've chosen are checked on the client tool guide and the Schedules Direct Account.

Basically I must now download manually to get the full guide with stations matched to channels.

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#853

Post by garyan2 » Fri Oct 19, 2018 7:26 pm

lostgreycells wrote:
Fri Oct 19, 2018 5:49 pm
Cannot set up scheduled task without having the "automatically match stations to channels" greyed out.
That option is set by your scheduled task. In order to change it, you need to delete your current task and create a new one.
lostgreycells wrote:
Fri Oct 19, 2018 5:49 pm
I need it checked to fully populate the guide. Without that option a few channels show up with "no data available". I then have to clear the cache and run manually to allow it to again fully populate my channels.
This doesn't make sense. The manual run and the scheduled run do the exact same thing. Did you recently upgrade to 1.2.5 from something prior to 1.2.1? If you did not delete the existing task and create a new one, then the scheduled task will be importing an old MXF file, but the manual run will be importing the new/current MXF file.

Also, clearing the cache and building a new MXF file gains you nothing in this case. Clearing the cache is really only there if we suspect some corrupted files causing the update to abort. All you are doing is creating the same file over and over again.
lostgreycells wrote:
Fri Oct 19, 2018 5:49 pm
All channels I've chosen are checked on the client tool guide and the Schedules Direct Account.
I'm assuming what you mean by "the Schedules Direct Account" is from the EPG123 Configuration GUI? If you are talking about their web interface, that is only for the XML server. EPG123 uses the JSON server.

Schedules Direct website: XML server only, no impact to EPG123.
EPG123 Configuration GUI: Identifies what stations from what lineups are to be downloaded.
EPG123 Client GUI: Left side is WMC tuner channels; checkboxes are enables to display the channels in the guide. Right side are lineups currently in the WMC database with collection of stations/channels availabe to map to the left side tuner channels.

Suggestion:
Check the EPG123 Configuration GUI to make sure all desired stations are selected for download.
Delete current scheduled task, select the 'Automatically match...' option, and create a new scheduled task.
Click the [Save & Execute] button.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

lostgreycells

Posts: 22
Joined: Wed Jan 13, 2016 6:11 am
Location:

HTPC Specs: Show details

#854

Post by lostgreycells » Fri Oct 19, 2018 9:31 pm

Thanks Gary! I thought I'd already done what you suggested several times without success, but this time deleting and adding schedule worked (check marks held this time, ran a scheduled update which loaded everything). So just changed the time to run in the middle of the night - the acid test....

(My Windows 7 OS got buggered up a week ago so replaced it with my out-of-date backup MacriumReflect-created cloned drive, am still updating/tweaking it until I can get everything working perfectly - dedicated box to EPG123 and WMC!! Then re-clone so I'll have two healthy Windows 7 C drives again.) Thanks again!!

dnabsuh

Posts: 6
Joined: Sat Mar 14, 2015 2:39 am
Location:

HTPC Specs: Show details

#855

Post by dnabsuh » Wed Nov 07, 2018 10:02 pm

Hi - After upgrading to 1.2.6,I am getting a unhandled exception error. I cleared the cache a few times - this is the log

Code: Select all

[11/7/2018 4:53:09 PM] ===============================================================================
[11/7/2018 4:53:09 PM]  Beginning epg123 update execution. version 1.2.6.0
[11/7/2018 4:53:09 PM] ===============================================================================
[11/7/2018 4:53:09 PM] [ INFO] Beginning EPG123 update execution. 2018-11-07 21:53:09Z
[11/7/2018 4:53:09 PM] [ INFO] DaysToDownload: 21 , TheTVDBNumbers : True , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: False , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: True
[11/7/2018 4:53:09 PM] [ INFO] Token request successful. serverID: 20141201.web.X
[11/7/2018 4:53:09 PM] [ INFO] Status request successful. account expires: 2019-09-05T22:52:39Z , lineups: 1/4 , lastDataUpdate: 2018-11-07T18:01:23Z
[11/7/2018 4:53:09 PM] [ INFO] system status: Online , message: No known issues.
[11/7/2018 4:53:09 PM] [ INFO] Successfully retrieved TMDb configurations.
[11/7/2018 4:53:09 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/7/2018 4:53:09 PM] Entering buildLineupServices() for 1 lineups.
[11/7/2018 4:53:10 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-NJ67162-X.
[11/7/2018 4:53:10 PM] Exiting buildLineupServices(). SUCCESS.
[11/7/2018 4:53:10 PM] Entering getAllScheduleEntryMd5s() for 21 days on 319 stations.
[11/7/2018 4:53:12 PM] [ INFO] Successfully retrieved Md5s for 238 station's daily schedules.
[11/7/2018 4:53:17 PM] [ INFO] Successfully retrieved 238 station's daily schedules.
[11/7/2018 4:53:45 PM] [ INFO] Successfully retrieved Md5s for 81 station's daily schedules.
[11/7/2018 4:53:47 PM] [ INFO] Successfully retrieved 81 station's daily schedules.
[11/7/2018 4:53:56 PM] [ INFO] Found 0 cached daily schedules.
[11/7/2018 4:53:56 PM] [ INFO] Downloaded 6699 daily schedules.
[11/7/2018 4:54:02 PM] [ INFO] Processed 6699 daily schedules for 319 stations.
[11/7/2018 4:54:02 PM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[11/7/2018 4:54:02 PM] Entering buildAllProgramEntries() for 47655 programs.
[11/7/2018 4:54:03 PM] [ INFO] Found 0 cached program descriptions.
[11/7/2018 4:54:06 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:54:30 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:54:55 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:55:19 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:55:44 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:56:10 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:56:35 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:57:01 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:57:27 PM] [ INFO] Successfully retrieved 5000 program descriptions.
[11/7/2018 4:57:50 PM] [ INFO] Successfully retrieved 2655 program descriptions.
[11/7/2018 4:58:01 PM] [ INFO] Processed 47655 program descriptions.
[11/7/2018 4:58:01 PM] Exiting buildAllProgramEntries(). SUCCESS.
[11/7/2018 4:58:01 PM] Entering buildAllGenericSeriesInfoDescriptions() for 9365 series.
[11/7/2018 4:58:01 PM] [ INFO] Found 0 cached series descriptions.
[11/7/2018 4:58:02 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:04 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:05 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:07 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:09 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:11 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:14 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:16 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:18 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:20 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:22 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:24 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:26 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:28 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:30 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:31 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:33 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:35 PM] [ INFO] Successfully retrieved 500 generic program descriptions.
[11/7/2018 4:58:36 PM] [ INFO] Successfully retrieved 365 generic program descriptions.
[11/7/2018 4:58:37 PM] [ INFO] Processed 9365 series descriptions.
[11/7/2018 4:58:37 PM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[11/7/2018 4:58:37 PM] Entering buildAllExtendedSeriesDataForUiPlus() for 9365 series.
[11/7/2018 4:58:37 PM] [ INFO] Found 6717 cached extended series descriptions.
[11/7/2018 4:58:39 PM] [ INFO] Successfully retrieved 2648 program descriptions.
[11/7/2018 4:58:39 PM] [ERROR] Unhandled exception caught from epg123.exe. message: Object reference not set to an instance of an object.
[11/7/2018 4:58:44 PM] ===============================================================================
[11/7/2018 4:58:44 PM]  Beginning epg123 client execution. version 1.2.6.0
[11/7/2018 4:58:44 PM] ===============================================================================
[11/7/2018 4:58:44 PM] [ INFO] Beginning epg123 client execution. 2018-11-07 21:58:44Z
[11/7/2018 4:58:44 PM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False
[11/7/2018 4:58:44 PM] Entering importMxfFile() for file "c:\programdata\garyan2\epg123\output\epg123.mxf"
[11/7/2018 5:00:15 PM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[11/7/2018 5:00:15 PM] Exiting importMxfFile(). SUCCESS.
[11/7/2018 5:00:15 PM] [ INFO] Skipped matching WTVEHD to channel 525 due to channel already having an assigned listing.
[11/7/2018 5:00:15 PM] [ERROR] Failed to perform the automatch of lineup stations to tuner channels task.
[11/7/2018 5:00:15 PM] [ INFO] Completed lineup refresh.
[11/7/2018 5:00:15 PM] Entering runWmcTask(ReindexSearchRoot)
[11/7/2018 5:00:15 PM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[11/7/2018 5:00:15 PM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[11/7/2018 5:00:15 PM] Exiting runWmcTask(ReindexSearchRoot). SUCCESS.
[11/7/2018 5:00:15 PM] Entering runWmcTask(PvrScheduleTask)
[11/7/2018 5:00:15 PM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\PvrScheduleTask".
[11/7/2018 5:00:15 PM] [ INFO] Successfully started the PvrScheduleTask task. Exit code: 0
[11/7/2018 5:00:15 PM] Exiting runWmcTask(PvrScheduleTask). SUCCESS.
[11/7/2018 5:00:15 PM] [ERROR] The MXF file imported is 43.53 hours old.
[11/7/2018 5:00:15 PM] [ INFO] Completed EPG123 client execution.
[11/7/2018 5:00:15 PM] [ INFO] EPG123 client execution time was 00:01:31.4039562.

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#856

Post by garyan2 » Wed Nov 07, 2018 11:58 pm

Interesting. I'll try to duplicate it when I get home later tonight, but in the mean time you can disable creating the MMUI+ support file. See if that gets you through.

I must have missed a nullable json value when creating the support file.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

dnabsuh

Posts: 6
Joined: Sat Mar 14, 2015 2:39 am
Location:

HTPC Specs: Show details

#857

Post by dnabsuh » Thu Nov 08, 2018 2:21 am

garyan2 wrote:
Wed Nov 07, 2018 11:58 pm
Interesting. I'll try to duplicate it when I get home later tonight, but in the mean time you can disable creating the MMUI+ support file. See if that gets you through.

I must have missed a nullable json value when creating the support file.
Disabling the MMUI+ Support did fix the generation, though now I got a [11/7/2018 9:21:02 PM] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -2146233082
[11/7/2018 9:21:02 PM] Exiting importMxfFile(). FAILURE.
[11/7/2018 9:21:02 PM] [ERROR] Failed to import .mxf file. Exiting.

Its possible I confused things by running too many times
Edit- after rebooting, things worked

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#858

Post by garyan2 » Thu Nov 08, 2018 3:34 am

Okay, my code was expecting the program's show type to be populated which is optional per the API. I'm actually surprised this is the first time the problem has been reported. I'll get an update released probably this weekend... maybe even Friday.

For the loadmxf problem now, it may be that you still have some mcupdate processes running after the previous import of the old files. I would recommend to reboot the computer to end all possible mcupdate processes running, and try the update again.

EDIT: I see you reboot the computer and everything is working now. :thumbup:
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

mike2400

Posts: 1
Joined: Tue Dec 25, 2018 3:01 pm
Location:

HTPC Specs: Show details

#859

Post by mike2400 » Tue Dec 25, 2018 3:24 pm

EPG123 is not pulling all the channels in the lineup from schedules direct. I have my OTA air lineup for zip code 23322 configured properly on the schedules direct site. However, when EPG 123 pulls the line ups it is missing a channel. The channel in questions is 43-3 WVBT H&I. I'm stumped. I have uninstalled and reinstalled EPG123. Cleared all the program data and even installed it on a totally different computer. Same issue with the missing channel. Has anyone else out there had a weird issue like this? What was the solution? Thanks, Mike B.

Examples of lineup on SchedulesDirect and EPG123

https://drive.google.com/file/d/1iH7LKB ... sp=sharing

https://drive.google.com/file/d/1ac7Ofr ... sp=sharing

https://drive.google.com/file/d/1_G8nQ9 ... sp=sharing

User avatar
garyan2

Posts: 3333
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#860

Post by garyan2 » Tue Dec 25, 2018 3:41 pm

mike2400 wrote:
Tue Dec 25, 2018 3:24 pm
EPG123 is not pulling all the channels in the lineup from schedules direct. I have my OTA air lineup for zip code 23322 configured properly on the schedules direct site. However, when EPG 123 pulls the line ups it is missing a channel. The channel in questions is 43-3 WVBT H&I. I'm stumped. I have uninstalled and reinstalled EPG123. Cleared all the program data and even installed it on a totally different computer. Same issue with the missing channel. Has anyone else out there had a weird issue like this? What was the solution? Thanks, Mike B.

Examples of lineup on SchedulesDirect and EPG123

https://drive.google.com/file/d/1iH7LKB ... sp=sharing

https://drive.google.com/file/d/1ac7Ofr ... sp=sharing

https://drive.google.com/file/d/1_G8nQ9 ... sp=sharing
It looks like Schedules Direct does not have that station on their JSON server. What you are looking at on their website is the DD server which does nothing for you and any changes you make there will have no impact.

Open a ticket with Schedules Direct to add the missing channel... once the channel is in the JSON server, then EPG123 will pick it up.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post Reply