I set macro 1 to be a toggle and learnt it to the Omnisphere Orb button, which all worked fine. However when toggling the control in Unify it only toggles between 0.25 and 0.75, whereas activating it via my PUSH3 it can be toggled between 0 and 1. Is there a setting that determines this or is it a bug? See 2 states in pic
Unify's "toggle" and "button" control variants are special cases of the "stepped knob" variant, where the parameter range 0.0 - 1.0 is divided into some number of equal-width sub-ranges. For toggle/button, the number of sub-ranges is 2, so the sub-ranges are 0.0 - 0.5 and 0.5 - 1.0 (with some care taken to ensure they don't actually overlap at 0.5).
To get consistent results (especially with the stepped curve type), it's critical that each of the steps places the value in the middle of the corresponding sub-range, not on the edge. For toggle/button (or a knob with 2 steps), this means 0.25 and 0.75.
From your screenshot, I see that you have wisely chosen a stepped response curve with 2 steps, with the first step having the value 0.0 and the second 1.0. This curve will effectively transform the input values 0.25 and 0.75 to output values 0.0 and 1.0. The plug-in sees only the output values.
This is something on our 'bug' list already.
I get there are technicalities as to why it is outputting those numbers, but I think this is going to confuse a lot of people in future, so I'll try to figure out how we can transform the value when we know it's a toggle or momentary button without needing to make a special curve to handle it.
Yes, we will address this issue soon. Toggle needs to do min/max values - I tried to set up a toggle for octave switching and it kinda doesn't work right since you don't know what .25 and .75 of 2 octaves is. It will be fixed! 😀
Life is Sound / Sound is Divine
www.pluginguru.com
@pluginguruforums Temporary solution is to do what Shane suggests with the macro curve. If you do that it will still be compatible with future updates.
