Guide failure to update after a few months of flawless performance

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 ★
Locked
Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#21

Post by Space » Sun Mar 22, 2020 3:34 am

Oh, what happened to the guideImages.xml?
Top
User avatar
garyan2

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

HTPC Specs: Show details

#22

Post by garyan2 » Sun Mar 22, 2020 3:52 am

The image links are now stored in the cache file as well along with the appropriate program (for movies) or series.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Top
Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#23

Post by Space » Sun Mar 22, 2020 12:36 pm

Oh, nice. I wondered why the guideImages.xml was not in the cache folder.

So you made the cache file smaller even though you added the contents of the guideImages.xml to it? That is some pretty good magic there. :clap:

One other related thing I am seeing...

I've been directly editing the task that runs EPG123 to change the start time. I've done this twice now. Each time I did it, for some reason the task got run TWICE the next day.

The first time it happened, I assumed it was something to do with not changing the date in the start time to the next days date. But the latest time I did it, I made sure to change the date and the time to the next days date, yet it still ran twice.

The first time, it seemed to run about 5 minutes after I had manually woken up the PC, even though it wasn't scheduled for hours later (at which time it ran a second time).

This latest time, I saw the task wake up the PC, run to completion (with an error regarding CSPAN having overlapping times), then about 5 minutes later it ran again.

I assume this won't happen again today, but I will keep an eye on it.

I haven't had much time to investigate why this happened but I was wondering if you had any ideas off the top of you head.
Top
User avatar
garyan2

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

HTPC Specs: Show details

#24

Post by garyan2 » Sun Mar 22, 2020 3:03 pm

Not a clue.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Top
User avatar
StinkyImp

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

HTPC Specs: Show details

#25

Post by StinkyImp » Sun Mar 22, 2020 4:24 pm

adam1991 wrote: ↑Thu Mar 19, 2020 4:19 am As always, update at your own risk.
Last year we had a discussion about whether updating was a wise idea. A few replies later I found that "My "gut feeling" is that it was a coincidence that I upgraded EPG123 and everything went POOF!"

