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
Comprehend. Maybe one of our VideoMakers here can give a helping hand...
Will be nice to see how the entire suite works with each other... Export to Ableton, etc.
Much Thanks..
@Gavinski 's tutorials are very good!
Ok, just tried on a fresh session and it's not crashing so it must be another thing I have in there
keep me updated!
@sinosoidal : the MIDI learn is great. It makes LK much more usable for me.
There are a couple of things that I have noticed when recording with LK. This is in AUM with my keyboard (either external or AUM’s built-in one) as an input to LK) routed to LK only and LK routed to the synths. The synths are getting their MIDI from LK only
There are definitely some tricky issues to resolve.
We have just uploaded a new build (191) that has a new panel under the menu to enable/disable dedicated controllers integration. This can be useful to allow the usage of a certain controller without being dedicated, via midi learn.
Ok tried LK out with my LP Pro Mk 3. There seems to be bad latency between hitting a note and recording a note via midi capture that was working and now isn’t. Also the latest build has brought in a time limit on matrix which is annoying for beta. I’m just not finding this app intuitive. When you press a button on hardware you expect it to do as the label say but that’s not the case half the time and I spent more time setting this app up rather than sequencing. Clip launching especially seems hit or miss. Not knowing what control are mapped or not on hardware feel like I’m diving in the dark. Overall I’m finding this app trips over itself with the amount of options available it’s just not enjoyable to use.
^ perfect example of how not to act as a beta tester.
Hi @sinosoidal
I find it very difficult to use the piano roll actions from the properties panel. Icons would be more suitable than text, scrolling to the right tab in the accordeon, switching on and off the other tabs is painfull.
Some settings are fine in the properties panel but i am wondering if note tools could not find a better place, so i made a little sketch.
It means that the timeline has to go somewhere else, maybe a thinner one between the action icons and the roll?
A contextual menu like Andrew Huang did in Flip app may be even better to manipulate notes.
If i can help…
Pleaaaase make this wonderful piece of software available on macOS!!
I dont use it, so no loss for me.
Sometimes, LK will send two copies of a note played on the keyboard (one delayed by a little). It is as if the note gets added to the sequence and the recorded note is being played back in addition to having been streamed through. I can’t reproduce it at will but it happens at least a few times per session. I have record quantization off.
Having that too, for me seems to happen when playing with low velocity.
Also had some problems when recording with the chorder from LP mk3 pro. Sometimes it has a latency, so the chords come a little late and some sound longer than they should. Once a note got stuck and once i had a crash when recording chords from the chorder. But i cant always reproduce it.
I tried the new lp mk3 pro integration:
Cliplauncher works fine. There is just one thing, when a clip is selected and the sequencer isnt playing it doesnt light up, as soon as i hit play it lights up.
The other functions Clear, quantise, record, etc. work fine. Duplicate and pan dont work. The volume faders work but there is no fade in when touching with low velocity.
Thanks for your great work, its nice to see how fast LK evolves
@White Thanks for the export midi tip. It is not quite as convenient as copying a buffer but it does the job. The "del all" is also useful as it means I do not have to stop the clip to remove the notes. Hopefully we will be able to MIDI learn the option at some point then I'll be able to do retakes without needing to touch the screen!
To trigger a clip in LK from a clip in the same instance on a different track I have the AU listen to its own output so it receives the trigger note. This triggers the clip as expected but is this the correct way to do this? It feels like I may be missing some internal routing way of triggering one clip from another on a different track rather than going out of the AU and back in as I am doing.
We had that issue with build 190. Ensure that you are running build 191. Check TestFlight app to see if there is an update to build 191.
The time limit has always been there since it's inception 5 years ago. Just go to menu->store and unlock the desired module on the standalone.
We are not here to waste anyone's time. If you don't want to receive anymore betas just let me know your email address and I will remove you from the beta list
You are not alone. We will see what we can do in future releases.
I agree that note tools text is one of the examples, where icons would be actually more suitable than e.g. in the bottom bar where “M” in circle or MIDI port buttons are not so intuitive (which is not a big issue, it can be learned and this is not an app for toddlers
).
With note tools, text descriptions are actually a bit slowing down the workflow as you need to actually read the description, instead of using sort of muscle memory where icons help a lot.
If I may suggest: I would really love just simple 4 arrows like on keyboard: up/down (currently transpose +- 1), left/right (currently time shift: left/right). I believe it’s pretty obvious in context of note tools. For tranpose +- 1 octave, a double arrows, e.g like these: ⏫⏬ should be also pretty understandable. I bet I have seen it like this in some DAW with touch interface, just can’t find now on iOS as I went through DAWs, maybe it was Bitwig studio...?
Also, I’d probably just separate the actions that are universal: Select all, Deselect all, Delete all, and those related to notes selection and maybe on top of the group of actions put a label that changes between:
1. “All notes:” (when no note is selected)
2. “10 notes:” (in case of having a note selection)
Then it’d be clear what is applied to all notes and what only to a selection and buttons that are not related to selection at all would be separated.
There is so much great software for music production in iOS. LK is just a controller app. How would you use it on mac OS?
Can you explain why do you want to trigger a clip with a clip in a different track? Seems far-fetched.
We definitely need an icon set. Thanks for your feedback!
Thanks for the reply. I am new to clip launching so I may be approaching this in the wrong way but my use case is that I want to automate the starting of clips and scenes in a chosen order to make up a song. I could do this by clicking on them manually, using a controller, or using follow actions but I would like to automate the song arrangement by triggering the clips and scenes from a timeline using their assigned trigger notes.
I could send the MIDI notes to the LK instance from another MIDI sequencer but it seems logical to have this information alongside the clips/scenes it will launch. Think of it as a kind of master controller track 80 bars long which triggers clips, and maybe even audio from other apps. This might even be a recording of me triggering the clips from an earlier live session which could then be played back.
Again, I may have missed something in the way that people traditionally put a song together in a DAWless way, I normally use a DAW with a timeline but thought I would give this way of working a go as it lets me try different song structure options out quickly.
This is pretty much the approach that atom 2 is going to take I think. You can have a timeline instance that triggers your other instances.
I think follow actions is the best way in LK although I’m only just starting to figure this out myself. I’d be interested to know how Live users approach this.
@gregsmith That's useful to know! Looks like we will soon have a nice collection of apps which interact well with each other to help with this way of working.
Yeah I’m really hoping LK can trigger atom 2 clips and atom 2 timelines can trigger LK clips. Of course Drambo can slot in there somewhere too...
Can’t you just do it already now with LK? Instance one has your clips. LK Instance two is the master timeline that can trigger clips in instance one. The beauty of AU multiple instances.
Instance one would have short looping clip lengths, and instance two would be set up with a long timeline length. With note folding it should be easy to visualize the timeline triggers.
Haven’t tried myself yet, though.
Good idea! I never think about having more than one LK instance. Not sure how you map the notes as triggers in the timeline one though.
They are soon to release an update with MIDI Learn. In the instance with the clips, you’ll set up the triggers. In your instance that will send the triggers, you enter those same note triggers in the timeline.
Nice!
In stores now... digging in.. Thanks.
Just tried assigning c3 on the AUM keyboard to launch a clip - worked flawlessly!
One bit of feedback @sinosoidal - n/a initially made me think of ‘not applicable’ so I probably would have assumed that you couldn’t use midi learn to launch clips.
I’m assuming it’s ‘not assigned’ but there’s probably a better way to show this.
This may just be on the beta though - if so ignore me ☺️