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.
Edit: solved, messed Firewall . Studio One Remote not working after update
The new update for this app seems to work only with Studio One 6. Trying to connect with a previous version of Studio One (in my case 5.5.2 Professional) ends up with a “connection with this version of Studio One is not supported”.
But the AppStore description still lists “Studio One 3 Professional or above” and they don’t state anywhere not to update if you don’t have v6…
Bad move by Presonus side…they were one of the few companies that were not doing things like this to force you to update… but it seems something changed (I hope not, honest companies are really rare these days and losing one would make me sad).
I’m trying to write a post in Presonus forum now, to warn other users and to see if we can have clarification by their side, but even creating a new post doesn’t seems too easy to find there…so I came here to warn you quickly since we are in any case talking about an iPad app that some of you could be using
Comments
Does someone know how to write a post in their forum?
Never mind…found
thanks, I was about to update the app
I solved the problem: it seems that the new update messes with Windows Firewall without asking for any permission (which is not a fair move to do anyway).
Turning it off and on again solved the problem
ah ok then, updating
yup, it works here with 5.5.2 👍
Yes. Did it not mess the firewall for you?
In any case, if someone has problems, try just simply to turn off briefly the firewall and on again, without even adding any rule or changing anything. It worked for me.
I’ll leave the post here anyway in case someone has same problem and search for a solution