GP10, Ableton Live 12.1 and MG3HEX - Help - 3.0.54 here

After a very successful testing, a lot of fun, with the standalone version (Mac OS Sonoma)
I am trying to use the plugin. Apologies if this topic was already discussed.
Live 12 does not allow me to use the MG3HEX Plugin in Ableton Live as designed :
Live allows for audio channels 1-8 or 4 couples (1-2,3-4,5-6,7-8) there’s no option to use the driver as MG3HEX does in standalone mode. Can you help? What I am missing?

Let me add that the 3.0.54 with GP10 standalone is fantastic! With chords it does not miss a bit.

Thanks
Pasha

Hope this helps. Use VST2 in Live 12.

1 Like

Thanks. I’ll test it - I was using AU.

I have tried with VST but with no success.
Live ‘sees’ the GP10 audio input as 4 pairs or 8 single sources.
My take is that 1&2 are the stereo output so I am using that to feed MG3 but it does not work with MG3HEX…

See this post…last part.

Thanks just answered there for the audio split issue. For this one I’d say, Live can react to pairs 3&4,5&6,7&8 so you need three instances of MG3HEX right?
As a plugin MG3HEX / MG3 depends on the input issued to the channel. Live can only pass pairs or single audio from GP10 USB driver so what I do with the MG3HEX standalone cannot be done with the Plugin (so far) that’s why we have the network mode, maybe to overcome those DAW limitations? Ableton is the problem not MG3HEX. That’s my best understanding so far. hope it’s right :innocent:

You only need one instance of MG3. In one of my recent posts there is a screen shot of the configuration in Live 12. You funnel three stereo pairs from the GP-10 — 3/4, 5/6 and 7/8 — from the to the MG3 plugin at the respective inputs using the audio routing dropdown selector in Live.

Thanks.
I have tried to reproduce in my setup (you have a SY1000 but should be the same with GP10).

But still does not work. Internally MG3HEX says no HEX input.
I spotted a difference: you have an additional line after Audio to but I haven’t.

Do not select "Track In” for the hex signals. Look lower and you will see specific channel inputs for the hex signals.

This assumes you have told MG3 to expose all channels to the DAW in the audio settings and that you have the hex tracker selected.

Also remember thst you must use MG3 as VST2 in Live since the VST3 and AU plugins do not expose the 8 ports as requested.

1 Like

Thanks exactly I thinks that’s the point.
In MG3HEX I can have Ask DAW to give it 8 channels or 1 channel.
It’s a little misleading having a button. Anyway I have tried both ways and closed and restarted live with no success. Track in won’t go away. I am using AU. …
Fixed by using VST. Now it works Thanks!

1 Like

I’m glad you got things working :slight_smile:

But I’m a bit curious as to why it is that only VST2 works in this manner. I guess it’s a limitation of each plugin format? FWIW, I tried to do the same routing in Logic Pro using the surround audio multi-channel config and I could not get it to work at all, but it may be user error on my part.

Perhaps @JamO could give us a hint? Though I guess it’s a moot point now since the intrduction of the caster tool means you don’t need to configure multi-channel audio in your DAW anymore.

I was just messing around with the caster tool transmitting to Bitwig and it’s smooth as butter.

2 Likes

You are right Midi Caster will keep us away from complex configurations due to Daw and formats!
I still have to experiment…
But I am sure it will work fine!