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
I found this video quite useful:
There’s also a great walkthrough video from imaginando much earlier in the thread.
Maybe some kind soul could find tips and links earlier in the thread and add the info to the wiki
https://wiki.audiob.us/doku.php?id=lk
Thank you Greg, much appreciated etc.
@sinosoidal One feature which would be super helpful is keeping clip properties during copy/paste, so settings like keyboard layout etc are preserved when duplicating clips. This is especially handy for drum clips. Thanks!
Will be fixed on the forthcomming 1.10.0. Thanks for reporting!
We have made available the first beta for 1.10.0.
It features multi channel midi import. We have just tested with a couple of midi files. Please do your own testing and let us know the out come. There is a slightly different behaviour though. It will only create new tracks for the imports.
I forgot to add to the description but we have also enabled bank/import export to patch manager to allow to backup/restore patches saved through patch manager.
We still want to include Ableton Live 11 support into this release. That's actually the primary goal of this release along with multi channel midi import.
The manual is open source in markdown and it‘s available at github: https://github.com/imaginando/imaginando.github.io/blob/master/lk
So, instead of writing a wiki article we could just fork and improve the manual. The question is why imaginando is not doing it. What are their plans? Would it be okay to put that into the hands of the community?
IMO, a few tens of minutes spent by a few people could put some really useful info at the community’s fingertips... while revising the manual is a bigger task with more overhead before there are accessible results.
Why is Imaginando not doing it? They are busy writing the software.
The reason is simple. We have limited resources. We are only two coding at full time (not exclusively on LK). All the others players are part time and do not know the product like we do.
Writting documentation takes almost much time as writing new features, and you keep asking new features at an incredible rate. We prefer to provide you new features instead of updating the manual.
The other reason is that english is not our main language and we take twice or more time writing decent stuff in english, which still needs to be validated by native english people.
Yes, the manual is open source and the community can fork and make pull requests. We just need to validate and merge those requests. That would be a tremendous help.
This is something I never wanted to ask to the community because in the end, that's our job. But we will definitely accept community help on this if anyone wants to contribute.
Honestly, I assumed that and I thought it‘s a good moment to clarify that. Unfortunately I am also not an english native speaker and my job keeps me quite busy. But I know how to work with github and I could create and maintain the community fork. But first we should check if there are english native speakers who could spare some time and like to get involved in that matter.
Awesome thank you! Just tried, working now for keyboard scales, but not keyboard layouts. On 13.7 iPad Pro 2016.
I have a new UBRIDGE beta, that install AL11 scripts. They are not finished yet but it loads a session. We need to use a new notes api in order to avoid some warnings. It is usable, not finished. Do you want to give it a spin and provide feedback? Thx!
@sinosoidal Just imported a five part song and that worked real well and it named the channels accordingly (Bass, Chords, Lead etc.) But, the parts had different length and that might be from the song, I can't really check I think (I'll get back if so) but all but one were at 96 Bars and the main one 104 Bars.
.
So I thought I just go in and change the length on the others. Jessis, It was like fighting with butter on a hot summers day - I don't know what have happened here but it used to snap pretty well at least to even numbers (140.0.0) but it just kept going - really frustrating. In the end I did get them right but my mood was not pleasant
There really would be awesome if you could type in the value OR slide directly on the numerical instead of trying to grab that little tab.
Another midi import I tested and I'm pretty sure it should be 16 Bars ended up 16.0.1 . That's an old problem that's been fixed I think but now seem to be back.
Other that that, awesome
Look forward to the next update...
Food for thought.. Nora (look alike) would compliment LK nice, in a new module...
Is there any direct way or work around for ratcheting notes? Thank you
I don't know what ratcheting means. Can you explain?
That was not fixed yet!
you can change the resolution to 1/32 in the piano roll editor and add ratchets manually. You can also turn off the grid by clicking the magnet icon and work without restrictions.
Cool, I'll be patient. 😄
ok, thats what i thought too. but did not see the possibility with the grid turned off. thank you!
Ratcheting triggers a step in a sequence multiple times. So for instance, you could have a sixteen step sequence and use ratcheting to trigger the first and ninth steps multiple times when the sequencer lands on their steps.
yes please! yesterday I found myself trying to implement py codes from sensels remote script
I def need my Ubridge back (:
Please send me pvt message with your email.
Not sure if this has been mentioned, but the ability to have follow actions / repeat counts for scenes would be fantastic.
+1 ... Or even better, clips rather than scenes. (IMO)
Sequencing clips through MIDI learn is good, but follow actions would be more streamlined.
Yes please!!
+1
Added to our long list of feature requests!
Thanks thanks and thanks 😀😀
Woo! 🙏
I‘m having a blast with my Launchpad Pro MK3 in AUM, thanks to LK. But there are a few things I noticed: