They're saying when it's mapped to any remote parameter, the full range of that parameter is divided into 128 increments. There is no work around for that without rewriting the way Live handles remote mappings, which would be a ridiculously large-scale undertaking. BUT you could make it so that holding down a button causes it to produce increments faster or slower, that's easy - which would feel like more control and may address some needs. But you're still fundamentally stuck with 128 values.

"The first one [my question about knob resolution] is due to the general MIDI data resolution of 128 steps. Also the Push knobs send regular MIDI CC to control parameters, which gives you those 128 steps. If your actual parameter has a smaller resolution, with every (MIDI) data increment/decrement sent in, the parameter changes several steps."

metastatik wrote:I've just uploaded a modification to the Push script that allows Shift + the Encoders to finely adjust parameter values (provides 1024 steps of adjustment). Install info is provided in the download.

This is brilliant, thanks very much. It makes Push much more useful for me.

Maybe Ableton should pay you to sort out push, you seem to have more knowledge about it than they do!

"The first one [my question about knob resolution] is due to the general MIDI data resolution of 128 steps. Also the Push knobs send regular MIDI CC to control parameters, which gives you those 128 steps. If your actual parameter has a smaller resolution, with every (MIDI) data increment/decrement sent in, the parameter changes several steps."

that is completely missing the point. i don't think people are talking about increasing the overall MIDI resolution, they are talking about how sensitive the knobs are. all it requires is changing how far you need to turn a knob per MIDI value.