Metagrid Pro - Editing Optimization ideas and discussion

[aaronbrownsound]

I’m digging into the editor and have a few requests that would streamline creating templates.

1. EDIT: This exists. It’s the Arrow on the right side of the text, but it requires tapping it, then selecting the text. I want it to be automatic or a preference for single naming as this isn’t much faster:

   1. Allow macro titles to also be the text label. It would speed up time to have macro title be the text label and also show the actions for midi CC and Notes all in the same dialogue. Some method to have text inherit that would be great.

2. Include app resources download with the metagrid server download. I had to go find those after instead of being an all in one download and the directions don’t have a link to these files.

3. Update installation steps. For example step 2 for cubase with the “MetaGrid Pro folder into the following location” doesn’t exist. So what do I copy there? The guide of the ReadMe.txt conflicts with the MIDI & DAW setup and I don’t know the right installation method. For the Midi Remote is it just the .js file because that isn’t showing up for me after a restart… It all needs a rewrite to be at parity and smooth, and a script would help immensely to copy things to the right spots, and adding examples of the files and folders with snapshots is critical due to the complexity.

   
   
   

4. Allow Copy and Paste via keyboard shortcut. I can’t use a bluetooth keyboard to copy and paste buttons, but it does work on text. It would be faster to stay on keyboard for these things.

5. Add content manager as an always visible view: The UI is very confusing to navigate while editing and I think it’s because it jumps around unless I’m in the target app. I have to hit either Desktop-ContentManager-Cubase-Workspaces-MYGRID or OMNISPACE-TopLeftOmnispace button?-Content Manager-Cubase-Workspaces-MyGrid. Both are awkwardly 4 clicks that change everything to get to my target grid. I suppose the idea is to get users in the app they are editing the grid for to leave it open automatically, but that isn’t initially intuitive and trying to manually find things is tough. Generally I want to dig into content manager and find the thing I want to edit. Mainly, every button I hit adjusts every single thing on screen without coherence so I’m lost every time I hit a button unless I’m in edit mode.

6. Updated Quickstart. The onboarding is extremely confusing to me as a new user. Having a single guide from start to finish showing how apps auto connect, to connect prior to editing a grid, how to add a grid to existing template/workspace

7. Ability to load presets in the content manager. Currently I go to presets, download a cubase option, but if I have one it prompts me with a new question to install as workspace or grid which confuses me. When I try to select my import destination of Cubase it asks to replace it instead of using a second workspace in that CUBASE area even though I made a secondary workspace. Trying to use 2 presets becomes risky and error prone. It would be great to instead be able to load those in the content manager like importing and exporting our own presets so it’s integrated in the app and fluid. As it is I can’t figure out how to use the gestures and generic remote together without blowing out my changes to it.

8. Base template with WS, SCENE, GRIDS we can copy and paste. Currently the onboarding to create a valid workspace, with grids that interoperate, and have scenes takes hours. A very handy template would be one that has these basic structures built in, likely similar to the single onboarding guide I’m talking about to get across the core concepts.

9. Ability to change the bottom left bottom from omnispace to content manager or a specific app. I don’t want to use Omnispace and it clutters up my flow.

10. Ability to hide the left bar. I want full screen and quick ability to hide the left panel.

11. Onboarding scripts to optimize prep. The amount of work to get Windows prepped is sturdy with all the settings and options. It all feels very scriptable to install things where they need to be rather than manual. Shortcuts could copy the proper files to the right directories, and surely the loopMIDI ports could be generated given the complexity. One wrong assignment and it’s all broken. I’m still not sure I put the logical editor or project editor files in the right place and it’s fairly convoluted. The overview of the installation has terminology I didn’t yet understand so it’s confusing from the start.

12. Export to Json/XML. It would be amazing to be able to use an LLM to quickly re-organize and adjust our templates. I’ve done this in touch osc using .xml and it speeds things up 1000%. If we can get the ability to import and export .xml structures we could use it to generate complex grids extremely quickly then use the interface to adjust further.

As a note for people getting into the editor, I’m realizing is there is a specific workflow to metagrid unlike others and adhering to that methodology smooths things over a lot instead of fighting it. First, open the app you are building the grids in or navigating the UI becomes unwieldly! It generally works best by using the shortcuts to first build the base for a single button, single grid navigation (secondary action), look and style, then copying and pasting those in bulk, and finally going assembly line style in each element one at a time for each aspect. This way you can leave the editor up while selecting buttons and quickly change things. So, do all icons for all buttons, then do all text for all buttons, then do all Macro CCs for all buttons.

[aaronbrownsound]

An addition. I see now after reading it a third time the Logical Editor (LE) and Project Logical Editor (PLE) files go in similar structures. A short diagram and snapshot like this up front would have made this clear. Essentially if it can’t be automatically copied to the right spot, then showing a general overview of where each file laneds (even it not 100% right per user) will say more than all the words of the guide given all the steps IMO.

