19 Mar 2018
Carly, where could you change the range? Dunno if Reason has an option to increase the 127 limit to the 32 bit maximum value... Though for an encoder, the 127 range makes more sense. The super fine details would be more useful for a potmeter, or maybe touch. Cause encoders rotate endlessly. BUT! One more option would be building a midi controller that works as follows: increasing and decreasing buttons for each digit. So, one pair adds +/- 0.00001 with each push, the next +/- 0.00010, etc. Or similar with a button-encoder, only with each button press, it would jump one digit, and then it could be increased/decreased with the encoder.
Think of the VMG-01 RE. Though after a digit would reach above the number 9, it would increase the digit above with 1, i.e. adding.
EdGrip, it depends on how the MIDI controller was coded. If you look up building a MIDI controller with an Arduino kit, you'll see, that details can either be coded, or set up in the host DAW if everything is true.
How about merging CV and Automation? Whatever knob you'd automate, Reason would reach under the hood with smooth 32 bit values. And the possibility of the sequencer generating CV signal, so we can draw it ourselves!
Selig, at the end of the day, Automation, CV, Envelopes, whatever, it's just about values. xD ...and computers are just 0s and 1s. Okay, they are different, but what they have in common is that they are going to change some other value.
antic604, I think it's what you think it's about... All in all, accuracy, access to fine details.
In the far past, 2010, I asked for setting up display values that we like: example, audio level on any device: 0-127, 0-100 % or dB