I was just wondering about the best way of automating Zebra in Ableton.
Up to now I have been automating Zebra by assigning the parameters I would like to tweak to the XY controllers.
Unless I am missing something would I be correct in saying that this is the only way of doing it in arrange view?
I remember when I was using Logic there was the option to call up a massive list of parameters and all you had to do was select for example 'Filter 1 Res' and off you went. You could draw in the automation directly as opposed to having to assign a parameter to the XY. I personally used to find this way of doing things a bit easier than using the XY's for controlling automation.
I cant seem to find any sort of similar list of parameters in Ableton and the only parameters for automation that appear to come up is for the XY functions.
Am I missing something? Is there a better or easier way of doing it?
Thanks
Automation Options For Zebra Using Ableton Live..?
-
grandmasterbird grandmasterbird https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=134988
- KVRist
- 440 posts since 7 Jan, 2007
-
- KVRist
- 493 posts since 20 Apr, 2004 from hki-fi
If you're using live 8, pressing the "configure" button works with zebra just like with any other instrument. I'd recommend this for quickmapping a single param for automation.
However, the XY's are nothing to be sniffed at. They are extremely powerful in Zebra, enabling 2+ (with xFade-like behaviour) functionality on a single knob for example. I guess you could do the same in logic but you'd have to mess around with the env a bit (?)
However, the XY's are nothing to be sniffed at. They are extremely powerful in Zebra, enabling 2+ (with xFade-like behaviour) functionality on a single knob for example. I guess you could do the same in logic but you'd have to mess around with the env a bit (?)
-
grandmasterbird grandmasterbird https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=134988
- KVRist
- Topic Starter
- 440 posts since 7 Jan, 2007
Configure button? Oh dear. Time to read the manual I think!tetsuneko wrote:If you're using live 8, pressing the "configure" button works with zebra just like with any other instrument. I'd recommend this for quickmapping a single param for automation.
However, the XY's are nothing to be sniffed at. They are extremely powerful in Zebra, enabling 2+ (with xFade-like behaviour) functionality on a single knob for example. I guess you could do the same in logic but you'd have to mess around with the env a bit (?)
Dont get me wrong, I understand the use and the potential for using the XY's but most of the time I want to have control over one parameter per automation lane.
I can do this using the XY's but sometimes I start to run out of XY's if I want to automate a few parameters....
-
- KVRAF
- 1617 posts since 11 Dec, 2008 from Minneapolis
If you do 'configure' Live's representation of a Zebra, the quickest thing is to right-click on configured parameters and choose 'show automation in a new lane' - this quickly pops into the relevant place in arrange view.
It's definitely worth saving a partially configured Zebra, in a rack, to some folder Live browses to. You might want to have some rack controls mapped by default to some Zebra parameters, and this will also save you the effort of configuring Zebra every time you use it.
It's definitely worth saving a partially configured Zebra, in a rack, to some folder Live browses to. You might want to have some rack controls mapped by default to some Zebra parameters, and this will also save you the effort of configuring Zebra every time you use it.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Btw. In version 2.5 I have addressed the issue of confusing parameters names. If you replace com.u-he.Zebra2.publicparams.txt with the other file (publicparams.xl or so, havn't got it ion front of me) then all parameter names are switched to something like VCF1:Res, Osc1:Tune etc.
Some names will remain cryptic, but opening the actual publicparams.txt file will reveal the meaning of each parameter in clear text as well.
Only caveat: Some hosts might get confused by the renaming, especially with existing projects. This would be odd, but it is the reason for me not making it the default option.
Oh, and of course you can rename the parameters yourself, but don't make the names too long (VST2: less than 24 letters should be fine, RTAS less than 16, AU less than 4 Gigabyte)
Some names will remain cryptic, but opening the actual publicparams.txt file will reveal the meaning of each parameter in clear text as well.
Only caveat: Some hosts might get confused by the renaming, especially with existing projects. This would be odd, but it is the reason for me not making it the default option.
Oh, and of course you can rename the parameters yourself, but don't make the names too long (VST2: less than 24 letters should be fine, RTAS less than 16, AU less than 4 Gigabyte)
-
grandmasterbird grandmasterbird https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=134988
- KVRist
- Topic Starter
- 440 posts since 7 Jan, 2007
Thanks for your responses guys.
It is becoming very clear that I am obviously missing something!
A lot of what has been said does not make much sense to me right now but once I read the manual I'm sure I'll be able to link up what you're saying and follow the advice.
Many thanks and a happy new year to you
It is becoming very clear that I am obviously missing something!
A lot of what has been said does not make much sense to me right now but once I read the manual I'm sure I'll be able to link up what you're saying and follow the advice.
Many thanks and a happy new year to you