Notifications
Clear all
Topic starter
September 2, 2022 5:42 pm
It would be handy to optionally store the MIDI CC number assigned to the macro controller for an individual patch.
System:
Windows 10 Pro 64Bit V 21H1(Build 19043) German
AMD Ryzen 9 5900X
32GB Ram
Tascam US 16x8
Cubase 12
September 2, 2022 7:15 pm
It would be handy to optionally store the MIDI CC number assigned to the macro controller for an individual patch.
You can do this in the Unify plug-in (including the built-in one used for embedded Unify instances), but not in the stand-alone app.
- CC assignments for the stand-alone app are intended to match your chosen MIDI controller, which doesn't change on a per-patch basis.
- CC assignments for the plug-ins are intended to match whatever CC modulation sources you use, which may be patch-dependent.
Robert.P reacted
September 2, 2022 8:05 pm
- CC assignments for the plug-ins are intended to match whatever CC modulation sources you use, which may be patch-dependent.
I was also thinking about it, thanks for letting us know that it works!
Topic starter
September 3, 2022 1:34 am
CC assignments for the plug-ins are intended to match whatever CC modulation sources you use, which may be patch-dependent.
Thanks Shane - didn't know that!
System:
Windows 10 Pro 64Bit V 21H1(Build 19043) German
AMD Ryzen 9 5900X
32GB Ram
Tascam US 16x8
Cubase 12
September 3, 2022 1:47 am
CC assignments for the plug-ins are intended to match whatever CC modulation sources you use, which may be patch-dependent.
Thanks Shane - didn't know that!
It wasn't always this way. I added this capability when we started to make patches with embedded Unify instances driven by MIDI files (in MIDIBox) containing CC data. Saving the CC numbers as part of the patch was the only way to make such patches play consistently, even if the user changed the current CC assignments for the Unify stand-alone.
Clark_Parker reacted