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

18081838586130

Comments

  • @Tatobx said:

    @sinosoidal said:

    @Tatobx said:

    @sinosoidal said:

    @Tatobx said:

    @Tatobx said:

    @sinosoidal said:

    @Tatobx said:
    Hi @sinosoidal I have a problem with mapping. I create 8 traks and 2 scenes and with the Midi Learn i mapped each clip with the 16 pads on my Novation Launchkey Mini MK3. After I armed a track I vould like engage the clip but mapping don’t match. Happen both on AUM and also standalone, both if I send Note that if I send CC.
    Thanks

    We need to investigate. Thanks for reporting.

    OK thanks. If you want to replicate the problem you can also try the AUM's internal keyboard or a software controller like KB-1. You need to add two or more scenes

    iPadPro 1st Gen - iPadOs 13.7

    Hi @sinosoidal , have you any news about this?
    Thanks

    We are aiming fix for that to next version 1.10.5. Beta testing should start next week. Sorry for the delay! :disappointed:

    Great, I'm in beta and will try it. Thanks so much

    We have submitted a beta version for App Store with the fix for this problem. It will take a while for App Store to allow the beta to be distributed to external testers but you will get an notification when it's ready. 1.10.25 (build 225)

    I @sinosoidal , I tested new beta. Midi mapping on the empty clips works really well in standalone (thank you so much)

    Great!

    By the way, I forgot to warn in the beta description. This fix will invalidate any previous midi learn mapping because it is a completely new model.

    Also, while the mapping directly on LK keeps tied to a certain track or slot, and if we add tracks the mapping will follow the track/slot.

    However if the mapping is done via AUM parameters, it will not work the same way. AUM parameters are absolute. A mapping made to Track 2 mute will always be on track 2, even if the track 2 is not track 3 because a new track has been inserted before.

    but on AUM:

    when I start recording, the clip stops recording automatically after 1 bar (or the value in “Trigger Quant.”).

    Can you make a small video reproducing this problem?

    the midi map of the global record button doesn’t work
    This happens only with my midi controller (LaunchKey Mini MK3), but if I map LK with software midi controller (eg. the internal key of AUM or KB-1) works well.

    Lets see what we find.

    Another thing only on AUM: LK is back in demo mode and the “Restore purchases” doesn’t work.

    I would say that is normal because you are using a beta and real purchases are not valid in beta mode. The good news is that you can purchase everything on the beta without paying.

    I recently learned that my controller will soon be natively supported by LK and I can wait, it was just to report this.

    Yes, I'm going to submit a new build which will add a lot of fixes and support for Launchkey Mini Mk3 and Launchpad Mini Mk3

  • I've just uploaded LK 1.10.5 (build 226) with the following changes:

    • Add support to Launchkey Mini Mk3
    • Add support to Launchpad Mini Mk3
    • Improve X/Y module midi/live assignment
    • Improve cc value label
    • Improve layout of modules with beat/clip time display
    • Fix a problem with midi learn that would break on song model changes
    • Fix vertical viewport navigation with fold notes
    • General bug fixes and improvements
  • @sinosoidal said:
    I've just uploaded LK 1.10.5 (build 226) with the following changes:

    • Add support to Launchkey Mini Mk3
    • Add support to Launchpad Mini Mk3
    • Improve X/Y module midi/live assignment
    • Improve cc value label
    • Improve layout of modules with beat/clip time display
    • Fix a problem with midi learn that would break on song model changes
    • Fix vertical viewport navigation with fold notes
    • General bug fixes and improvements

    LaunchKey Mini MK3 works perfectly here. It is perfectly integrated, the best solution for my current workflow! Huge!!
    The only thing I can't understand is how the individual tracks are armed for recording with the controller (if it is possible).

    To thank you for all this work you keep doing I'm going to buy FRMS (I already have everything else) :))

  • @Tatobx said:

    @sinosoidal said:
    I've just uploaded LK 1.10.5 (build 226) with the following changes:

    • Add support to Launchkey Mini Mk3
    • Add support to Launchpad Mini Mk3
    • Improve X/Y module midi/live assignment
    • Improve cc value label
    • Improve layout of modules with beat/clip time display
    • Fix a problem with midi learn that would break on song model changes
    • Fix vertical viewport navigation with fold notes
    • General bug fixes and improvements

    LaunchKey Mini MK3 works perfectly here. It is perfectly integrated, the best solution for my current workflow! Huge!!
    The only thing I can't understand is how the individual tracks are armed for recording with the controller (if it is possible).

    The controller itself does not seem to have this functionality. It allows to stop, solo and mute a track, but not work. Personally I think it was a poor decision.

    We always try to mimic the original controller intended behaviour/functionality. If you think we are missing something, please let us know.

    To thank you for all this work you keep doing I'm going to buy FRMS (I already have everything else) :))

    Thank you for your feedback and support. It means the world to us! :blush:

  • edited April 2021

    @sinosoidal said:
    The controller itself does not seem to have this functionality. It allows to stop, solo and mute a track, but not work. Personally I think it was a poor decision.

    We always try to mimic the original controller intended behaviour/functionality. If you think we are missing something, please let us know.

    Could you add something like "Arm track when selected" in LK's preferences to turn it on or off?

    To thank you for all this work you keep doing I'm going to buy FRMS (I already have everything else) :))

    Thank you for your feedback and support. It means the world to us! :blush:

    While I was there, I also bought Iconic sound 2 & 3 for my DRC :))

  • edited April 2021

    @Tatobx said:

    @sinosoidal said:
    The controller itself does not seem to have this functionality. It allows to stop, solo and mute a track, but not work. Personally I think it was a poor decision.

    We always try to mimic the original controller intended behaviour/functionality. If you think we are missing something, please let us know.

    Could you add something like "Arm track when selected" in LK's preferences to turn it on or off?

    I didn't want to add a general setting that will only work with a specific controller, if you know what I mean. I think this is definitely a bad design design from Novation not including the track arm functionality in the same button you do solo and mute.

    Ideally, this could be implemented as something using only the controller itself. Some sort of combination of key press that does not conflict with the implementation and plays well with current work follow.

    I would love to have more Launchkey users around so we could find a solution toghether.

    To thank you for all this work you keep doing I'm going to buy FRMS (I already have everything else) :))

    Thank you for your feedback and support. It means the world to us! :blush:

    While I was there, I also bought Iconic sound 2 & 3 for my DRC :))

    Thank you! :blush:

  • edited April 2021

    @sinosoidal said:

    @Tatobx said:

    @sinosoidal said:
    The controller itself does not seem to have this functionality. It allows to stop, solo and mute a track, but not work. Personally I think it was a poor decision.

    We always try to mimic the original controller intended behaviour/functionality. If you think we are missing something, please let us know.

    Could you add something like "Arm track when selected" in LK's preferences to turn it on or off?

    I didn't want to add a general setting that will only work with a specific controller, if you know what I mean. I think this is definitely a bad design design from Novation not including the track arm functionality in the same button you do solo and mute.

    Ideally, this could be implemented as something using only the controller itself. Some sort of combination of key press that does not conflict with the implementation and plays well with current work follow.

    I actually saw it as a general setting and not specific to a controller. It could be very convenient during an improvisation set regardless of the controller used.
    Ableton Live does the same thing if you unarmed all tracks, then right click on the arm button and turn off arm exclusive.
    https://youtube.com/watch?v=IWABDpX3Htw&t=155s

    I would love to have more Launchkey users around so we could find a solution toghether.

    Alternatively as a specific shortcut for the controller I would propose “hold global REC and select the track to arm it” or “hold Fixed chord and select the track to arm it”

    Thank you

  • In case you need to work several tracks at the same time you can disable it from the preferences or, Ableton style, by long pressing the arm record button ;)

  • edited April 2021

    @Tatobx said:
    Alternatively as a specific shortcut for the controller I would propose “hold global REC and select the track to arm it”

    This was precisely the first thing that crossed my mind when thinking about an alternative! :blush:

  • Updated... nice... seems much smoother on my early dig...

    Thanks.. sweet.

  • @sinosoidal said:
    I would love to have more Launchkey users around so we could find a solution toghether.

    Just saw that launchkey support was added, really awesome! (LK for LK;) ) Just started exploring what it can do with my launchkey mini mk3, thanks for this :) happy to test specific things if needed.

  • @RajahP said:
    Updated... nice... seems much smoother on my early dig...

    Thanks.. sweet.

    :blush:

  • @mangecoeur said:

    @sinosoidal said:
    I would love to have more Launchkey users around so we could find a solution toghether.

    Just saw that launchkey support was added, really awesome! (LK for LK;) ) Just started exploring what it can do with my launchkey mini mk3, thanks for this :) happy to test specific things if needed.

    Looking forward to hear your feedback!

  • Hi @sinosoidal would it be possible for the Play and Rec buttons to light up in LaunchKey when activated? Thanks

  • edited April 2021

    Anyone else having this delay, when hosting LK in Drambo, switching from LK module to LK module?

  • @Frank303 said:
    Anyone else having this delay, when hosting LK in Drambo, switching from LK module to LK module?

    Switching LK modules is smooth here, but my Drambo projects have less tracks than yours, about 5-6. Could it be the CPU load? I’m on an iPad 2020 10.2 btw

  • wimwim
    edited April 2021

    That was my first thought as well. There are a lot of tracks going on there. The delay doesn't surprise me. Both LK and AUM are certainly going to prioritize audio and midi processing over UI updates so as to not produce audio glitches.

  • edited April 2021

    @branis
    Bad example perhaps. It’s the same with a new track.
    (Edit: sorry the gif maker app speeds it up but hope you get the idea 😂)

  • I wonder if it will help to enable reduce motion in the iOS accessibility settings. I do that and it helps with many things on my aging iPad.

  • @wim thanks! As for my tired eyes, while still in the same session and changing that setting funnily enough seems to shave of about 0.5 seconds of the 2. But I need to investigate that more tomorrow, as 4 am kinda calls for some sleep 😂

  • @Frank303 said:
    Anyone else having this delay, when hosting LK in Drambo, switching from LK module to LK module?

    What's your device?

  • @wim said:
    That was my first thought as well. There are a lot of tracks going on there. The delay doesn't surprise me. Both LK and AUM are certainly going to prioritize audio and midi processing over UI updates so as to not produce audio glitches.

    Yes, that is correct. If the device is a bit older, than everything will get worst.

  • @Tatobx said:
    Hi @sinosoidal would it be possible for the Play and Rec buttons to light up in LaunchKey when activated? Thanks

    If there is a light, we shall turn it on! :smiley:

  • edited April 2021

    @sinosoidal I got the iPad mini 5th gen, iOS 14.4.1. I’m on TestFlight. I tested with standalone, no problem. In AUM and Audiobus same problem as in Drambo, in all three hosts, with a fresh restart, and all right after opening, new projects. Deleted LK, reinstalled the TestFlight, and it appears the have helped, a bit. Now down to 0.5 as opposed to 2.0 sec before enabling the ‘reduce motion’ iOS setting. This short delay was perhaps always there, isn’t really an issue. I’m on limited data otherwise I would also have tried installing the AppStore version.

  • @sinosoidal By default each time you open a saved AUM project it seems all the controllers in the LK Controllers list are set to green (active). Is it possible to make that setting persist in an AUM session so I can have them inactive to avoid conflicts?
    In my experience the setting persists with other apps.

    If i use the LP session mode with something else (which I do all the time) it conflicts with the LK mapping and I have to go in and manually disable every time I open the project.

    I'm not sure what the "cost" is of having all the Controllers active but I think there would be hardly anybody using more than one Controller connection. (Controllers as opposed to Midi connections)

  • @soundtemple said:
    @sinosoidal By default each time you open a saved AUM project it seems all the controllers in the LK Controllers list are set to green (active). Is it possible to make that setting persist in an AUM session so I can have them inactive to avoid conflicts?
    In my experience the setting persists with other apps.

    If i use the LP session mode with something else (which I do all the time) it conflicts with the LK mapping and I have to go in and manually disable every time I open the project.

    I'm not sure what the "cost" is of having all the Controllers active but I think there would be hardly anybody using more than one Controller connection. (Controllers as opposed to Midi connections)

    Yes, it can be done! Thanks for pointing this out. Should be fixed on 1.10.6.

  • @sinosoidal said:

    @Tatobx said:
    Hi @sinosoidal would it be possible for the Play and Rec buttons to light up in LaunchKey when activated? Thanks

    If there is a light, we shall turn it on! :smiley:

    Great!! :)

  • Is anyone using the X/Y Pad in LK?

    For some reason, this only works for me as an X-pad - that is, movement on the Y-axis does not register into the second Y-coordinate: both X and Y appear to be only controlled by movement along the X-axis.
    Am I missing something here, or might there be a bug? - Thanks!

    I am trying to use an X/Y pad in MIDI mode to emit two different controller values. Reaching for LK appears easier than creating a Mozaic script for this.

  • @Tim6502 said:
    Is anyone using the X/Y Pad in LK?

    For some reason, this only works for me as an X-pad - that is, movement on the Y-axis does not register into the second Y-coordinate: both X and Y appear to be only controlled by movement along the X-axis.
    Am I missing something here, or might there be a bug? - Thanks!

    I am trying to use an X/Y pad in MIDI mode to emit two different controller values. Reaching for LK appears easier than creating a Mozaic script for this.

    It’s working as expected here.

Sign In or Register to comment.