Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
App or Plugin Presets…..Not Being Saved with the AUM Session?
Hi,
I am using AUM. I noticed that my app/plugin presets are NOT being saved with the session.
Example - I am using Moog Model 15 app or plugin in. I created my own preset and (most importantly) SAVED it in AUM. There are two save options for plugin presets 1) In the PlugIn - which most plugins don’t support because of iOS 13 changes and 2) In AUM
So I made my own preset for my Moog and saved it in AUM
Then…. I save my Session in AUM; thinking….or believing…..when I close AUM, and then reopen it, my Moog Model15 will be ‘opened’ to the last preset or the ‘state’ it was when I saved the AUM session. But it’s not 
when I close and reopen AUM and this particular session, my Moog Model 15 plugin is NOT opened to the preset (or the previous state). The Moog Model 15 starts on some generic app preset.
I’ve seen with the A2M plugin I’m using as well.
Is there some setting or trick to get AUM to save any/all of the current plugin presets being used - when you save the session?
Frustrated in Philly
Comments
State Save and Preset Save are two different things. So, just to verify, when you save the session in AUM, the actual patch and sound are different when you restore the session? That doesn't seem right. I can do some testing but I want to make sure I understand what you mean first.
Some plugins restore the State, but not the Preset Name when reloaded. This is because you can't assume that just because a preset was loaded, settings haven't been modified after the fact. Those settings would get restored by the state restore but the preset would not actually still match the state-saved settings.
Another common mistake is people using the IAA version of an app rather than the AUv3. That doesn't sound applicable here though.
(There are plugins that have bugs with state saving. I'd be surprised if Model 15 was one of them though.)
The preset doesn't save with the session information. It saves in the AUM app file area. The session saves the state of the AU that the AU gives to AUM when AUM asks for the data.
I did a quick test with AUM and Model 15 and one of my plugins (LRC5) and everything looks to be working as expected for me. Note that it won't update the name of a preset on session load because it gets the data from a different path than the preset. But, the parameter values are updating for me on session load.
As far as I know AUM stores the 'state' NOT the 'preset' when saving a session.
The AUM 'presets' as far as I know are used to 'set the state' of a plug-in.
I would when ever possible use a plug-ins built-in preset management to save presets since this way I can easily use the same preset with multiple hosts and just let AUM save the state of the plug-ins.
Unfortunately in many cases the 'preset name' is not part of the 'plug-in state' so some plug-ins may start with a generic preset name but the 'state' is properly recalled. (ie. some plug-ins may show 'init' as the preset name but the parameters are still properly restored).
That's all details I've collected when messing around with AUM and AUv3's...
Some tru philly taggin' style right here:
Jawn is legit.
I can't replicate Model 15 not saving state with the AUM session. Works every time here.
Yes, the preset doesn't show the checkmark next to it, but Model 15 is in exactly the same state it was before. Not showing the checkmark next to the preset makes sense IMO because there's no way of knowing that the preset you had selected hasn't been modified since you saved it. (Well, I guess they could track that and put an asterisk after it if it has been modified but they don't.)
Check if the actual synth sound, knob settings, and wires are the same after saving and restoring a session. I'm reasonably sure they will be. If not then my next thought would be that the session wasn't saved completely. I've noticed that the new session save mechanism where you have to confirm that you want to overwrite a session within a brief time has tripped me up a few times. You have to hit the button again within that short interval and actually see the popup in the center of the screen confirming that the state is being saved or restored. Not an ideal UI choice IMO.
Just to reinforce this explanation, when you save a Session in AUM, it obtains the state from each plugin and saves it all, along with the connection data. When you reload the Session, AUM loads the plugins, then sends them the state data, so they return to the same condition they were in before. So, you should see Model 15 in the same configuration as before. Whether a preset name is saved/restored is up to the app itself, and is somewhat irrelevant, since a preset is just a way of initializing a configuration.
If you want to remember how you reached a certain point, you can name the session appropriately when saving. You can also add a Note in AUM to record any details.
FIRST…..as always….. Thanks for all the response. I “think” I get what you’re saying.
Just to clarify. For the 2 plugins mentioned (Moog Model 15 and A2M), I have loaded a preset in each of these, and then changed nothing (no knobs, no values, no anything) in the preset……and now I’m ready to save the session. So I “believe” when I save the session, and close AUM and then restart AUM and load up that AUM session; these two plugins (Moog Model 15 and A2M) will be in the same state as when I save the session.
I think I see my confusion.
Although the presets will be in the same state as they are when I save the session; in other words all of the knobs and configurations will be EXACTLY as I had them when I saved the session in AUM. That DOES NOT mean, that when I reload the saved session, the plugin will show or appear that a certain preset for that plugin is selected. AUM knows the values of the configuration of the plugin (where all of the knobs, the connections, the sliders, etc.) - but AUM doesn’t know or care that this configuration for this plugin (Model 15 and A2M) has a certain preset name.
So taking the Moog Model 15; I loaded a preset called AJzSmoothMachine - and I changed nothing in this preset, and then I save the session in AUM, all of the values and configuration for the preset are saved. However if I close AUM, then open it and reload the session I saved - while I do get all of the values exactly as they were when I saved the session; I will not see that Model 15 has the preset ‘AJzSmoothMachine’ loaded. This preset will “in effect” be loaded because all of the values for all of the knobs and controls were saved with the AUM session…. but AUM doesn’t know or care that this Model 15 configuration (all of the values of all of the knobs) is called ‘AJzSmoothMachine’
Is this understanding correct?
Yep. You got it.
Some plugins do save the selected preset name as part of the state. Some save the name but have some kind of indication that the preset has been modified after the save. Some don't do either. But all should save the state (knobs, etc.). If not then that's a bug. I does happen.
As always…. Thanks Wim - I appreciate the help here.
👍🏼
OK……. well, it turns out that the values/configuration in A2M are NOT getting saved in the AUM session.
You can see the value of the Threshold setting BEFORE I saved the session.
Then after I closed AUM out, reopened it, and then you can see the value of the Threshold
I “THINK” in this case a work around is to one of my FabFilter plugins (the Gate plugin) in front of A2M and use it to assure that a certain volume level is required before A2M will change the audio to MIDI.
[AAaarrrggggh]
I took a look at what A2M is doing in GarageBand. In GB you check what's happening with the parameters using the default view instead of the AU GUI. It looks like the parameters are being set correctly but the A2M UI is reflecting the change when the parameters are loaded via a session/project load.
Edit: After a bit more investigation, it looks like GB is doing some additional parameters setting or something. Checking A2M in Audiobus and none of the parameters or other settings are set when the session is loaded. It looks like there is an issue with the state saving in A2M or it isn't loading the parameters when the host returns the state to it.
The host doesn't really do anything with this. It's the AU's responsibility to hand the correct data to the host and then load that data when it is returned to the AU. The host doesn't do anything to the data. It just keeps it as a serialized data structure.
Oh yeah, what version of iOS are you on?
I’m on 14.8.1
@NeonSilicon are you the dev?
Not for A2M, no.
We are on different versions of iOS, so it's not likely to be an iOS bug.
I tested A2M without the IAP. Maybe restoring the parameter state is disabled in the demo mode? If that's not it, it would seem to be a bug in A2M.
Not sure which thread to use for this question so I'm gonna just use this one.
@j_liljedahl I have just noticed that when saving old sessions, the usual option to "overwrite" is not coming up, and the session is being saved again, as a different instance of the original, with the same name.
This has only just started happening. Anyone know why?
Considering this doesn't seem to correlate at all with this thread, you should probably just start a new thread, or ask on the AUM Users facebook group, or AUM discord server, or email me
I see now that you did create a new thread, so will reply there.