zebra 2.5 automation with ableton 8.1.1

[BIOFLUX.]

hey guys,
has anyone else had a problem trying to automate some parameters?
im running live 8.1.1 so not sure if its an ableton or possibly
zebra bug.

when i use the configure button to create a slider for ie lfo rate
nothing appears.this happens with lfo1,2,3,4 and lfo g1/2
i want to modulate the pan in the voice mixer,i can easily just
render the part panning and use that but cant seem to automate
the mod rate there either.

has anyone else come across this with zebra 2.5 and ableton 8.1.1?
could it be a bug in either one?

thanks.


ps will post this on ableton forum too

[xh3rv]

This is kind of a stock response but have you tried assigning the desired parameters to XY pads? They're very good at solving this sort of problem.

[BIOFLUX.]

i actually havent tried that but im sure it would work.
thank you.

[grandmasterbird]

I have had this problem too but have got round it by (as already suggested) assigning the lfo rate to an xy controller

[BIOFLUX.]

cheers guys.
im using the xy as suggested.

[highkoo]

OK, Im pretty late to the party, but is the X/Y assign still the best work around?
I have been googling the shiat out of this to no avail.

I saw literally a mention of a midi-mapping-editor within Z2. Is that right? The manual does not seem to hint at remapping or that some parameters are invisible to the host.

Whats best practice these days? (Im in FL)
Thanks!

[Urs]

It's still XYs... any major change would break backwards compatibility.

Nevertheless, the whole automation/midi control stuff has become major point on our priority list.

[highkoo]

Thanks for the quick reply!!
I didnt even think of the backwards breakage. Of course!

Well, somewhere I stumbled across what must have been musings about a system inside of Z2 to allowed the user to 'swap out' the limited midi assignments.
That sounds... like quite the job if it does not already exist.
Is that even possible?

Fwiw to you, it is only for the sake of 'mental organization' that I resist the X/Y solution. It is just easier to think "one knob=one knob" for simple assignments. Navigating to the XY pad and 'wasting' the other axis are not mentally neat. But, is a more than easy enough work around.

And dammit, by the way, that user lib page of yours is fantastic!!
It is sort of incredibly awesome that I havent looked at it in so long.