WAVEXT channel configuration

[Mercury]

I am using REAPER for video game audio production. I would like to be able to specify 6.0 (L R BL BR SL SR) in the WAVEXT channel configuration in the project render metadata for the rendered wav files.

This is one of the supported channel configurations in Wwise, an audio middleware widely used in the video game industry. Wwise has a total of 21 different configurations, but REAPER only supports 5.
https://www.audiokinetic.com/en/libr..._are_supported

I believe that support for all of these would increase the usefulness of REAPER.

[schwa]

We can add 6.0 waveext metadata support, but I'm not entirely sure how the waveext channel definitions map to the wwise ones, and it's not clear to me that the ordering will be the same.

waveext supports (L R Ls Rs Lsd Rsd), in that order. I *think* wavext's Ls/Rs may be what wwise is calling BL/BR, and Lsd/Rsd may be wwise's SL/SR, but I'm not sure :/

[X-Raym]

@schwa
As far as I know, channel order isn't relevant, it is not encoded. All matters is which channel is selected.



that is why I didnt had to add order in my dwchannel mask injector script.


https://i.imgur.com/b3Za60M.gif

[Mercury]

@schwa
Sorry for the late reply.

Wwise 6.0 (L + R + BL + BR + SL + SR) is matched to waveext 6.0 (L R Ls Rs Lsd Rsd). As X-Raym points out, channel order is irrelevant. I actually tested that a wav file containing waveext 6.0 metadata was correctly recognized by Wwise.

The mapping between Wwise and waveext seems to be fine if the channels are read as follows.
BL = Ls
BR = Rs
SL = Lsd
SR = Rsd

[schwa]

This format is supported in REAPER 6.82 which should be released today.

[Mercury]

@schwa
Thanks for the quick update! I'll try the release.

[Mercury]

@schwa
REAPER 6.82 works appropriately.
Wwise correctly recognized a 6.0 WAV file rendered by REAPER.
Appreciate your support once again.