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 think I'm about done with virtual analog softsynths. I wanted to love it, Flowtones can sound good, but I am also troubled by harshness. I find highly resonant patches, xmod, and often times unison sound unpleasant with va softsynths, for iPad and for desktop.
I am not anti-digital- I like many digital synths, like the Nord Leads, and I like wavetable synths. But I get irritated by harshness in the upper midrange and the piercing resonance of so many va softsynths. I don't know why developers don't hear it, too. Highly resonant patches on my analog synths sound sweet like syrup.
I still enjoy apps that take advantage of the touch space like Spacecraft and Geoshred. And I'm totally thrilled with Streetlytron Pro, it's worth it to me to own an iPad just for that app.
Guessing it’s the EQ/monitors/room/headphones/ears ?
I never ever claimed "all VAs except Nord Leads have problems with harshness", don't make up words to put in my mouth. You fabricated that "bold and weird" statement yourself.
The argument that if someone doesn't like a synth you like it means they don't have good monitoring, can't hear, or don't know how to program is tired and lazy. It could easily be argued that someone who can't hear the harshness has poor hearing or doesn't have good monitoring, but I'm not going there because that kind of nonsense is just a not-so-clever way to shut down conversation. I have an opinion formed after years of playing analog, hardware digital, and softsynths and I have as much right to express an opinion as you do.
Egad! That’s a lot of steps to “fix” a preset…but it works. The thing is deep. I now understand that ya gotta be able to extensively tweak it to make it work for one’s own tastes. A blessing in disguise to ensure no presets wind up on your recordings. HA!
No offense. Just trying to help solve a problem.
I also used to get offended when receiving beginner level advice.
Lots of noobs and pros here.
We don’t all know each other’s skill level.
Just trying to help.
Does anyone still have the problem with Flowtones not saving the preset properly the first time?
I load Flowtones in AUM, load a preset, play around, save my AUM session. Next time I load it up, it’s gone back to ‘light breeze’ again. I then have to load the preset again, save the session, and we’re all good.
Annoying if you’ve done lots of modifications to a patch though.
@DJB
Shutting down conversation and belittling opinions is what the internet is here for. I mean yesterday I saw a comment on here that Garageband was way better than NS2 and I thought “this guy HAS to be joking” but then I remembered that I was reading an opinion on the internet and so ignored it and carried on with my day (i.e. finishing another track effectively & efficiently in NS2).
I just remind myself that there is no such thing as a correct opinion, not even my own.
Now, break’s over, time to get back to making some music 😊
This is still happening! Anyone else getting this? So frustrating as I’m really putting some time into this synth and getting some fantastic sounds out of it.
@gregsmith , I had saving problems too. For some reason, Flowtones was built with a unique saving workflow compared to other softsynths. I understood it at one point, but found it unwieldy, so I eventually stopped using FT altogether.
Thanks, not just me them. I’ve emailed them so hopefully will be able to get it sorted with them.
I know a lot don’t seem to like it, but I love Flowtones, so happy to persevere. Will report back.
Cool new update!![](https://forum.audiob.us/uploads/editor/6v/dy7zpc6cy4wf.jpeg)
Nice new updates. And finally, a load of new patches! Lots of free patches are the most valuable thing any synth developer can offer for their product and it’s great to see this synth continue to improve.
True
Fantastic! Love this synth.
I really hope they’ve improved their AU state saving so that the patch doesn’t keep reverting to light breeze or whatever it is!
Gotta have that delft blue
Seriously, I love the TB willingness to include different color palettes. It’s a small but important to me bonus. I think of all the things I don’t use because the color scheme or UI is drab or just puts me in a funk.
I'm sure that diving in could prove rewarding, but when there are so many synths that come close to what I'm after right away, I'm not inclined to tweak and prune when I generally find 80 percent of the presets just as prickly.
But Toneboosters are great, and maybe the added presets will help give a better idea of its character?
That's the question! Seems to be specific to a certain era? The passionate opinions on either side definitely keep me interested.
hows Flowtones on cpu ?
thnx
The default patch is 'The flowing tones'. If you get a different one every time you start the stand-alone app, you have probably created your own default settings for loading new instances. Go into the hamburger menu and see if you can delete the default settings (they should be greyed out if no default settings were saved). See our manual on how to work with custom defaults when re-starting the app.
For Auv3, we can't restore the state of the previous setting in the app, because that's host functionality.
Oh @DJB while you're here and talk about patches: may I ask what's the logic behind providing previous/next arrows for the various color schemes in the top menu, but not providing one for the patches? Wouldn't that be the more important option for a synth?
By the way, the new patches sound fantastic!
I think I must have set the default as light breeze at some point by mistake. I remember this same issue with the flowing tones before.
To be more specific, the bug I was having is that I’d load Flowtones as an auv3, choose a patch, mess with it a bit, start creating a song, save the song. When I reopened it again, it would have gone back to the default patch.
Sometimes I’d have to do this dance 2-3 times before it would ‘stick’. After that it’s usually fine, although I’d occasionally have to revert to a backup after it’d load the default patch again. This may be a host issue but it doesn’t happen with my other synths.
This is with FT hosted in AUM, although it was happening in loopy pro as well.
I reported it to your team via the contact form on your site some time ago. I’m not sure I’m the only one here seeing this issue.
As I say, I love FT and see it as my go to synth, so want to be able to use it confidently.
For auv3, restoring your previous setting is not the task of the auv3 app, but of the host. Hence this is something you'd need to check in with the devs of the host.
Simple example: let's say you have two instances of FT running in AUM with different settings. Which of these two should be re-loaded in the synth when starting a new instance? Things get very messy if AUv3's would store and recall settings outside the control of the host...
The meaning of next/previous will depend on what category/library you have selected. Hence these previous / next buttons are provided in the preset manager, where you can filter based on text, category, library name etc, and simply go previous/next with that filter applied. We've now made that manager resizable and movable so it should be easier to keep it on screen when browsing patches. Moreover, with some people having thousands of patches, the previous/next buttons without some filter applied don't really make much sense anymore. That was the consideration anyway ;-)
This and Mela2 are the 2 main virtual analog type synths I want to try but haven’t bought yet. How are people still liking this one? Worth it or should I wait for a sale?
AUM has absolutely no state saving issues with any AUV3, at least it’s never on its host side, it’s the most reliable iOS host since many years @DJB . So what’s going on here? @gregsmith is an experimented user and has some issues with your synth regarding state saving, perhaps you could find a fix for this (or reach some hosts devs)? I’m also very tempted to buy this synth as I like how how it sounds, but state saving issues are truly a no go for me. Once session is saved in AUM, closed then reopened Flowtones should restore entirely without any hiccups.
Edit: @Shabudua had state saving issues too it seems.
There was a small bug in the preset browser in August 2021 that could result in state saving issues but that was resolved pretty much within just a couple of days - most of that time was taken by the Apple app store review process to push out the update ;-)
In all of the tests we've done in AUM with the most recent release, all states are perfectly recovered when loading/saving sessions. Same in other hosts.
Perhaps there is something special going on your side @gregsmith? Did you reinstall the app? Any factors you could describe which could help for a potential fix? Perhaps iPadOS version?