This is the first entry in the log:
Code: Select all
[3/28/2016 2:43:01 PM] [ERROR] epg123 is not recognized as an approved app from Schedules Direct. code: 1005 , message: Did not recognize the submitted client. , datetime: 2016-03-28T18:43:00Z
Code: Select all
[3/28/2016 2:43:01 PM] [ERROR] epg123 is not recognized as an approved app from Schedules Direct. code: 1005 , message: Did not recognize the submitted client. , datetime: 2016-03-28T18:43:00Z
For now, that's normal, you should be all good.mldenison wrote:I'm on the latest version of EPG123.
This is the first entry in the log:
No other errors reported so the Guide updated correctly?Code: Select all
[3/28/2016 2:43:01 PM] [ERROR] epg123 is not recognized as an approved app from Schedules Direct. code: 1005 , message: Did not recognize the submitted client. , datetime: 2016-03-28T18:43:00Z
That will work. It would make more sense to move the automatch after the load but I don't think it makes a bit of difference.glorp wrote:This right, for now? Or does the match occur between the load and reindex ? And before you say anything my sched task on each client sets the default directory to the epg123 location.Code: Select all
@ECHO OFF ECHO Importing guide data START /WAIT %SYSTEMROOT%\ehome\loadmxf.exe -i \\WSE\Backups\epg123\epg123.mxf ECHO Initializing the reindex task of the guide data START /WAIT schtasks.exe /run /tn "Microsoft\Windows\Media Center\ReindexSearchRoot" ECHO Beginning channel match START /WAIT epgAutomatch.exe -match EXIT
I switched the order for todays run. Every step ran successfully and was confirmed by looking at runs times etc. on task. I also implemented some minimal logging for it (steps, command outputs, and return values redirected).garyan2 wrote:That will work. It would make more sense to move the automatch after the load but I don't think it makes a bit of difference.glorp wrote:This right, for now? Or does the match occur between the load and reindex ? And before you say anything my sched task on each client sets the default directory to the epg123 location.Code: Select all
@ECHO OFF ECHO Importing guide data START /WAIT %SYSTEMROOT%\ehome\loadmxf.exe -i \\WSE\Backups\epg123\epg123.mxf ECHO Initializing the reindex task of the guide data START /WAIT schtasks.exe /run /tn "Microsoft\Windows\Media Center\ReindexSearchRoot" ECHO Beginning channel match START /WAIT epgAutomatch.exe -match EXIT
Get 0.9.2 to avoid this. The registry access is now only when opening the GUI ... will no longer affect an update run.JTScribe wrote:I can manually run the update with no issues, but the scheduled update task has a failure message in the log file - unhandled exception in main program, requested registry access is not allowed. I am using 0.91, should I try the newer version?
Did running epgAutomatch.exe -nologo not work?glorp wrote:I still get messed up logo graphics rather than the desired call signs on every channel in the guide. I've been running the channel matching feature for several days now and notice that I get the same repeated logo graphic on every channel in my guide. Always just the first time WMC starts up but now almost every day. The graphic is always from one of the shows I have a series recording for but it varies as to which series.
Is the only solution to start from scratch with the database again or will one of the "tools" handle this? I see nothing in Guide Tool that affects the channel logos but maybe I'm missing it.
It didn't b/c I didn't notice the extra CL switch needed!garyan2 wrote:Did running epgAutomatch.exe -nologo not work?
I can go to Tasks > Settings > TV > Guide > Edit Channels and select the missing channel.mldenison wrote:On the latest version, I had disabled some stations in the right pane and they were gone in the guide. Last night, I re-enabled some of the channels in the right pane but they don't show up in the guide. I had to use GuideTool to re-enable them.
Unfortunately for those of us that use ATSC, WMC doesn't scan VHF frequencies (channels 2-13) ... they need to be added manually. Sorry, I haven't updated the website to note this for everyone to see.fzy8gc wrote:I thought I try EPG123 today to prepare for the inevitable. Everything seemed to build perfect. The system I used was a Win 7 system with a Silicon Dust HDHomerun dual turner and an ATI analog cable turner. The zip I used was 34243 (Sarasota, FL). The listings I chose were Sarasota OTA and Hotwire - Cascades Standard Cable. All the channels were included. When they were loaded into WMC, many of the OTA channels were missing. For example, 8.1, 8.2, 10.1, 10.2, 10.3, 13.1, 13.2, 13.3, and 13.4 to name a few. Some were there: 40.1, 44.1, 44.2. The channels that loaded had perfect guide information. The channels that loaded played just fine. The HDHomerun turner is plugged into an antenna. The ATI turner is plugged into a cable feed from the community. The cable feed carries OTA signals as well and analog cable channels. The strange thing I noticed, when I tried to edit out the OTA signals from the Hotwire channels using EPG123, it also edited out the corresponding analog cable channels. That is when I tried using all channels for both listings and editing the channels inside the Guide edit function in WMC.
There is no trouble with this setup when using the Rovi guide other than the obvious lack of updates from time to time.
Interesting that you mentioned WMC doesn't scan VHF frequencies. Is that only when using EPG123 or has something changed within WMC? I ask because the Chicago area used to have 2 VHF HD channels & still has CBS on VHF 12 and I don't recall ever manually adding a channel.garyan2 wrote:Unfortunately for those of us that use ATSC, WMC doesn't scan VHF frequencies (channels 2-13) ... they need to be added manually. Sorry, I haven't updated the website to note this for everyone to see.fzy8gc wrote:I thought I try EPG123 today to prepare for the inevitable. Everything seemed to build perfect. The system I used was a Win 7 system with a Silicon Dust HDHomerun dual turner and an ATI analog cable turner. The zip I used was 34243 (Sarasota, FL). The listings I chose were Sarasota OTA and Hotwire - Cascades Standard Cable. All the channels were included. When they were loaded into WMC, many of the OTA channels were missing. For example, 8.1, 8.2, 10.1, 10.2, 10.3, 13.1, 13.2, 13.3, and 13.4 to name a few. Some were there: 40.1, 44.1, 44.2. The channels that loaded had perfect guide information. The channels that loaded played just fine. The HDHomerun turner is plugged into an antenna. The ATI turner is plugged into a cable feed from the community. The cable feed carries OTA signals as well and analog cable channels. The strange thing I noticed, when I tried to edit out the OTA signals from the Hotwire channels using EPG123, it also edited out the corresponding analog cable channels. That is when I tried using all channels for both listings and editing the channels inside the Guide edit function in WMC.
There is no trouble with this setup when using the Rovi guide other than the obvious lack of updates from time to time.
Go to settings->TV->Guide->Add Missing Channels->Add DTV Channel ... you will then need to add 3.1 for the digital TV channel, enter 13 for assigned frequency, and WEDUDT for the callsign. Repeat for all missing tuner channels.
3.1, 3.2, 3.3, 3.4 use assigned frequency 13
8.1, 8.2 use assigned frequency 7
10.1, 10.2, 10.3 use assigned frequency 10
13.1, 13.2, 13.3, 13.4 use assigned frequency 12
Actually I had to do this quite often with Rovi. It was always missing a channel here and there. You can find the actual frequency by giving the call letters + Wikipedia in a search engine. When the switch to HD happened some stations were forced to use a different frequency. If you look above channel 10 got to keep frequency 10. Channel 13 had to use frequency 12.Mike88 wrote:Interesting that you mentioned WMC doesn't scan VHF frequencies. Is that only when using EPG123 or has something changed within WMC? I ask because the Chicago area used to have 2 VHF HD channels & still has CBS on VHF 12 and I don't recall ever manually adding a channel.garyan2 wrote:Unfortunately for those of us that use ATSC, WMC doesn't scan VHF frequencies (channels 2-13) ... they need to be added manually. Sorry, I haven't updated the website to note this for everyone to see.fzy8gc wrote:I thought I try EPG123 today to prepare for the inevitable. Everything seemed to build perfect. The system I used was a Win 7 system with a Silicon Dust HDHomerun dual turner and an ATI analog cable turner. The zip I used was 34243 (Sarasota, FL). The listings I chose were Sarasota OTA and Hotwire - Cascades Standard Cable. All the channels were included. When they were loaded into WMC, many of the OTA channels were missing. For example, 8.1, 8.2, 10.1, 10.2, 10.3, 13.1, 13.2, 13.3, and 13.4 to name a few. Some were there: 40.1, 44.1, 44.2. The channels that loaded had perfect guide information. The channels that loaded played just fine. The HDHomerun turner is plugged into an antenna. The ATI turner is plugged into a cable feed from the community. The cable feed carries OTA signals as well and analog cable channels. The strange thing I noticed, when I tried to edit out the OTA signals from the Hotwire channels using EPG123, it also edited out the corresponding analog cable channels. That is when I tried using all channels for both listings and editing the channels inside the Guide edit function in WMC.
There is no trouble with this setup when using the Rovi guide other than the obvious lack of updates from time to time.
Go to settings->TV->Guide->Add Missing Channels->Add DTV Channel ... you will then need to add 3.1 for the digital TV channel, enter 13 for assigned frequency, and WEDUDT for the callsign. Repeat for all missing tuner channels.
3.1, 3.2, 3.3, 3.4 use assigned frequency 13
8.1, 8.2 use assigned frequency 7
10.1, 10.2, 10.3 use assigned frequency 10
13.1, 13.2, 13.3, 13.4 use assigned frequency 12