[aaronbrownsound]

Another big one, streamline macros or rename to actions with value visibility at top level.

When onboarding I had no idea where to add a simple midi note or CC. The current flow is Macro, Platform (Win), Name Macro (doesn’t show as label), Actions Add, Midi Note On, top, select from list (no ability to type in values or filter), hit X (which saves but feels scary as there is no apply or save button).

To edit it’s select button, tap macro, tap actions, tap editable value, manually select value, click x, repeated.

What would speed this up is allowing keyboard input for values, or skipping the whole embedded macro for simple one off actions which is 90% of what I want to do. I want a simple action option that just shows the note on, duration, and note off and allows keyboard input to adjust it or click it to show a dropdown or enter a value. That way the flow is Button - Action - Edit value - DONE. This would also show the CC while editing instead of having to hit the macro, to enter another menu just to see the value.

That is 3-4 steps instead of 8 steps and that really adds up over time here. Not being able to see the basic values of buttons without digging into macros is a major workflow slow down.

[aaronbrownsound]

Option for double or Triple tap to show/hide value slider bar:

It would speed up going between arranging butons/resizing grid mode and value mode without having to hit the 3 sliders, or the arrow to hide it. It’s finicky going between modes as it is. Having a single toggle to both show and hide like double/triple tap would enable smooth transition between each mode to speed it up.

Partially because I often hit “DONE” in the top right on accident when in value mode because it feels like I’m “done value editing” but done exits edit mode all together being a frustrating edit mode. Having a single toggle prevents all that to streamline the flow.

[aaronbrownsound]

Multi-select - Auto snap function.

I’d like to select a set of buttons and have a function to auto snap them together to remove space. It would also be cool to allow them to auto fill the space I’ve dragged to.

Came up when resizing things and now there are a bunch of gaps I can’t close quickly.

MULTI-SELECT - Bulk edit a parameter in sequence.

For auto sequencing CC #s or Note On/Off #s to cascade the changes. This would save a bundle of time to quickly set multiple values of actions in order.

[aaronbrownsound]

NOTEON&OFF W/DURATION - MIDI action request

Expression maps tend to need a note on and note off. However with metagrid that’s nearly instant and often you need a delay between the two. The lowest pause in metagrid is too long for this with the time being .1 (100ms). Hacks involve adding a text action to get a variable delay while that occurs, but that’s sloppy. So the request is to add a new midi type of note on and off with a duration. One simple action that does Note On, Duration value for how long it’s held, then note off with the same note. That way it’s one simple action with a tunable duration of 10-100 ms (default 50ms) to specifically work with keyswitches that tend to want both triggers.

Other optimization, when selecting note on and note off they look exactly the same with no indication which you have selected. When selected I still want to see if it’s a note on or note off action for clarity. Also, if we don’t get the new action, it would be nice to copy and paste a note on event and change it to note off type to save the extra work.

[aaronbrownsound]

DEBUG VIEW - A view that shows the actions or CC#s or NOTE#s on the icons. Important when building complex layouts but not wanting that info on the actual buttons. Particularly when that info is embedded in macros which requires 3 clicks to see. Being able to know which CC or NOTE is on each button and toggle would be invaluable. Both useful when selecting a button, or a view that is on every button that can be toggled to see those action values in some way.

[aaronbrownsound]

MACROS - Clear onboarding for process required.

I can’t see anywhere on the macro list where it mentions building generic remotes for the macros. Metasystem 1,2,3 were there with their midi inputs and outputs, but not the .xml. I had the macros in the metaserver setup and that’s all.

Please add full steps for macro remote prep so users see it needs to be in metaserver setup, and in the generic remote, using metasystem cubase in, and import those XMLs.

The first process of assigning a Keyboard Shortcut Macro - That triggers a Project Logical Editor viewset - that is then triggered by metagrid button - which uses the Metagrid: User Macros - Which is Macro 001 - Which links to the generic remove Macro 001 - and is assigned a commaned in the device to then trigger that macro is very difficult.

Here is an example of all the hooks required to get the macro to work. It’s a lot to prep and snapshots are essential here along with robust guides where each hooks in on metagrid and Cubase. Here the PLE preset is made, which gets called via the key commands as part of a macro, then the generic remote holding metasystem_macros.xml data with macro_001 trigggers the command for that key command macro. Then when Metagrid uses the Metagrid: User Macros Macro 001, and the midi is set up correctly via loop midi and in cubase midi, it triggers the macro.

Specific snapshots that work.

Additional update: This is the better method to use Metagrid to trigger macros that control visibility. It doesn’t alter selections and is faster.

Cubase Visibility Workflow Summary

1. Logic (PLE Presets): Two Project Logical Editor presets control the view. First, a global preset hides all tracks (Hide Track: Enable). Second, a specific preset unhides tracks matching your criteria (e.g., String/Color) by flipping the visibility flag (Hide Track: Disable).

