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
Works perefectly...
Did you connect the AUM keyboard to the TeraPro instance?
(Fastest way is to tap the little piano keyboard icon top left in the AUv3 window).
Try a hard reboot?
Yup, did that.
Just trying hard reboot now @Gavinski
Thanks chaps
Update: still nothing. Shut down ipad and rebooted. Got the latest TP update, released yesterday I believe. HOw strange. Any thoughts @VirSyn ?
Have you checked the MIDI Input setting inside Tera Pro?
I've tried it multiple times now with iPad Air 2, iPadOS15.1.8 and 11" M1 iPadPro, iPadOS16.6 no issues at all, it just works?!
...there is indeed a small possibility
at least for the first request, not sure about the second...
@VirSyn I might be misstaken or have severe case of amnesia but I recall TeraPro having y-axis/vertical velocity at some point in time?!
Thanks for trying @Samu . I'm totally stumped. Hopefully @VirSyn Harry has a suggestion?
Have you seen my comment above about MIDI settings? Already tried?
Shit! I didn't see that, sorry man. And yes, you're absolutely right. Dumbass user error as usual; the other day I was exploring the new FM pack, sending Zoa into TP, and having it on Omni mode was causing the CPU (or whatever it's called) to go through the roof, so I switched it to midi channel 2. Sorry! and thanks.....
This was AudioLayer...
Tera Pro has Modwheel set to y-axis movement on the keys.
Maybe some time I should unify this all. So many things to do...
Given the last sentence, I'm sure this would not be a priority. However, I am curious why the change in browser situation from Tera to Tera-verse/Pro. Was there a specific reason the current presets aren’t able to be sorted in the same manner as the Legacy set was?
Any plans for the situation to change, if it’s even possible at this stage.
Many thanks.
We’re the worst (so many requests)… fortunately, you’re the best!
The current preset browser is actually more capable as the old one - this had only one level of depth.
If you look at the Legacy sound set it's pretty much organised the same way as in the original Tera Synth on iPad.
The new one expands this to unlimited depth and I used this to bring the newer presets more upfront.
The real problem is not how it's displayed but the time needed to categorise thousands of sounds. It is simply too much time...
AT least I've added a search function to make it easier and there will also coming favourites.
If you look at my Poseidon synth preset browser you see it can get even more advanced:
I look forward to the addition of a Favorites function. Huge timesaver.
Thanks for the thorough reply. And yeah...It was actually the Legacy folder in Teraverse that made me start to wonder why that had been ditched.
'Favourites' functionality would definitely be welcome, and the 'Poseidon' screenshot is even more than I was hoping for, when considering upgrading to Tera Pro. Of course, I understand that it must be a huge amount of lower-priority work to categorise presets. But what if you had help with that part of the process? I don't mind doing some of that work. Maybe there're others who'd be happy to chip in. If you had all the presets classified and tagged etc. would it make a poseidon-like browser possible in TP?
Interesting idea...
kind of community work. Thank you for your kind offer in helping. Will definitely think about it!
Happy to do it myself if nobody else is interested. Of course, it'll take a little longer
Let me know.
.> @el_bo said:
Haha, it was you who threw the bone. You have a problem organizing keywords for 1k+ patches. Now, just imagine how you would design, develop, publish (PR included), maintain the whole plethora of apps that @VirSyn has. 😅
It’s already borderline impossible imho.
BTW, it’s noble of you to offer help, salute! 🫡
No problems here using the AUM keyboard or external sequencer. Have you tried rebooting?
As far as I know, Harry is either a sole developer or working in a very small team. So this was never about loading more low-priority work on top of everything else. I just thought it at least worth asking them if it was something that was planned for...even if only as a far off and distant goal.
I actually don't have a huge amount of time, either. But flicking through presets and assigning attributes is not too much stress for me, whereas it would be for the developer. A few handfuls per day, and soon enough it'd be done
Anyway, i pretty much made the same offer to another dev, during a PM conversation. Clearly it's something I find important
No worries, you are not alone. I will join the cause! Just PM me when needed. I'm a sucker listening through sound banks anyway, also love to categorize. We could use charts like these ones:
I thought you might perhaps volunteer, given your previous comments. i just didn't want to put you on the spot. And thanks for those charts. I've seen similar, many years back. But these seem even more useful (Always good to be able to distinguish one's HONK from one's HUM
).
But when it comes to categorising presets (and this presumes we get an official go-ahead), I'd assume it might work out better, at least for the dev(s), to follow the scheme shown for the 'Poseidon' browser. Would likely make it easier to transfer to other products. Dev's call, really. The only necessary differences for a full 'Tera Pro' browser would be a way to (de)select for the inclusion/exclusion of owned IAP, in any particular search.
This would be a more official approach. So far it seems to be something under consideration, but no doubt not a huge priority.
The other way to approach this is in more of an unofficial manner.
We could categorise everything in a format appropriate for Harry etc. should they at some point decide to use it. But at the same time as categorising we could perhaps re-save/'Save As' each preset to our own folder substructure within the main menu, which is simple to do. This way, we're just duplicating presets which should in no way break previous project compatibility. And with appropriate prefixes and/or suffixes it'll be possible to use the search functionality with better accuracy.
I do have an idea for a structure and naming convention that should make it very easy to get to the types of sounds being looked for. Will test it out in Teraverse to see if it works.
Again..All of this presumes that doing this and sharing it won't be forbidden.
Thanks again
the virsyn apps are the only one i remember let me save a preset without annoying "yes override old preset " warning. i wish all developers do it this way, iam serious.
had a fun time yesterday during a 5 hour flight with tera pro. love it!
I sorted this , thanks @espiegel123 . I had changed midi setting from "omni" to "midi channel 2" a few days earlier and totally forgotten....!
You can't transfer those charts even if you want. Those should be for rough guidance only, for us to be on the same page for certain terms and maybe inspiration. You are right, Harry will make framework and official guidance.
Now is the time for you and the rest of the community that wished for advanced patch management to step up and help design structure for keywords and patch management with ideas.
You started this so it’s on you how will be best to manage all input from the community, whatever method you choose I will do my best to comply.
For my personal database I took keywords from SugarBytes, it’s more than enough for my needs. Many of them are same as in Poseidon, here is the list for inspiration purpose:
8-Bit
Slow
Hats
Robot
Random
Guitar
Brass
Atmospheric
Keys
Bubbly
Fast
Morph
Distorted
Digital
Arp
Reverb
Complex
Drums
Synth
Pluck
Simple
Bass
Synthesizer
Bell
Sweep
Melodic
Natural
Strings
Choir
Evolving
Synthetic
Pad
Piano
Chord
Init
Chiptune
Game
Lead
FX
Snare
Vocal
DnB
Sequenced
Clean
Noisy
Analog
Bright
Beat
FM
S + H
Vintage
Percussive
Cinematic
Dark
Gated
Expressive
Kick
Organ
Nature
Flanging
Church
Gate
Many thanks for the list. Definitely a lot of options there.
Perhaps we can keep the conversation going by 'pm', for the moment. If we can manage to get a working proposition together, we could update the thread?
I guess @VirSyn's To-Do list is like 30 min. just scrolling through.
So when or if that patch framework ever happens we will be ready!
good guess, but I need to cross read to get this tempo
But anyway, please keep your spirit, I will need your help then. And a new patch management simply has to come anyway...