Ever since then I have made it a point to update to the most recent version and have not had a single issue.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/22/2020 at 09:05:28
================================================================
[9/30/2019 12:15:29 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/1/2019 5:37:26 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/1/2019 5:40:33 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/2/2019 12:15:57 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/3/2019 12:18:47 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/4/2019 12:19:01 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/5/2019 12:19:50 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/6/2019 12:15:39 AM]  Beginning epg123 client execution. version 1.2.18.0
[10/7/2019 12:18:48 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/8/2019 12:15:26 AM]  Beginning epg123 client execution. version 1.2.18.10
[10/9/2019 12:19:06 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/10/2019 12:15:29 AM]  Beginning epg123 client execution. version 1.2.18.10
[10/11/2019 12:19:20 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/12/2019 12:18:18 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/13/2019 12:18:33 AM]  Beginning epg123 client execution. version 1.2.7.0
[10/14/2019 12:17:03 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/15/2019 12:18:20 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/16/2019 12:18:05 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/17/2019 12:18:04 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/18/2019 12:15:56 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/19/2019 12:18:08 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/20/2019 12:19:27 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/21/2019 12:23:22 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/22/2019 12:18:43 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/23/2019 12:18:48 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/24/2019 12:18:49 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/25/2019 12:19:10 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/26/2019 12:18:39 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/27/2019 12:17:14 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/28/2019 12:18:26 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/29/2019 12:18:37 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/30/2019 12:19:29 AM]  Beginning epg123 client execution. version 1.2.19.0
[10/31/2019 12:18:36 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/1/2019 12:18:59 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/2/2019 12:19:39 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/3/2019 12:19:00 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/4/2019 12:18:29 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/5/2019 12:18:39 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/6/2019 12:18:38 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/7/2019 12:19:13 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/8/2019 12:19:18 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/9/2019 12:19:05 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/10/2019 12:20:10 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/11/2019 12:19:00 AM]  Beginning epg123 client execution. version 1.2.19.0
[11/12/2019 12:18:48 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/13/2019 7:46:20 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/14/2019 12:18:15 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/15/2019 12:18:55 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/16/2019 12:20:10 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/17/2019 12:18:46 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/18/2019 12:19:34 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/19/2019 12:18:57 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/20/2019 12:19:09 AM]  Beginning epg123 client execution. version 1.2.22.0
[11/21/2019 12:19:12 AM]  Beginning epg123 client execution. version 1.2.23.0
[11/22/2019 12:19:03 AM]  Beginning epg123 client execution. version 1.2.23.0
[11/23/2019 12:19:09 AM]  Beginning epg123 client execution. version 1.2.23.0
[11/24/2019 12:20:13 AM]  Beginning epg123 client execution. version 1.2.23.0
[11/25/2019 12:19:31 AM]  Beginning epg123 client execution. version 1.2.23.0
[11/26/2019 12:15:49 AM]  Beginning epg123 client execution. version 1.2.23.0
[11/27/2019 12:18:46 AM]  Beginning epg123 client execution. version 1.3.0.0
[11/28/2019 12:18:53 AM]  Beginning epg123 client execution. version 1.3.0.0
[11/29/2019 12:19:07 AM]  Beginning epg123 client execution. version 1.3.0.0
[11/30/2019 12:19:01 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/1/2019 12:19:07 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/2/2019 12:19:10 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/3/2019 12:19:09 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/4/2019 12:19:16 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/5/2019 12:19:03 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/6/2019 12:15:33 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/7/2019 12:19:29 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/8/2019 12:19:10 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/9/2019 12:18:44 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/10/2019 12:19:02 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/11/2019 12:19:21 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/12/2019 12:19:15 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/13/2019 8:51:07 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/14/2019 12:19:05 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/15/2019 12:19:03 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/16/2019 12:18:59 AM]  Beginning epg123 client execution. version 1.3.0.0
[12/17/2019 12:19:00 AM]  Beginning epg123 client execution. version 1.3.1.10
[12/18/2019 12:19:05 AM]  Beginning epg123 client execution. version 1.3.1.10
[12/19/2019 12:19:01 AM]  Beginning epg123 client execution. version 1.3.1.20
[12/20/2019 10:15:20 AM]  Beginning epg123 client execution. version 1.3.1.30
[12/21/2019 12:18:47 AM]  Beginning epg123 client execution. version 1.3.2.0
[12/22/2019 12:18:59 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/23/2019 12:18:46 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/24/2019 12:18:50 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/25/2019 12:19:16 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/26/2019 12:18:49 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/27/2019 12:18:49 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/28/2019 12:18:47 AM]  Beginning epg123 client execution. version 1.3.2.10
[12/29/2019 12:18:35 AM]  Beginning epg123 client execution. version 1.3.3.20
[12/30/2019 12:18:52 AM]  Beginning epg123 client execution. version 1.3.3.20
[12/31/2019 12:18:49 AM]  Beginning epg123 client execution. version 1.3.3.20
[1/1/2020 12:18:46 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/2/2020 12:18:37 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/3/2020 12:18:35 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/4/2020 12:19:05 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/5/2020 12:18:47 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/6/2020 12:18:48 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/7/2020 12:18:37 AM]  Beginning epg123 client execution. version 1.3.4.0
[1/8/2020 12:18:42 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/9/2020 12:18:39 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/10/2020 12:18:39 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/11/2020 12:18:37 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/12/2020 12:18:40 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/13/2020 12:18:43 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/14/2020 12:18:47 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/15/2020 12:18:42 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/16/2020 12:18:28 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/17/2020 12:18:42 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/18/2020 12:18:46 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/19/2020 12:19:01 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/20/2020 12:18:56 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/21/2020 12:18:54 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/22/2020 12:18:57 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/23/2020 12:18:46 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/24/2020 12:18:52 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/25/2020 12:18:48 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/26/2020 12:15:33 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/27/2020 12:18:07 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/28/2020 12:18:25 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/29/2020 12:18:22 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/30/2020 12:18:24 AM]  Beginning epg123 client execution. version 1.3.5.0
[1/31/2020 12:18:19 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/1/2020 12:18:25 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/2/2020 12:18:42 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/3/2020 12:18:28 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/4/2020 12:18:29 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/5/2020 12:18:40 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/6/2020 12:18:23 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/7/2020 12:18:34 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/8/2020 12:18:45 AM]  Beginning epg123 client execution. version 1.3.5.0
[2/9/2020 12:18:38 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/10/2020 12:18:38 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/11/2020 12:18:39 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/12/2020 12:18:58 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/13/2020 12:18:57 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/14/2020 12:19:26 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/15/2020 12:18:53 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/16/2020 12:19:06 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/17/2020 12:19:01 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/18/2020 12:19:07 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/19/2020 12:19:08 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/20/2020 12:19:04 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/21/2020 12:19:14 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/22/2020 12:19:05 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/23/2020 12:19:15 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/24/2020 12:18:47 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/25/2020 12:18:48 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/26/2020 12:19:15 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/27/2020 12:19:00 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/28/2020 12:19:05 AM]  Beginning epg123 client execution. version 1.3.5.30
[2/29/2020 12:19:08 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/1/2020 12:19:22 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/2/2020 12:19:09 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/3/2020 12:19:15 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/4/2020 12:18:59 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/5/2020 12:18:47 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/6/2020 12:19:09 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/7/2020 12:19:29 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/8/2020 12:19:26 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/9/2020 12:19:16 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/10/2020 12:19:22 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/11/2020 12:19:21 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/12/2020 12:15:32 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/13/2020 12:21:15 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/14/2020 12:19:19 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/15/2020 12:19:36 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/16/2020 12:19:07 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/17/2020 12:19:01 AM]  Beginning epg123 client execution. version 1.3.5.30
[3/18/2020 12:19:11 AM]  Beginning epg123 client execution. version 1.3.6.0
[3/19/2020 12:15:33 AM]  Beginning epg123 client execution. version 1.3.6.0
[3/20/2020 12:15:34 AM]  Beginning epg123 client execution. version 1.3.6.0
[3/21/2020 12:15:37 AM]  Beginning epg123 client execution. version 1.3.6.10
[3/22/2020 12:15:28 AM]  Beginning epg123 client execution. version 1.3.6.10

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log and trace_2019.log
Search String:		t execution. version
Date Range:		09/30/2019 thru 03/22/2020 (175 days)
Total results found:	176
Query time:		24 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2019 thru 3/22/2020 (447 days)
Total lines processed:	37568
I noticed this morning that Gary uploaded v 1.3.6.20 and I immediately installed it without hesitation. I have every confidence that I'll wake up tomorrow morning with no issues. If I do, then I know I can report any EPG123 related bugs to Gary and he'll work to make his (already awesome) program better.

