Hello everyone,
In cubase SX 2, Lets say I put an eq effect as an insert in a channel. Is there any way to enable/disable it in different parts of the song ?
Also another question, how can I automate effects which I have set as insert effects ? ( for the send effects it opens a midi FX channel but no such thing for insert effects )

Thanks in advanced,
Scr1pt3r

Automating inserts? Easy. Pull up the effect, and click on the R and W in the upper left corner. A new track will pop up. Look for Effect On/Off as a parameter in there.

Devon

Quote:

Automating inserts? Easy. Pull up the effect, and click on the R and W in the upper left corner. A new track will pop up. Look for Effect On/Off as a parameter in there. Devon

Hi Devon, where does the new track should pop up ?
Didn't see anything changing when I clicked the R and W.

Scr1pt3r wrote:

Quote: Automating inserts? Easy. Pull up the effect, and click on the R and W in the upper left corner. A new track will pop up. Look for Effect On/Off as a parameter in there. Devon Hi Devon, where does the new track should pop up ? Didn't see anything changing when I clicked the R and W.

The Arrange window, or whatever the actual name of the window with all of your tracks, and has the inspector over on teh left. I still get confused between Logic and Cubase with all its names for everything. I'm also not at home to check either. BUT, once oyu turn on automation, a new track should appear.

Devon

Thanks for the help Devon, It works now

probably you figured this out already, but just to clarify: pressing R so it lights up activates the reading of your existing automation, while W allows you to press buttons on your fx and it'll get recorded to the corresponing track-automation. pushing + or - on a track as you've done shows one or more automation tracks for drawing automation.

Thanks for the help powerparrot , now I know what the R and W are for, so according to what you say if I'll automate an insert effect but when playing I wont have its R button turned on so it wont play its automation ?
My 2nd question is this... I've used the Voxengo CurveEq and automated a bypass of it in certain parts of a track, this caused some clicks from some to time.
Is that a voxengo bug or there's nothing to do against such behaviour ? Maybe reducing latency will help or maybe when bouncing the clicks wont appear ?
Anyone got an answer to that ?

Thanks in advanced, Scr1pt3r

yes "R" should be highlighted if you want your mixer automation to be played back. for more info on automation (different modes in recordings etc) check the automation section in the documentation..

for your "clicks" problem - does the CPU usage go up when this happens? (i.e could it be a "denormalization" problem??) can't test this sorry, but I guess you could try "on off" on the CurveEQ instead of bypassing.. Perhaps Picoder can advise to why this might happen.

Scr1pt3r wrote:

Thanks for the help powerparrot , now I know what the R and W are for, so according to what you say if I'll automate an insert effect but when playing I wont have its R button turned on so it wont play its automation ? My 2nd question is this... I've used the Voxengo CurveEq and automated a bypass of it in certain parts of a track, this caused some clicks from some to time. Is that a voxengo bug or there's nothing to do against such behaviour ? Maybe reducing latency will help or maybe when bouncing the clicks wont appear ? Anyone got an answer to that ? Thanks in advanced, Scr1pt3r

You're going from latency to no latency, of course you're going to get a click. Least I'd expect one. To get around it, automate it back to 0db across the board, and then when you want ot back, put it back where you want it and record those movements.

Devon

DevonB, that sounds way more plausible than what I suggested.. (blush). Good workaround.

Quote:

for your "clicks" problem - does the CPU usage go up when this happens? (i.e could it be a "denormalization" problem??) can't test this sorry, but I guess you could try "on off" on the CurveEQ instead of bypassing.. Perhaps Picoder can advise to why this might happen.

hmm... thats what I did, the on/off on the voxengo.
I didn't 'bypass' it by any different way... so I assume according to your question that other than the on/off on the voxengo there should be another parameter I've missed of an actual bypassing of the effect.

Quote:

You're going from latency to no latency, of course you're going to get a click. Least I'd expect one. To get around it, automate it back to 0db across the board, and then when you want ot back, put it back where you want it and record those movements. Devon

Cubase got a delay compensation so I thought it'd be smart to handle it.
Anyway, I did'nt understand your solution devon, could you give a more detailed explanation ?

Quote:

automate it back to 0db across the board

automate what? the volume of the insert effect ?
I want it on a certain part turned on and on a different part turned off...

Quote:

and then when you want ot back, put it back where you want it and record those movements.

lost you
Anyway, If you could give a more detailed explanation I'd appreciate it.

at least for a standard eq you can automate the attenuation to be 0db for all bands during the passage where it should not be heard.. just pull up those parameters (if you have many bands) in your automation track and start drawing. leave the plugin on the whole time.. not sure how CurveEQ handles "bands" as I understand you can have virtually as many as you like so pull up the automation scroll list and see what parameters are available

a different workaround is of course to use offline processing for the parts you need processed and leave the others untouched.

Scr1pt3r wrote:

Quote: You're going from latency to no latency, of course you're going to get a click. Least I'd expect one. To get around it, automate it back to 0db across the board, and then when you want ot back, put it back where you want it and record those movements. Devon Cubase got a delay compensation so I thought it'd be smart to handle it. Anyway, I did'nt understand your solution devon, could you give a more detailed explanation ? Quote: automate it back to 0db across the board

Yes, but if you turn it off, you're jumping 'back in time' with the latency. What I meant was at the point you want it off, change your EQ curve to be a straight line across 0db, so there is no attenuation, and when you want it back change it back to where you had it, with automation data. You could also write PiCoder as well to see if he has better solutions since he wrote the thing too. The beauty of KVR.

Devon