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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

LK - for Ableton Live & Midi by Imaginando - AUv3 Clip Launcher Finally Available in AUM!!

1121122124126127130

Comments

  • @Bruques said:
    Definitely!

    @Synthi said:
    Yes! LK and FMRS user from day 1, would be glad to help testing

    @HotStrange said:
    I would absolutely love that! Been using your apps for years now probably and am a huge fan of your work!

    Please send me pvt message with your email :blush:

  • Even with the development of the new app, they are still responding. Sent a message last month regarding LK features on Android and they replied quickly.

  • @sinosoidal said:

    @Bruques said:
    Definitely!

    @Synthi said:
    Yes! LK and FMRS user from day 1, would be glad to help testing

    @HotStrange said:
    I would absolutely love that! Been using your apps for years now probably and am a huge fan of your work!

    Please send me pvt message with your email :blush:

    Done 👍🏻

  • Hello all, love this app, huge respect to the team responsible.
    Just wondering if any one else is noticing jittering velocity values when you try and adjust multiple at once by dragging, in the piano roll ? They keep jittering and readjusting themselves long after I’ve stopped touching the screen.

    Anyone having this problem or know of a fix?
    Thanks in advance for your help.
    I’m using Ableton 11 on a MacBook Air m1 with LK on a 2018 ipad 6th gen.

  • The Imaginando team has moved on from LK. They have only been working on their new BAM groovebox and not on improving and bugfixing LK anymore.
    Ironically, BAM comes with a functionally completely stripped-down LK matrix module, but it is intended as a DAW-like groovebox. Get in the beta if you like. Interestingly, the LK-like module won't seem to be expanded any time soon for stability reasons ... go figure.
    My guess is that bugfixing LK is too time-consuming (hence costly) for the developers, since the problem seems hard to actually spot and fix (otherwise it would have been fixed long ago).

    After more than year of daily LK use and daily crashes and failures, my reasoning is:

    LK remains my favorite iOS sequencer workflow-wise, but it is too unreliable for serious music production
    LK is clearly too unreliable for true live
    Drambo is slowly evolving into a clip launch controller and is rock-stable
    Helium has clip launch capabilities and seems very stable so far

    Thus, I am transfering all my projects into Helium and/or Drambo and keeping LK only for toying around.
    My advice to new users would be to wait to mid-2024 or so and see if LK got updated before spending any time on it.

    Sorry guys, this is a frustrated user/Imaginando enthusiast speaking ...

  • @henningz said:
    The Imaginando team has moved on from LK. They have only been working on their new BAM groovebox and not on improving and bugfixing LK anymore.
    Ironically, BAM comes with a functionally completely stripped-down LK matrix module, but it is intended as a DAW-like groovebox. Get in the beta if you like. Interestingly, the LK-like module won't seem to be expanded any time soon for stability reasons ... go figure.
    My guess is that bugfixing LK is too time-consuming (hence costly) for the developers, since the problem seems hard to actually spot and fix (otherwise it would have been fixed long ago).

    After more than year of daily LK use and daily crashes and failures, my reasoning is:

    LK remains my favorite iOS sequencer workflow-wise, but it is too unreliable for serious music production
    LK is clearly too unreliable for true live
    Drambo is slowly evolving into a clip launch controller and is rock-stable
    Helium has clip launch capabilities and seems very stable so far

    Thus, I am transfering all my projects into Helium and/or Drambo and keeping LK only for toying around.
    My advice to new users would be to wait to mid-2024 or so and see if LK got updated before spending any time on it.

    Sorry guys, this is a frustrated user/Imaginando enthusiast speaking ...

    I think it is a bit bold from you to state that we have moved on from LK...

    Yes, we are working on a new product and many here in the forum know that. If you are an enthusiastic Imaginando user you understand that making BAM is mammoth task and we have been stalling ALL products updates to be able release this app this year.

    The changes behind the hood to make BAM happen has forced to stop updates to other apps due to the complexity and the massive improvements that have been made to the core of our technology, specially in what regards to parameters handling, stability and reliability.

    BAM represents the union of all what we have done in the past in a single product. BAM uses the same core of LK, but evolved, something that LK will inherit when it is updated again.

    If you were familiar with our struggles you would understand that it is impossible to work on an update to a complex product while developing an even more complex product on top of the same core features, with a micro sized team, specially when those updates, have always been free of charge.

    Sometimes you need to take a step back in order to move two forward. We are precisely in that point.

    I must agree with you in two things though:

    • LK has stability problems
    • LK will not be updated soon

    I strongly believe that in the end LK will benefit from the BAM effort.

  • @sinosoidal said:
    I strongly believe that in the end LK will benefit from the BAM effort.

    exactly what I had in mind :wink:

  • We've just released a new beta (version 1.13.0 build 299). We learned a lot while developing BAM and there were some major structural changes to our base code. With BAM we really wanted to make a rock solid product, that could be efficient, performative and powerful. In contrast, with LK, our main focus was updating the app with all the features you were asking for, and the structural aspect of the code was somewhat neglected since we simply didn't have the time to work on efficiency while introducing new features. With BAM we decided to take a new approach and rethink our previous code. We knew that this would delay BAM release (and consequentially future updates of our existing apps) but we also knew that our apps would benefit from this new product once it was done.
    LK has now been refactored to incorporate all the new baseline code. We are mostly focused on addressing the UI freeze states that some people were experiencing and also on stability/performance.
    Also, please note that LK underwent some major refactoring. Despite thinking LK has all the functionalities working, let us know if something got broken.

    We're sorry for all this delay on updating LK. But we're back on action, hoping to deliver you all with a more robust and efficient LK =) Thank you all for your patience and for sticking with us!

  • edited November 2023

    @xglax said:
    We've just released a new beta (version 1.13.0 build 299). We learned a lot while developing BAM and there were some major structural changes to our base code. With BAM we really wanted to make a rock solid product, that could be efficient, performative and powerful. In contrast, with LK, our main focus was updating the app with all the features you were asking for, and the structural aspect of the code was somewhat neglected since we simply didn't have the time to work on efficiency while introducing new features. With BAM we decided to take a new approach and rethink our previous code. We knew that this would delay BAM release (and consequentially future updates of our existing apps) but we also knew that our apps would benefit from this new product once it was done.
    LK has now been refactored to incorporate all the new baseline code. We are mostly focused on addressing the UI freeze states that some people were experiencing and also on stability/performance.
    Also, please note that LK underwent some major refactoring. Despite thinking LK has all the functionalities working, let us know if something got broken.

    We're sorry for all this delay on updating LK. But we're back on action, hoping to deliver you all with a more robust and efficient LK =) Thank you all for your patience and for sticking with us!

    Great news!!!! 🍻Is it already on TestFlight?

  • @Janosax said:

    @xglax said:
    We've just released a new beta (version 1.13.0 build 299). We learned a lot while developing BAM and there were some major structural changes to our base code. With BAM we really wanted to make a rock solid product, that could be efficient, performative and powerful. In contrast, with LK, our main focus was updating the app with all the features you were asking for, and the structural aspect of the code was somewhat neglected since we simply didn't have the time to work on efficiency while introducing new features. With BAM we decided to take a new approach and rethink our previous code. We knew that this would delay BAM release (and consequentially future updates of our existing apps) but we also knew that our apps would benefit from this new product once it was done.
    LK has now been refactored to incorporate all the new baseline code. We are mostly focused on addressing the UI freeze states that some people were experiencing and also on stability/performance.
    Also, please note that LK underwent some major refactoring. Despite thinking LK has all the functionalities working, let us know if something got broken.

    We're sorry for all this delay on updating LK. But we're back on action, hoping to deliver you all with a more robust and efficient LK =) Thank you all for your patience and for sticking with us!

    Great news!!!! 🍻Is it already on TestFlight?

    Agree! This is great news. I’ve been using Drambo for sequencing patterns, but it’s kind of overkill (as this is all I use it for) and I like LK’s ability to resize the “building blocks”. I’ll be looking forward to revisiting LK again when the beta becomes the real thing 👍😊

  • @Janosax said:
    Great news!!!! 🍻Is it already on TestFlight?

    Not yet, it is currently being reviewed by apple. Maybe tomorrow =)

  • Awesome! LK is one of my favorites so I’m glad you guys were able to cycle back to it :)

  • @xglax said:

    @Janosax said:
    Great news!!!! 🍻Is it already on TestFlight?

    Not yet, it is currently being reviewed by apple. Maybe tomorrow =)

    Hi, I’ve just tried it and LK beta doesn’t start at all with AUM sync transport and tempo is 20 when AUM is 102. iPhone 14 Pro Max latest iOS.

  • @Janosax said:

    @xglax said:

    @Janosax said:
    Great news!!!! 🍻Is it already on TestFlight?

    Not yet, it is currently being reviewed by apple. Maybe tomorrow =)

    Hi, I’ve just tried it and LK beta doesn’t start at all with AUM sync transport and tempo is 20 when AUM is 102. iPhone 14 Pro Max latest iOS.

    Thanks! We're on it

  • Thanks for the update!! I’m also experiencing weird issues before restoring state, just close LK, reopen and the preset is called name +”restored state”. Then rename and save as… LK now goes to 20bpm or freeze…

  • @Synthi said:
    Thanks for the update!! I’m also experiencing weird issues before restoring state, just close LK, reopen and the preset is called name +”restored state”. Then rename and save as… LK now goes to 20bpm or freeze…

    Can you tell us if the issue persists with the new build we have just published?

  • @xglax said:

    @Janosax said:

    @xglax said:

    @Janosax said:
    Great news!!!! 🍻Is it already on TestFlight?

    Not yet, it is currently being reviewed by apple. Maybe tomorrow =)

    Hi, I’ve just tried it and LK beta doesn’t start at all with AUM sync transport and tempo is 20 when AUM is 102. iPhone 14 Pro Max latest iOS.

    This should be fixed now!

  • @xglax said:
    LK has now been refactored to incorporate all the new baseline code. We are mostly focused on addressing the UI freeze states that some people were experiencing and also on stability/performance.

    That’s the most wonderful news for the LK we could ever expect! It shows your integrity as a team, and it's a reward for everyone who supported and believed in you. 🤩

  • random question but i was wondering what the differences were between lk and atom2 were. i’m really needing an app that does piano roll and intuitive clip launching for performance. can’t really seem to decide between the two. how do people feel who have both? thanks!

  • @drewhino said:
    random question but i was wondering what the differences were between lk and atom2 were. i’m really needing an app that does piano roll and intuitive clip launching for performance. can’t really seem to decide between the two. how do people feel who have both? thanks!

    You might want to start a new thread for that question.

  • @sinosoidal said:

    @xglax said:

    @Janosax said:

    @xglax said:

    @Janosax said:
    Great news!!!! 🍻Is it already on TestFlight?

    Not yet, it is currently being reviewed by apple. Maybe tomorrow =)

    Hi, I’ve just tried it and LK beta doesn’t start at all with AUM sync transport and tempo is 20 when AUM is 102. iPhone 14 Pro Max latest iOS.

    This should be fixed now!

    Yes it’s fixed thanks!!

  • @espiegel123 said:

    @drewhino said:
    random question but i was wondering what the differences were between lk and atom2 were. i’m really needing an app that does piano roll and intuitive clip launching for performance. can’t really seem to decide between the two. how do people feel who have both? thanks!

    You might want to start a new thread for that question.

    yeah i thought so. ok will do

  • Such an essential app.. Thanks

  • @sinosoidal said:

    @Synthi said:
    Thanks for the update!! I’m also experiencing weird issues before restoring state, just close LK, reopen and the preset is called name +”restored state”. Then rename and save as… LK now goes to 20bpm or freeze…

    Can you tell us if the issue persists with the new build we have just published?

    Seem to e resolved!! 🙏🏻

  • @Janosax said:
    LK4Ever <3

    Please let us know if it is better stability wise. We are looking for a freeze free experience.

  • @sinosoidal said:

    @Janosax said:
    LK4Ever <3

    Please let us know if it is better stability wise. We are looking for a freeze free experience.

    Will do some test in the coming days and let you know! I hope for the best

  • edited November 2023

    @xglax all midi learn settings are lost in beta

    AppStore version

    Beta version

  • @Janosax said:
    @xglax all midi learn settings are lost in beta

    AppStore version

    Beta version

    Have you tried sending midi messages to LK to confirm that the mappings are lost? Just to make sure this isn't only a bug on the labels

  • @xglax said:

    @Janosax said:
    @xglax all midi learn settings are lost in beta

    AppStore version

    Beta version

    Have you tried sending midi messages to LK to confirm that the mappings are lost? Just to make sure this isn't only a bug on the labels

    Yes midi messages were not received too.

Sign In or Register to comment.