Using MG3 output as MIDI device in REAPER

1

Ok, I am not sure if this makes any sense, but here goes. In REAPER I would normally create a track with MG2 and use that as my master midi device, meaning that I would then be able to arm whichever MIDI track I was using to record in them. This is the way it still works in Logic. In REAPER, however, this option seems to have been lost with MG3, as I am only able to send the MIDI output of that track to other tracks using sends. Is there anything I might be missing?

Obviously, the quick fix is just to use the standalone app, but I’d rather have it all in the box.

This creates a number of complications, though it does allow for slightly more granular approaches if I use multiple instances—which I would rather avoid for the time being.

Thanks!

EDIT: I have fixed it for the moment by selecting the AU version of MG3 rather than the VST version. I have no idea why this fixes it, but it does.

1 Like
2

That is exactly the fix for it. The AU creates as virtual MIDI Guitar OUT that you can choose as you would any other (external) MIDI device.

Skärmavbild 2024-06-12 kl. 10.37.12
Skärmavbild 2024-06-12 kl. 10.37.121920×990 151 KB

Whereas the VST plugin does not create this virtual MIDI, and have to be routed directly to its target track instead.

Skärmavbild 2024-06-12 kl. 10.30.03
Skärmavbild 2024-06-12 kl. 10.30.031920×990 112 KB

This difference between the AU and the VST version of the plugin applies to all DAWs, but Logic does only show you the AUs, which is why you probably haven’t been confronted with this peculiarity there. In Ableton however, you can use these different functionalities together. I actually set up in Gig Performer with both an AU creating a general MIDI IN and another VST on the side for specific purposes - feeding a very particular chain (for whatever reason).

3

Thanks! I thought this might have been the reason. And you are absolutely right that this adds a layer of versatility—thanks!

1 Like