Hi there!
Long time MG2/MG Bass user here and also MG3 Hex user. I am blown away by the new features I’ve tried in the MG3 beta and there one “feature” I keep wishing for as I try to work with the new version.
Sorry to piggyback off of this other person’s feature request, but I can’t help but wonder if there’s bound to be some overlap between the 7,8, 12 string (and so on) crowd and what’s atop my wishlist.
For context my current setup is running 6 separate instances of MG2 to convert the audio from six separate channels (input from my SY-1000) to midi and I have these combined (and split) various ways in my host DAW (Ableton).
Essentially I would love to have a lightweight MG3 plugin that I can run multiple instances of and feed (post-fx) audio from channels in my DAW. I could see it working a couple of ways:
Option A (this would be my preference)
A lightweight MG3 plug-in (ideally VST3) that is pretty stripped down, favoring pitch to midi conversion (switch for Monophonic or Polyphonic processing), MPE support and some other “essentials” (e.g. sustain function able to be mapped to Midi CC controls in the Host DAW, Pitch range to limit ghost notes, etc.). You can run as many individual instances as you want (or you CPU can handle anyway :P) and feed them audio from the individual string channels setup in the DAW.
Option B
Similar concept but the multiple plugin instances could have some interconnected features on the backend (to save resources, etc.). I like the way the MAutoAlign plugin (by Melda Productions) implements “groups” so you can, for example, work with a set of inputs such as a mic’d drumkit to get the best phase cohesion from several sources at once. I know there are other plugins that take this kind of “hivemind” approach on the backend, but the Melda one is the only one that comes to mind right now.
To add more detail about my use case, I actually prefer to do much of the audio and midi routing in my host DAW, either with native effects or third party plugins, and so even the noise gate for the “lightweight” version would be unnecessary for me as I prefer to tweak that myself with plugins. Currently I have each instance of MG2 fine tuned to the individual string to reduce ghost notes and re-triggering, etc. I use automation in Ableton to mute audio input to the various instances of MG2 during performance and also to manipulate the midi in various ways—post MG2-before it’s handed off to virtual instruments and so forth. MG3 has many impressive bells and whistles but beyond the core pitch-to-midi conversion and new MPE functionality I find that most of those things I prefer to manipulate myself outside of MG.
I may sound like a crazy person after that big spiel, but ultimately the reason so much of my workflow is achieved outside of MG itself is because I am using several external audio devices at once and leveraging Mac OS Aggregate Device to combine them and present them all to Ableton (I’m running two SY-1000s simultaneously as well as other Boss/Roland gear).
The way MG3 Hex currently is designed to communicate directly with your chosen audio interface (GP-10, SY-1000, et.) doesn’t allow for the same possibilities as my previous setup with multiple instances of MG2. For me I would much prefer the ability to feed each plugin audio processed by my DAW and combine and route the midi afterwards.
I realize that exploring this request might contradict the all-encompassing MG3/MG3Hex powerhouse approach, and possibly be more cumbersome for the average user to implement, so I certainly want to acknowledge that. I also want to say that the many new features are awesome and there’s obviously been an incredible amount of work put into the new version(s) so far! Truly amazing stuff! Keep up the great work!!!
Cheers!
) and only a few minutes ago I tested this amazing 12-string with the iPad version of MG3! 
