The existing Keyboard Shortcuts list is extremely useful. A similar list showing MIDI CC assignments per profile would be equally helpful.
At present, there is no built-in way to see which MIDI CC numbers are already assigned within a profile. This makes it difficult to track available versus used CCs without keeping a separate manual record for each profile.
Use case:
When working in Studio One, custom macros cannot be triggered directly from MetaGrid Pro, so the available options are keyboard shortcuts or MIDI CCs. MIDI CCs allow access to a much larger number of controls, but they introduce a management issue. It becomes hard to remember which CCs are already assigned and which are still free.
Having a visible list of assigned MIDI CCs, similar to the Keyboard Shortcuts view, would reduce conflicts, save setup time, and simplify complex profiles that rely heavily on MIDI CC control.
Even better from my perspective would be an option to show the CC number on the fader/button separate from Text and other visible options. An extra bit of info that would really help in getting things mapped
Thanks for the detailed explanation and use case — this is a very valid pain point, especially in CC-heavy setups.
One important thing to clarify is that in MetaGrid Pro a control isn’t a single assignment — it can trigger a macro with multiple actions (keyboard shortcuts, MIDI, scripts, etc.), and MIDI CC is just one possible action inside that chain. Because of this, there isn’t a simple or reliable 1:1 “button → CC” mapping that we could list without making incorrect assumptions.
That said, we can reliably track which MIDI CC numbers are already used by CC actions within a profile, and one direction we’re actively considering is a helper like:
“Suggest next unused CC” when adding a MIDI CC action.
This would automatically propose a CC number that isn’t already used within the current profile (and channel), helping avoid conflicts without forcing users to manually keep track or introducing restrictive rules around CC reuse.
This approach keeps MIDI flexible (intentional reuse still works) while removing a lot of friction during setup. Thanks again for raising this — it’s solid input and very much aligned with real-world workflows.
This would be great, except if we’re are using multiple iPads. Then it doesn’t really work. Because what might be available on one iPad, may not be available on the other(s).
Maybe it would be better to just grey out the CC’s and note numbers (and velocities) that are in use. Then we can check on both (or all) of our iPads that the CC etc is available.
I run everything through Bome, so I just take a guess at what I haven’t used and then see if there is any activity in Bome.
