globally modifying push 2 on/off behaviour?

[Joost]

Hi,

I love my Push2 but the one thing that always bothers me is the way it reacts to paramteters with only on/off switch functionality. Standard push2 is set to change the parameter to on from value 65. Have any of you found a way to change this behaviour? (maybe in the push2 script?)
I would love to have on/off switches globally switch on with every positive value and off with every negative value so it turns on and off directly when using the encoder instead of having to find value 65 first.

I know when the paramters are mapped to a midicontroller you can edit the settings so it behaves this way but im looking to alter this globally. I hope one of you have allready found out how to do this

Greetings

[jestermgee]

I'm not seeing this behaviour? Are you talking when using Push with a Live device or a VST?

I have opened Analog and tried turning things ON/OFF and basically as soon as I start to turn to the right, it's on, the left, it's off.

With a VST it depends on what the developer has set for the parameter. Some make 0-64 as OFF and 65-127 as ON and some make it as 0 = off and < 0 as ON. I don't believe it's possible to change this for Push.

[Joost]

For example Guitarrig 5, i use the on off switches to rythmicly turn effects like filter, gate, beatslicer on and off in a rythmical way.

[jestermgee]

Yeah then that isn't a push thing. There isn't a way to set the range of a control on push itself.

Off the top of my head (I could be wrong, often happens) what you could try is create an Instrument rack and assign the controls to Macro knobs. I then believe you could set a Min/Max value for the macro which should allow you to reduce the resolution of the control.

I have the opposite issue with Keyscape where some multi-position selectors have a range of 0-127 but have 4 options assigned to values 1, 2, 3, 4 so trying to select something between 1-4 when you have a whole 127 scale is insane. Spectrasonics can't step out their own world and understand the points from customers within any less time frame than 2.5 years tho (which is how long it took them to fix automation of Radio buttons).

[Joost]

that wont work because when they are assigned to macro's they wont be available in the banks i need them in. I contacted ableton support aswell and idd at this time there is no workaround. I really hope ableton will improve their mappingfeatures, specially because its so important for creating workflows aswell for the studio and on stage

Things like naming banks, at least doubling the parameterlimit to 256, making the ext instrument able to map parameters from the routed channel and making multipresetmappings for vst's like reaktor would be such a huge improvement. The mappingfeatures are just about the only thing in which live breaks my workflow. I know isotonik PReditor will fix some of these features but it needs to be in the box

On namm18 the new standards for midi2.0 got presented, that will be a big step forward once it will be supported, i guess this will take a year or two though