WMC crashes on attempting new recording

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

#41

Post by garyan2 » Thu Mar 15, 2018 2:41 pm

This looks to me to be a corrupted database and using the [Rebuild WMC Database] button in the client should fix it for you.

Two things:
1) The errors you see in the log right after the " Entering importMxfFile()..." line are generated by the loadmxf.exe utility which is part of WMC. At this point, the only way epg123 could cause a failure is if there are structural errors in the MXF file which would be identified in the error text. This is not the case and is actually database errors.

2) By default, epg123 will not perform the import while there is an active recording. This was instituted quite a few versions ago. Could you provide more of your trace log to show updates during a recording?

When epg123 goes to import the MXF file into the database using loadmxf.exe, it checks for active recordings. If there are recordings active, it will query the scheduled end times of the recordings and wait until after they are complete to try again. If there are more/different active recordings at that point it will repeat and keep waiting for up to 5 hours before aborting completely. Because of this logic, I don't think the initial database corruption could have been due to an import during a recording. That's not to say a bad import did not cause the corruption in the first place, just that it wasn't during a recording.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Space

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

HTPC Specs: Show details

#42

Post by Space » Thu Mar 15, 2018 10:33 pm

This might be a bit off topic, but...

I've done many manual updates to the guide (using WMCs default guide provider) while recordings were in progress and have never had any issue (unless that update included updates to one of the episodes that were in the process of being recorded, in which case the recording of that particular episode would stop.)

It's strange that using loadmxf with an external mxf file would cause problems, when the normal update (which I believe also uses loadmxf) does not.

Have you ever been able to decrypt the mxf that comes from Microsoft to see how it may differ from the one you generate? Perhaps it is doing something differently that allows it to be imported without affecting recordings.

Post Reply