I thought that “convert channels “would be a substitute for the missing drag and drop capabilities of multichannel files to split mono tracks and vice versa.
But it seems to ignore edits like clip gain, crossfdes and cuts and also the name is the one of the target channel?
I imported an aaf from media composer and converted the clips from the two mono “Musik” tracks to the “Audio 01” track.
Not what I hoped to get.
Am I expecting the wrong thing?
Cheers,
Dirx
That’s bad.
No, you’re not.
Just to clarify and separate Issue from Feature Request
Secondly, this would be a good use case for Multi-Channel Tracks to be open individual channels the user can drop multiple mono channels onto, edit on, etc?:
I would expect this result:
the green clips converted to the blue clips. With correct clip gain, edits, crossfades etc.
And with preserved handles and metadata would be nice.
That is my “Issue”.
My “feature request” would be a proper import in first place.
These “Musik” tracks are stereo Tracks in the Media Composer project and Pro Tools imports these as stereo Tracks as well.
Only in Nuendo they are imported as mono Tracks.
Does this command actually “bounce” files to event boundaries when converting?
I just converted channels from AAF and not only were crossfades ignored, but now I seem to have lost handles as well.
Is that how this function works?
As far as I tested it unfortunately yes.
No handles,
no Clip Gain
no Fades.
ok… thanks for confirming…
Anyone in post who imports stereo content from AAFs probably already knows what I think about that…
Once again, I and others just asked for doing it the way PT does it.
What’s the over under on how soon after v15 release we get handles, clip gain and fades? A year? Three?
Forgive me if I’m misunderstanding but are you all saying that the “convert mono to multi channel” is not preserving the edits and crossfades for you?
Yes, that’s what I’m seeing.
Sorry, i should be more clear. I want cross fades preserved and i need handles.
Same but I AM getting crossfades, edits and handles when I use “convert mono to multi channel”. Just tested it to make sure I wasn’t missing something, works as advertised for me. FWIW, I’m on Mac OS15.7.4 Sequoia and I’m running in Rosetta due to the Nuage. john
Well, when I execute the command the result is “bounced” (consolidated) files on a new track with the crossfades rendered into audio, and the boundaries of the original events become “hard” with no handles.
My system is in my sig.
I absolutely hate that there is so little participation by Steinberg on this forum. It really, really sucks and it’s really getting on my nerves.
Wow, that is messed up! I re-read thru the manual (pg 223), how the hell can it act so differently on different systems?!?
And I agree, their lack of participation is annoying and very disappointing.
I had coffee and I think I see the problem here. We’re not talking about the process you put in quotes above, we’re talking about the new feature in v15.
“convert mono to multi channel” is the old feature that creates a new track for the newly converted audio, “Convert Channels” allows you to select mono events and then select a stereo audio track to use as a target.
Can you just confirm that we’re talking about different things so there’s no confusion?
I just checked and it’s the same for me on OSX as it is on Windows.
Here’s the new function just for reference:
Yes, there it is. I have indeed been talking about the older feature and wasn’t aware of this new one. john
