Re-entering the testing world, on iOS

BETA TESTING
,
1

Greetings gang. I’ve been off the T&E circuit for entirely too long now, but have just recently gained access to an M3 iPad, and am now set up to do some of the MG3 testing I’d hoped to do long before now. So, I’m hopeful to soon have a few questions, hopefully intelligent, and please forgive me in advance if I don’t manage to catch an already-asked question before I ask myself… :sunglasses:

First and foremost: wow, this M3 iPad seems to be every bit the heavy-lifter (over the A-series iPads) that I’d been led to believe. I tried a few quickie ideas to see if I could load it down with hungry plugins (both within MG3 standalone, and with Audiobus) and so far I haven’t been able to do it: this bodes well I think!

My plan is to start my testing from the ground-up, starting with MG3 standalone both in host mode and in “straight-to-MIDI-out” mode with other apps, and then work my way back in to Audiobus after that, with hopes to start learning Cubasis 3 at some point (I’m new to that app).

Based on things I’ve learned from this community (and bless you all for that!) I’m specifically hopeful also to wring out a few of the SWAM instruments (double-reeds, for starters), and the new Circa looping plugin from Audio Damage, at the same time.

Future questions will get their own specific posts, but for this one, given that several pieces of this technology stack are actually new to me, I am curious about these things:

First: AUv3 plugins only on iOS? I immediately notice that, when running MG3 standalone on iOS, I don’t get the same list of available Instrument or Audio Effect plugins that I see when I use Audiobus. (For example, the installed AudioKit Synth One app doesn’t seem to appear as an Instrument in MG3 standalone, but is available as a “MIDI receiver” app in Audiobus.) By contrast, on Mac, MG3 standalone makes available Instrument plugins that I know are not AUv3 (e.g., SampleTank 4) along with ones which are. Is there a limitation on iOS for the AUv3 format within MG3?

Second: use of ‘network session’ for MG3 output? With the caveat that I have never tried to use “network sessions” for MIDI before, I tried setting both the MG3 standalone MIDI output, and the standalone SWAM plugin’s MIDI input, to “Network Session 1” as offered in both places. This doesn’t seem to successfully send anything to the instrument. If I change (or just add) the “MIDI GUITAR OUT” to the standalone SWAM plugin, and then change MG3’s output target to “Virtual MIDI output”, it’s instant happy place. So my question is, how would one use the “network session” to send MIDI to an Instrument?

Thanks gang. Here’s to some happy testing forthcoming. :nerd_face: :nerd_face: :nerd_face:

2

Welcome back :slight_smile:

No, but in an AUv3 host (which MG3 standalone is) you’ll only see AUv3 plugins, no Inter-App Audio, which has been deprecated but which is implemented and still works (for now) in some hosts, like AUM, Audiobus 3, Ape Matrix, Loopy Pro, etc…

You don’t need to use it and probably the only reason you would use it is if you wanted to send MIDI to a Mac over WiFi. Stick to the MG3-created virtual MIDI port.

3

Thanks for that. So is MG3 for Mac not just an AUv3 host then (since I can see and use non-AUv3 plugins in it), while MG3 for iOS is explicitly an AUv3 host?

And roger that on the networking thing. Maybe it’s one of those “if you need it, you’ll know you need it” items! :nerd_face:

4

Correct. Consider how many AUv3s you have on your Mac and how many plugins MG3 finds after a full scan.