Skipped Matching...

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
Post Reply
Sammy2

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

HTPC Specs: Show details

Skipped Matching...

#1

Post by Sammy2 » Tue Jan 23, 2018 2:01 am

Code: Select all

[1/22/2018 1:21:00 AM] [ INFO] Skipped matching EDAC to channel 183 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching KCETDT3 to channel 195 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching GOLTV to channel 274 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching ESPN to channel 35 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching ESPN2 to channel 36 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching FSW to channel 37 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching PRIME to channel 38 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching FS1 to channel 40 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching KVMDDT to channel 21 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching SNLA to channel 431 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching IMPCNHD to channel 211 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching TOONPHD to channel 1326 due to channel already having an assigned listing.
[1/22/2018 1:21:00 AM] [ INFO] Skipped matching DXDHDP to channel 1304 due to channel already having an assigned listing.
I looked at a couple of these in GuideTool and they are matched to the call signs indicated. What gives?

TIA

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Tue Jan 23, 2018 5:43 am

Probably a side effect of going from "EPG123 Lineups with Schedules Direct" to lineups specific to your actual lineup, i.e. "EPG123 Cox Communications - Digital (Tucson)" that I added in 1.1.18. When performing automatch, it compares the primary channel in the merged channel to the channel in the EPG123 lineup. If they are considered not equal, then you will get that message. It could very well be that the one existing in the merged channel is pointing to the old lineup and not the new. The channel and channel ID are exactly the same so there is no risk of losing guide data because of this.

How long after you updated until you started seeing these messages?
- 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

#3

Post by Sammy2 » Tue Jan 23, 2018 3:35 pm

garyan2 wrote:Probably a side effect of going from "EPG123 Lineups with Schedules Direct" to lineups specific to your actual lineup, i.e. "EPG123 Cox Communications - Digital (Tucson)" that I added in 1.1.18. When performing automatch, it compares the primary channel in the merged channel to the channel in the EPG123 lineup. If they are considered not equal, then you will get that message. It could very well be that the one existing in the merged channel is pointing to the old lineup and not the new. The channel and channel ID are exactly the same so there is no risk of losing guide data because of this.

How long after you updated until you started seeing these messages?
This appeared in the 1/22 and 1/21 runs but I didn't look any farther for it before reporting it. I'll look today to see if it repeats since I updated or if it started sometime after that.

Thanks Gary!

Sammy2

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

HTPC Specs: Show details

#4

Post by Sammy2 » Thu Jan 25, 2018 5:00 pm

garyan2 wrote:Probably a side effect of going from "EPG123 Lineups with Schedules Direct" to lineups specific to your actual lineup, i.e. "EPG123 Cox Communications - Digital (Tucson)" that I added in 1.1.18. When performing automatch, it compares the primary channel in the merged channel to the channel in the EPG123 lineup. If they are considered not equal, then you will get that message. It could very well be that the one existing in the merged channel is pointing to the old lineup and not the new. The channel and channel ID are exactly the same so there is no risk of losing guide data because of this.

How long after you updated until you started seeing these messages?
This continues in each run. I'll still need to go back up and check but I'm not sure exactly when I upgraded. My post somewhere here will probably tell me!

Sammy2

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

HTPC Specs: Show details

#5

Post by Sammy2 » Tue Jan 30, 2018 5:16 pm

And this same [INFO] continues.. How to fix it?

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Wed Jan 31, 2018 4:21 am

Sammy2 wrote:And this same [INFO] continues.. How to fix it?
There's really nothing to fix. Like I said, there is no harm. But to maybe stop the log entries, you could try using the client GUI to manually unsubscribe one of the channels and subscribe it back with the desired lineup. I have had success doing this but don't think it is a 100% solution.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply