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.
SAGA Synth state saving in AUM not working correctly
I'm having problems with state saving of SAGA in AUM.
Can anyone test the following?
- Start a new project in AUM
- Add an instance of SAGA and select the preset "A Coo Stick Bass"
- Open the keyboard and play a few notes to familiarize yourself with the sound of the preset
- Save the AUM project
- Clear the project in AUM
- Re-load the project
- Open SAGA
- Problem one: the selected preset name is not displayed
- Problem two: if you open the keyboard and play the preset it doesn't sound the same as it did previously, it also seems mapped differently across the keyboard
- If you open the preset list and re-select the preset it sound as it should again
I have the same problem with some other presets as well (e.g. Bad Omen PAD) but I haven't checked them all...
Comments
Yep - replicated - I’ll send this to matt
@lasselu Typically, AUv3 do not save the name of the last preset loaded with the state. This is because they don't know if you've modified the preset since loading. To the app, the "preset" is just a historical event.
I'm not sure about the keyboard mapping. Are you sure you're in the same octave as when you saved the session?
Yes the name thing is not an issue, but basically it sounds when you open the saved session that the preset is magically up an octave or something, even if you play the exact same note you played before
Thank you!
Um, that's not my experience...just did a quick check with Trooper, Ivoks and FRMS...they all state save the preset name...
Yes...
We had this bug on old audiokit apps...
I can verify that in drambo the state isn't saved also, I tested copying and pasting the auv3 module
I can confirm Saga synth does the same thing in Nanostudio 2.
I must admit that I'm a bit surprised that this kind of bug hasn't been caught in testing...
Have to agree here...
...my guess is that most of the focus for this release was put on Sounds, UI, Playability and Stability.
No doubt this will be fixed asap and after that it's framework update for the other apps.
I'm also curious about this "coded from the ground up" claim if they have the same bug older audiokit apps had
the sounds are epic tho
I’m very surprised - I guess most ppl like me who were added to the beta - I’m not sure at what point the testing had started in-house, but presumably quite some time before - were more there to make presets etc and get to know the app a little before release. I would assume it had been thoroughly beta tested before by the team, and I really don’t have time to do thorough beta testing of multiple apps. I purely focused on making presets with this, I didn’t save any sessions. But also, it seems like this only affects some presets from what Lasselu said earlier, so might have been a tricky bug to find.
It'll be fixed by next week Matt told me to tell you. Cheers all. ❤️
Good good
Yep. Lots of love goes into these Audiokit apps I can tell. A labour of passion. I'll postpone my Chiptune Lofi beat and make something else meantime.
As it stands, I think I'll make more synthwave.
Good to hear...
The fix has been released! Matt's on top of this. Also today is his birthday, but he gave us the gift.
FWIW same problem in Loopy Pro
Did you update it yet? If so, did you restart your iPad?
I did both.
Oh sorry, I missed your post saying it was solved. Just updated and it’s fine now 👍
Excellent! ☺️