Hello,
I'm using Zebra 2.5 in Live 8.21 on a mac os 10.6.3.
In live, if you want to automate a parameter, you need to configure the plugin, where you click a knob in the gui of the plug-in, and then it shows up in live.
This works fine for everything except the lfo parameters. They won't show up in Live. This happens in VST and AU versions.
Does this make sense?
Ableton Live Automation bug
-
- KVRAF
- 4141 posts since 11 Aug, 2006 from Texas
the problem is that Zebra2 has greater than 128 parameters that it exports to the host. The easiest way to get around this is to Automate one of the 8 XY paramters and then have that parameter automate the LFO parameter(s) you want to adjust.
If that can't work the alternative is to look into the custom naming of exported parameters. They're in the file com.u-he.Zebra2.publicparams.txt which is found in Zebra2.data/Support. Open the file with a simple text editor and move the appropriate LFO parameter higher up in the list above the 128 limit.
I recommend the XY option as it preserves compatibility with older saved projects using Zebra2 automation and is a lot safer.
If that can't work the alternative is to look into the custom naming of exported parameters. They're in the file com.u-he.Zebra2.publicparams.txt which is found in Zebra2.data/Support. Open the file with a simple text editor and move the appropriate LFO parameter higher up in the list above the 128 limit.
I recommend the XY option as it preserves compatibility with older saved projects using Zebra2 automation and is a lot safer.
-
- KVRAF
- 13133 posts since 7 May, 2006 from Southern California
By default the only LFO parameters which are automatable (without assigning to a modulation source like mod wheel or an XY controller) are Sync and Delay. This is because, by default, Zebra does not publish these parameters to the DAW. If you'd like to automate them without assigning them to a modulation source, you must edit the u-he.Zebra2.publicparams.txt to include those parameters (as Brian suggested).
-
- KVRist
- Topic Starter
- 69 posts since 24 Dec, 2008
Thanks for the insight. That's interesting. Is there any good reason for this ommision?justin3am wrote:By default the only LFO parameters which are automatable (without assigning to a modulation source like mod wheel or an XY controller) are Sync and Delay. This is because, by default, Zebra does not publish these parameters to the DAW.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Yes. There has been a bug in MacOS X. If a certain number of automatable parameters is crossed (which I assume to be about 700), then the event/automation system would occasionally "loose touch". The communication between gui, host and plugin would break up. That means, if all parameters were automatable, automation or mousing the gui would sometimes have no effect on the sound anymore. Thus I left a few hundred parameters out from automation.benj3737 wrote:Thanks for the insight. That's interesting. Is there any good reason for this ommision?
I'm slowly getting there though. Adding the option to make these parameters automatable is on the to do list.
For now however the XY-Controls are the best and easiest method for automation - also because they are "non-destructive"
Urs-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
How about... can you modulate your target parameter with a ModMixer? - Then you could use the Constant parameter of the ModMixer to automate that parameter... it's a long shot though, and I'm not 100% certain that the Consts can be automated...benj3737 wrote:Thanks for the clarification Urs. Unfortunately, the xy grids are all used for live performance.
Oh well.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
A spare MSEG could do that as well. I'm pretty sure there are plenty of viable workarounds...Urs wrote:How about... can you modulate your target parameter with a ModMixer? - Then you could use the Constant parameter of the ModMixer to automate that parameter... it's a long shot though, and I'm not 100% certain that the Consts can be automated...
Last edited by Howard on Wed Dec 15, 2010 11:34 pm, edited 1 time in total.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
HowHoward wrote:A spare MSEG could do that as well.Urs wrote:How about... can you modulate your target parameter with a ModMixer? - Then you could use the Constant parameter of the ModMixer to automate that parameter... it's a long shot though, and I'm not 100% certain that the Consts can be automated...
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
Attack controlUrs wrote:HowHoward wrote:A spare MSEG could do that as well.Urs wrote:How about... can you modulate your target parameter with a ModMixer? - Then you could use the Constant parameter of the ModMixer to automate that parameter... it's a long shot though, and I'm not 100% certain that the Consts can be automated...
Or a spare envelope, via Sustain control or...
-
- KVRAF
- 26978 posts since 3 Feb, 2005 from in the wilds
Constant can be automated... and there are 4 modmixers... so it is a good one to use cause there are always some extras...Urs wrote:How about... can you modulate your target parameter with a ModMixer? - Then you could use the Constant parameter of the ModMixer to automate that parameter... it's a long shot though, and I'm not 100% certain that the Consts can be automated...benj3737 wrote:Thanks for the clarification Urs. Unfortunately, the xy grids are all used for live performance.
Oh well.