Advanced Fader Range Setup This is an example of an eventhandler that makes it so moving the full range of the physical fader only moved the top half of the actual "fader" parameter, using the "Analog to Analog" conversion and Map1: "EventHandlers": { "change": { "EventPreProc": { "A2A": { "InputMapping": { "Default": { "Map1": { "InputEnd": 1000, "OutputStart": 500, "OutputEnd": 1000 } } } } }, "BinarySetValues": {}, "IOReference": {} } }, This does however completly remove the option to go to 0 on the param, if you want that you might want this kind of code instead where Map2 makes it so the last 5% of the physical fader makes it jump down to 0 or "inf" when talking audio faders, while still keeping the scaling on the rest of the fader positions: "EventHandlers": { "change": { "EventPreProc": { "A2A": { "InputMapping": { "Default": { "Map1": {}, "Map2": { "InputStart": 50, "InputEnd": 1000, "OutputStart": 500, "OutputEnd": 1000 } } } } }, "BinarySetValues": {}, "IOReference": {} } }, All Values here are set in a "Normalized" range, so this will always be a number between 0 and 1000, think of it as a % of the values on your param where 1000 = 100%, 500 = 50% and so on. InputStart and InputEnd controls the max movement of the physical fader, so setting these can give you "deadzones" at the ends of a fader, if you'r newer quite able to hit the max and min values. by default you would always want them on 0 or 1000 on a fader when using map1. If you're using map2 you might want the lower one to be a certain % above 0, so our recommendation would be to start at 50 (5%) or 100 (10%) and experiment from there, and keeping the max on 1000. OutputStart is the minimum value you want the fader to set OutputEnd is the maximum value you want the fader to set In the example above you will see them limit the output values to only cover the upper 50% of the parameter by using the values 500 and 1000. play around with these to fit your desired outcome range.