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.
Comments
I can reproduce the issue with 4x Phasemaker in BM3. For my own sanity I doublechecked opening Cubasis sessions and AUM sessions with 4x Phasemaker which work OK.
/Devmode: @mathieugarcia I loaded Phasemaker in debug mode into BM3 and it seems it's sending large quantities of AU Parameters to the plugin before it's properly done loading. I can add a safeguard mechanism which may prevent it from hanging but it will always result in undefined behavior since all these AU Parameter values are lost. Maybe you can use the requestViewControllerWithCompletionHandler method to notify you when the AU has finished loading, because as far as I know you won't be able to access the viewController until the plugin is open for business. Just an idea.
This is probably also the reason Poison and Reslice et al. don't work; they miss the early burst of parameter data.
Hope this helps!
@brambos to the rescue!
I installed BM3 on my old IPad Air 2 and I can confirm that everthing works perfect on my old iPad Air 2 running the old iOS 10.0.1. I can run multipal instances of Poison-202 and reopen the session and the audio still works.
This has got me thinking that the problem is due to iOS 10.3.2 or the model of iPad used which explains why Samu had no problems running multipal instances of Poison-202 because he probably used an earlier version of iOS10 with an iPad Air 2.
I'm running 10.3.2 on an Air 2 and having these issues.
Hey everyone!
Our forums are back, see you there: https://intua.net/forums
Cheers!
Mathieu.
Strange! I have also installed BM3 on another old iPad this time my old iPad mini 2 but it is running the latest iOS 10.3.2. However I thought the problem was iOS10 related but multipal instances of Poison-202 AUv3 plugin still work with audio when reopening on my iPad mini 2 running iOS 10.3.2. The no audio issue only happens when I reopen sessions which have multipal instances of the same AUv3 plugins on my iPad Pro 9.7 (iOS 10.3.2) and iPad mini 4 (iOS 10.3.2).
Great to hear. Thanks for the alert!
On the Intua forum Matthieu acknowledged the AU bug. I forwarded Bram Bos diagnosis so hopefully that will help.
I suggest everyone report bugs there from now on. Including ones you've reported here.
I'm delighted to report that @brambos has updated Phasemaker to work in multiple instances of Phasemaker AUv3 plugin with audio now working in playback even when the session is reopened. However the other AUv3 plugins still don't have any audio when reopening a session. Hopefully the other developers like Virsyn and JimAudio will update their apps to work properly in BM3.
Good to hear it solved the issue. But just to clarify; the problem is actually in BM3's loading mechanism. I loaded my plugins in BM3 in debug-mode to see what went wrong, so I could implement a bug-catching workaround. But it's up to Intua to fix the actual problem, because loading behavior may still be unpredictable as long as the bug is in there. Once they fix it (and I'm confident they will) individual plugins won't need to be updated and will simply work as expected
Hey guys, is there a known issue with this affecting all AUv3 instruments? I’m getting audio engine loss when instanciating Syntronik and iSEM, these are the only two i’ve tried so far. Seems to happen mostly when there’s already one instance of said plugin(s) in the session and you attempt to load another. Only workaround i can find is saving, force quitting the app and relaunching. Will check out the Intua forum mentioned above now