I finally got the HEX version and I have a question regarding how to set it up in Studio One. This is for a GK3 pickup with a breakout box directly to my Presonus 1824c interface (song setup inputs 3-8).
I have everything working just fine with the MG3 stand alone in HEX mode and I can transmit MIDI via LoopMIDI to Studio One and play my VST instruments there. All with that single interface.
But for some reason, if I try to use MG3 HEX VST in Studio One, I can’t get it to work. Single input base MG3 works though.
I see that the input module shows “No HEX Input” and if I click on it, I don’t see all the parameters I saw previously in the stand alone app. I only see “Ask Daw to give it 8 input channels”. I tried that and restarted the DAW and got nothing.
The forthcoming plugin version release of MG3 Hex for macOS has access to multiple audio inputs independent of the DAW/host’s audio I/O. It’s a big deal for hex users. But I can’t say for sure that this will be possible on Windows as I don’t know the ins and outs of audio on that OS so well.
It means MG3 Hex should work in all DAWs, even ones that don’t support multi-channel audio inputs for plugins — on macOS.
For now sticking to MG3 Hex standalone is your best bet but hopefully the new version will be able to do this in Windows also.
It isn’t working as you assumed. The problem in Studio One seems to be that the routing options are very limited. The best results I achieved setting up a 5.1 input bus with the six single inputs from a GP-10. It is possible to insert MG3Hex on a track with a 5.1 input configuration and the 5.1 bus as input. MG3Hex accepts the input and it can be configured, but due to unknown reasons the D string (input on the “C” / center position) of the 5.1 input is passing the dry guitar signal in addition to any VST sound used. Further you can not pan all strings to the center position.
This rings a bell for me. You might want to test all the string inputs individually, because I seem to remember having a problem where they were not all in the expected channel order, but they were all there.
Unfortunately, after a few more trials suggested by you guys, I still can’t get any connection from my interface to the MG3 HEX VST. I’ve tried a lot of things. I can get a signal—like with the 5.0/5.1 tip—but I haven’t had any success passing it through MG3. I hope I’m not missing something critical.
Hopefully, a future update, like the one Vaultnaemsae described, could make it a lot easier.
So, I’ll keep using the standalone version for now. Seems like it’s my only reasonable option.
@cldmrqs , perhaps it is worth discussing the problem in the forum studiooneforum.com .
It’s a manufacturer-independent forum, but there are also some well-known presonus people in the forum who are sure to pass it on if there’s a problem with studio one.
In fact, you just need to declare a 7.1 audio input and MG3Hex works correctly in StudioOne7. In my case, I use the VG-800 as an audio input. This is the same scenario as with GigPerformer. The channels of the six strings of the VG800 are from channel 3 to 8.
It doesn’t work for me with the GP-10 connected. It is the same as if I set up a 5.1 input bus. One string is always sending the dry raw signal in addition to the VST sound.
But I don’t need Studio One since it works perfectly in Cubase. I was just trying to help @cldmrqs.
The next version of MG3Hex, 3.0.63, will introduce a new feature that will simply resolve the issues with defining dedicated audio inputs for MG3Hex, regardless of the DAW used and the selected audio interface:
“The MG HEX module will open any GP/GM/SY automatically, if such a thing is connected.
You should see the “configure” button instead say “GM-800”, “SY-1000”, or “GP-10”, if there is a connection.
That means you should not set the GP/GM/SY as input in audio devices, and not set 8 channel input.
Instead, use another audio interface, maybe?
Should also open a GP/GM/SY when running as a VST/AU, simplifying DAW routing.”
However, I don’t know when JamO will release this version, so let’s wait for this great new feature…
@xtian82 The 7.1 configuration seems to work. I haven’t tested it fully yet, but I’m getting some results. I did notice some dry signal coming from the strings, similar to what @Dutti67 experienced, but I think there might be a fix. Honestly, I’m not entirely sure what I’m doing, but it seems to work. I went into the surround pan control, hard-panned everything, and the dry signal disappeared. I’ll keep testing tomorrow and report back.
Really appreciate all the help from you guys—this is great!
UPDATE : I haven’t found anything to complain about, apart from my computer might be a bit too slow, cause I get some crackling sounds at buffer size 64. Or maybe I will sort it out.
