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
User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

Skipped matching

#1

Post by StinkyImp » Tue Mar 20, 2018 1:24 pm

Hi garyan2,

I've been receiving the following "Skipped matching" message every day since January. What can I do to make it go away?
Skipped matching.png

User avatar
12noon

Posts: 127
Joined: Mon Oct 06, 2014 4:23 pm
Location:

HTPC Specs: Show details

#2

Post by 12noon » Tue Mar 20, 2018 8:56 pm

I had this issue (among others) a while back, and here's Gary's solution.

viewtopic.php?p=124647#p124647

You might want to read the whole thread because it took me a couple of tries to get it right. :-)
USA 60005
WOW Chicago Suburbs - Digital
USA-IL58819-X

User avatar
garyan2

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

HTPC Specs: Show details

#3

Post by garyan2 » Tue Mar 20, 2018 10:32 pm

StinkyImp wrote:Hi garyan2,

I've been receiving the following "Skipped matching" message every day since January. What can I do to make it go away?
That's easy ... stop looking at it.

This is a side effect of breaking all the unique lineups out of the legacy "EPG123 Lineups with Schedules Direct". In the database, you now have 2 lineups with the same station. Here is what you do...

1) open the client and toggle the [Custom Labels]/[Original Labels] button to read [Original Labels].
2) on the left merged channel list view, highlight both 25.2 K18JLD2 and 7.4 KAZTCD2, right-click and select unsubscribe.
3) select your OTA lineup on the right side.
4) click the Match by: [# Number] button or manually subscribe both channels to a right side lineup channel.

That should make the information only entries disappear.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#4

Post by StinkyImp » Wed Mar 21, 2018 1:28 pm

garyan2 wrote:That's easy ... stop looking at it.
Sometimes the most elegant solution is also the easiest!

Even so, I followed the additional instructions. Afterward a different channel exhibited the same "Skipped matching" anomaly. Fortunately it was a channel I never use so I unchecked and unsubscribed it... Channel 7.4 still suffers.
7.x Channels.png
Original Channel
7.x Custom.png
Custom Channel
It appears that the "custom" channel 7.4 conflicts with 7.2 in the "original" listing. If I right-click on the pink highlighted channel, the only option available is "Unsubscribe". All other options are grayed out.

Is there any way to change the "original" channel to 7.4? :)
7.4 Channel.png
After changes

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Wed Mar 21, 2018 3:26 pm

It looks like 7.2 is the actual problem and not 7.4 per se. If you look at the tuningInfo for KAZTCD2 7.2, you will see a UHF 36.2 + VHF 7.4. Where did the VHF 7.4 come from? Is this a user added channel? If so, go to Add Missing Channels and delete it. This may clear it up.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#6

Post by StinkyImp » Thu Mar 22, 2018 12:45 pm

garyan2 wrote:It looks like 7.2 is the actual problem and not 7.4 per se.
Good Morning garyan2!

I looked into my user added channels and only 7.4 has been added. I don't know how the UHF 36.2 + VHF 7.4 were assigned to channel 7.2 ??

Should I delete the 7.4 from the user added section?
Edit Channel.png
Looks like 7.4 is the only bugger in the mix now...
7.4 Skipped.png
EDIT: The strange thing is... It's skipping assigning KAZTCD2 to channel 7.4 when it should actually be KAZTCD4. It's correct in the user added section and in the EPG123 client.

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Thu Mar 22, 2018 2:35 pm

StinkyImp wrote:Should I delete the 7.4 from the user added section?
Yes, I would suggest removing the user added channel 7.4. I don't even think it is a valid addition. Let's see what happens after that.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#8

Post by StinkyImp » Thu Mar 22, 2018 3:51 pm

garyan2 wrote:Yes, I would suggest removing the user added channel 7.4. I don't even think it is a valid addition. Let's see what happens after that.
Results after deleting 7.4 from user additions:

EPG123 Log after "Save & Execute":

Code: Select all

