Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 786358" data-attributes="member: 82144">You're exactly correct. I had to upgrade my installation from a pre-1.2.0rc state to test the patch, and it clean slipped my mind that we've upgraded the version number in the last day or so. Try the attached one... :sorry:Note: the previous one may still be useful if you decide to upgrade to 1.2.0 final when it is released (hopefully within the next 5 days).Yes. We plan a follow up release to 1.2.0 in roughly two weeks time, but it may take a bit longer than that. I'd hope that we can get the fix in there.I don't think you're too far off track. What is failing is MP is assuming that your system registry is reliable, correct, and complete - usually a safe assumption, but obviously not always true. If you're experiencing the same problem that I was able to reproduce then it is caused by attempting to add codecs with no names to the lists of codecs that you can choose from in the &quot;codecs and renderer&quot; section of MP configuration. At this point I'm not entirely sure how you end up having codecs with no names registered in your system, but the last thing we want is people's first impression of MP to be that it crashes at the drop of a hat. Regardless of whether it is a code problem on our side or a registry problem on their side, we want our software to be robust and reliable. Yes, you should fix this (use <a href="http://paul.glagla.free.fr/filmerit_en.htm" target="_blank">filmerit</a> as hoborg suggested) because you won't be able to use those codecs without repairing the registry, but we should also handle this too.Let me know how you get on with the attached exe...mm</blockquote>

[QUOTE="mm1352000, post: 786358, member: 82144"] You're exactly correct. I had to upgrade my installation from a pre-1.2.0rc state to test the patch, and it clean slipped my mind that we've upgraded the version number in the last day or so. Try the attached one... :sorry: Note: the previous one may still be useful if you decide to upgrade to 1.2.0 final when it is released (hopefully within the next 5 days). Yes. We plan a follow up release to 1.2.0 in roughly two weeks time, but it may take a bit longer than that. I'd hope that we can get the fix in there. I don't think you're too far off track. What is failing is MP is assuming that your system registry is reliable, correct, and complete - usually a safe assumption, but obviously not always true. If you're experiencing the same problem that I was able to reproduce then it is caused by attempting to add codecs with no names to the lists of codecs that you can choose from in the "codecs and renderer" section of MP configuration. At this point I'm not entirely sure how you end up having codecs with no names registered in your system, but the last thing we want is people's first impression of MP to be that it crashes at the drop of a hat. Regardless of whether it is a code problem on our side or a registry problem on their side, we want our software to be robust and reliable. Yes, you should fix this (use [URL="http://paul.glagla.free.fr/filmerit_en.htm"]filmerit[/URL] as hoborg suggested) because you won't be able to use those codecs without repairing the registry, but we should also handle this too. Let me know how you get on with the attached exe... mm [/QUOTE]

Verification