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
Yes I was part of that thread but for some bizzare reason it no longer automaps.
Might map it to the drum mode since at least it divides into 4 parts and the parts are lit. I could make four parts, 1 for drums, 1 for bass, 1 for melody and one for say effects
Do you guys succeed to control Loopy Pro with LK, loaded as a midi au ?
I’ve been able to do it the other way round, controlling LK clips with loopy donuts. You can make a blank donut by recording a silent source, then use the follow actions to send midi messages to LK. I haven’t got it perfect yet but it’s getting there.
I’ve had more success with loopy donuts launching atom2 clips.
Gonna do a video about it soon. Just waiting for @Michael to look at an issue with the order that follow actions are triggered.
If you have a launchpad pro mk 3 , there isn’t anything you need to do for loopy to activate session mode.
If your launchpad pro is a different version, I don’t know.
If you have LK of Atom 2 running, they might be taking control.
Are you connected vis USB?
You probably had a midi feedback loop. If so then you may be able to fix it and keep the midi plugged in by ensuring that Loopy and/or isn't sending the mk1 isn't sending midi clock and isn't routed back to the RC300.
aaaaand thank you!
IAA now supported in latest update. Also search fields great thank you @Michael
For those that haven't noticed, version 1.04 was released which includes some bug fixes and support for IAA apps.
Launch Pad Pro not mk version.
Connected via usb, silly thing is I have had it working but not now.
My work around is to use the drum section in Launchpad. That gives me a block of 4 banks of colour, if I create a Loopy version to look the same then map it to the Launchpad. Using this technique each pad pressed on Launchpad will be highlighted and play on Loopy.
SAMPLR!!!!!!
For LaunchPad Pro, only the LP Pro mk3 is plug and play for session mode. For the other versions there are things that you have to do to enable session mode.
You posted here about how you got yours working:
https://forum.audiob.us/discussion/comment/1041970/#Comment_1041970
Has anyone tried Bleass motion fx or slow machine on an IAA channel? I’ve got Samplr recording ok but Bleass don’t seem to do anything…
Are you able to record them into AUM or other host?
Hello @espiegel123, thanks for the reply. Yes, they work ok in AUM and I’ve been using them on input channels in Loopy with no problem until the update. Now when I press play they don’t react at all.
I know but the is that same fix now won’t work. No idea now what am doing wrong. Replaced the cables before and that worked but they are now new cables.
I am puting the Launchpad into live mode by holding down the session button chosing the green button which takes me into live mode but the screen remains blank.
Are you saying that they work fine processing hardware input channels and AU instruments but not IAA channels? Does it make a difference if you disable idle enablement?
Anyone else having issues loading IAA apps? I haven’t managed to successfully open Indian Drummer yet, and MidEast Drummer only works about half the time.
Have you tried launching them first?
It looks like you may have removed the microphone input. This screws up IAA big-time in Loopy Pro. I was having all kinds of troubles until @Michael suggested adding the mic input back in. I did, and just muted it instead. This fixed everything.
If the mic input is there but just scrolled off-screen, then it's something else.
Great! Old Crystaline and Borderlands, etc. working well for me so far. Thanks for the update @Michael ! Great IAA stuff I’d completely forgotten about
@Michael thx so much for IAA Support.
Are there any plans to play the loops chromatically? Like in, put them to one shot mode and play them on the keyboard.
That would be my ultimate wish.
Pabam🤨
Try with the microphone input not removed. Reboot the iPad first, or close Loopy, open Cubasis, quit it, then open Loopy and start a fresh project, making sure not to remove the mic input. You can mute it. Cubasis should load, though you may have to tap it a second time to get it to load.
IAAgets real flakey in Loopy if you remove the hardware audio input.
Thanks. Turn out. We will study further🙌
Yup, on the roadmap. Till then use Koala!
thx for reply and hero!
Hello, I’ve now tried Bleass Motion FX and Slow Machine on AU and IAA channels and they load up but do not ‘run’ or start when I press play. I checked the ‘idle’ setting but they just seem to be asleep. I’ve sent Michael a message to see if he is aware. I use Motion FX regularly with Loopy as it is great for adding a pulse to things like Beatcutter so I’m really hoping it can get sorted.
Thanks for replying.
I have the MK3 and can confirm some conflicts/ strange behavior with Atom 2 instances running. Obviously it’s because Loopy Pro and Atom 2 are both trying to auto-connect to the Launchpad.
So what I do is, if I’m planning on using the Launchpad to perform, is make sure any instances of Atom 2 are used ahead of time, and whatever it was sequencing gets recorded to a clip, and the Atom 2 instance deleted.
I’ll be interested to see the video someone said they’ll make of “having a loopy donut launch Atom 2 clips in the follow actions” because I can’t for the life of me imagine a workflow where I’d need to do that, but everyone makes different kinds of music, and everyone has their workflow.
Wow! Now this is HUGE!
“Loopy, I’d like to introduce you to an old friend of mine”
Ok, thanks. That’s probably it. I do usually remove the mic input if I plan on jamming with only software instruments. I’ll have to get into the habit of muting instead.
If using LK or Atom 2 in Loopy, you can turn off their hijacking of the launchpad. Both have settings for that.
I'm aware. I was just saying, in my particular workflows, anytime I’d use Atom 2 for something, whatever I’ve sequenced with it, has already been recorded to audio (a loopy clip), therefore the Atom instance can safely be deleted as I wouldn’t need it anymore.
I would be interested though, in seeing what these guys are talking about “using a “follow action” to launch Atom 2 clips”. I’m still scratching my head, trying to imagine how or why that would even be useful.