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.
Modstep AU plugin issue
I have run into an annoying issue with Modstep with patches on AU plugins. The problem is that when I use AU plugins like Phasemaker and PPG Phonem and I use my own patches in a song I am working on even though I have saved the session the patches are lost on this AU plugins when I reopen the session. I have to manually find and load my patches every time I reopen the session on Modstep. Is this a bug?
Comments
BUMP!
I guess I am the only one who uses AU plugins in Modstep judging by there being no replies.
If you own AUM just host the AU in there and route the midi. To be honest even though AU integration has improved a ton in modstep I prefer to keep it as a midi sequencer only. Also because I use hardware synths and currently modstep doesn't have audio inputs so modstep+AUM is the perfect combo for me.
Are you sure that the patches are not loaded correctly.....some have reported in other AU hosts that instances load with the correct patch but with the name of the first one...if that makes sense.
Yeah, the patches are loaded correctly, I think I have my patches loaded on Phasemaker now even though "80s piano" patch is displayed. However, the patches on the PPG synth plugins always reset every time I open the project I have been working on and it is driving me crazy.
Yes, the 80s piano thing is a known AU quirk, and it's the consequence of Phasemaker offering its own preset manager (officially AUs are not supposed to offer their own preset management because that's the task of the host, but many hosts don't properly do that yet).
Basically, when you load a project with an AU the host just dumps a bunch of parameter values to the plugin (state saving) but Phasemaker has no way of knowing to which preset these values belonged (and whether the user changed the preset beyond recognition). So the sound should be correct, but the preset-display is meaningless until the user loads another preset.
Quirks like that will remain the norm until Apple finally create clarity around AUv3 preset handling...
Either way, state saving should work bullet-proof with Phasemaker!