v1.1.16 Release

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

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

HTPC Specs: Show details

v1.1.16 Release

#1

Post by garyan2 » Sat Sep 16, 2017 11:36 pm

Details to follow; available on the website. http://epg123.garyan2.net
v1.1.16release.PNG
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#2

Post by Sancho » Sun Sep 17, 2017 2:33 am

Installed it (Win 7), ran the config app, didn't change anything, ran Save & Execute.... finished in under a minute, per trace.log, but the Client Execution section never appeared in the log. There were a ton of Time Discontinuities listed in the "Update" section, but never got to the client execution. The last lines written were:

Code: Select all

[9/16/2017 10:13:12 PM] [WARNG] Time discontinuity detected. Service 49141 (MTVLIVE) SH012857740000 (entry 239) ends at 2017-09-28 15:00:00Z, SH016981260000 (entry 240) starts at 2017-09-28 11:00:00Z.
[9/16/2017 10:13:12 PM]         No further discontinuities on MTVLIVE will be reported for 2017-09-28.
[9/16/2017 10:13:13 PM] [ INFO] Processed 10174 daily schedules for 519 stations.
[9/16/2017 10:13:13 PM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[9/16/2017 10:13:13 PM] Entering buildAllProgramEntries() for 47520 programs.
[9/16/2017 10:13:13 PM] [ INFO] epg123 update execution time was 00:00:53.5704941.
[9/16/2017 10:20:16 PM]
(last line is running 1.1.15 after reinstalling)

Reverted to 1.1.15, went through the same steps, still had some Time Discontinuities, but the Client Execution section was written to the log, and everything looked normal.

User avatar
garyan2

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

HTPC Specs: Show details

#3

Post by garyan2 » Sun Sep 17, 2017 3:35 am

It's actually the initial epg123 update execution that is bombing out and not the client. I'm testing out a theory right now, but in the mean time, what is your lineup?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Sun Sep 17, 2017 4:04 am

Confirmed the defect. I didn't test upgrading from 1.1.15 to 1.1.16. With the addition of the season and episode numbers from TheTVDB.com, the structure of the files I had cached using v1.1.15 are not the same as what SD is actually providing and v1.1.16 is saving/caching.

Basically, I had code present in v1.1.15 in anticipation of this new feature, but the final structure of the response from SD was not the same. Version 1.1.15 was saving them in the wrong format.

EDIT: To make it work, clear the cache and rebuild... (this will also add the TVDB S/E numbers which won't happen with programs that are already cached). Or, you can wait a few hours while I release 1.1.17.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#5

Post by Sancho » Sun Sep 17, 2017 4:29 am

I'll wait. A bit late on a Sat. night at this point ;-)

If you still need to know, Comcast Digital for zip code 22508. Ceton InfiniTV 4, if that helps.

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Sun Sep 17, 2017 4:31 am

Sancho wrote:I'll wait. A bit late on a Sat. night at this point ;-)

If you still need to know, Comcast Digital for zip code 22508. Ceton InfiniTV 4, if that helps.
Nah, I'm good... thanks. Just released v1.1.17 with the fix.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#7

Post by Sancho » Sun Sep 17, 2017 2:40 pm

Looking at the Download page, I see this:

"The silver lining to this is realizing that if anyone wants to take advantage of the new feature immediately, then you must clear the cache and rebuild to actually use the new data."

Above, you implied that 1.1.17 would fix the problem without having to clear the cache and rebuild. Is that true, or does 1.1.17 require clearing the cache and rebuilding (the database)? I'm interested in trying the new option for S/E numbers, just want to do it right the first time. So, when upgrading from 1.1.15, what are the proper steps? Install 1.1.17 first, then...? Or do the clear and rebuild, then upgrade?

Thanks!

User avatar
garyan2

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

HTPC Specs: Show details

#8

Post by garyan2 » Sun Sep 17, 2017 3:47 pm

If you do not want to use the season/episode numbers by tvdb, then v1.1.17 will work just fine with the cached files from v1.1.15 and below.

If you want to use the season/episode numbers by tvdb, but don't mind if they really don't take effect until your cached program files have expired/no long in guide, then v1.1.17 will work just fine with the cached files from v1.1.15 and below.

If you want to use the season/episode numbers by tvdb, and want all programs in the guide to show them immediately after update, then you will have to clear the cache and rebuild. The cached files from v1.1.15 do not have the tvdb numbers.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#9

Post by Sancho » Sun Sep 17, 2017 4:04 pm

Thanks for the quick reply, Gary. Had a feeling that was the deal. I installed 1.1.17, so I'll clear the cache and rebuild. Thanks for providing the one-click options for both tasks :-)

LOL, one last question. The "rebuild" in question is only of the cache, not the WMC database, correct? I don't want to go through the latter unnecessarily.

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Sun Sep 17, 2017 4:17 pm

Sancho wrote:Thanks for the quick reply, Gary. Had a feeling that was the deal. I installed 1.1.17, so I'll clear the cache and rebuild. Thanks for providing the one-click options for both tasks :-)

LOL, one last question. The "rebuild" in question is only of the cache, not the WMC database, correct? I don't want to go through the latter unnecessarily.
Right, just the cache. So the clearing of the cache will use the [Clear Cache] button, and the rebuild of the cache is simply the next update or using the [Save & Execute] button.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#11

Post by Sancho » Sun Sep 17, 2017 4:21 pm

garyan2 wrote:
Sancho wrote:Thanks for the quick reply, Gary. Had a feeling that was the deal. I installed 1.1.17, so I'll clear the cache and rebuild. Thanks for providing the one-click options for both tasks :-)

LOL, one last question. The "rebuild" in question is only of the cache, not the WMC database, correct? I don't want to go through the latter unnecessarily.
Right, just the cache. So the clearing of the cache will use the [Clear Cache] button, and the rebuild of the cache is simply the next update or using the [Save & Execute] button.
Thanks for confirming. That's pretty painless then. Also, thanks for implementing the atuo retry of MXF imports when recordings were initially in progress. That's a great feature.

Sammy2

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

HTPC Specs: Show details

#12

Post by Sammy2 » Sun Sep 17, 2017 7:24 pm

I'll wait a few days.. Everything is working fine over here as it is. What is the compelling reason for this update? TIA

AndyS

Posts: 30
Joined: Mon Aug 27, 2012 11:05 pm
Location:

HTPC Specs: Show details

#13

Post by AndyS » Sun Sep 17, 2017 7:54 pm

I'm coming from way back at the last major outage of MS's Guide, so back on 1.1.1.

What's the upgrade process on this? It it the same as the regular install? Not sure I'm clear in the instructions about not losing my tuner setups, etc. I do see some backups now run.

User avatar
garyan2

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

HTPC Specs: Show details

#14

Post by garyan2 » Sun Sep 17, 2017 8:57 pm

AndyS wrote:I'm coming from way back at the last major outage of MS's Guide, so back on 1.1.1.

What's the upgrade process on this? It it the same as the regular install? Not sure I'm clear in the instructions about not losing my tuner setups, etc. I do see some backups now run.
Just run the setup file. It will overwrite the old files with the new and you're good to go. No need to do anything with WMC.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

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

HTPC Specs: Show details

#15

Post by garyan2 » Sun Sep 17, 2017 9:04 pm

Sammy2 wrote:I'll wait a few days.. Everything is working fine over here as it is. What is the compelling reason for this update? TIA
You mean something other than the feature you and a few other have requested? viewtopic.php?f=99&t=11219&p=121916#p121896

The addition of using season and episode numbers by TVDB would be nice to have in place before the premieres start in earnest. Other than those 2, changes are more for stability and initial setup and maintenance. Personally, I like the language codes in the configuration GUI even if it's just to look at.
- 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

#16

Post by Sammy2 » Sun Sep 17, 2017 10:04 pm

garyan2 wrote:
Sammy2 wrote:I'll wait a few days.. Everything is working fine over here as it is. What is the compelling reason for this update? TIA
You mean something other than the feature you and a few other have requested? viewtopic.php?f=99&t=11219&p=121916#p121896

The addition of using season and episode numbers by TVDB would be nice to have in place before the premieres start in earnest. Other than those 2, changes are more for stability and initial setup and maintenance. Personally, I like the language codes in the configuration GUI even if it's just to look at.
I know this provides pretty good improvements but I need the time to do it an verify results. Thanks again Gary for this actively supported product. Much appreciated.

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#17

Post by Sancho » Mon Sep 18, 2017 8:13 pm

One good reason to upgrade is the delayed MXF import function. I tested it this morning, as I had something recording to just passed the update time. Sure enough, the import happened (on the second attempt in this case) five minutes after the first attempt. The log is wonderfully verbose, showing what's recording on what channel, and the beginning and ending scheduled recording time.

Sammy2

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

HTPC Specs: Show details

#18

Post by Sammy2 » Mon Sep 18, 2017 8:43 pm

Of course I jumped in but as the V1.1.16 release had a bug quickly fixed in v1.1.17 I like to let others be Guinea Pigs first!!

All seems well here but I haven't tested it while an active recording is going yet.

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#19

Post by Sancho » Mon Sep 18, 2017 9:21 pm

Sammy2 wrote:Of course I jumped in but as the V1.1.16 release had a bug quickly fixed in v1.1.17 I like to let others be Guinea Pigs first!!

All seems well here but I haven't tested it while an active recording is going yet.
I got yr back (see test results, above ;) )

I'm rarely an early adopter these days, but when I know the dev or company is reliable I can't seem to help myself.

Alan G

Posts: 89
Joined: Mon Feb 22, 2016 8:27 pm
Location: Bethesda, Maryland

HTPC Specs: Show details

#20

Post by Alan G » Tue Sep 19, 2017 5:19 pm

Sancho wrote:
Sammy2 wrote:Of course I jumped in but as the V1.1.16 release had a bug quickly fixed in v1.1.17 I like to let others be Guinea Pigs first!!

All seems well here but I haven't tested it while an active recording is going yet.
I got yr back (see test results, above ;) )

I'm rarely an early adopter these days, but when I know the dev or company is reliable I can't seem to help myself.
I agree with Sancho but v1.1.11 is working so well that I don't have the energy to do an upgrade!!! :D

Post Reply