Editing WAVEFORMATEXTENSIBLE in the wav file header

[Travesty]

I want to define the channel format when importing 3 channel files into wwise, so it uses LCR instead of 2.1.

I found this on the website?

https://www.audiokinetic.com/en/libr..._are_supported

It says:

If you have a specific multichannel configuration that you want Wwise to preserve on import, you must define it in the WAVEFORMATEXTENSIBLE format chunk in the WAV header. If the channels defined in the channel mask of the WAVEFORMATEXTENSIBLE are not supported by Wwise, they will be changed automatically to supported values. For example, if a configuration defines a Left channel but no Right channel, the Left channel (0x01) is changed to the Center channel (0x04), and if a configuration defines Side (Surround) channels but no Rear (Back) channels, the Side channels (0x100 and 0x200) are changed to Rear channels (0x10 and 0x20).


Does anyone know how to edit WAVEFORMATEXTENSIBLE in the file header? It doesn't seem like this is possible in the metadata editor in Reaper.

[schwa]

In the REAPER metadata dialog, Technical/Channel Configuration is embedded as WAVEFORMATEXTENSIBLE (aka WAVEXT) when written to a .wav file. However, LRC is not currently one of the supported options, although we can add support for it.

Note that a basic limitation of WAVEXT is that only the existence of a channel can be encoded, not the order, so what we'd be adding is LRC, not LCR.

[Travesty]

Thanks, that would be great if you added it, it might do the trick. Wwise should be looking for LRC anyway

The context is that a company we are working with is Protools based, and the 3ch files we have sent are being detected by wwise as 2.1 rather than 3.0.

Apparently Protools doesn't have this issue, so I'm investigating what could be the difference between what Reaper and Protools are doing, and how we can adjust the pipeline to match.

[X-Raym]

I have a script to inject dwchannel mask on wav files


https://www.extremraym.com/en/downlo...dwchannelmask/


But of course any native improvements at render will be welcome,
Though working on existing wav files like my script could still be useful to some

[Travesty]

Thanks a lot Xraym, though I hope you don't mind, but I will wait to see if it can be added natively, simply because this could cause an argue about the bill situation.
I will note it as a last resort though, cheers.

[Travesty]

Thanks for adding LRC into the metadata selection, could we also get:

L R C Ls Rs

Thanks