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.
iceGear AUv3 Multiple Instance Issues
Anyone else having a problem loading more than 1 instance of an iceGear AUv3 in AB3? I have Laplace and Mersenne, having the same issue with both:
Clear session, load first instance. Synth UI appears as normal, playback is as expected.
Open 2nd instance, tap to edit - synth UI is missing, no sound
Go back to first instance - UI is missing there now too, also no sound
Now, if I also have another AUv3 instrument loaded (let's say Ripplemaker, though I also tested with mood), then after going through the above steps the UI of Ripplemaker shows up as normal but there is no sound.
I'm on an iPhone 7 Plus, iOS 10.3.2. Multiple instances of other AUv3 instruments in AB3 work just fine.
Can anyone replicate this behavior? If so, does Redshrike behave the same way?
EDIT - added iOS version number
Comments
I just loaded three instances of Laplace in AB3 audio page. Went to each one and changed sounds and adjusted parameters. No problem detected here.
Awesome, thanks. What model device and iOS version?
iPhone 6. iOS 10.3.2
Added two Ripplemakers also and I can go back to each AU instance and adjust everything just fine.
Thanks for checking!
Was just able to try it on an 6 plus, works fine on that device.
Can confirm exactly the same issues and behaviour presented by eddielovesyou on iPhone7 plus with iOS 10.2.1
I wonder if it has something to do with the 7/7+ lack of headphone jack? Did the underlying audio output device change when they omitted that?