So in conclusion... Update at your own risk with extreme confidence! :D
Top
adam1991

Posts: 2893
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#26

Post by adam1991 » Sun Mar 22, 2020 4:53 pm

Awhile back, after holding back for awhile, I upgraded--and picked the worst time possible to do so. I upgraded to a version that Gary had just released, and one that was quickly found to have some serious issues.

I ran into those issues immediately. Fortunately, I had kept the installer for the version I had just replaced. I deleted the new version and re-installed my prior version, which just worked--and is working to this day.

EPG123 is one of the simplest things you can imagine. I agree with that. It gets the guide data, and presents it to WMC. Tell me: if you have a setup that is doing exactly that, what benefit does updating bring? Does it *better* do the job of getting guide data? It presents the data to WMC; is the result a *better* view of the guide in WMC?

Update at your own risk, unless what really makes you happy is the act updating and accepting the risk of having things not work and then spending time helping chase it all down so Gary can fix it.

And don't think I'm beating up on Gary here. Update at your own risk is true for ANY software. If it's doing what you need it to do, why? If it's not, then update it to where it does do what you need.
Top
User avatar
garyan2

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

HTPC Specs: Show details

#27

Post by garyan2 » Sun Mar 22, 2020 5:25 pm

You flatter me, @adam1991 to say EPG123 is one of the simplest things you can image. I whole-heartedly believe that the best software packages out there are the ones that make the typical user think so, so Thank You.

The statistics below show that it is not quite that simple.
epg123Stats.PNG
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Top
adam1991

Posts: 2893
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#28

Post by adam1991 » Sun Mar 22, 2020 6:13 pm

Oh, I understand that it was a blue ton of work for you. And it took a little while before it worked very well. But I meant that sincerely--from an end user perspective, it does two simple things, and for a long time now it has done them very, very well. And once running, It Just Works. (Consider: how many complaints have I seen about "IT JUST STOPPED! HELP!" were resolved a few minutes later with "oh, sorry, my Schedules Direct sub expired, it's OK now" ?)

The problems I've seen here on TGB seem to have come primarily from people who won't or can't read instructions, who seem to think they must know what's happening despite that, then come running for help once everything's borked up. (I'm sure some of the problems have been very real edge cases that you couldn't have predicted, but at this point, those surely have wound down to a very tiny number.)
Top
Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#29

Post by Space » Sun Mar 22, 2020 10:26 pm