2. Execution (Macro): A Cubase Macro in the generic remote (imported from the metagrid macros .xml) triggers a keyboard shortcut macro that chains these two presets together, refreshing the view instantly without altering your track selection.

3. Control (Metagrid): The macro is linked to a generic remote slot (Metasystem Input), allowing a Metagrid button (User Macro) to trigger the view change via MIDI, bypassing keyboard shortcuts.

[MetaGrid_Admin]

Thank you for taking the time to write this and for putting so much effort into exploring MetaGrid Pro in depth. It’s clear you’ve approached it seriously and tried to integrate it into a real, production-level Cubase workflow. That kind of detailed feedback is valuable to us, even when it highlights friction or mismatched expectations.

MetaGrid Pro is intentionally a deep application. It is not designed as a DAW-specific controller, a MIDI-only surface, or a quick-setup remote. It is a general-purpose automation system that can be used across different applications, platforms, and workflows. That design choice influences the editor, the object model, and how concepts like grids, workspaces, actions, and presets behave.

Buttons in MetaGrid Pro are not single-purpose triggers. A button can behave as a momentary control, a latching switch, or a menu, and it can evolve over time. It can trigger MIDI actions, keyboard shortcuts, application-level actions, or chains of actions. This consistency is fundamental to keeping larger and more complex setups maintainable.

It’s also important to clarify that MetaGrid Pro is not MIDI-centric. MIDI is only one of several supported action types, and many workflows do not rely on MIDI at all. Because of that, the editor and data model cannot be optimized solely around MIDI-style assumptions without compromising the universality of the system.

Some of the friction you describe comes from discoverability rather than missing functionality. A number of advanced features already exist, such as batch editing of MIDI values, hiding the sidebar or individual sidebar items (including OmniSpace), and quickly accessing Content Manager via shortcuts and gestures like double-tapping the grid name in the top bar. These workflows are described in the User Guide, but we understand they are not always immediately obvious when first learning the app.

We’ve made a strong effort to provide a comprehensive User Guide that explains every object, feature, and concept in depth. Given the scope of MetaGrid Pro, this documentation is not an afterthought but a core part of the product. Many advanced workflows, shortcuts, object behaviors, and setup details are explained there because surfacing all of that directly in the UI would quickly overwhelm users. A fully guided, DAW-specific onboarding flow inside the app itself is not realistic for a tool that is intentionally broad and flexible.

Regarding presets, backups, and imports, it’s important to clarify how the system works. MetaGrid Pro never overwrites grids or workspaces silently. Any operation that could replace existing content always requires explicit user confirmation. During import, you are always prompted to choose whether to create new content or replace an existing grid or workspace. Replacement only occurs when a specific target is selected and confirmed by the user. The system is designed to be conservative and safe by default.

Where confusion can arise is in understanding the scope of what is being imported. Grids, workspaces, presets, and backups serve different purposes, and if that distinction isn’t fully clear yet, import prompts can feel more risky than they actually are. In practice, MetaGrid Pro gives you control at every step, but having a clear mental model of what a grid represents versus a workspace makes those choices much easier and less stressful.

Some of the points raised also relate specifically to Cubase workflows. Cubase is particularly complex when Generic Remote files, Logical Editor presets, Project Logical Editor presets, and keyboard shortcuts are all involved. While MetaGrid Pro must remain DAW-agnostic, clearer diagrams, better alignment between guides, and more visual explanations of how these pieces fit together are reasonable areas for improvement.

In terms of editing speed, MetaGrid Pro is designed around a methodology that differs from many controller apps. It works best when you first build one correct element, then duplicate it and refine properties in focused passes rather than completing one button fully before moving to the next. Once this workflow is adopted, large grids become much faster to build and manage, but this approach is not always obvious at first and can feel unintuitive coming from other tools.

None of this means the feedback is dismissed. There are valid points here around documentation clarity, discoverability, preset handling clarity, and visibility into complex configurations. These are areas where improvements can be made without compromising the core architecture.

One additional request for the future: if you have further feedback or feature suggestions, it would help us greatly if they were split into separate, focused forum posts rather than a single large thread covering many unrelated topics. From a product development and tracking perspective, it’s very difficult to evaluate, prioritize, and respond meaningfully to long streams of mixed concerns. We genuinely value the input, but handling it in a more structured way allows us to engage with it more effectively.

MetaGrid Pro deliberately prioritizes flexibility, consistency, and long-term scalability over immediate simplicity. That trade-off is intentional, and it’s what allows the same system to support very different workflows without fragmenting into multiple modes or assumptions. Once the underlying model clicks, the system tends to become far more predictable and powerful.

Thanks again for the time and thought you put into this. Feedback like this helps highlight where expectations and design intent don’t always align, and that insight is useful as we continue refining how MetaGrid Pro is explained, documented, and evolved going forward.