I try to setup the Metagrid Pro Cubase Midi Grid.
While some of the buttons work (Play, Track selects, Range selects, Quantize grid, Zoom function) some very important buttons don’t work:
cc copy paste
transpose
velocity change
vel/cc ramps
I used the manual to install everything including generic remotes for metasystem1/2/3.xml and metasystem_macros1/2 as well as both Commands and Selected Channel in the MIDI Remote manager.
Maybe you know which of the xmls makes the not working areas work?
How can I repair my setup?
Yes, I forgot to copy the LE xmls to the “earlier presets” folder. I’ve done that now, started Nuendo anew and it is still not working for me.
I realized I cannot load the Metagrid presets when I’m in the Project Logical Editor when choosing a preset. My other presets that are not from Metagrid can be loaded and show what they do. Does that indicate that something is wrong or is that normal with these presets?
Are you sure you have put the macros in the corresponding folders - there is a difference for PLE and LE macros - and the macros you have mentioned are LE macros (not PLE macros).
This is what i have set up. Can you spot any mistakes or have other ideas?
So the metasystem_macros.xml & metasystem_macros2.xml are the PLE Macros? If so I couldn’t find in the Manual where to copy them to.
Yes it’s been there all along. In your screenshot its not in the “Earlier Presets” Folder as described in the Setup Guide. Tried both in the Logical Edit Location. My Location is called different (“Project Logical Editor”) which is probably a Nuendo thing.
What might be the problem: I cannot load the MetaGrid presets in the logical editor to apply them directly in Nuendo whereas if I make my own preset I can load it and use the apply button to use the preset without my iPad. Is that normal or is this where the problem is?
If your location is called “Project Logical Editor” then it is not the correct path I am afraid - this is for PLE macros (in MGP these are custom visibility scenes for example). LE macros are MIDI specific and have their own dedicated folder.
