Page 5 of 6

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 8:47 am
by TomViolenz
Well isn't 128 something like 8 Bit?! It could be that this limitation is hardcoded into Live. It's interesting in a way that you can side step that problem in Push, if you use their own devices. But I think the process of maping with them works as a totally different process.
There you just can't map certain parameters, that they decided, for some reason, not to make accessible to the API.

LFO and AUX Amount in Sampler, I'm looking at you! :evil:


Wait: 128 is 7 bit! That doesn't look right, 7 is not a "biting" that's used. What's the other bit doing? Maybe one more doubling would be possible...
Don't you got contact to people from Ableton in the Beta forums? Maybe ask there if they could double the parameters easily.

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 8:57 am
by queglay
it would be great if we could somehow catch a dial that is being touched to assign out own lfo...

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 9:02 am
by TomViolenz
queglay wrote:it would be great if we could somehow catch a dial that is being touched to assign out own lfo...
come again...? :?
I didn't get that, do you mean the M4L lfo?

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 9:17 am
by queglay
yes, the m4l lfo for example.

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 10:34 am
by TomViolenz
queglay wrote:yes, the m4l lfo for example.
But don't you set the learn behaviour of the LFO up in the LFO? You can make your own mapping of M4L devices for Push, no?! Try to assign its maping behavior to an encoder in Push.

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 10:56 am
by queglay
welll theres no way yet, but im sure we could hack something together somehow.

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 3:29 pm
by tedlogan
TomViolenz wrote:Well isn't 128 something like 8 Bit?! It could be that this limitation is hardcoded into Live. It's interesting in a way that you can side step that problem in Push, if you use their own devices. But I think the process of maping with them works as a totally different process.
There you just can't map certain parameters, that they decided, for some reason, not to make accessible to the API.

LFO and AUX Amount in Sampler, I'm looking at you! :evil:


Wait: 128 is 7 bit! That doesn't look right, 7 is not a "biting" that's used. What's the other bit doing? Maybe one more doubling would be possible...
Don't you got contact to people from Ableton in the Beta forums? Maybe ask there if they could double the parameters easily.
Well I always post what I think is needed to the suggestion box on the site, as well as on the forums. At present, I think not many, if anyone cares about being limited to 128 parameters, which is totally understandable.

And you're lucky if you get feedback from Ableton at all, although they do respond to bug reports, two of mine being false.

On a final note, earlier I restarted my laptop after it powered off (battery is dead) plugged in Push and loaded up Live. It asked if I'd like to recover my work, which was a delightful gesture. I said of course, waiting for it to load up with a few instances of zebra etc. A critical error window popped up saying basically I have to fuck off. Then I starting hearing zebra-like feedbacks, synths, reverbs, and random sounds, even though Live was definitely not running anymore. I unplugged Push, checked everything, and every now and then still random harmonies of a dissonant nature.

I was sitting laughing at the whole impossible situation, so absurd, and the first time a crash was enjoyable.

It so happened that when I restarted, so did Firefox which was on a YouTube page with the 47 u-He tutorials by Howard Scarr running in the background, one after the other. I need a break.

Re: Post Your Push VST Mappings

Posted: Sat Nov 16, 2013 6:38 pm
by queglay
128 is a vst limitation i believe. we are screwed if we want to tackle that problem. it should have been fixed when everything went 64 bit. that was the best change we had.

Re: Post Your Push VST Mappings

Posted: Mon Aug 18, 2014 12:41 pm
by selthym
After "configuring" a vst, in my case Zebra, when i change a preset in the VST, the configured paramaters don't refresh.

Does anyone know why this is or a way around it?

My solution at present is to create a couple of additional configured racks that have a different sonic character.

Re: Post Your Push VST Mappings

Posted: Mon Aug 18, 2014 2:11 pm
by tedlogan
selthym wrote:After "configuring" a vst, in my case Zebra, when i change a preset in the VST, the configured paramaters don't refresh.

Does anyone know why this is or a way around it?

My solution at present is to create a couple of additional configured racks that have a different sonic character.
I rack up each preset for Zebra 2. I also have different macros for each rack, tailored to the presets. You will occasionally find that when hotswapping/browsing racks, that some of the macros from the previously loaded rack will remain in the new one, as well as some Configure panel parameters slipping over. This creates total chaos with the newly loaded presets. I think it has to do with the modular nature of Zebra 2.

I have submitted a bug report to Ableton, and they did get back to me. I've sent them 4 examples of my racks in a set and they're looking in to it. Maybe it's just me.

Re: Post Your Push VST Mappings

Posted: Tue Aug 19, 2014 9:32 pm
by tedlogan
tedlogan wrote:
selthym wrote:After "configuring" a vst, in my case Zebra, when i change a preset in the VST, the configured paramaters don't refresh.

Does anyone know why this is or a way around it?

My solution at present is to create a couple of additional configured racks that have a different sonic character.
I rack up each preset for Zebra 2. I also have different macros for each rack, tailored to the presets. You will occasionally find that when hotswapping/browsing racks, that some of the macros from the previously loaded rack will remain in the new one, as well as some Configure panel parameters slipping over. This creates total chaos with the newly loaded presets. I think it has to do with the modular nature of Zebra 2.

I have submitted a bug report to Ableton, and they did get back to me. I've sent them 4 examples of my racks in a set and they're looking in to it. Maybe it's just me.
They've been able to recreate this bug in-house. It's not that high on their priority list though, but at least I know it's not my setup that's gone askew somewhere. When swapping between Zebra Instrument Racks, you will occasionally find that things go FUBAR.

Re: Post Your Push VST Mappings

Posted: Mon May 04, 2015 5:15 am
by Citizen
Just wondering if anyone else has VST mappings to share?

FabFilter Twin, Albino anyone? :lol:

Re: Post Your Push VST Mappings

Posted: Thu May 14, 2015 3:31 pm
by muthafunka
Any more love for this thread or is there a better workround these days? Got a Push cheap and starting to explore....wow

Re: Post Your Push VST Mappings

Posted: Sun May 17, 2015 8:11 pm
by lovelight
Ive made about 35 vst presets racks for Push, by hand no macro auto, tryed to make the best an easy mapping for easy tweak. more are comeing every week/month.
come and get them for free. look what i done here: https://www.facebook.com/AbletonPushVstRacks and join the Group for free and pro Push ready Vst Racks.

Re: Post Your Push VST Mappings

Posted: Wed May 20, 2015 8:08 pm
by lovelight
kontour and razor Push ready tonight, join in and get a lot of racks to transform your push to your favourite VST




https://www.facebook.com/AbletonPushVstRacks