First Question: When I use dropout protection, which I usually do, the MG 3 Window tuns to grey fog and says, my buffer size is unsupported. However, I am using 128 samples - only with dropout-protection buffer of 2048, which I regularily do. Unfortunately, the warning is true… If I record an instrument track under these circumstances, the latency is high, certainly not 128-sample-like…So I have to change to “dropout-protectionless” use. Will this change?
Second question: If I try to follow this video-tutorial: https://www.youtube.com/watch?v=gBhukhxEDq8
I cannot configure the new “Keyboard”=MidiGuitar-Device the right way, because I never see the “Midi Guitar Out” from which this device should receive data. Off Course, on Windows, I cannot choose the AU-Version, only the VST-Version of Midi Guitar 3…Does that mean, that MPE is impossible on Studio One 7? Thanks for an answer!
I’m neither a Studio One nor Windows user, but on macOS you can configure either the AU as a “fixed” device or the VST2/3 versions to send MIDI directly from the plugin/track. I can’t imagine why the VST version would be all that different in Windows.
There’s a fair bit of info on here about using Studio One with MG3. You should be able to find all the answers you seek in that regard.
I don’t know about the dropout protection thing you mentioned but maybe you should disable it for the purpose of using MG3 for the time being.
First Point: Yes, I can send Legacy-Midi directly from the VST in Studio One, but not MPE- Midi. This is mentioned in the video I linked in my first post. As I have mentioned before, the method to get MPE working via configuring a new device, which is also shown in the mentioned video, does not work on my (Windows) machine, because no „Midi Guitar Out“ shows up. My question was whether I did something wrong, or whether MPE is not available on Studio One (Windows). If not, then for me, this would be a very obious feature request.
Second Point: Of course I can skip dropout protection, this is not hard to do, but has unfavourable consequences (considerably higher CPU load). My question was, whether the non-usability in connection with Midi Guitar 3 will be fixed in the future or is it inevitable? If it is inevitable right now, then it would, for me, be a feature request.
That being said, the vastly improved tracking makes Midi Guitar 3 nevertheless very, very attractive.
I’m afraid that not Jam Origin has to change anything but Presonus in their Studio One software. Why don’t you just use some of the free DAWs to check if there is a huge difference between MIDI 1.0 Legacy and MPE?
Edit: when I watched LoFiLeif’s video I was wondering how complicated a DAW can be…
Works fine with “Waveform Free”:
and “Luna”:
and “Cakewalk”:
The DAW guide you posted was for macOS so I don’t think you could extrapolate much from that.
Ok, so you’re after MPE and on you’re on Windows so you might need to use MG3 standalone (use the MIDI GUITAR MINI preset) and some third-party virtual MIDI software (I think most people use LoopMIDI but hopefully a pro Windows user can chime in). That should get your MPE data into Studio One. At least that’s what I’d try if I was going to use Windows for audio-MIDI.
This might also render your dropout protection issue solved for the moment.
I hope this answer adequately addresses your questions. But the only person who can address questions on future software changes is the developer so please understand that this advice is only to help you get up and running and nothing further.
There is a “second” part for win that clearly states that MPE mode isn’t possible. LoopMIDI works fine with the DAWs I have on my win Laptop.
MG3 Standalone via LoopMIDI into Cubase:
Well, this works really fine! No I can finally start practicing the interaction with synths…Works rather nice with Pigments…
Thank You very much!
Hi @Captainzero, I haven’t been able to get it to work in Studio One with LoopMidi. Would you be kind enough to share your exact steps? I would be very pleased 
Have you tried the MG3 standalone (+LoopMIDI) setup as well?
This response is a little confusing. There is no reference to Windows in the linked video. It simply indicates that there is a different approach to using VST2/3 in Studio One 6 (on macOS) as compared to using the AUv2 format, which provides a virtual MIDI port and can be manipulated as a MIDI device in the DAW. This is distinctly different to the way the VST2 and VST3 work. But perhaps the routing possibilities are the same in SO6 between different OS platforms?
Anyway, at the end of the day, it seems we’re recommending the same solution to the OP and other Windows users: MG3 Standalone + LoopMIDI.
Correct @Vaultnaemsae
There is no explicit reference to either platform really. Instead it focuses on the difference between th AU functionality (creating a Virtual MIDI OUT that can be used to create the MPE enabled keyboard) as opposed to the VST3 MIDI OUT that is sent “directly to track” and don’t show up as an alternative when you want to create a new “Keyboard”. And the reason for why you need to create that Keyboard in the first place, was that it was the only place I could find to MPE enable this MG3 MIDI output.
But since AU is a Mac thing, I guess there could be some way of construing this as a Mac vs. PC thing. But it really isn’t. It is AU vs VST3.
@LoFiLeiF @Vaultnaemsae @anjo : I will try to sum up exactly what I did, and what worked to get MPE running on Windows 11. it is sort of a “how to…”:
-
Download and install loop Midi by Tobias Erichsen here: loopMIDI | Tobias Erichsen
-
start LoopMidi. If no port shows up on Your machine, create one using the “+” button on the bottom left. The window should look something like that:
- Start Midi Guitar 3 Standalone. Choose “Midi Guitar Mini” as a starting point and choose loopMIDIPort as Output. Like this:
- create a new external Device in Studio One. As a starting point, choose “new keyboard”. This makes no sense as a name, so rename it. Let the new device receive from “Loop Midi Port”, and don´t let it send anything. Enable MPE. On my machine it looks like this:
- Set up an instrument track in Studio One. Chose the new device receiving input from MG3 standalone as instrument input. I took in this example Pigments as an instrument. It should look roughly like this:
- Don´t forget to activate MPE in the instrument window too, like this:
Now, MPE should run smoothly, and You can also use dropout protection any way You like! It is really fine to use, because if You set up the Windows Task Bar appropriately, You can very easily switch between Studio One and MG3 Standalone if You need to adjust something (i.e. if You change to an instrument that should not receive bends, etc.). And now play!
@Captainzero, thank you for describing in detail how MG3 MPE works successfully as a stand-alone with Studio One 7 under Windos 11. Of course, many thanks also to everyone else who is helping to solve the problem.
I am using Windows 10 with Studio 6.6.4 and a Zoom R16 audio interface (with the latest driver). Unfortunately, despite many attempts, it has not worked for me so far.
I have set up Studio One with loopMidi as Keyboard and MPE enabled, as a track with instrument input.
Case 1: If I then start MG3 Stand alone first, I can no longer load the Zoom driver in Studio One, the message “already in use by another device” appears.
Case 2: If I start Studio One first, I can load the Zoom driver. If I then start MG3 Stand alone, I get the message from MG3 and Windows “can’t detect asio-channel”.
Case 3: If I start Studio One first and only load the slow Windows standard audio driver instead of the Zoom driver, then I can start MG3 Stand alone and load the Zoom driver there. And then the transmission to Studio One via loopMidi also works, unfortunately with the high latency of Windows.
I don’t know what else I should do to get it to work successfully as MG3 MPE via LoopMidi.
Hello Anjo, I recommend a class compliant audio interface such as the IK Multimedia iRig USB. This can serve two applications. You can also run it in parallel to a ASIO driver based interface. E.g DAW on the ASIO driver interface and MG3 standalone on the iRig USB.
Hello Anjo, thank You for the thanks and sorry to hear that it still not works the way it should. All I can say is that using a Babyface pro FS the problem does not occur. I don’t know any details about the details, I am just an amateur….So may be You try Dutti76‘s advise!
it is likely that the zoom asio driver is single client. if so, you might be able to get around that by using asio4all or one of bluecat’s tools.
unlike a second audio interface, either of those could possibly introduce some latency or stability issues.
That is exactly because your “Babyface Pro” is USB class compliant. You can also hook it up on an iPad or Android device without any problems.
It is indeed, but I set it up as asio device in MG3 standalone. This works, because it is a multiclient interface, as kimyo pointed out. I did not know that, I just did it that way…RME interfaces are really good.
Hi @Dutti and @Captainzero, is USB conform (=class compliant?) or this multiclient feature crucial for a successful connection to MG3 MPE Standalone, which should then be forwarded to Studio One via Loopmidi?
I am trying to install a Katana:Go as USB audio interface for MG3 standalone. Unfortunately this does not work. I get the message in MG3 : “cannot find device, please connect device”.
Katana:Go should be USB compliant and with 48Khz USB audio interface.
What else am I doing wrong?
I don’t know about the Katana:go but make sure you take a real USB cable and not just a charging cable (they don’t transmit data).