For all it isn't worth... for me it reported 698 entries like this:
Code: Select all
Lineup: Scanned (Digital Antenna (ATSC))
DisplayChannelNumber: 11.1 OriginalNumber: 11 OriginalSubNumber: 1 Number: 11 MatchName: OC:11:1
DisplayChannelNumber: 11.2 OriginalNumber: 11 OriginalSubNumber: 2 Number: 11 MatchName: OC:11:2
DisplayChannelNumber: 11.3 OriginalNumber: 11 OriginalSubNumber: 3 Number: 11 MatchName: OC:11:3
DisplayChannelNumber: 12.1 OriginalNumber: 12 OriginalSubNumber: 1 Number: 12 MatchName: OC:12:1
DisplayChannelNumber: 12.2 OriginalNumber: 12 OriginalSubNumber: 2 Number: 12 MatchName: OC:12:2
...
Lineup: Scanned (Satellite)
DisplayChannelNumber: 70 OriginalNumber: 70 OriginalSubNumber: 0 Number: 70 MatchName: DNTWRK
DisplayChannelNumber: 71 OriginalNumber: 71 OriginalSubNumber: 0 Number: 71 MatchName: INFOM
DisplayChannelNumber: 104 OriginalNumber: 104 OriginalSubNumber: 0 Number: 104 MatchName: INFOM
DisplayChannelNumber: 217 OriginalNumber: 217 OriginalSubNumber: 0 Number: 217 MatchName: INFOM
DisplayChannelNumber: 107 OriginalNumber: 107 OriginalSubNumber: 0 Number: 107 MatchName: COMEDY
DisplayChannelNumber: 107 OriginalNumber: 107 OriginalSubNumber: 0 Number: 107 MatchName: COMEDY
DisplayChannelNumber: 669 OriginalNumber: 669 OriginalSubNumber: 0 Number: 669 MatchName: DRAMA
DisplayChannelNumber: 72 OriginalNumber: 72 OriginalSubNumber: 0 Number: 72 MatchName: PAID
DisplayChannelNumber: 73 OriginalNumber: 73 OriginalSubNumber: 0 Number: 73 MatchName: BLUEHYW
DisplayChannelNumber: 81 OriginalNumber: 81 OriginalSubNumber: 0 Number: 81 MatchName: ICTV
....
And in an unwanted surprise it apparently kicked off a Rovi update (first one for this db) which I attempted to cancel. But it loaded "28509683_ListingData.mxf" and bloated mcepg2-0.db an extra 100 megs or so. I mapped a Rovi channel with Guide Tool to check and sure enough 2 weeks of Rovi listings right next to my 21 days of SD gracenote.
In a strange twist this time, I don't notice anything amiss from the contamination. Searches initiated from "AMG" screens still find items both in and not in guide. This as opposed to the oddities I experienced when I first ran for a few days with a fully Rovi infested install of EPG123.
But why this data point may not matter much is because I have to "agree to terms" in order to get a functioning Colossus input from the MC Hauppauge software tuner. I spent hours trying and the only way to get valid sat channels in MC is to "agree" and let it successfully down load the zip code setup data. Then I can pull the ethernet and it will finish a full scan for sat channels without the Rovi listing download completing (in the background) and hitting the db.
I went 16 days without any Rovi listing downloads reaching C:\ProgramData\Microsoft\eHome\Packages\EpgListings. Everything working perfect. It seemed to only be doing client maintenance every 5 days during that time.
So do unmapped Rovi listing downloads matter beyond wasted bandwidth and db bloat? I think I will let this go for a while and see if I notice anything. The most obvious problem is I haven't yet found a way to complete a Colossus setup (offline) without the rovi zip code setup data successfully downloading as part of the process.
This may age it's way out of the db but it says the next update is scheduled in 2 days. Wish I could NOT agree and get 10,000 blank working sat channels but I suspect those must originate from something with the vendor setup software/drivers for the cable card tuner.