I dont seem to be able to automate the lfo amp using live 7 or logic 8.
Does anyone know if it can It done?
zebra 2 lfo automation
-
- KVRist
- 73 posts since 9 Apr, 2009 from Australia
-
- KVRAF
- 1617 posts since 11 Dec, 2008 from Minneapolis
The easiest way would probably be to map LFO amp to an X-Y control.Bounce to audio wrote:I dont seem to be able to automate the lfo amp using live 7 or logic 8.
Does anyone know if it can It done?
Another way might be to use a ModMixer; it would be on 'scale by constant', the LFO you want to use should be one mod source and the others empty, and anywhere the LFO was used, replace with the ModMixer. The MMix constant then becomes essentially an amp control for the LFO, and should be automatable.
There might be a complicated way too; on OS X there's a config file in /Library/App Support/U-He that I think can be modified to add or remove parameters visible by the plug-in host.
-
- KVRist
- Topic Starter
- 73 posts since 9 Apr, 2009 from Australia
Thanks heaps xh3rv, Ill give it a go 
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
???? Can't you learn a MIDI CC for that knob? Works here (tested for LFO1 in Logic8).Bounce to audio wrote:I dont seem to be able to automate the lfo amp using live 7 or logic 8. Does anyone know if it can It done?
Why the indirect route?xh3rv wrote:The easiest way would probably be to map LFO amp to an X-Y control.
-
- KVRist
- 299 posts since 15 Apr, 2004
In my world Midi CC is not the same as Daw automation.Howard wrote:???? Can't you learn a MIDI CC for that knob? Works here (tested for LFO1 in Logic8).Bounce to audio wrote:I dont seem to be able to automate the lfo amp using live 7 or logic 8. Does anyone know if it can It done?Why the indirect route?xh3rv wrote:The easiest way would probably be to map LFO amp to an X-Y control.
Also, CC is 128 steps, automation can be finer than that. (if you really always need that resolution is another question...
)//L
-
- u-he
- 30215 posts since 8 Aug, 2002 from Berlin
I recommed that too. MIDI CC is destructive, just like automation. XYs are non-destructive, just double click (sets the ball to center) and you're back to the original sound.Howard wrote:Why the indirect route?xh3rv wrote:The easiest way would probably be to map LFO amp to an X-Y control.
Furtherly, the influence/depth of the XYs can be constrained for each situation, which might make automation a tad easier.
Also, you can MIDI learn the XYs and have a different set of automations for each patch, with just 8 knobs.
Urs-
- KVRian
- 505 posts since 13 Feb, 2009
now that is really cool. I did not know that (but I don't know much anyway. ha!)Urs wrote:Also, you can MIDI learn the XYs and have a different set of automations for each patch, with just 8 knobs.
-
- KVRian
- 1184 posts since 13 May, 2004 from SF Bay Area, California
MIDI CC and host automation aren't really destructive: just reload the preset and you're back to the original sound. The reason I prefer host automation in general is that most synths report their parameter values to Logic in meaningful units, so instead of setting Pad 3 X to 40%, you can set a filter cutoff in Hz.Urs wrote:I recommed that too. MIDI CC is destructive, just like automation. XYs are non-destructive, just double click (sets the ball to center) and you're back to the original sound.sHoward wrote:Why the indirect route?xh3rv wrote:The easiest way would probably be to map LFO amp to an X-Y control.
If you like 80s retro sounds, check out my latest tune…
-
- KVRer
- 3 posts since 21 Apr, 2020
Does anyone know where this stuff would be on windows?xh3rv wrote: Thu Apr 09, 2009 5:22 am There might be a complicated way too; on OS X there's a config file in /Library/App Support/U-He that I think can be modified to add or remove parameters visible by the plug-in host.