MeldaProduction

CableChannel · Post by **CableChannel** » Mon May 19, 2014 6:25 pm

OK here is what I see in Cubase 7.0.7:

MMultiBandDelay 8.0.1.

I tried to automate the Modulator 1 on/off button. It does not work, you can't automate it.

So then I go into the modulator and try to automize the destination parameters. I use Cubase's write mode to write the controller movements.

Band1-Tap1-Gain - Value -> changes correctly written
Band1-Tap2-Gain - Value -> changes not recorded correctly
Band2-Tap1-Gain - Value -> changes not recorded correctly
Band2-Tap2-Gain - Value -> changes not recorded correctly

So only the first destination parameter is recorded correctly. The others even get a wrong scale in Cubase. All should range from silence to 0 db, but only the first does, the latter three range from 0-100 percent on Cubase's automation lane. Still, if I write automation values manually they work. 0% translates to silence and 100% to 0db.

So. It works after all, but it is a little mess in Cubase. I hope you get what I described, it is rather complicated.

MeldaProduction · Post by **MeldaProduction** » Mon May 19, 2014 8:54 pm

Hmmmm, I'll check, but I'm a little lost - are you automating it or modulating it?? Because to me it seems like you are trying to do both, or neither

???

CableChannel · Post by **CableChannel** » Mon May 19, 2014 9:13 pm

I am modulating the delay gain values and I am automating the range of these. Basically to turn the modulation on and off. The default modulation range is min 0 db and max 0 db, so basically the modulator does nothing. Then I change the min to silence via automation, and voila, the modulator starts to modulate

MeldaProduction · Post by **MeldaProduction** » Mon May 19, 2014 10:26 pm

Aaaha, so the problem is that you cannot automate "Mod enable", right?

CableChannel · Post by **CableChannel** » Mon May 19, 2014 10:30 pm

Right, that was the original problem.

As a workaround I tried to automate the ranges. That works, but the values/unit displayed in Cubase are not correct (percent scale instead of db scale).

MeldaProduction · Post by **MeldaProduction** » Mon May 19, 2014 10:37 pm

Aaaha I'll check it out. Anyway there's a pretty big possibility, that it won't be fixable - you know it's a parameter, controlling a range of other parameter, kinda problematic transition...

CableChannel · Post by **CableChannel** » Mon May 19, 2014 10:40 pm

OK. But the "modulator enable" should be less problematic I guess?

MeldaProduction · Post by **MeldaProduction** » Wed May 21, 2014 10:24 am

It's pretty possible, that the automation units for mutiparameter ranges won't be possible. But I'll add the modulator enable to to-do. It's actually very hard, because on enable the modulator may need to do some initialization stuff, so I'm not sure it if will be possible at all. We'll see.

MeldaProduction · Post by **MeldaProduction** » Tue May 27, 2014 10:25 am

I was just checking this and found out you CAN actually automate it, but the plugins do not send the automation, so you have to find it manually. It will hopefully be fixed, but you can already automate mod enable using "LFO 1 - Enable" parameter for example

.

CableChannel · Post by **CableChannel** » Tue May 27, 2014 9:55 pm

MeldaProduction wrote:I was just checking this and found out you CAN actually automate it, but the plugins do not send the automation, so you have to find it manually. It will hopefully be fixed, but you can already automate mod enable using "LFO 1 - Enable" parameter for example .

Ah ok. Good enough for now

MeldaProduction

KVR Audio

Automation bug