Man, I feel like I should already know this, but: on the iOS platform, how would one import or otherwise make available, NAM models (and other resources like IRs, reverbs, etc.) available for use? It’s really straightforward on Mac, but I’d like to start looking at the internal NAM plugin on iOS, and I can’t see how to do it.
This is a good question and something I wondered about too!
iOS/iPadOS use a sandboxed runtime which works differently than the non-sandboxed version of Mac.
On iOS I believe we do not have permission to retrieve a directory of files to show, whether NAMs, IRs, etc.. So all discovery of files must be based on Apple native iOS file selector dialog, so that native dialog is the nam file browser.
But whenever you select a file, MG also creates a bookmark for it, which it shows and persist for next session. So essentially you get a listing of all bookmarks that you have previously opened.
But there may be better ways to do this that im not aware of. Im curious if anybody have experience with another music app that does things differently.
I do notice that many apps (e.g. AUM, Cubasis) seem to have data folders in the OEM Files app under the “On My iPad” location, and some apps also seem to allow you to reach in to the “iCloud Drive” location (I remember doing this with Audiobus and QuantiLoop quite a bit). I have certainly transferred files between devices by dropping them in these kinds of folders before.
With the significant caveat that I am not an iOS developer 
, is there something that prevents MG from having such a data folder? (e.g., maybe because it’s TestFlight and not a regular App Store app?)
Just a notice that I’ve implemented “fat patches” for next update. A fat patch embeds any external resources (IRs, SampleBanks, NAMs, BackingTracks, Tuning Files, etc..) and can load on another computer or iPad directly.
1 Like
NAM profiles load and can be recall from saved presets in MG3 standalone for iOS/iPadOS.
If you select Neural Amp Models then Browse the file system is accessible (iCloud/On My iDevice). Import a NAM profile (.nam) then save as a patch – it will be recalled when you load the patch next. I assume this is as long as the target NAM profile stays in place in the file system.
Selected NAM files also seem to be saved in an MG3 database once loaded for the first time. Note, if a previously loaded NAM file is no longer present and you try to load it, you can crash MG3!
MG3 as an AUv3 plugin running in a host on iOS/iPadOS is a completely different thing. The NAM “Browse” command doesn’t allow access to anything.
As a regular AUM user, I simply use GigFast Lite (Artera DSP) to load/recall NAM profiles separately from MG3. It appears to import each NAM file into itself permanently so profile recall is completely reliable when you use it as an AUv3.
The Artera DSP method seems a bit different to the kind of thing you’ll be moving towards, @JamO.
1 Like