Midi Memory

Have any feature requests? No promise they'll get to Reason Studios, but you can still discuss them here.
Post Reply
User avatar
AttenuationHz
Posts: 2048
Joined: 20 Mar 2015
Location: Back of the Rack-1

14 Jun 2017

Simply put when you set automation it remembers what the default state of a control is.

What I would love to see and have not seen it at all in any DAW is being able to set a control to remember what its default state is. When you edit a remote override in between sessions there is no memory for that CV value on the midi controller. Unless it has call back function and presets to set the controls automatically, really expensive studio mixers have this. What if the control knob in reason could flash green when you move the midi control to that value and so remembering the value that it was set to previously.

When you save a session the remote overrides are stored with the session but if you change sessions and set new overrides for completely different devices. Or have faders on your controller setting the volume for your mix when you switch sessions after changing all the faders the first session will comply with the midi data of the other session as soon as you move the fader to the position it was in if you can remember the position it was in.

If there was an indicator of some kind on a fader knob or button in the session lets say all faders turn amber when they don't match the cv number sent from the controller and when you have the correct cv value set on the controller the fader flashes green and the indicator disappears until you change the value again. One of the cons when working with midi controllers and remote overrides is no memory for it. This would be a passive thing with the sole purpose of reminding you what the value is and should be.

:thumbs_up:
It is not too much of an ask for people or things to be the best version of itself!

Post Reply
  • Information
  • Who is online

    Users browsing this forum: No registered users and 5 guests