EPG123 & Hauppauage Collossus Anyone? Tuner Not Available
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
This was at the bottom of the trace file:
[6/25/2016 1:49:44 PM] [WARNG] Time discontinuity detected. Service 58532 (SMTHHD) SH024586730000 (entry 313) ends at 2016-07-08 01:00:00Z, SH024586730000 (entry 314) starts at 2016-07-08 00:00:00Z.
[6/25/2016 1:49:44 PM] No further discontinuities on SMTHHD will be reported for 2016-07-08.
[6/25/2016 1:49:44 PM] [WARNG] Time discontinuity detected. Service 58532 (SMTHHD) SH024586730000 (entry 405) ends at 2016-07-12 01:00:00Z, SH024586730000 (entry 406) starts at 2016-07-12 00:00:00Z.
[6/25/2016 1:49:44 PM] No further discontinuities on SMTHHD will be reported for 2016-07-12.
[6/25/2016 1:49:44 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[6/25/2016 1:49:44 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[6/25/2016 1:49:44 PM] Failed to create MXF file. Exiting.
[6/25/2016 1:49:44 PM] [STATS] epg123 update execution time was 00:00:45.7646176.
[6/25/2016 1:49:44 PM] [WARNG] Time discontinuity detected. Service 58532 (SMTHHD) SH024586730000 (entry 313) ends at 2016-07-08 01:00:00Z, SH024586730000 (entry 314) starts at 2016-07-08 00:00:00Z.
[6/25/2016 1:49:44 PM] No further discontinuities on SMTHHD will be reported for 2016-07-08.
[6/25/2016 1:49:44 PM] [WARNG] Time discontinuity detected. Service 58532 (SMTHHD) SH024586730000 (entry 405) ends at 2016-07-12 01:00:00Z, SH024586730000 (entry 406) starts at 2016-07-12 00:00:00Z.
[6/25/2016 1:49:44 PM] No further discontinuities on SMTHHD will be reported for 2016-07-12.
[6/25/2016 1:49:44 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[6/25/2016 1:49:44 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[6/25/2016 1:49:44 PM] Failed to create MXF file. Exiting.
[6/25/2016 1:49:44 PM] [STATS] epg123 update execution time was 00:00:45.7646176.
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
All right, I just duplicated this with your lineup. Looks like we either failed to receive a schedule file or failed to cache the schedule file. Hopefully I'll figure this out before it clears up.fzy8gc wrote:This was at the bottom of the trace file:
[6/25/2016 1:49:44 PM] [WARNG] Time discontinuity detected. Service 58532 (SMTHHD) SH024586730000 (entry 313) ends at 2016-07-08 01:00:00Z, SH024586730000 (entry 314) starts at 2016-07-08 00:00:00Z.
[6/25/2016 1:49:44 PM] No further discontinuities on SMTHHD will be reported for 2016-07-08.
[6/25/2016 1:49:44 PM] [WARNG] Time discontinuity detected. Service 58532 (SMTHHD) SH024586730000 (entry 405) ends at 2016-07-12 01:00:00Z, SH024586730000 (entry 406) starts at 2016-07-12 00:00:00Z.
[6/25/2016 1:49:44 PM] No further discontinuities on SMTHHD will be reported for 2016-07-12.
[6/25/2016 1:49:44 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[6/25/2016 1:49:44 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[6/25/2016 1:49:44 PM] Failed to create MXF file. Exiting.
[6/25/2016 1:49:44 PM] [STATS] epg123 update execution time was 00:00:45.7646176.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
More data:
I move the epg123 directory to a backup directory and reloaded the epg123 files from the beta 7z zip file. I executed epg123.exe with a 1 day guide. It executed successfully to completion. I did it again for a 21 day guide. It looked to stop in the same place while processing Md5s download. I checked the trace file. It failed with the same error as before.
Jim
I move the epg123 directory to a backup directory and reloaded the epg123 files from the beta 7z zip file. I executed epg123.exe with a 1 day guide. It executed successfully to completion. I did it again for a 21 day guide. It looked to stop in the same place while processing Md5s download. I checked the trace file. It failed with the same error as before.
Jim
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Yah, I've narrowed it down to the 7/1/2016 schedule of WGBODT2. Now gotta figure out what is going wrong here. See if you can do a 21 day without that station in your lineup.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Looks like a SD problem. This station actually has 3 schedules that have a md5 problem on 7/1/2016, 7/4/2016, and 7/15/2016. The problem is when I look up a listing of all the schedule md5's I check to see if they are already cached... if not, then I request it from SD. The response from SD is what I requested, but the embedded md5 is different and that is what I use to name the file with.
So when I request schedule md5s it provides 1 hash, when I download it it provides a different hash.
To clarify, stationId 86446 for 7/1, 7/4, and 7/15.
So when I request schedule md5s it provides 1 hash, when I download it it provides a different hash.
To clarify, stationId 86446 for 7/1, 7/4, and 7/15.
Last edited by garyan2 on Sat Jun 25, 2016 8:24 pm, edited 1 time in total.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
We had this problem on a much larger scale recently as described here -> http://www.thegreenbutton.tv/forums/vie ... 95#p107195
EDIT: This looks to be more localized. The schedule response we get for this channel on those dates don't appear to be complete ... hence the different md5. The schedule on 7/1 is 3 movies only which covers 8 1/2 hours of the day but there is nothing else.
EDIT: This looks to be more localized. The schedule response we get for this channel on those dates don't appear to be complete ... hence the different md5. The schedule on 7/1 is 3 movies only which covers 8 1/2 hours of the day but there is nothing else.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
Where do you go from here?
I checked the trace log from my other WMC system. It did not successfully run either early this morning.
[6/25/2016 12:00:08 AM] Entering getAllScheduleEntryMd5s() for 21 days on 1081 stations.
[6/25/2016 12:00:29 AM] [ INFO] Successfully retrieved Md5s for 1081 station's daily schedules.
[6/25/2016 12:00:34 AM] [ERROR] Unhandled exception caught from main program. message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Is there anything that can be done from my end?
Jim
I checked the trace log from my other WMC system. It did not successfully run either early this morning.
[6/25/2016 12:00:08 AM] Entering getAllScheduleEntryMd5s() for 21 days on 1081 stations.
[6/25/2016 12:00:29 AM] [ INFO] Successfully retrieved Md5s for 1081 station's daily schedules.
[6/25/2016 12:00:34 AM] [ERROR] Unhandled exception caught from main program. message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Is there anything that can be done from my end?
Jim
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
I already sent an email to rkulagow about this problem ... haven't gotten a response. You could open a formal ticket on Schedules Direct with the problem basically being MD5 comparison errors on station 86446 (WBGODT2) for dates 7/1, 7/4, and 7/15.
I just wish there was a way I could populate this information in the error log and make it easier to identify and report. I'm working on it. I am also thinking about continuing the build without that days schedule. Worst case with this scenario is there will be a time period in the channels guide data that is not up-to-date.
I just wish there was a way I could populate this information in the error log and make it easier to identify and report. I'm working on it. I am also thinking about continuing the build without that days schedule. Worst case with this scenario is there will be a time period in the channels guide data that is not up-to-date.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
Formal ticket #13866 on Schedules Direct has been opened.
Jim
Jim
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
So did you do an epg123 update without the offending station? Would be interested in hearing the Dish channels (Colossus/HDPVR) and ATSC channels are cooperating without duplicates or any other strangeness.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
I change my number of days back to 21 and ran the update at 8:15 am this morning. I had to leave before it completed. Turns out when I got home it successfully ran to completion.
Jim
Jim
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
So far so good. I have test recorded across all 3 tuners simultaneously.garyan2 wrote:So did you do an epg123 update without the offending station? Would be interested in hearing the Dish channels (Colossus/HDPVR) and ATSC channels are cooperating without duplicates or any other strangeness.
You have to control the channels in the "Edit Guide" function of WMC. If I try controlling channels with the SD screen across multi line ups, I end up wiping out those channels across all line ups with the same call sign. For example, If I uncheck WEDU in the Dish line up, it unchecks WEDU in the OTA line up.
Jim
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Yah, I checked that channel late last night and got no errors... looks like the problem was corrected.fzy8gc wrote:I change my number of days back to 21 and ran the update at 8:15 am this morning. I had to leave before it completed. Turns out when I got home it successfully ran to completion.
Jim
This is be design right now. I don't discriminate between lineups, in epg123 you are actually selecting what stations to download. If you disable a station in one lineup that is also in another lineup, you disable both. Like you said, you would have to use WMC 'Edit Guide' function to remove one of them from the guide (and recording sources).fzy8gc wrote:So far so good. I have test recorded across all 3 tuners simultaneously.
You have to control the channels in the "Edit Guide" function of WMC. If I try controlling channels with the SD screen across multi line ups, I end up wiping out those channels across all line ups with the same call sign. For example, If I uncheck WEDU in the Dish line up, it unchecks WEDU in the OTA line up.
Jim
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 60
- Joined: Thu Mar 03, 2016 3:35 pm
- Location:
- HTPC Specs:
fzy8gc gets a golden thumbs up for his patience and persistence with testing.
[6/25/2016 1:20:14 PM] Entering getAllScheduleEntryMd5s() for 25 days on 260 stations.
[6/25/2016 1:20:19 PM] [ INFO] Successfully retrieved Md5s for 260 station's daily schedules.
[6/25/2016 1:20:38 PM] [ INFO] Successfully retrieved 260 station's daily schedules.
[6/25/2016 1:21:10 PM] [WARNG] Time discontinuity detected. Service 58623 (SYFYHD) SH024584520000 (entry 50) ends at 2016-06-28 08:30:00Z, SH024584520000 (entry 51) starts at 2016-06-28 08:00:00Z.
[6/25/2016 1:21:10 PM] No further discontinuities on SYFYHD will be reported for 2016-06-28.
[6/25/2016 1:21:11 PM] [WARNG] Time discontinuity detected. Service 58623 (SYFYHD) SH024229070000 (entry 197) ends at 2016-07-05 08:30:00Z, SH024229070000 (entry 198) starts at 2016-07-05 08:00:00Z.
[6/25/2016 1:21:11 PM] No further discontinuities on SYFYHD will be reported for 2016-07-05.
[6/25/2016 1:21:12 PM] [WARNG] Time discontinuity detected. Service 28506 (AXSTV) EP009555540429 (entry 2) ends at 2016-06-25 05:30:00Z, EP010092340447 (entry 3) starts at 2016-06-25 06:30:00Z.
[6/25/2016 1:21:12 PM] No further discontinuities on AXSTV will be reported for 2016-06-25.
[6/25/2016 1:21:18 PM] [WARNG] Time discontinuity detected. Service 68049 (UNIHD) SH013814960000 (entry 54) ends at 2016-06-26 18:00:00Z, SH003072200000 (entry 55) starts at 2016-06-26 19:00:00Z.
[6/25/2016 1:21:18 PM] No further discontinuities on UNIHD will be reported for 2016-06-26.
[6/25/2016 1:21:18 PM] [WARNG] Time discontinuity detected. Service 68049 (UNIHD) SH024349710000 (entry 61) ends at 2016-06-27 03:00:00Z, SH003072200000 (entry 62) starts at 2016-06-27 04:00:00Z.
[6/25/2016 1:21:18 PM] No further discontinuities on UNIHD will be reported for 2016-06-27.
[6/25/2016 1:21:19 PM] [WARNG] Time discontinuity detected. Service 12553 (NASA) SH023078220000 (entry 94) ends at 2016-06-27 19:30:00Z, SH001329680000 (entry 95) starts at 2016-06-27 20:00:00Z.
[6/25/2016 1:21:19 PM] No further discontinuities on NASA will be reported for 2016-06-27.
[6/25/2016 1:21:21 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[6/25/2016 1:21:21 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[6/25/2016 1:21:21 PM] Failed to create MXF file. Exiting.
[6/25/2016 1:21:21 PM] [STATS] epg123 update execution time was 00:01:08.7649208.
Once I noticed all machines were doing the same thing (obvious SD problem of some sort) I successfully executed the import and automatch using Thursdays epg123.mxf via Whole Home Configuration switches. But I was thinking someone doing a new setup with no completed epg123.mxf to fall back on might be frustrated at that point. After I logged on here and saw problem channel and dates identified I was able to complete a single day update on all machines to freshen listings (including WBGODT2) in the nick of time before last night. As noted all is apparently back to normal today.
BTW my clean install of Colossus with OTA using this new fix went without any (other) hitch and is working as expected so far.
That might be a good idea (probably for everyone) if it's reasonably possible without breaking something else. I too was attempting (another) clean install yesterday with 1.0.0 Colossus beta and ran into the same issue:garyan2 wrote:...I just wish there was a way I could populate this information in the error log and make it easier to identify and report. I'm working on it. I am also thinking about continuing the build without that days schedule. Worst case with this scenario is there will be a time period in the channels guide data that is not up-to-date.
[6/25/2016 1:20:14 PM] Entering getAllScheduleEntryMd5s() for 25 days on 260 stations.
[6/25/2016 1:20:19 PM] [ INFO] Successfully retrieved Md5s for 260 station's daily schedules.
[6/25/2016 1:20:38 PM] [ INFO] Successfully retrieved 260 station's daily schedules.
[6/25/2016 1:21:10 PM] [WARNG] Time discontinuity detected. Service 58623 (SYFYHD) SH024584520000 (entry 50) ends at 2016-06-28 08:30:00Z, SH024584520000 (entry 51) starts at 2016-06-28 08:00:00Z.
[6/25/2016 1:21:10 PM] No further discontinuities on SYFYHD will be reported for 2016-06-28.
[6/25/2016 1:21:11 PM] [WARNG] Time discontinuity detected. Service 58623 (SYFYHD) SH024229070000 (entry 197) ends at 2016-07-05 08:30:00Z, SH024229070000 (entry 198) starts at 2016-07-05 08:00:00Z.
[6/25/2016 1:21:11 PM] No further discontinuities on SYFYHD will be reported for 2016-07-05.
[6/25/2016 1:21:12 PM] [WARNG] Time discontinuity detected. Service 28506 (AXSTV) EP009555540429 (entry 2) ends at 2016-06-25 05:30:00Z, EP010092340447 (entry 3) starts at 2016-06-25 06:30:00Z.
[6/25/2016 1:21:12 PM] No further discontinuities on AXSTV will be reported for 2016-06-25.
[6/25/2016 1:21:18 PM] [WARNG] Time discontinuity detected. Service 68049 (UNIHD) SH013814960000 (entry 54) ends at 2016-06-26 18:00:00Z, SH003072200000 (entry 55) starts at 2016-06-26 19:00:00Z.
[6/25/2016 1:21:18 PM] No further discontinuities on UNIHD will be reported for 2016-06-26.
[6/25/2016 1:21:18 PM] [WARNG] Time discontinuity detected. Service 68049 (UNIHD) SH024349710000 (entry 61) ends at 2016-06-27 03:00:00Z, SH003072200000 (entry 62) starts at 2016-06-27 04:00:00Z.
[6/25/2016 1:21:18 PM] No further discontinuities on UNIHD will be reported for 2016-06-27.
[6/25/2016 1:21:19 PM] [WARNG] Time discontinuity detected. Service 12553 (NASA) SH023078220000 (entry 94) ends at 2016-06-27 19:30:00Z, SH001329680000 (entry 95) starts at 2016-06-27 20:00:00Z.
[6/25/2016 1:21:19 PM] No further discontinuities on NASA will be reported for 2016-06-27.
[6/25/2016 1:21:21 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[6/25/2016 1:21:21 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[6/25/2016 1:21:21 PM] Failed to create MXF file. Exiting.
[6/25/2016 1:21:21 PM] [STATS] epg123 update execution time was 00:01:08.7649208.
Once I noticed all machines were doing the same thing (obvious SD problem of some sort) I successfully executed the import and automatch using Thursdays epg123.mxf via Whole Home Configuration switches. But I was thinking someone doing a new setup with no completed epg123.mxf to fall back on might be frustrated at that point. After I logged on here and saw problem channel and dates identified I was able to complete a single day update on all machines to freshen listings (including WBGODT2) in the nick of time before last night. As noted all is apparently back to normal today.
BTW my clean install of Colossus with OTA using this new fix went without any (other) hitch and is working as expected so far.
-
- Posts: 65
- Joined: Sun Jul 26, 2015 11:41 pm
- Location:
- HTPC Specs:
Suggestion:
Instead of naming Colossus channels C1...C9999, name them Z1...Z9999. That way when editing guide channels you can "Sort by Name" causing all the unused channels to be last so you do not have to page through the whole 9999+ channels to select the active channels you want in your guide.
Jim
Instead of naming Colossus channels C1...C9999, name them Z1...Z9999. That way when editing guide channels you can "Sort by Name" causing all the unused channels to be last so you do not have to page through the whole 9999+ channels to select the active channels you want in your guide.
Jim
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Excellent idea. Consider it done.fzy8gc wrote:Suggestion:
Instead of naming Colossus channels C1...C9999, name them Z1...Z9999. That way when editing guide channels you can "Sort by Name" causing all the unused channels to be last so you do not have to page through the whole 9999+ channels to select the active channels you want in your guide.
Jim
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Just sent out a new beta to KenL and fzy8gc ... makes setting up a HDPVR/Colossus very easy. Anyone else want to take it for a test run?
If you are curious, you can look at the updated guide here -> http://epg123.garyan2.net/downloads/epg ... 160627.pdf
If you are curious, you can look at the updated guide here -> http://epg123.garyan2.net/downloads/epg ... 160627.pdf
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 60
- Joined: Thu Mar 03, 2016 3:35 pm
- Location:
- HTPC Specs:
Beta 2 looks great.
Makes more sense now, hit the elevated Colossus button between "Step 1 Clean Start" and "Step 2 Windows Media Center TV Setup" so then setup proceeds like normal and it's obvious when the scan finds 10,000+ channels. Well perhaps not obvious... it kind of sputters along but let it fully finish before going on to "Step 3" for the download and automatch. Simple and straightforward.
The "z" channels also look and work great. They now drop below all occupied channels when sorting by name so the channel editor is much more usable.
I think we're close to 1.0 now. This Colossus fix is amazing.
Makes more sense now, hit the elevated Colossus button between "Step 1 Clean Start" and "Step 2 Windows Media Center TV Setup" so then setup proceeds like normal and it's obvious when the scan finds 10,000+ channels. Well perhaps not obvious... it kind of sputters along but let it fully finish before going on to "Step 3" for the download and automatch. Simple and straightforward.
The "z" channels also look and work great. They now drop below all occupied channels when sorting by name so the channel editor is much more usable.
I think we're close to 1.0 now. This Colossus fix is amazing.
-
- Posts: 193
- Joined: Thu May 28, 2015 1:24 am
- Location:
- HTPC Specs:
Shoutout to garyan2 for taking time out of his busy life to help Colossus users, and everyone else for that matter. He's done far more than Microsoft ever did.