Quote:
Originally Posted by schwa
Re channel configurations, there are two metadata formats that support a channel configuration tag, WAVEXT and CAFINFO (core audio).
The WAVEXT tag doesn't support rearranging channel order, only marking channels within a fixed-order list as existing or not existing. The set of WAVEXT tags that REAPER can embed is:
L R
L R Ls Rs
L R C LFE Ls Rs
L R C LFE Ls Rs Lsd Rsd
In other words something like "L C R Ls Rs LFE" cannot be represented as a WAVEXT tag, because the channels are not ordered in a way that the tag supports.
Everything else listed under the channel configuration dropdown is a CAFINFO layout tag. The tags are taken verbatim from the Core Audio definitions.
The confusing part I suppose is that under the common metadata scheme, both WAVEXT and CAFINFO tags are listed, even though wav files will only support the WAVEXT tags. Maybe we should list only the WAVEXT tags in the common scheme list.
I don't know what other DAWs look at these tags when importing, all REAPER can do is embed the tag.
|
Also Here is a file bounced from Protools.
https://drive.google.com/file/d/1S0e...ew?usp=sharing
Here is the same file exported from Soundminer
https://drive.google.com/file/d/1S3W...ew?usp=sharing
You can see Soundminer is doing something right. Hence Protools seems to read the channel order correctly as it should.
Here is the same file exported from Reaper
https://drive.google.com/file/d/1S5L...ew?usp=sharing
This file doesn't play in protools with the right channel order
I opened it in reaper as well as Soundminer. Both app seems to read the channel Layout as it should. Maybe if reaper tries to embed the channel layout in the same way as sound miner other apps such as protools will read it too ?
Also Checkout The attached screenshot. When I open the reaper exported file and protools exported file in Soundminer, Soundminer shows the channel layout order in the protools exported file but not on the reaper exported file