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
one of the diffuculties in using midi, is keeping track of midi values, In realearn we have the find source or find target which is great...
but if we want an overview , or gauge, what midi channels/values are still free and unassigned.
As time goes on and we ever increase our CC mapping, with other controllers and other software we may use... we can inadvertently trigger events unintentionally... im sure we've all dealt with that issue
if it were ever possible to output every source element, from every realearn instance, on every project loaded, with some order or naming convention... would go a long way to keep track of issues.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
one of the diffuculties in using midi, is keeping track of midi values, In realearn we have the find source or find target which is great...
but if we want an overview , or gauge, what midi channels/values are still free and unassigned.
As time goes on and we ever increase our CC mapping, with other controllers and other software we may use... we can inadvertently trigger events unintentionally... im sure we've all dealt with that issue
if it were ever possible to output every source element, from every realearn instance, on every project loaded, with some order or naming convention... would go a long way to keep track of issues.
thoughts about it welcomed
Beta Was this translation helpful? Give feedback.
All reactions