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
The ‘dark mode’ color should be Tera Pro’s default color, I think it looks great and distinguish itself from the original Tera.
Thanks! 😎
Agreed. You know me, I love anything Organ related lol and that’s a big reason why.
Edit: site glitch caused double post.
I like that idea! Also, the question regarding dark mode has been asked so many times now, it should be mentioned somewhere in the documentation, if it isn’t there already.
Yes, or an option in the menu to switch it on/off
@VirSyn would you consider adding previous/next bank buttons to FM7, like the ones it already has for patches? Also, making the bank browser remember the last opened location would make browsing easier.
Just used TP as AUV3 in AUM, with Zoa triggering notes. Every time I press stop in AUM, Tera Pro crashes...It did this 3 times, consecutively. Anyone else had weird behaviour since last update?
Just tried to reproduce but worked here.
Does it continue to fail after a reboot?
Everything works fine here. Tested just Zoa and TP in AUM alone.
It does, unfortunately.
Just shut down ipad and rebooted. Same thing...
Worth mentioning: just tried with Polybud and Fugue Machine and all is well.....so, might be a Zoa thing?
Same here. Crashes when pressing stop in AUM. But works fine when using the IAA version (instrument or generator).
I can't reproduce this problem no matter what I try.
Can someone who has experienced it post the name of a patch or two that you've used when the app crashes?
Ahhh! 100% reproducible when operating at 44.1kHz. At 48kHz it's fine.
@VirSyn
[correction] eh. It is not fine. After making it crash, now it crashed on pressing stop in Zoa at both sample rates. Even after an iPad reboot. But then after a reboot it crashed at 48kHz but ran OK at 44.1kHz. Then I unloaded Zoa, changed to 48kHz, and the problem stopped.
I can't draw any conclusions except to strongly expect it's related to sample rate. Changing sample rate while the AUv3 is loaded crashes the app instantly in addition to the above mentioned weirdness.
Tried everything you tried but haven't got a single glitch here. What audio interface are you using? Or just built in?
No interface.
iPad Air 2, iPadOS 15.7.8.
Want some crash logs?
@VirSyn are you testing specifically with ZOA midi sequencer routed to Tera Pro AUv3 in AUM? Because other sequencers I’ve tried so far, such as Rozeta Particles don’t crash it.
@VirSyn if you need a copy of zoa to test I can put you in touch with the dev
@VirSyn it is the CC 123 value 0 (all notes off) that ZOA sends on transport stop that crashes Tera.
I can crash Tera 100% of the time by sending B0 7B 00 from Midi Messenger. The sample rate changes must have been coincidental in my previous tests. Perhaps I forgot to route ZOA a time or two. Sorry for the confusion.
I strongly suspect the 'note off / all notes off' which ZOA sends out on transport stop...
...this can get a bit get massive when using multiple output channels which could confuse Tera Pro?!
(ie. if Tera Pro is in omni mode it will receive note-offs/all notes off for notes that are already off and well, this needs to be handled).
Thanks for your help @wim . Am quite relieved it’s not just my stupidity, which it normally is when things like this happen….😁
It’s not a mass of note off messages that’s doing it. It’s just the standard “All notes off” midi message that is a single cc message (cc 123, value zero) on a single channel.
It doesn’t have to come from ZOA. Any app or hardware that sends that particular message even once crashes the app in every host I’ve tried.
Midi Messanger is a free app that can be used to send this message.
Nice investigating! So Tera Pro just needs to handle CC#123 with 0 value...
...that would be a good test to run against just about any AUv3 that exists
Adding support for Midi CC#120 with value 0 would be good to stop the output including sustained notes.
Btw, ZOA also sends the “All sounds off” (CC 120, value 0) message on stop, but that message doesn’t crash Tera Pro.
[edit] ha! We cross posted. 😎
I should have picked this up hours ago, but I was reading my midi logger in reverse order so I missed it. 🙄
All note off (B0 7B 00) not crashing TP here. Even when Zoa plays, sending ‘All Notes Off’ will not crash TP.
(M2, iOS 16.6, 48kHz, 256 buffer)
Strange. I can reproduce 100% here.
yes, tried with ZOA. Will check later your investigation regarding All Notes Off. Nice work!
I didn’t test it on 44.1kHz though.
Doesn’t matter for me. They both crash TP instantly.