Then these 6 files all have a specific destination/channel routing.
Left, Center, Right, Ls, Rs and LFE, and they should be named accordingly.
They should be merged into a “correct” 5.1 audio file. Correct channel layout and metadata, so that when the file is loaded into a DAW with another channel layout, the channels are routed to the correct outputs.
That’s why the function is called “Convert Tracks” and not “Convert events”.
Also, why do all the other files in these 6 “surround” tracks don’t have to be converted into a multichannel file?
If you have 6 channels -I assume routed to the correct 5.1 channels- then all of these files could benefit from being merged into a multichannel, no?
When we receive an AAF from the video editors, the Music tracks are mostly split into two mono tracks.
After verification that all is OK on these tracks, the complete MX tracks get converted to stereo, retaining levels, edits, handles, etc …
Can’t be more convenient, no?
You are ignoring the fact that any channel within the multichannel .wav need to have a correct identification of which channel it belongs to.
Your 6 mono files are named correctly (Left/Right/Center/etc …)
This information is (and needs to be) written within the Multichannel audiofile as metadata.
If you are currently merging your 6 mono files into 5.1 files without taking care of the channel config, then all is going to end up in the wrong channels.
Your files/tracks need to be arranged according the channel layout, from top to bottom.
Track 1 : Left
Track 2 : Right
Track 3: Center
If you change this order (or import them in alphabetical order)
Track 1 : Center
Track 2 : L
Track 3 : LFE
Track 4 : Ls
Track 5 : R
Track 6 : Rs
After converting above example into a 5.1 file, your LFE channel will end up in your Center speaker and the Left Surround channel will be routed to your Sub.
Then you would also have to fill in the information in some sort of matrix before you can (blindly) merge your files.