Hoping someone can clear this up for me. I’m in the processes of attempting a transition from Cubase to REAPER. I just got REAPER connected to MetaServer and went through the setup, but I’m confused about how limited it feels compared to the Cubase integration.
What I did so far:
Downloaded the REAPER keymap through MetaServer and imported it into REAPER’s Action List (Key map… → Import shortcuts/custom actions)
Confirmed I now have 382 “Metasystem” macros sitting in my Action List
Checked REAPER’s Preferences → MIDI, and I do NOT see a “Metasystem - Reaper - In” port anywhere in the input list, only my old Cubase ports show up there
In MetaServer itself, REAPER shows up with a green “Connected” status and the version number, so it clearly sees REAPER is running
Create a new profile in Metagrid for REAPER
So here’s my confusion: with Cubase I feel like I basically have access to the whole commands list, but with REAPER it seems like I’m stuck with these 382 pre-made macro slots that are all empty placeholders I have to fill in one by one. Is that really how deep the REAPER integration goes right now, or am I missing a step somewhere? I keep expecting there to be a way to just browse/search REAPER’s full action list from inside a MetaGrid button, the way it feels like other DAWs work, but I’m not finding that anywhere.
Also curious if the missing MIDI port is actually a problem or not, since MetaServer says REAPER is connected without it ever existing in my ports list. Are those two things related, or is the “Connected” status happening through something else entirely on newer MetaServer versions? Should I be seeing MetaServer REAPER in the Preferences > Midi In list of input devices?
Any clarity appreciated. Feels like either I’ve got a gap in my setup, or my expectations for REAPER support are just off compared to Cubase. Thanks!
Thanks for laying out the setup steps. We need to check the imported action content and the MIDI route separately.
Please share your operating system and the exact MetaGrid Pro, MetaServer and REAPER versions, plus the filename and source of the imported keymap.
Could you also show:
One of the imported Metasystem actions
MetaServer’s REAPER MIDI settings
REAPER’s MIDI input list
One MetaGrid button’s selected REAPER command
Please tell us what happens when you press that button.
The green Connected indicator alone does not confirm that the selected command is reaching REAPER. We need the version and setup details before confirming whether a port is missing, an installation step is incomplete, or the requested action browsing goes beyond the current integration.
Please hide personal information in screenshots and keep diagnostic packages private.
Hey, thanks for the quick reply — turns out the issue on my end was simpler than I made it sound: I hadn’t enabled the REAPER toggle in MetaServer’s MIDI tab, so the port was never actually receiving anything from MetaGrid even though it showed as Connected. I’ve turned that on now and confirmed the button press is reaching REAPER correctly, so that specific issue is resolved. But since you asked, here is the system information:
One thing I’m still curious about, separate from the bug: is the 382-slot macro keymap the full extent of the REAPER integration right now, or is there a path to something closer to what Cubase has (direct access to the action list, or instantiating a specific plugin from a button without pre-wiring a macro slot for it)? If this is it for now, any tips for instantiating plug-ins without using up most of the 382 slots I have available on that. I’ve got probably 300+ plugins I would like to map. Also, are there plans to expand Reaper integration in the future ?
Hi,
I don’t use the dedicated Metagrid - Reaper DAW integration Macro Structure.
There are different ways to call - for instance - Plug-Ins! (You have to understand thus Reaper is “tag-able” in nearly any place - and this allows you to customize it to your needs - (compared to the fully inflexible CUBASE Structure)
One way to call an Plug IN is:
with the key CMD “Shift + F” to open the FX Browser.
This can be one Button in Metagrid to do so (Macro sends that Key-Command “Shift + F”). (by this the FX Browser opens and the cursor is placed in the "search field of the FX-Browser, Than a second Metagrid Button is sending a Text-String - say “MAnalyzer” (It’s a MeldaProduction Plug-In - may be not on your system, or better “ReaEQ”
see what happens. - try just sending “Rea” or only “EQ” and see what happens, too !?!?
got it?! (Send a Text having just Vendors in mind “Arturia”, “Sonible”, “SSL”, (or any other maker you own PlugIns from)
You can combine these two commands also into one Metagrid Button if you like (create a Macro which sends first the key-command to open Reapers FX-Browser (Shift + F), than place a second action - a (Pause) of 0.100 sec - and as third entry of this Button the name of the PLUG-In which you like to trigger! (ReaEQ))
Metagrid classes of Actions are: Keyboard Shortcuts, Modifier Keys, Mouse Actions, Text, Pause, Active Application, etc…
But watch out that there is no sub category in the FX Browser previously selected, this might cause irregular results (Hierarchy is one step off)
When you understand this concept you can use the “tagging” in a lot of place (I tag my Tracks with 3 letters to categorize them, with just one Metagrid button pressed I select all Tracks containing Drums or see only Tracks with Harmonic Structure or call just Brass-Sections or Orchester Groups.
Very fast, and you can focus on the important Parts! (Track and Mixer are displaying
Another way is: You can create Reaper Custom Menus, which then are accessible by (At least on MAC OS) Metagrids Menue-Commands Macros!
Yeah, I’ll try the FX Browser search method. And when you say tag-able do you mean in any place other the track name? There’s this script called Track Tags by Bird Bird that allows you to quickly do this sort of thing without having to actually rename your tracks. This is something I always kinda disliked, having to re-name things to something specific to run searches on it. I would rather hit it with a sort of tag and keep the name whatever I like. Is this possible in Reaper without the Bird Bird script. I’m kinda new to Reaper (in case you couldn’t tell). Grateful to whatever tips you can share.
Hi Jeff,
I don’t know any other way - only to use “text-tags”.
The script you mention is quite nice - when you are a mouse user - I like to use Metagrid for most of my workflow!
I use two I-Pads - one with a more central tasks (for reaper, or Mac-Operations), while the other is for deeper level actions for all Apps I’m using often (RX11, SpectraLayer, Cubase, Reason, Reaper)
(I have 3 Grids 9x12 just to call my Plug-Ins in Reaper)
there is also another Grid for the Text-Tagging and actions to use them.
Just go with the cursor to the end of the “Track name” and push a Metagrid Button sending (_dr) as Text to this Track, sometimes I mark them with more than just one Text-Tag.
(Reaper has a function to Auto-color - Tracks by Text-Tags (Theme depending - this can also effect The Fader Knobs), so it can have a much wider user friendly impact - (But this is entirely my way to do things - and I know Reaper by just 40% - I assume
All my best - Michael. (below screen dump of a few Grids)
Hi Jeff, glad enabling the REAPER MIDI toggle got the commands working!
To answer your remaining question: the current dedicated REAPER integration uses those 382 assignable macro slots. Actions, custom actions and scripts are assigned to them within REAPER; MetaGrid currently doesn’t browse REAPER’s full Action List or plug-in library directly.
Since you’re on Mac, you can also use MetaGrid’s Menu Command action to trigger REAPER menu items without using a macro slot. Our REAPER guide covers both methods.
For your plug-in collection, Michael’s FX Browser suggestion lets you keep the slots for other workflows. A single MetaGrid button can open the FX Browser using your assigned REAPER shortcut, pause briefly, type a distinctive plug-in name and then confirm the desired result. Check the browser’s filter and search-field focus, and test one button before duplicating it for other plug-ins. These are keyboard/text macros, so they don’t consume the 382 REAPER slots.
REAPER integration expansion is on our future backlog, but we don’t have a confirmed release or date to announce yet.
?
