• SONAR
  • X3 wish list in automation
2013/07/07 14:41:14
phrygiann
In write volume automation, link two or more tracks so that if i increase volume in one track the other linked track will decrease its volume or if i decrease one track the other linked increases.
2013/07/07 14:50:17
sharke
I would like them to fix the automation parameter labeling, so that when you automate a parameter in an FX chain effect, the parameter name is shown on the automation lane. Currently it shows either nothing at all or some other generic parameter like "volume." 
2013/07/07 16:13:14
Grem
To the op, you can do this now. Not at my box so I can't step you through it, but when you group faders together you can have them do exactly what your describing.
2013/07/07 16:16:15
Grem
Sharks I think the label sonar gets if from the plug. Not really sure but I think that's were the name is derived. And that would be up to the plug developer as to what they decide to call what.

A feature request would be for us to have the ability to name the envelopes what we want.
2013/07/07 16:36:57
jb101
At last, an X3 wish list thread.

@phrygiann - did you sort your inspector issue? Did you see my post in the other thread?
2013/07/07 19:12:05
stevec
Grem
To the op, you can do this now. Not at my box so I can't step you through it, but when you group faders together you can have them do exactly what your describing.



Yeah, that seems familiar, though I can't recall where you access those settings.
2013/07/07 20:09:19
sharke
Grem
Sharks I think the label sonar gets if from the plug. Not really sure but I think that's were the name is derived. And that would be up to the plug developer as to what they decide to call what.

A feature request would be for us to have the ability to name the envelopes what we want.



 
That's not the case. When you select the parameter from the menu, its proper name is given. Sonar has the name, it just doesn't bother displaying the name of it in the automation lane when it's from a plug in an FX Chain. No vst manufacturers are giving their parameters blank names, or calling delay feedback "volume" (at least no reputable ones). 
 
Another problem is when you have two of the same plug in an FX Chain. Sonar doesn't differentiate between them in the parameter menus, it just cites one of them and mixes all of the parameters from each plug in the menu so that you don't even know which one is which. To be honest I don't think the "new" features like the ProChannel were finished properly - I get the feeling they were rushed out for the release. Not being able to automate an FX Chain's on/off switch unless the ProChannel in question is open in the console - there's another one. Cakewalk officially called it a "limitation" rather than a bug, which to me is another way of saying "we didn't really get a chance to finish the code before the release deadline." 
2013/07/07 21:48:41
phrygiann
@Grem,you might not get what i meant, what i meant was link two tracks, lets say track 1&2, if i want to write automate the vol of track 1 by trying to increase its volume(presence in the mix) the track 2 behave in the opposite way(volume/ presence in the mix decreases). I came to think of this because i am making a song that has two instrument where at some point i wanted one track move forward and the other to be at the background and vice versa. Im newbie in mixing that i dont know if the masters find it useful.
2013/07/07 22:05:08
stevec
FWIW, this is what I was thinking of:
http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR X2&Lang=EN&Req=Mixing.52.html#1098181
 
 
Edit: The link is wrapping so you'll have to copy both lines and paste.
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account