[3/22/2018 8:00:08 AM] ===============================================================================
[3/22/2018 8:00:08 AM]  Beginning epg123 client execution.
[3/22/2018 8:00:08 AM] ===============================================================================
[3/22/2018 8:00:08 AM] [ INFO] Beginning epg123 client execution. 2018-03-22 15:00:08Z
[3/22/2018 8:00:08 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: True
[3/22/2018 8:00:08 AM] [ INFO] epg123 client version: 1.1.24 for Win7
[3/22/2018 8:00:09 AM] Entering importMxfFile() for file "H:\epg123\epg123.mxf"
[3/22/2018 8:00:54 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[3/22/2018 8:00:54 AM] Exiting importMxfFile(). SUCCESS.
[3/22/2018 8:00:54 AM] [ INFO] Matching KAZTCD2 to channel 7.4
[3/22/2018 8:00:54 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[3/22/2018 8:00:54 AM] Entering reindexDatabase()
[3/22/2018 8:00:54 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[3/22/2018 8:00:54 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[3/22/2018 8:00:54 AM] Exiting reindexDatabase(). SUCCESS.
[3/22/2018 8:00:54 AM] [ INFO] Completed EPG123 client execution.
[3/22/2018 8:00:54 AM] [ INFO] EPG123 client execution time was 00:00:45.8176206.
[3/22/2018 8:01:12 AM] [ERROR] There are no tuners associated with "36.4 : KAZTCD4 - 46C46D = { (36.4 : KAZTCD4 - 46C468) + [ ] }". Deleting channel.
It matched KAZTCD2 to channel 7.4 and the correct listing is KAZTCD4.

Sidenote for a different time: That last [ERROR] entry is curious...

EPG123 Client after deleting and performing "Save & Execute":
After deleting 7.4.png
After deleting 7.4 C.png
Schedules Direct for my zip:
After deleting 7.4 SD.png
NOTE: 7.4 exists in the SD lineup but doesn't show up in the EPG123 client now?

7.4 is a recently added channel in my area and is shown as the Charge network. Tuning to the channel confirms this is valid and accurate!

I don't want to restore my backup because it'll just put me back to where I started from. Is there any way to completely delete/destroy/obliterate channel 7.4 and then rescan or set it back up in the user additions, or some other method?

This just gets freakier and freakier...

Thanks for all your wisdom in this matter! I probably won't check back until later today or (most likely) tomorrow morning.

User avatar
garyan2

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

HTPC Specs: Show details

#9

Post by garyan2 » Thu Mar 22, 2018 5:24 pm

StinkyImp wrote:Is there any way to completely delete/destroy/obliterate channel 7.4 and then rescan or set it back up in the user additions, or some other method?
There is. With OTA, the easiest thing to do to repair/rebuild the tuners so they are clean is to go to settings->TV->TV Signal->Scan for More Channels, click the [Delete All] button and then [Scan again] button. This will require the channels to be matched with the listings again, but that is extremely easy to do manually in the client GUI. Just click the Match by: [# Number] button.

The no tuners associated thing ... I dunno. That one doesn't make any sense, but nothing about all your 7.x (36.x) channels do. The above should get everything nice and clean once again.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#10

Post by StinkyImp » Fri Mar 23, 2018 2:02 pm

garyan2 wrote:With OTA, the easiest thing to do to repair/rebuild the tuners so they are clean is to
  • go to settings->TV->TV Signal->Scan for More Channels CHECK
  • click the [Delete All] button CHECK
  • and then [Scan again] button. CHECK
  • This will require the channels to be matched with the listings again, but that is extremely easy to do manually in the client GUI.
  • Just click the Match by: [# Number] button. CHECK
I stopped here because I'm experiencing the following problem:
7.4 Missing.png
7.4 is now missing from SD even after several "refreshes".
which is weird because it was there previously. I even sorted by callsign and there's no KAZTCD4 (or Charge) within the list.

As previously shown, 7.4 is listed in the Schedules Direct "Local Broadcast Listings" for my zip.

Other info:
Win 7 Pro
EPG123 v 1.1.24

User avatar
garyan2

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

HTPC Specs: Show details

#11

Post by garyan2 » Fri Mar 23, 2018 2:21 pm

StinkyImp wrote:I stopped here because I'm experiencing the following problem:
7.4 Missing.png
which is weird because it was there previously. I even sorted by callsign and there's no KAZTCD4 (or Charge) within the list.

As previously shown, 7.4 is listed in the Schedules Direct "Local Broadcast Listings" for my zip.
You must have unselected 7.4 for download in the configuration GUI. I'm still showing it as available in your lineup and just downloaded a days worth of scheduling.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#12

Post by StinkyImp » Fri Mar 23, 2018 3:28 pm

garyan2 wrote:You must have unselected 7.4 for download in the configuration GUI.
Check that! I'm starting to believe that the conversion to ATSC 3.0 that's occurring here is wreaking havoc on my channels. I'm currently working with SD on channels that evidently flow from a parent station in another city (on one channel) but are transmitted in my city on a totally different channel.

In other instances it appears that broadcasters are (seemingly) randomly assigning stations to their subchannels. The "stations" for the broadcaster are listed in SD in one order, but they're actually broadcast in a different order.

Therefore, the channels that actually exist here can't, and aren't, being matched with their lineup. YAY OTA Broadcasters!

User avatar
garyan2

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

HTPC Specs: Show details

#13

Post by garyan2 » Fri Mar 23, 2018 10:59 pm

StinkyImp wrote:
garyan2 wrote:You must have unselected 7.4 for download in the configuration GUI.
Check that! I'm starting to believe that the conversion to ATSC 3.0 that's occurring here is wreaking havoc on my channels. I'm currently working with SD on channels that evidently flow from a parent station in another city (on one channel) but are transmitted in my city on a totally different channel.

In other instances it appears that broadcasters are (seemingly) randomly assigning stations to their subchannels. The "stations" for the broadcaster are listed in SD in one order, but they're actually broadcast in a different order.

Therefore, the channels that actually exist here can't, and aren't, being matched with their lineup. YAY OTA Broadcasters!
I had this happen in my area a few weeks ago where I had one of my towers decide to change their logical channel numbers to be the same as logical channel numbers from 2 different towers (the joy of living in the center of 3 mountain ranges). It totally screwed up my scanning results. We're supposed to be in the midst of frequency changes for new allocations, but nothing has moved yet.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply