trace.log entry: [WARNG] Time discontinuity

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Sammy2

Posts: 1708
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#41

Post by Sammy2 » Mon Apr 18, 2016 3:58 pm

STC wrote:THIS is what makes EPG123 top banana thank you both.
Yes it is!

As far as these time discontinuities go, do they effect recordings or guide information? I don't watch SPROUT but have seen a few other stations I watch occasionally show up in the log but haven't noticed any issues in the guide.

User avatar
garyan2

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

HTPC Specs: Show details

#42

Post by garyan2 » Tue Apr 19, 2016 1:51 am

Sammy2 wrote:
STC wrote:THIS is what makes EPG123 top banana thank you both.
Yes it is!

As far as these time discontinuities go, do they effect recordings or guide information? I don't watch SPROUT but have seen a few other stations I watch occasionally show up in the log but haven't noticed any issues in the guide.
Neither of the observed discontinuities will affect the guide. For those missing a time slot, epg123 will correctly set the start time of the next program. For those with duplicates, epg123 will create 2 entries but they will be overlapping in the guide and WMC will treat them as a single entry.

What we haven't seen in awhile is when the stop or start time is off by a minute or two. Then you will have overlapping programs and you will have a "missing" program in the guide, though it will still be there and can be recorded. The guide just doesn't know how to display it, so one of them is hidden.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sammy2

Posts: 1708
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#43

Post by Sammy2 » Fri Apr 22, 2016 2:24 pm

I am happy to report that these discontinuities are not showing up in my trace.log since April 18. Has this issue been resolved by Gracenote/SchedulesDirect?

glorp

Posts: 369
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#44

Post by glorp » Fri Apr 22, 2016 3:20 pm

Sammy2 wrote:I am happy to report that these discontinuities are not showing up in my trace.log since April 18. Has this issue been resolved by Gracenote/SchedulesDirect?
Mine were all resolved as well several days ago.

User avatar
garyan2

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

HTPC Specs: Show details

#45

Post by garyan2 » Fri Apr 22, 2016 4:23 pm

Were the errors corrected, or just died out?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sammy2

Posts: 1708
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#46

Post by Sammy2 » Fri Apr 22, 2016 4:35 pm

garyan2 wrote:Were the errors corrected, or just died out?
I think Richard will have to answer that one because all I know is that the errors aren't there anymore.

glorp

Posts: 369
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#47

Post by glorp » Fri Apr 22, 2016 6:45 pm

Sammy2 wrote:I think Richard will have to answer that one because all I know is that the errors aren't there anymore.
Same. They are/were all on channels I didn't care about so I never looked to see what issue they flagged in the guide appearance itself in those spots and would never have noticed it ever. That's really why I asked if they could be surpressed.

BTW, it's also possible they just filtered their way out of the guide and nothing new is there now. They were around for ~2 weeks, about the length of my guide.

rkulagow

Posts: 246
Joined: Sun Jul 19, 2015 1:04 am
Location: Schedules Direct

HTPC Specs: Show details

#48

Post by rkulagow » Fri Apr 22, 2016 7:15 pm

They're gone (or at least mitigated a lot more) due to my work with Gracenote.

glorp

Posts: 369
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#49

Post by glorp » Fri Apr 22, 2016 7:21 pm

Thank you for that then.

User avatar
garyan2

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

HTPC Specs: Show details

#50

Post by garyan2 » Fri Apr 22, 2016 7:25 pm

glorp wrote:That's really why I asked if they could be surpressed.
Was going to propose a compromise on the suppression. To avoid another checkbox/selection on the GUI, how 'bout epg123 only identifies the first discontinuity for a channel on a given day? There would just be a single line saying there was a discontinuity detected on this channel on this day.

rkulagow: would this be enough information for you to investigate? or would you also want the time?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

rkulagow

Posts: 246
Joined: Sun Jul 19, 2015 1:04 am
Location: Schedules Direct

HTPC Specs: Show details

#51

Post by rkulagow » Fri Apr 22, 2016 8:00 pm

The existing format is fine, but I really only need to know one per stationID. But the time is important because it allows me to zero-in on the issue.

glorp

Posts: 369
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#52

Post by glorp » Fri Apr 22, 2016 8:12 pm

garyan2 wrote:
glorp wrote:That's really why I asked if they could be surpressed.
Was going to propose a compromise on the suppression. To avoid another checkbox/selection on the GUI, how 'bout epg123 only identifies the first discontinuity for a channel on a given day? There would just be a single line saying there was a discontinuity detected on this channel on this day.
That's fine. Have you considered just adding some "advanced" options that can be set via editing the .cfg file? It's just xml. You can start with whatever defaults you like but it would provide a greater level of user control and w/o having to mess with an interface for every possible combination of stuff most will never care about in the gui. Just a thought.

webminster

Posts: 657
Joined: Tue Dec 20, 2011 11:05 pm
Location:

HTPC Specs: Show details

#53

Post by webminster » Fri Apr 22, 2016 11:34 pm

Looking through my logs, they're not all gone. But few are left, only one or a few each day.
-Alan

artm

Posts: 183
Joined: Tue Aug 04, 2015 9:00 pm
Location:

HTPC Specs: Show details

#54

Post by artm » Fri Apr 22, 2016 11:46 pm

Just keep the notifications as is, totally visible. The more data for the source the better to troubleshoot. I don't need to "feel" good about the log at the expense of information being hidden.
-Art --
Win7 Ultimate x64 (NO UPDATES!), EPG123 v1.1.19, Schedules Direct, HDHomerun Prime,
Dell 980 SFF, i5, Nvidia GT710
Dell 780 SFF, i5, HD4000

User avatar
garyan2

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

HTPC Specs: Show details

#55

Post by garyan2 » Sat Apr 23, 2016 7:25 pm

^ That is my preference, that is why it was proposed as a compromise. I still want to point out a problem if it exists, and if all that is needed to troubleshoot is the first entry, then mission accomplished.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sammy2

Posts: 1708
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#56

Post by Sammy2 » Sat Apr 23, 2016 10:48 pm

rkulagow wrote:They're gone (or at least mitigated a lot more) due to my work with Gracenote.
:clap: :clap: :clap: :clap: :clap:

Post Reply