Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1215284" data-attributes="member: 82144">MP Config selects the LAV codecs as defaults the first time you view the settings... and that's why you saw what you saw. Prior to that, MP itself was not using the LAV codecs. Many people get confused by this.Let me put it another way: if MP had been using the LAV codecs, why would there be log entries mentioning &quot;MONOGRAM AAC Decoder&quot; and &quot;Microsoft DTV-DVD Audio Decoder&quot;? Answer is, there wouldn't be.I know it's confusing. If you're confused, you may just have to trust me.It's crashing because the update added, removed or changed codecs or codec dependencies that MP is or was trying as part of the auto-loading process that I mentioned.Changes outside MP - including Windows updates, driver updates, other software being installed or removed, and other things too - can affect MP. I've seen this sort of thing time and time again. MP get's the blame and bad press... but it's not our fault.</blockquote>

[QUOTE="mm1352000, post: 1215284, member: 82144"] MP Config selects the LAV codecs as defaults the first time you view the settings... and that's why you saw what you saw. Prior to that, MP itself was not using the LAV codecs. Many people get confused by this. Let me put it another way: if MP had been using the LAV codecs, why would there be log entries mentioning "MONOGRAM AAC Decoder" and "Microsoft DTV-DVD Audio Decoder"? Answer is, there wouldn't be. I know it's confusing. If you're confused, you may just have to trust me. It's crashing because the update added, removed or changed codecs or codec dependencies that MP is or was trying as part of the auto-loading process that I mentioned. Changes outside MP - including Windows updates, driver updates, other software being installed or removed, and other things too - can affect MP. I've seen this sort of thing time and time again. MP get's the blame and bad press... but it's not our fault. [/QUOTE]

Verification