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.
Problems with Kaspar as IAA in AUM... Not saving state...
Ugh... I just realized that when I use Kaspar in AUM as IAA (which is required as you lose a lot in terms of preset management as an AU).
For example...
Load Kaspar in AUM
Open Kaspar
Make a change to a voice like arp type
Shut down AUM
restart AUM
Change to arp is gone...
I had really thought Kaspar may be my multi-timbral solution... Yonac doesn't seem to respond to emails, tweets, etc. either... so I guess maybe it's a dead product?
Comments
For IAAs it‘s complicated:
AUs save their state and manage presets in the AU hosts session, some additonally offer an own preset system for cross-host presets.
Back to your question:
According to the AB3 app page, KASPAR supports AB3 state saving. So try a setup where KASPAR and AUM are hosted and connected in AB3.
I suspect that IAAs hosted in AUM which itself is hosted in AB3 don‘t save their state since AB3 does not know about the sub-IAA.
Best to use AUs if you have the option ...but for IAA only apps which support midi program change, you could use Streambyter to recall a patch in a host session such as AUM or apeMatrix. Theres’s a thread I posted in apps tricks section. Kaspar stand-alone supports this.
I was thinking of hopefully updating this script with instructions for various apps as time goes on (maybe others will add to it). I’m finding it a really good way of recalling patches in IAA apps.
One of the reasons why IAA is pretty much dead in the water: it has no state saving mechanism.
As @_ki also said: if you're using IAA apps each one has to be saved separately, manually. Every session.
Unless they support AB3 state saving.
Sure, but that's not much use when hosting things in AUM. Only when you use AB for hosting, and even then it's 50/50 chance if an app actually supports it properly, unfortunately.
It's still true that "IAA has no state saving". AB3 is a separate thing, built on top of IAA, that adds state saving and other things.
Thanks a lot guys on the tips. It's been a while I tried to do anything with IAA in AUM and forgot about how much "fun" it is.
So i need to manually save Kaspar presets when I make changes, but AUM does remember what preset was actually loaded.
No, AUM doesn't know what the preset of an IAA app is it's hosting, so the only way to recall it is to load the preset manually, or use the midi program change method I mentioned earlier, which is a workaround.
If Kaspar supports AB3 state saving, you could set up an AB3 doc that loads Kaspar and the AUM doc.
Ten why is it when I load AUM, then click Kaspar, it has the same preset I was last using... Anyhoo, I've decided to just say F it and deal with Kaspar as an AU. Problem solved.
That's because some IAAs load the last preset that was loaded, which isn't the same as statesaving, if you loaded Kapsar outside of AUM and changed the preset to something else, it would just revert to that one, not the one in the AUM session etc.....yeah it's annoying so best to use AUs if you want to recall everything.