I ran the new v1.3.6.20 version and the cache file increased in size from 160,391 to 164,950.

Not sure if this is an issue if it just means there is more program data that offset the savings. It did download all the series image links again due to it not using the guideImages.xml anymore (I suppose).

I don't remember how big the old guideImages.xml was, so it may be that mine was bigger than usual and resulted in an overall increase in size.
Top
User avatar
garyan2

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

HTPC Specs: Show details

#30

Post by garyan2 » Sun Mar 22, 2020 10:34 pm

The file size will start going down each day as the current programs in your cache, with the unnecessary information, are no longer needed. I didn't program a way to remove that info from existing cache entries... only for newly added entries.

The first time .20 is run, it will get all the series images again and cache them. The guideImages.xml file only contained 1 image for the series, but now it will get 1 image for every aspect ratio available which is typically 4. The multiple images will be used for the XMLTV file. Also, if you change your configuration to use 2x3 for series images, it won't have to contact SD again to do so.

The movie poster art from the guideImages.xml file were transferred to the cache file directly.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Top
Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#31

Post by Space » Mon Mar 23, 2020 2:29 am

Interesting.

I'm really loving this 5-minute update/import time. Just updated a bunch of the station logos and I was able to load them all in 5 minutes instead of having to wait over 30 minutes like I used to.
Top
User avatar
StinkyImp

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

HTPC Specs: Show details

#32

Post by StinkyImp » Mon Mar 23, 2020 3:47 pm

In the past seven days I've used four different versions of EPG123. Last night I allowed version 1.3.6.20 to run automagically as scheduled.

Four different (updated) versions used in the past 7 days:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 08:26:20
================================================================
     1 [3/17/2020 12:19:01 AM]  Beginning epg123 client execution. version 1.3.5.30
     2 [3/18/2020 12:19:11 AM]  Beginning epg123 client execution. version 1.3.6.0
     3 [3/19/2020 12:15:33 AM]  Beginning epg123 client execution. version 1.3.6.0
     4 [3/20/2020 12:15:34 AM]  Beginning epg123 client execution. version 1.3.6.0
     5 [3/21/2020 12:15:37 AM]  Beginning epg123 client execution. version 1.3.6.10
     6 [3/22/2020 12:15:28 AM]  Beginning epg123 client execution. version 1.3.6.10
     7 [3/23/2020 12:15:24 AM]  Beginning epg123 client execution. version 1.3.6.20

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		t execution. version
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	7
Query time:		04 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
Errors in the past 7 days:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 08:25:44
================================================================

          NO RESULTS FOUND

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		[ERROR]
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	None Found
Query time:		03 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
Warnings in the past 7 days:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 08:26:05
================================================================

          NO RESULTS FOUND

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		[WARNG]
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	None Found
Query time:		04 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
It's been "very rare" for an update to be released with an issue. Even so, Gary provides a fix in superhuman time...

In my opinion (in over three years of using EPG123) I don't think anyone should have any concerns about updating.
Top
Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#33

Post by Space » Mon Mar 23, 2020 5:01 pm

garyan2 wrote: ↑Sun Mar 22, 2020 10:34 pm ...
Also, if you change your configuration to use 2x3 for series images, it won't have to contact SD again to do so.
...
I have a question about this...

Let's say I just wanted to install new logos for some of my channels. I would have to use the "Save & Execute" button to do so, correct?

What if SD happens to be down during this time? Will I still be able to install my logos (ie: will it rely solely on the cached data) or will it fail to update due to SD being down?

I think it would be a good idea to de-couple this from the status of SD. It would be a bit frustrating to make changes (logos, or perhaps some other change such as changing to 2x3 series images) and not be able to put it in to effect just because SD was down. If changing EPG123 to use 2x3 series images requires you to "Save & Execute" and that (I think) requires SD to be up to complete successfully, then your statement above is not really correct.

This all assumes that if SD is down, you cannot enable these features. I believe this is true because the last time SD was "down for maintenance" I don't think I could even run the EPG123 tool (it would not allow me to do anything due to not getting a token from SD).
Top
stuartm

Posts: 723
Joined: Mon Nov 05, 2012 8:05 pm
Location: Longmont, CO

HTPC Specs: Show details

#34

Post by stuartm » Mon Mar 23, 2020 7:05 pm

Space wrote: ↑Sun Mar 15, 2020 10:25 pm
But now, after a month, each daily update takes in excess of 30 minutes.

