1.8.2.8 Released

[garyan2]

All, I just released 1.8.2.8 in the beta section. All good changes, but the big thing is that I am only digitally signing the installer and uninstaller of the setup package. I just found out today that it costs $1 per file that I sign with my new certificate so I'm trying to limit the impact. Every release up until now has been with me signing all of my files (17 files plus the 2 setup files). So that was $19 per release and doesn't count any signing I did during testing that didn't make it to release.

So, I am hoping some will install this version and give me any feedback as far as problems with OS or antivirus issues with using unsigned executables.

[alhaunts]

Okay, I'll go first. 1.8.2.8 installed without incident.

OS: Windows 7 Professional, 64-bit [Version: 6.1.7601.24544]
Antivirus: Microsoft Security Essentials (with up to date definitions)

[pju4711]

Count me in - no problems at all. Neither on download/install or executing.
Just the small nag on install - "are you really sure you want to do this?". I have no problem with that at all.
But, I will admit - I would think twice if I were a new user. Still, from the epg123 web site and the content in this forum, I would be comfortable downloading.
So, just go ahead - spare the money
*** Windows 11 Pro, 64-bit [Version: 10.0.22635.2486] (23H2) ***
Windows Defender, latest upgrade.

I'm btw very happy with your aborting mxf import of too old data. Good enhancement!
Is it configurable? I have not found it, but that's for sure not the same as saying it isn't there

[garyan2]

Not configurable. Just a flat "if it is older than 24 hours, then abort" logic.

[Space]

Not configurable. Just a flat "if it is older than 24 hours, then abort" logic.

Does it still allow you to import an older MXF file manually?

My only concern with not automatically importing older files is the scenario where you are away and there is a spontaneous WMC DB rebuild (so all guide data is gone) and then you also have issues with creating a new MXF file for some reason (admittedly, probably a rare occurrence for both of these things to happen at the same time).

Is there any way it could check the WMC DB to see if it is "empty" and if so, import the MXF even if it is old? Or maybe if there is a reliable "last updated" timestamp you can read from the WMC DB (one that is only updated if the import on the date of that timestamp was successful), import the MXF file only if it is newer than this timestamp?

[garyan2]

The only way to manually import an old MXF file is to use the client GUI and the [Manual Import] button. So in your scenario, if you are away you won't be able to do that.

My initial inclination is to say no to doing anything about this unlikely corner case, but I may just be able to query when the MediaCenterRecoveryTask was last run (spontaneous WMC DB rebuild), and if within 24 hours then force an import. The problem there is I think the only time that task is run is when you open WMC and it detects a database error. Since you are "away", that won't happen.

EDIT: It is not MediaCenterRecoveryTask, but ObjectStoreRecoveryTask that I would check if implemented.

[Space]

How about if the MXF file is > 24 hours old but less than 1 week old (or perhaps 17 days, the max available from SD), then check in WMC "Settings -> TV -> Guide -> About guide listings" (assuming this value is available through the API) to see the date when the guide ends. I assume this date will either not be there or be invalid if the DB was rebuilt. If the date is not valid or not there, then import the MXF even though it is older.

[garyan2]

That "Guide End Date" is pulled from a registry value, not the database itself, and is the latest date for all services with assigned guide listings so can be multiple lineups and multiple sources. In other words, not a reliable source to make any determination of guide health. That value is not reset if a database recovery occurs.

[IT Troll]

Late to the release party, but installed OK without any warnings.
I noticed that the system tray was grey with an unknown status after installation. I guess this addresses the residual status issue we used to see after an update.

[garyan2]

Late to the release party, but installed OK without any warnings.
I noticed that the system tray was grey with an unknown status after installation. I guess this addresses the residual status issue we used to see after an update.

Yup. The installer clears the last status so it becomes "unknown".

Sent from my SM-G781U1 using Tapatalk