www.makemkv.com

This is fixed ong ago by having a setting in a conversion profile. You can create "always LPCM" profile and specify "raw" WAV header for all LPCM data.

mike admin wrote:This is fixed ong ago by having a setting in a conversion profile. You can create "always LPCM" profile and specify "raw" WAV header for all LPCM data.

Hi Mike.

Thanks for this info. I hadn't read about conversion profiles before so this is exciting to know there are some extra settings we can control when creating MKVs.

When I checked the default conversion profile XML file (default.mmcp.xml), these are the relevant settings for LPCM:

-<outputSettings outputFormat="LPCM-raw" name="lpcm">
<description lang="eng">Save as raw LPCM</description>
<description lang="ger">Als RAW LPCM speichern</description>
</outputSettings>

-<outputSettings outputFormat="LPCM-wavex" name="wavex">
<description lang="eng">Save as LPCM in WAV container</description>
<description lang="ger">Als LPCM im WAV-Container speichern</description>
</outputSettings>

<!-- Save LPCM mono or stereo as raw LPCM -->
-<trackSettings input="LPCM-stereo">
<output defaultSelection="$app_DefaultSelectionString" outputSettingsName="lpcm"> </output>
</trackSettings>

<!-- Put multi-channel LPCM into WAVEX container-->
-<trackSettings input="LPCM-multi">
<output defaultSelection="$app_DefaultSelectionString" outputSettingsName="wavex"> </output>
</trackSettings>

Based on this XML and your post, it looks like it would only be a matter of changing the setting outputSettingsName="wavex" to outputSettingsName="lpcm" in that last TrackSettings XML branch (bolded part above).

Since mono or stereo LPCM are already configured this way, and confirmed to work, is there a reason multi-channel LPCM is defaulting to "wavex" in these profiles?

cipher wrote:Based on this XML and your post, it looks like it would only be a matter of changing the setting outputSettingsName="wavex" to outputSettingsName="lpcm" in that last TrackSettings XML branch (bolded part above).

Yes, this is correct. Make sure to rename the profile from "default" as MakeMKV will discard profiles with duplicate names.

cipher wrote:Since mono or stereo LPCM are already configured this way, and confirmed to work, is there a reason multi-channel LPCM is defaulting to "wavex" in these profiles?

Because there is no way to put channel mask (what channels are present and in what order) into LPCM container. A 4-channel audio may be 3.1(L+C+R+LFE) or 2/2 (L+R+BL+BR). If you are willing to assume that every 6-channel audio is 5.1 then there is no need for wavex header. This is the only reason.