I''m not sure why it is now taking more than double the time to complete. I am running it at about the same time of day as I ran it initially.
Wow, you must be running on a floppy disk to get such slow times :D
As a datapoint. my nightly update stats on a couple of year old flash drive running a fairly down-level version of EPG123:

2:32:22 AM - Processed 9216 daily schedules for 576 stations.

[3/23/2020 2:33:14 AM] [ INFO] epg123 update execution time was 00:01:14.1582416.

[3/23/2020 2:35:39 AM] [ INFO] EPG123 client execution time was 00:02:25.4243178.

I would imagine with that slow a drive just bringing up the guide in WMC might be fairly slow.
I noticed quite an improvement in that when I migrated from a spinner to a flash drive for my system drive.
You might want to look into migrating to a SSD for your system disk as a general performance upgrade.
Top
User avatar
StinkyImp

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

HTPC Specs: Show details

#35

Post by StinkyImp » Mon Mar 23, 2020 8:02 pm

Wow!

Here are my execution times over the past 7 days using the various versions shown previously!

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 12:57:21
================================================================
[3/17/2020 12:19:01 AM] [ INFO] epg123 update execution time was 00:03:53.1553357.
[3/17/2020 2:04:34 AM] [ INFO] EPG123 client execution time was 01:45:33.1692365.
[3/18/2020 12:19:10 AM] [ INFO] epg123 update execution time was 00:04:02.5568734.
[3/18/2020 2:04:33 AM] [ INFO] EPG123 client execution time was 01:45:22.3686188.
[3/19/2020 12:15:33 AM] [ INFO] epg123 update execution time was 00:00:25.3204482.
[3/19/2020 2:04:51 AM] [ INFO] EPG123 client execution time was 01:49:17.7500818.
[3/20/2020 12:15:34 AM] [ INFO] epg123 update execution time was 00:00:26.3485070.
[3/20/2020 2:04:33 AM] [ INFO] EPG123 client execution time was 01:48:58.8680018.
[3/21/2020 12:15:37 AM] [ INFO] epg123 update execution time was 00:00:29.5896924.
[3/21/2020 12:16:13 AM] [ INFO] EPG123 client execution time was 00:00:35.7160428.
[3/22/2020 12:15:28 AM] [ INFO] epg123 update execution time was 00:00:20.1121504.
[3/22/2020 12:16:01 AM] [ INFO] EPG123 client execution time was 00:00:32.7948758.
[3/23/2020 12:15:24 AM] [ INFO] epg123 update execution time was 00:00:23.4993441.
[3/23/2020 12:16:06 AM] [ INFO] EPG123 client execution time was 00:00:42.3334214.

===== QUERY INFORMATION (Custom) ===============================
Logs used:		trace.log ONLY
Search String:		execution time was
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	14
Query time:		04 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
Top
Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#36

Post by Space » Mon Mar 23, 2020 8:15 pm

stuartm wrote: ↑Mon Mar 23, 2020 7:05 pm
Wow, you must be running on a floppy disk to get such slow times :D
...
I would imagine with that slow a drive just bringing up the guide in WMC might be fairly slow.
I noticed quite an improvement in that when I migrated from a spinner to a flash drive for my system drive.
You might want to look into migrating to a SSD for your system disk as a general performance upgrade.
I don't have any delays with bringing up the guide in WMC, it is relatively quick.

I'm not sure why it was so slow with the older version of EPG123, I'm pretty sure it is a 7200 RPM drive. I just think randomly seeking and reading in over 65k of tiny files may just be something most mechanical HDs are not very good at.

As for SSDs, I'm not a big fan yet. The only SSD I had was on my work laptop and it had a total failure where I lost everything.

I've had failures with mechanical hard drives, but they have always given a warning before failing (noises, performance anomalies, etc.) and I was able to get most if not all the data off of them before total failure.

Anyway, one day maybe I'll try it. SSDs are a bit too new to get a good idea of how reliable they are.

StinkyImp wrote: ↑Mon Mar 23, 2020 8:02 pm Wow!

Here are my execution times over the past 7 days using the various versions shown previously!
...
Hmmm, not sure why your client execution times went down so much, I don't think any change in EPG123 would have caused that...
Top
User avatar
garyan2

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

HTPC Specs: Show details

#37

Post by garyan2 » Mon Mar 23, 2020 9:01 pm

Looks like he had some recordings in progress. Those were 1h49m times for the import which includes delays.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Top
stuartm

Posts: 723
Joined: Mon Nov 05, 2012 8:05 pm
Location: Longmont, CO

