When using MG3 inside AUM I cant load any instrument and I get the message: “no compatible plug-in format”.
So its not possible to use any instrument when using MG3 as a plug-ing itself?
To my knowledge it is so far not possible to host any instrument inside MG3 for iOS yet.
AUv3s cannot host AUv3s. You can, however, use the built-in instruments and effects.
You would typically use MG3 in AUM (or any other host) as a pitch-to-MIDI conversion tool only.
Its sad news, so I cant use my own MG3 presets if I use MG3 inside a host.
Is that an IOS limitation or a MG3 one?
I believe that it is an iOS limitation.
Forgive me if I may have missed something in the conversation here…but you can certainly use MG3 presets inside the plugin instance of MG3 within AUM; I do that all the time! But it is true that you can’t include, in those presets, other AUv3 plugins like you can do with MG3 standalone.
In AUM on iOS, I rely heavily on my library of MG3 presets to orchestrate both the MIDI and the audio output that the MG3 plugin will give me, even though all of that just gets handed on down the line to other things in the AUM session. They are certainly simpler than my standalone MG3 presets, but on the flip side I get a lot more configurability options on the downstream target Instrument plugins via AUM, than I would in MG3 standalone.
Anyway, this distinction might not matter as much in your case as it does in mine, but clarity is always good, right? 
As Vaultnaemsae said, yes you can “use the built-in instruments and effects.” and you can create presets with this material “only”, so yes you can use presets.
But I use MG3 mainly to play synths and my presets many times if not ever have included synths AUv3s, so if I try to load those presets I get the topic error. So no, I can load my presets.
That, at least for me, is a disturbing limitation.
I’m not sure that limitation, though–of not being able to “nest” AUv3s so that they’re in effect “sub-let” by an intermediate host–is unique to MG3, is it? Are there other hosts which do permit that behavior?
I know that for a while, before I invested in some of the SWAM solo instruments on iOS to use with MG3 there, I was trying to figure out how to use MG3 itself as a standalone plugin host on its own (this was on Mac, where I don’t have a familiar live plugin host), and I found the number of Module slots among the three MG3 Chains to be limiting, plus only four points of exposure, from each Module, for external control. (I had some pretty complex presets there, for sure!) But…when MG3 became available for iOS and I set myself up to test it out with AUM and a couple of SWAM instruments, that completely changed my thinking.
I find it much more flexible to have MG3 dedicated to setting up either a rich output of MIDI (to send to a SWAM plugin) or of audio (to send to audio plugins like guitar amp and effect plugins); thus used as an AUv3 plugin fully parallel in function to the other plugins with which it works in the AUM session, I no longer feel limited by MG3’s Module slot space at all (in fact it’s opened up control ideas I’d never thought about before), and as of this writing I don’t recall, either, feeling constrained by the four “pass-in” mappings for control in the MIDI Out module, since that shift in my thinking.
Anyway, just to be clear: yeah, it would be pretty cool to be able to “nest” plugins inside MG3 itself running as a plugin, no argument there. (The tech nerd in me would love that.) But having tried it “both ways”, I think I get a lot more mileage out of it by not asking it to be a host-within-a-host.
(But even that’s not fully cut-and-dried, either, is it–from the data-nerd perspective–with the built-in MDA pianos and AM/FM synths and now the Guitar Mods, which are kind of “hosted” internally. I’ve spent much less time with those thus far, but if the MG3 beta experience overall has taught me anything, it’s that I should keep an open mind about the things that don’t immediately make sense to me. I think I’ve now actually lost count of how many things I’m doing now that I’d have never thought of but for this beta, and this community. )
1 Like
This is Drambo (an AUv3) loaded in Logic Pro on an M1 mac. It cannot load an Audio Unit when it is loaded as an Audio Unit. Only when it is in standalone can it do that. The same applies in the iOS/iPadOS environments. If anybody knows of any genius who has circumvented this please let us all know.
A user may be “disturbed” but the limits of operation set by Apple do not care about user emotions.