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!!

1…4849515354…130

Comments

  • sinosoidalsinosoidal

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

  • aratxtraratxtr

    @sinosoidal said:

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

    Oh Yeah! Obrigado!

  • krassmannkrassmann

    @sinosoidal said:

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

    That was fast 👏👏👏

  • sinosoidalsinosoidal

    @krassmann said:

    @sinosoidal said:

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

    That was fast 👏👏👏

    1.9.2 beta became available this night. Are you in TestFlight?

  • w_irow_iro

    I got beta, MIDI workin fine right now, but i got 70-95 % DSP usage on iPad Pro 2018. Anybody got similar problem?

  • sinosoidalsinosoidal

    @w_iro said:
    I got beta, MIDI workin fine right now, but i got 70-95 % DSP usage on iPad Pro 2018. Anybody got similar problem?

    Is that an AUM project? Can you please share the project with me? If you are ok with that, please send me a pvt message with it.

  • w_irow_iro
    edited January 2021

    @sinosoidal said:

    @w_iro said:
    I got beta, MIDI workin fine right now, but i got 70-95 % DSP usage on iPad Pro 2018. Anybody got similar problem?

    Is that an AUM project? Can you please share the project with me? If you are ok with that, please send me a pvt message with it.

    hm, weird thing i opened project again and now is fine, no cpu spikes :D

    i will observe this and send you a pvt messege if any problem occurs

  • sinosoidalsinosoidal

    @w_iro said:

    @sinosoidal said:

    @w_iro said:
    I got beta, MIDI workin fine right now, but i got 70-95 % DSP usage on iPad Pro 2018. Anybody got similar problem?

    Is that an AUM project? Can you please share the project with me? If you are ok with that, please send me a pvt message with it.

    hm, weird thing i opened project again and now is fine, no cpu spikes :D

    i will observe this and send you a pvt messege if any problem occurs

    Great! Thanks! :)

  • ronniebronnieb

    @sinosoidal said:

    1.9.2 beta became available this night. Are you in TestFlight?

    How do I sign up for the beta? I already have test flight :)

  • sinosoidalsinosoidal

    @ronnieb said:

    @sinosoidal said:

    1.9.2 beta became available this night. Are you in TestFlight?

    How do I sign up for the beta? I already have test flight :)

    Please send me a private message with your email. :blush:

  • NTKKNTKK

    Hi @sinosoidal
    Would it be possible to make a view mode in the controller module where you can see more than 8 channels at a time?

  • sinosoidalsinosoidal
    edited January 2021

    @NTKK said:
    Hi @sinosoidal
    Would it be possible to make a view mode in the controller module where you can see more than 8 channels at a time?

    16 would be feasible on iPad but not on a phone (everything would be extremely small). This exception would break things up a lot. I don't say it is impossible, but not a priority.

  • NTKKNTKK

    Sure - Guess I'll just build a version in Lemur.

  • aratxtraratxtr

    @sinosoidal said:

    @krassmann said:

    @sinosoidal said:

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

    That was fast 👏👏👏

    1.9.2 beta became available this night. Are you in TestFlight?

    Just checked. Works just fine now with the Arturia Midilab. Thanks!

  • krassmannkrassmann
    edited January 2021

    @sinosoidal said:

    @krassmann said:

    @sinosoidal said:

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

    That was fast 👏👏👏

    1.9.2 beta became available this night. Are you in TestFlight?

    Just jammed for an hour without any problems. I even turned the Korg nanoKey Studio’s MIDI clock on again. Before I could reproduce the bug within 5 min with this setup. Seems like you cracked it.

    One more thing: since LK supports the Launchpad mini mk2 it is so much more fun to jam around with LK. It really lifts my AUM workflow on another level. It took me a while to find out about the mixer page. You should add that to the docs.

  • sinosoidalsinosoidal

    @krassmann said:

    @sinosoidal said:

    @krassmann said:

    @sinosoidal said:

    @sinosoidal said:

    @krassmann said:

    @aratxtr said:

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Today tried to trigger LK inside AUM with my Digitakt, which i trigger with my old Korg R3 as a midi keyboard. Elektron send midi clock was turned off. Korgs clock was on external. Bug still appeared.. no more latching notes, but LK does not get triggered after a while, then works again after a while. Also tried it with only the Arturia Minilab mkII as a midi keyboard, but the same problems appeared. For the Arturia i do not have the editor, so i dont know about its midi clock, but since it has no arpeggio or sequenzer buildt in. But yes, AUV3 keyboards inside AUM do work when the external gear is disconnected.

    I need to update my bug report. The other day I was just trying different setups to find the problem but today I really played and then I noticed that the problem still persists although MIDI clock from my external MIDI keyboard is turned off. The problem has just changed. As before there are notes accepted and routed through LK and suddenly notes are ignored. But now the length of these intervals got much longer. Now I can play about 3-5 minutes and then there is the same duration of LK ignoring notes. Also controlling LK from my connected Lanchpad mini mk2 is not working then. This happens regardless if my Korg nanoKey Studio is connected via BT or wired.

    Thanks for your update. We have created this form to try to gather more information about the bug:

    https://forms.gle/hucojKcAysWDwbRU9

    Thank you! :blush:

    Finally! We have identified the problem. It was happening only on iOS 14 and above.

    We should have a beta version of 1.9.2 that fixes the problem. Looking forward to share this with all of you.

    Thanks for those who answered the form. It was crucial to identify the problem! :blush:

    That was fast 👏👏👏

    1.9.2 beta became available this night. Are you in TestFlight?

    Just jammed for an hour without any problems. I even turned the Korg nanoKey Studio’s MIDI clock on again. Before I could reproduce the bug within 5 min with this setup. Seems like you cracked it.

    Awesome! :smile:

    One more thing: since LK supports the Launchpad mini mk2 it is so much more fun to jam around with LK. It really lifts my AUM workflow on another level. It took me a while to find out about the mixer page. You should add that to the docs.

    What is the mixer page for you?

    Thanks for your feedback! :blush:

  • krassmannkrassmann

    @sinosoidal said:
    What is the mixer page for you?

    Thanks for your feedback! :blush:

    I've applied the ableton labels to my launchpad and when I push the mixer button (on the top right) this Launchpad ‘page‘ appears where you can adjust levels, mutes, solo, etc just as it’s labeled for ableton. That enables to operate LK with the LP when the song is playing and can leave LK‘s UI closed.

  • sinosoidalsinosoidal

    @krassmann said:

    @sinosoidal said:
    What is the mixer page for you?

    Thanks for your feedback! :blush:

    I've applied the ableton labels to my launchpad and when I push the mixer button (on the top right) this Launchpad ‘page‘ appears where you can adjust levels, mutes, solo, etc just as it’s labeled for ableton. That enables to operate LK with the LP when the song is playing and can leave LK‘s UI closed.

    Oh, I understand now. I believe that dedicated controller support is still not mentioned anywhere in the documentation. That was what you were suggesting.

  • sclurbssclurbs
    edited January 2021

    This is amazing.

    700$ for Ableton Suite has been a joke for many years now, but god damn, they're like decades behind 15$ apps like AUM. What a joke of a company. EDIT: sorry, just salty that Ableton has failed to recognize 3 of my 100% perfectly functional audio interfaces for the 12th time this week. Apparently for 700$ what you need to do is reload the program multiple times, and restart your computer and then maybe if you're lucky Ableton will decide that yes, yes, an audio interface is indeed connected. Meanwhile: AUM has never failed me for more than a few seconds at a time.

  • clowmclowm

    @sinosoidal I’m having trouble to correctly record pitchbend messages in LK AUv3 on iPhone. It records far too less events than was being sent.

  • sinosoidalsinosoidal

    @clowm said:
    @sinosoidal I’m having trouble to correctly record pitchbend messages in LK AUv3 on iPhone. It records far too less events than was being sent.

    What is your grid quantization value?

  • rs2000rs2000

    @sclurbs said:
    This is amazing.

    700$ for Ableton Suite has been a joke for many years now, but god damn, they're like decades behind 15$ apps like AUM. What a joke of a company. EDIT: sorry, just salty that Ableton has failed to recognize 3 of my 100% perfectly functional audio interfaces for the 12th time this week. Apparently for 700$ what you need to do is reload the program multiple times, and restart your computer and then maybe if you're lucky Ableton will decide that yes, yes, an audio interface is indeed connected. Meanwhile: AUM has never failed me for more than a few seconds at a time.

    You must be kidding. Seriously.

  • SergiuSergiu
    edited January 2021

    I feel the same when i see that similar tasks can be achieved outside of my Ableton Live ( which I started with...) but I would not say Ableton Suite its a joke or behind iOS working environment. After all, you can make really cool tracks with both setups.

    And, I forgot about max4live....that is a playground...similar to iOS apps...some are free...some are $10

  • clowmclowm

    @sinosoidal said:

    @clowm said:
    @sinosoidal I’m having trouble to correctly record pitchbend messages in LK AUv3 on iPhone. It records far too less events than was being sent.

    What is your grid quantization value?

    I'm recording into new clip with Rec Quant set to None.
    I just tried to record into empty clip with a "snap to grid" setting turned off — same result.

  • sinosoidalsinosoidal

    @clowm said:

    @sinosoidal said:

    @clowm said:
    @sinosoidal I’m having trouble to correctly record pitchbend messages in LK AUv3 on iPhone. It records far too less events than was being sent.

    What is your grid quantization value?

    I'm recording into new clip with Rec Quant set to None.
    I just tried to record into empty clip with a "snap to grid" setting turned off — same result.

    Rec Quantization setting on status bar will only affect notes recording.

    There is a grid quantization setting on the clip composer status bar. Try to set it to 1/32 or to none and see if the results are different.

  • SergiuSergiu

    Anyone using the Akai apc mini with Lk? for triggering the clips?

  • sinosoidalsinosoidal

    @Sergiu said:
    Anyone using the Akai apc mini with Lk? for triggering the clips?

    We have one in the office. Any particular question about it?

  • sinosoidalsinosoidal

    Version 1.9.2 released to the App Store:

    • Fix midi input bug
    • Fix layout issues on smaller screens
    • Fix glitch while recording notes to a clip
    • Fixes a bug where a note off wouldn't be sent out on clip stop
    • General bug fixes and improvements
  • SergiuSergiu

    How’s the mapping integration? Can I recall as preset , once the pads are mapped?> @sinosoidal said:

    @Sergiu said:
    Anyone using the Akai apc mini with Lk? for triggering the clips?

    We have one in the office. Any particular question about it?

  • sinosoidalsinosoidal

    @Sergiu said:
    How’s the mapping integration? Can I recall as preset , once the pads are mapped?> @sinosoidal said:

    @Sergiu said:
    Anyone using the Akai apc mini with Lk? for triggering the clips?

    We have one in the office. Any particular question about it?

    You just need to connect the controller. It will automatically reflect the clip grid on the pads. Is that you are looking for?

Sign In or Register to comment.

© Vanilla Keystone Theme 2024