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
Very nice.. Thanks..
Awesome additions, thanks! LK is better at clips than Ableton. 😄
One other feature request that actually comes from using Bitwig. It has midi channel per note in clips, this would be epic if possible.
Thank you very much
Are the midi channels per note or per clip time region?
Actually you can define the midi channel per time region and per note. Didn't know that! Thanks for the info. We'll see if there is anything that can be done regarding this in the future
Woo, thanks! 😄
Thanks a lot. I’m looking forward to this. And thanks for being such “active listening” developers.
Aren't you in the TestFlight? If you want to be added, send me your email via pvt message.
Awesome new feature that loop count follow action, would be possible adding a “chance” for follow actions ?? That’s the most wanted and unique Live feature that I can’t replace in LK 🙏🏻
You can check it here: https://www.ableton.com/en/manual/launching-clips/#14-7-follow-actions
@sinosoidal Thank you for fixing the note behavior with Ableton Live! Works like a charm!
+1!!!!!
@Synthi @Janosax
What do you think should happen with the change functionality? Since we don't have two follow actions to choose from, should the clip create a new change event everytime the clip reaches the defined loops, and keep creating until the follow action is applied, or should it create only one chance event and don't do any follow action if the probability isn't sufficient?
Or having the counter follow action (when the probability isn't satisfactory) is mandatory in this case?
Both are good, but if we need to choose I prefer the first option: « the clip create a new change event everytime the clip reaches the defined loops, and keep creating until the follow action is applied».
Edited
First of all, many thanks to the LK team for taking great care of the beautiful LK app!
It's so much fun to use and the best clip based AUv3 sequencer I can imagine.
If there is one thing I'd be allowed to ask for regarding the new follow actions and launch modes in general, I would love to see a third clip play mode:
1. From Start
2. Continue
3. Punch In
The new "Punch In" mode would allow for the following scenarios:
Enabling playback of any clip while holding it, always playing the clip at the correct beat position with other clips. A clip longer than one bar would play from the same position like it had been playing since the beginning when hitting Play.
This would extend spontaneous clip playing to a very fun, playful live experience.
Spontaneous Punch-In recording on any clip just by holding the clip or holding a MIDI note for as long as recording should occur, overwriting existing notes on that clip.
@Janosax @Synthi
As requested, new build (292) has probability in follow/transform clip actions. Hope you like it
Wowww so lightning fast incredible!!!! I will test it ASAP thanks
Awesome.
We are feature freezing this release of LK. Please test as much as you can so we can have time to fix any arising issues. Thank you for your input and feedback, as always!
Thanks!!! 😍
Awesome addition.
Follow action works perfectly here, awesome new feature thanks. When you will have time, you could add chance setting with a percentage, this could give more randomization to this game. This is what I understood with @xglax « the clip create a new change event everytime the clip reaches the defined loops, and keep creating until the follow action is applied».
@sinosoidal, I'm still experiencing instability and crashes in AUM, getting hung notes from various synths including Synthmaster 1 and 2 and shockwave and factory, also when this occurrs and I open the lk window it's blank and I have to reboot the AUM project to get everything back again..
Is anyone else having this behaviour? Are you using the TestFlight version or the store version? As you can see in the image below, we don't have record of crashes in beta for this upcoming release:
What do you mean with "you could add chance setting with a percentage"? Are you talking the follow actions probability of the notes probability? Both are a percentage.
I'm using the beta version at all times nowadays.. should I be using the latest store version..
For example: if you play a 16 bars scene and drum loop has its follow action set on random other after 2 bars, as it is another drum loop will be played after 2 bars. A chance setting for example 20% will let 1/5 chance for this same random other follow action to be triggered after 2 loops, then another 2 loops, etc (2,4,6,8 up to 16. If the chance is never triggered, the scene change or play again depending on its own eventual follow action setting or not). This specific chance is reapplied every two bars in this example except if scene is changed or if initial drum loop is not played.
No, you can use the beta.
Software can become really complex. It seems that in your case some thing is highlighting the issues even further.
Are you sharing your analytics with developers? Otherwise we won't receive your crash reports.
https://kb.eway-crm.com/faq-1/eway-crm-mobile-android/how-to-share-analytics-data-with-developers-on-ios
Don't know if I fully understand what you're asking. Right now you have clip follow actions with pre loop amount and probability. When you have probability, the clip will loop the pre loop amount, check the probability event and if it passes it will trigger the follow action, if not it will loop the pre loop amount again until making a new probability event. Isn't this what your describing in your example?
For some reasons I was on 291 not 292 sorry!! It’s perfect!! Perhaps probability could be added to scene too?
Okey dokey I'll enable analytics and stress test it all, seems pretty reproducible, I'm on and m1 air with latest builds of everything I'm using..
It would be great to have the minimal setup that is able to make things crash. If there are 10 different synths and 20 fx, that wont help.
If there are only one synth and the crash happens, we could try to get that same synth and load your aum project. The more sistematic, easier it would be to reproduce.
Software can become very complex. Reducing the potential variables helps a lot when looking for something that is hard to reproduce.