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
Ah yes I remember now. The Ruismaker GM map seems to work on channel 10
Greta update
Can’t seem to trigger ElasticDrums
It could be me, am sure ElasticDrums has given me problems in the past
Got Ruismaker to trigger no problem
Any tips please
@Gdub What setup are you using ?
I loaded LK as AUv3 in a midi track in AUM and ElasticDrums as IAA in the input of an audio track. Then i used AUMs matrix to route LKs midi to ‚ElasticDrums (Virtual)‘ port. In LK, you need to configure the track‘s midi output channel to 10.
Thanks @_ki
I had all channels enabled in AUM
Still didn’t work
I seemed to have to go in and out of both apps a couple of times
And then it seemed to spring into life
Then I could just select the individual channel output and it worked
Thanks
Strange but it works now
@sinosoidal
I have the free version of LK on my iPad, but I'm having some MIDI connection issues when I run it as AUv3 in AUM.
The output MIDI from LK is fine, but when choose my MIDI keyboard as the MIDI input of LK (for recording) and activate record of the first track, it first starts receiving MIDI signals from my keyboard, but only for a short period of time. At some point it suddenly stops receiving signals (even in the middle of recording). I tried everything from deactivating/activating global recording, and recording on tracks, started/stopped playing, nothing. Then after about 3 or 4 minutes, the signals come back again, but only for a short period of time.
So I wonder whether this is a limitation of the free version, or not?
What OS version?
Big thanks to @sinosoidal and Imaginando for the quick record quantize fix in the 1.9.5 update! Had a total blast sequencing a bunch of fun hardware with AUM+LK over the weekend. It’s amazing how much easier my iOS workflow has become since incorporating LK into the mix. Very excited to watch the continued evolution of this fantastic app!
The only limitation of the demo version is the popup.
The problem you are having was an issue on version around 1.9.0. What's the version you are running? Can you please check the about box?
Thank you very much for your feedback. It totally makes our day to know that our software is being usefull.
We would love to see and hear that. Please share with us some videos!
If I remember, you are using a phone. Can you please do a video where you stumble on the problems you mention while trying to do something for real? We would love to see in realtime the problems you are facing, so we can work on a solution. You can upload a video to youtube and share a private link with us. Thanks!
How are you loading your Drum Drops samples? Which app? Thanks!
@sinosoidal
iPhone 11 OS 14.3
Made session in AUM
With ElasticDrums keyboard map in LK
Saved in AUM
When I open the session again
The drum map isn’t set to ElasticDrums
Is this a minor bug, or due to ElasticDrums being iaa?
Or due to AUM saving ?
It's bug! We forgot to save the keyboard layout in the clip. Will be fixed on 1.9.6
@audiobussy The exs file from the multi-sample pack loads straight into AudioLayer
@sinosoidal
Many thanks for quick reply
Is it me or... it seem you cannot ‘touch’ to play clips anymore.. You need to go into ‘clip properties’ and hit play to switch clips...???
Are you with shift locked?
Seems so.. it is green.. how do you disable ‘shift lock’? Thanks..
Thanks... solved now.. .. double tap shift lock...
Thanks..
In the vid below it actually looks easier than it is cos I’ve been practicing. It’s quite hard to grab that little red square and place it all the way off to the left, then try moving it up and down whilst reading the value it has.
Definitely not impossible, but tricky. And I still don’t know how I hit that tiny plus symbol!
I use iPad too but sometimes I just wanna mess on my phone.
Hope that helps. I don’t really know what would make it better. If you could select nodes with a lasso like notes then move them with a separate scroller like we discussed before, that would probably help?
We will see what we can do. No promises!
To be able to smoothly add and edit automation really is gold, I agree with Greg that the window is to small and the dots are somewhat "unwilling" to cooperate at times. I'm using the automation in LK now where I used to take an LFO instead so that's a great option.
. If you want to look at some automation tools that work, take a look at Nano studio, not perfect either but the best in my opinion when it comes to drawing automation as you can copy and paste points and curves and there is some space to draw.
I used Cubasis midi tools the other day and they are really bad spitting out points all over so don't look there for ideas
This got me thinking about how cool would it be to have an automation generator some day. Similar to the note generator, but in this case we would have options to choose the CC number, waveform, speed and amount.
So LK could e.g. generate a sine at 1/4 with an amount of 80% for CC 10
That's actually a great idea! And maybe with some wide range presets we could make life easier on smaller screens too. What do you think @gregsmith?
Yes that would be ideal
automation presets and a generator makes a lot of sense on a mobile touch screen.
@sinosoidal : are the following issues on your radar:
Is there a way to scale the velocities of all selected notes?
Nope. I've written down this bugs. Thanks for reporting.
Yes, press shift while changing the velocity of a group of notes.
Yea, this would be great! DualVCF by Toneboosters has a great implementation of pre-defined automation curves. So, could "borrow" that idea. 😉
Great idea!
I always refer to it but xequence 2 handles this sort of thing extremely well like curve generation. It’s well worth checking out for ideas.
One thing I thought would maybe help is the ability to make the automation window full height like the piano roll bit. Also maybe have a small gap before the first beat so it’s easier to place the node there.
Here’s a screenshot from Xequence 2. It uses ‘bars’ instead of nodes (I kinda prefer your nodes actually) but you can lasso select the bars you want then move them using the up/down and left/right tools so you’re not just trying to grab a tiny node with a fat thumb.
If you add those tools to the note editor and the node editor that would basically solve all of the problems I have with LK.
@sinusoidal I ran into an issue with Matrix. Maybe it's intended behaviour, but it had me baffled for a while. I'm using it to trigger a looper (Group The Loop) in AUM. I assign CC numbers to GTL loop slots, and if I send it any value from an LK clip it will toggle between 'record' and 'play' repeatedly on the relevant loop. (after the first record/play it switches to overdub/play, but essentially the same thing.)
Anyway, I was testing this with an LK clip 1 bar long, with an automation node at beat 3 (could be any value above 0 to trigger the looper). What would happen is that the first time I'd trigger the clip, LK would send that CC message 3 times - at beat 1, at beat 3 where my node was, and at the end of the clip. So I'd get GTL going into record at beat 1, play at beat 3, and record(overdub) at the end (and not coming out of that mode.)
However when I triggered the clip the second time, and any time after that, LK would only send the CC message 2 times - at beat 3 and at the end. So GTL would go into record at beat 3 and playback at the end of the clip. I figured I'd have to actually enter 2 values to do this; I wasn't expecting any CC messages to be sent at the beginning or end of the clip, but only where I'd drawn nodes.
It seemed odd to me that triggering the clip the first time would give different behaviour than subsequent times. I had a midi monitor checking this, so I know it wasn't just the behaviour of GTL. I was thinking that maybe LK wasn't ideal at sending discrete CC messages, mimicking say a button press rather than knob movements.
I thought I'd point this out in case it was important in any way, despite me having realised there is a different and better method that avoids this issue. Seeing GTL will also respond to notes, I'm going to do that, as they are far easier to enter on the Matrix piano roll, and I'll also be able to see multiple loops laid out graphically.
So really this just FYI,