HTPC Specs: Show details

#38

Post by stuartm » Mon Mar 23, 2020 9:28 pm

I'll respond WRT SSD's, My last 2 jobs were working for companies that were building all flash storage systems for commercial data centers and supercomputers. They had no worries about SSD reliability ;) That said, as with any important stored data, keep a relatively recent backup of your data and you should be safe. I switched to SSDs when Samsung offered a 10 year warranty on their 850 Pro line of drives And still every couple of months I clone the System drive off to a backup drive. SSD's are a relatively mature technology these days. (PS I will admit the storage arrays we built used fancy RAID strategies for data redundancy and typically had hot spare drives available which is one main reason they didn't worry about drive failures).
Top
User avatar
StinkyImp

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

HTPC Specs: Show details

#39

Post by StinkyImp » Mon Mar 23, 2020 10:27 pm

garyan2 wrote: ↑Mon Mar 23, 2020 9:01 pm Looks like he had some recordings in progress. Those were 1h49m times for the import which includes delays.
Yep!

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 15:25:55
================================================================
[3/17/2020 12:19:02 AM] [ INFO] Recording in progress: 12:00 AM - 01:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Skin Deep
[3/17/2020 1:04:00 AM] [ INFO] Recording in progress: 01:00 AM - 02:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Manifest Destiny
[3/18/2020 12:19:12 AM] [ INFO] Recording in progress: 12:00 AM - 01:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - The Beholder
[3/18/2020 1:04:00 AM] [ INFO] Recording in progress: 01:00 AM - 02:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Seeds of Destruction
[3/19/2020 12:15:34 AM] [ INFO] Recording in progress: 12:00 AM - 01:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Stasis
[3/19/2020 1:04:00 AM] [ INFO] Recording in progress: 01:00 AM - 02:00 AM on channel 8.1 KAETDT -> Nature - Yosemite
[3/19/2020 1:04:00 AM] [ INFO] Recording in progress: 01:00 AM - 02:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Down to Earth
[3/20/2020 12:15:35 AM] [ INFO] Recording in progress: 12:00 AM - 01:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Glitch
[3/20/2020 1:04:00 AM] [ INFO] Recording in progress: 01:00 AM - 02:00 AM on channel 3.2 KTVKDT2 -> The Outer Limits - Decompression

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		Recording in progress
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	9
Query time:		03 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
Top
adam1991

Posts: 2893
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#40

Post by adam1991 » Mon Mar 23, 2020 11:24 pm

StinkyImp wrote: ↑Mon Mar 23, 2020 3:47 pm In the past seven days I've used four different versions of EPG123. Last night I allowed version 1.3.6.20 to run automagically as scheduled.

Four different (updated) versions used in the past 7 days:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 08:26:20
================================================================
     1 [3/17/2020 12:19:01 AM]  Beginning epg123 client execution. version 1.3.5.30
     2 [3/18/2020 12:19:11 AM]  Beginning epg123 client execution. version 1.3.6.0
     3 [3/19/2020 12:15:33 AM]  Beginning epg123 client execution. version 1.3.6.0
     4 [3/20/2020 12:15:34 AM]  Beginning epg123 client execution. version 1.3.6.0
     5 [3/21/2020 12:15:37 AM]  Beginning epg123 client execution. version 1.3.6.10
     6 [3/22/2020 12:15:28 AM]  Beginning epg123 client execution. version 1.3.6.10
     7 [3/23/2020 12:15:24 AM]  Beginning epg123 client execution. version 1.3.6.20

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		t execution. version
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	7
Query time:		04 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
Errors in the past 7 days:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 08:25:44
================================================================

          NO RESULTS FOUND

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		[ERROR]
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	None Found
Query time:		03 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
Warnings in the past 7 days:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 03/23/2020 at 08:26:05
================================================================

          NO RESULTS FOUND

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		[WARNG]
Date Range:		03/17/2020 thru 03/23/2020 (7 days)
Total results found:	None Found
Query time:		04 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 3/23/2020 (83 days)
Total lines processed:	6733
It's been "very rare" for an update to be released with an issue. Even so, Gary provides a fix in superhuman time...

In my opinion (in over three years of using EPG123) I don't think anyone should have any concerns about updating.
Ah, anecdata.

No matter how many times you say "mine's never failed," a single "mine did" instance is all it takes to put some teeth behind "update at your own risk".
Top
Locked

Return to “EPG123”