You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, recur will will instantly change a shader parameter to whatever value it receives from MIDI CC. This often results in a jumpy image when the shader has been switched, or edited using the keypad.
A solution for this would be to include catch up and relative modes for MIDI inputs.
In catch up mode, the shader parameter does not update until the MIDI CC input crosses its current value. For instance, imagine I changed shaders and X0 is on .5 but my MIDI knob is currently at a CC value of 0. With catch up activated, the shader parameter would not begin updating until the CC value crosses 63, giving the knob parity with the parameter.
Relative mode is similar but more immediate. A parameter would begin updating immediately when an offset CC is received, but only at a relative value to the MIDI CC. So if X0 is .5 and MIDI knob is 0, X0 will immediately begin changing as I increase the CC value, but starting at .5 instead of 0. When CC reaches 63, X0 would be now at 1, but full range of the knob isn’t restored until the CC reaches 127 and catches up to the parameter.
The text was updated successfully, but these errors were encountered:
Do you have any examples of open source projects that do this so that I can get some inspiration for how to implement this? I really need it for my customisations too now..
As of now, recur will will instantly change a shader parameter to whatever value it receives from MIDI CC. This often results in a jumpy image when the shader has been switched, or edited using the keypad.
A solution for this would be to include catch up and relative modes for MIDI inputs.
In catch up mode, the shader parameter does not update until the MIDI CC input crosses its current value. For instance, imagine I changed shaders and X0 is on .5 but my MIDI knob is currently at a CC value of 0. With catch up activated, the shader parameter would not begin updating until the CC value crosses 63, giving the knob parity with the parameter.
Relative mode is similar but more immediate. A parameter would begin updating immediately when an offset CC is received, but only at a relative value to the MIDI CC. So if X0 is .5 and MIDI knob is 0, X0 will immediately begin changing as I increase the CC value, but starting at .5 instead of 0. When CC reaches 63, X0 would be now at 1, but full range of the knob isn’t restored until the CC reaches 127 and catches up to the parameter.
The text was updated successfully, but these errors were encountered: