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
IAA is a dead format full of issues that'll never get resolved. By the time anyone gets an IAA working somewhat properly in a host app, all inspiration is lost. I hope to see DRC updated with AU.
Well on my iPad air2 on latest versions of everything I have failed to get it to work as IAA instrument on
MTS
Music Studio
Yamaha Mobile Music Sequencer.
Cubasis is my main 'Daw' on the iPad and will most likely remain that way for long time to come.
(I've got no intention of getting MTS, Music Studio or Auria Pro just to test this).
To get DRC working I just launch DRC first and then attach it in Cubasis.
It doesn't matter if Cubsis is running or not, just make sure to launch DRC before attaching it.
If a Cubasis session uses DRC and neither of the apps are running I launch DRC first and voila the Cubasis project using DRC works without issues.
Launching DRC from hosts such as Cubasis is still a bit shaky so I've simply adjusted my workflow to launch DRC first when I plan to use it. Remains to be seen if Cubasis 2.0 improves on the situation...
I suspect something else is at work in my case: does the DRC update you're using have the arrow in the upper left that sends you to IAA host?
The point is surely that the developer should be aware that the IAA implementation in DRC is faulty not that you should buy apps to test it even in cubasis it needs a fudge.
Thanks for the workaround. Cubasis is my main DAW as well. I'm fairly satisfied with it for the most part. But I wish Steinberg would make some improvements concerning IAA. Your workaround is similar to loading Thor in Cubasis. Unfortunately, I've been avoiding IAAs like the plague. Too much frustration in general for me, which sucks all my creativity away.
I think AU is the way forward too, BUT there are many IAA apps that you just select and go for example Cassini, Cubesynth (to name a random 2)
Like that? Yepp...
The fudge doesn't even work in my case, it's weird. I'd had something like this happy wig another synth, just having it on the device, not even in the bg, created havoc with midi IAA - I don't get it. Meanwhile it did load in BM2 on my iPhone. Go figure...
Yeah, true. Some of those synths work well. But it's always the synths I wanna use that end up giving me the most problems. Then I end up opening Gadget to avoid all the IAA issues and wish some of those synths were more advanced. It's difficult to find a happy medium with iOS.
So weird... The download I get from the store of the newest version does not have this - maybe because I'd been on the beta I can't get the version that's at least able to get on Cubasis with a workaround.
Quick ?, is there any plans have full MIDI Out for the arps, meaning all the arp notes, and not just the notes triggered on the keyboard?
I really like the arp on this app, it has a very natural and smooth feel when the subdivisions are changed in real time. I'd really love to capture that on an external sequencer!
I'm on the 'beta' too and usually when a 'final' hits the app-store i re-download it over-writing the last beta.
It's really strange because this time I first got 1.0.4 from the Appstore and then just a few moments after that 1.0.5 update. It must be an Appstore bug that an 'old' version gets pushed out just to get updated a few moments later...
I do agree that most of the time I too end up using Gadget because it 'just works' with it's 'limitations'.
Once it gets a 'sampler keyboard' with 'sample pool' it's going to take a lot to drag me away from Gadget
@Samu
Gadget just keeps getting better. Tons of great synths now!
Incidentally, I just tried the Cubasis workaround. I don't have the IAA control panel either.
This got lost below the fold. Which is another way of saying Please acknowledge my special problem!
And that "arrow" transport — you all have seen it too!
It's not your special problem, it's @Samu 's special gift
"Samu's special gift" is the name of the young adult novel I'm working on.
Hahahahaha.... Hope it's not too Tongue-In-Cheek/Crack!
Possible to have keyboard size and scale settings saved as well? Or have I missed this option somewhere?
The movie version will have Tobey Maguire as the older brother.
AUx version comming?
I don't think the world really needs an AU version of Toby Maguire...
As a non-engineer, I'm truly baffled why DRC would work so beautifully one evening and then just fail the next day. Is there any reason NOT to delete DRC and reinstall?
Maybe not...
The only reason not to is that delete and reinstall didn't work either.
From what I'm gathering there are 2 binaries out there, one that has the arrow button that sends u back to the IAA host, and one that doesn't, one that opens in Cubasis as IAA (by opening DRC first), and one that doesn't
Yeah, but I'm telling you. I HAD THE ARROW TRANSPORT LAST NIGHT! Frustrating.
The arrow appears when it is connected to a inter-app audio host. At least it is supposed. Which version are you having problems with? Go to about and let me know the version that you see there. Which version were you running last night? Did you updated in the mean time?
Version 1.05
Updated earlier in the day.
Here's a question about the MIDI menu in DRC. There are 12 apps listed, including DRC a number of times, as well as modstep a number of times, and every other app I have opened. It's kind of random which apps have a check mark. (Sunrizer seems to attract them.) I remove them all and recheck the modstep ... nearest the top?
By default all midi (in and outs) start active. The option is supposed to be kept by name. I have tested this with a only a few inputs/outputs. In fact I didn't predicted what could possible be the maximum number of inputs and outputs. Looking forward for feedback on this new feature.