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
It's not a great experience, but then again the app window is pretty much the same size on a Mac which is really sh#t when it's a 5k screen.
Of course, it's never going to be playable like a normal mpe synth, in the same way that mononoke isn't either. The mpe is not that interesting for me in this, I think, I'm more interested in the modulation
Errmmm....No, not really - unless you have the Morph with the Buchla overlay and a setup file...which costs....£££
It was tested first on a seaboard, why is it only designed for morph? It seems like it should be just as playable on a seaboard, no?
Both that crash on reload problem and problems loading scala presets have been solved and an update is imminent. True the app has a few glitches right now but I am confident they will be resolved, dev is very dedicated
Gui issues are something we'll have to live with
How do you set up you seaboard with it?
For reasons I don’t understand, roli designed the seaboard to require things like custom modulation curves to be built into synths (or at least, between the seaboard’s output and your synth’s input.) Without that, IMO, the seaboard usually feels awkward to play at best on every dimension of control except pitch. My understanding is that the morph just doesn’t have that problem: a lot of users find the default output (Eg with overlays like Thunder) very playable without adding custom scaling. So at a basic level we could say it’s Roli’s fault.
But over time it’s become good practice to add some amount of support for custom modulation curves in MPE synths (because all mpe controllers - the morph too - have quirks that benefit from scaling customization for every synth patch.) That side is on synth devs.
It’s not strictly true that Fundamental was designed to work with the morph and not other controllers. It’s just that their implementation might feel awkward to use depending on what you need to do with your controller for your gestures to cover the range of values Fundamental needs to see on the x and z axes for you to get the musical result you want.
@ohwell good answer. Midi Curve (part of the Blueveek midi tools collection) goes some way towards making at least Velocity control a bit more normal. Yeah, wouldn't really recommend buying a seaboard at this point, could have been a great controller, they dropped the ball
@Charlesalbert read the manual, it's a bit complicated. I think u need to do it in the AUv3 by the way, didn't see any midi settings in the standalone
Really starting to feel like false advertising at this point. Maybe I should become an Ios app developer and make a fully MIDI capable synth that in reality is just a static picture of a cs-80 that can't do anything. According to app store industry standard practices, that should be perfectly acceptable
This does connect Bluetooth midi in standalone. I just tested. Strange thing is that it has no midi section in settings. So it seems it will take in midi messages from any Bluetooth controller you have connected to your device.
@Gavinski said:
That's good to know, thanks
Don't get me wrong - I love this app on both platforms. My slightly frustrated comments were due to MPE fatigue setting in after too many hours trying to get cc74 messages through...😁
I'm seeing UX issues with AUv3 in AUM and apeMatrix on iPad Pro 11"
UI is cropped in both, even in full screen.
In AUM there is a workaround: move the window frame up and then resize to reveal the full UI, which consequently obscures the AUM window frame... not ideal, but at least there is a workaround.
In apeMatrix there is no workaround.
I sent feedback to the dev.
After seeing similar issues in Scythe, I wonder if it would be helpful to create a "guidelines for AUv3 beta testers" page in this forum that specifies the minimal acceptable functionality we expect from AUv3 plugins.
Geez. I was really looking forward to this one. I was going to buy it at launch but held off. Now... after this thread and all of the detailed reports of issues, layout problems, comments that it should've been tested by iOS users, that it doesn't translate from the desktop well, etc. Especially all the detailed issues coming from someone who seemingly was really enthusiastic about this one.
I don't really want to fall for the odd critique here and there at launch, but given the plethora of detailed shortfalls and issues... gives me pause that maybe I ought to sit this one out to see if all this gets ironed out.
It works really nicely in full screen but I’m not sure there’sa way to pipe audio out, it didn’t show up in AB...
at least you could see this 10 bucks as a donation to Hainbach and the dev.
the knob of the original hardware is very smooth and a joy to turn.
even if you map this software to hardware that joy is completely lost.
unless you map it to something like this maybe
http://www.tristanshone.com/portfolio/big-knobs/
Legend
Do you have a newsletter? 🤣
>
This assumes there are testers. The Scythe developers is really nice and responsive to bug reports but for some reason can’t / won’t do. beta tests.
This is, and was always going to be, a somewhat niche app, but it sounds like it is definitely your kind of niche. I recommend it despite the interface, and the other issues seem to be getting sorted. The interface issues, I THINK it will be possible to get used to over time though they are problematic for sure. It's pretty unique though in many ways, worth getting if you like these sounds and want to support a dev who will potentially bring a bunch of interesting stuff to iOS.
I like the idea behind this app. Do I need a midi controller connected, midi routed to the app, inserted as auv3 etc. to use it?
Is it possible to export audio? For sample import?
Clearly this was never tested on an 9.7 screen iPad in any AUv3 App.
Totally brilliant on desktop, sounds great on the iPad, works great in Standalone, although a touch glitchy, but a disaster in AUv3 on a 9.7
You definitely don't need any kind of controller to use it. It has gates and envelopes and automation built in. It has no audio export, you would load it in a host and use record in tbe host to do that.
Great, thank you.
@brambos just saw your mononoke comment, got lost in the flux. Thanks for weighing in.
Can someon, Doug or anyone, tell me clearly what the problem is, exactly, with 9.7 ipad for this. Is the problem only in AUM or in standalone too and is there a decent enough workaround or not?
It should never take hours trying to get cc74 to work. I can't understand why apps struggle with stuff like that. It's not even an MPE thing, lots of midi controllers have mod wheels! It's like releasing a synth without an oscillator
I got cc74 working. It took seconds. There's nothing hard about it, maybe there was human error involved