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

15152545657130

Comments

  • @skrat said:

    @RajahP said:
    Is it me, of is it difficult to just record to a clip? How do you do it, Thanks..

    Looking forward to the ‘fold’ update.. nice..

    With MIDI controller on current stable version it's virtually impossible, so it's not you, just wait for update 😉

    Is an update for this planned.. seems it’s essential.. anyway, thought it was me.. Thanks..

  • @sinosoidal : LK is sometimes recording notes when link to host is on if you have record-enabled a clip but haven't started the host transport.

    • New LK project in AUM
    • Set Link to source on
    • Long tap on the 1 bar long empty clip and choose delete (as I want to record clip of unknown duration)
    • Set the track to record mode
    • Tap the clip to record enable
    • Play some notes WITHOUT having tapped play in AUM
    • OBSERVE: the pressed keys are recorded at time zero
  • @espiegel123 said:
    @sinosoidal : LK is sometimes recording notes when link to host is on if you have record-enabled a clip but haven't started the host transport.

    • New LK project in AUM
    • Set Link to source on
    • Long tap on the 1 bar long empty clip and choose delete (as I want to record clip of unknown duration)
    • Set the track to record mode
    • Tap the clip to record enable
    • Play some notes WITHOUT having tapped play in AUM
    • OBSERVE: the pressed keys are recorded at time zero

    Nice catch. Thanks for reporting!

  • I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

  • @sinosoidal : is it intentional that LK only registers one touch at a time? I've noticed but never mentioned that trying to start multiple clips at once by touching them at the same time doesn't work.

  • @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    A huge improvement! Thanks for a super quick update :smile:

    One thing I noticed at first glance, I don’t know if it’s intentional, is if I press full screen first and then inspector, the composer fully expands, but if I first press inspector and then full screen, the composer doesn’t stretch vertically.

    Also, if the composer is fully expanded (first case from above) and I press full screen twice, the composer won’t get back to being fully vertically stretched.

  • If I remember correctly...with an external controller like apc mini it works ( even though I remember pressing 2 pads) but it definitely works with the entire row...trigger the entire row with the right side pad > @espiegel123 said:

    @sinosoidal : is it intentional that LK only registers one touch at a time? I've noticed but never mentioned that trying to start multiple clips at once by touching them at the same time doesn't work.

  • in us 1.9.3. not available yet...

  • @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    This is great 😊

    I found one thing:

    If the clips view is in full screen

    And I tap on the inspector button to open the pianoroll in full screen

    Then I have to tap twice on the full screen button to get the nice track overview visible at the top of the screen

  • edited January 2021

    @espiegel123 said:

    @sinosoidal : is it intentional that LK only registers one touch at a time? I've noticed but never mentioned that trying to start multiple clips at once by touching them at the same time doesn't work.

    It should work. We are definirely missing something here.

  • @Sergiu said:
    in us 1.9.3. not available yet...

    It is under testing. Not yet available on the App Store. Let me know if you want to join TestFlight.

  • @White said:

    @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    This is great 😊

    I found one thing:

    If the clips view is in full screen

    And I tap on the inspector button to open the pianoroll in full screen

    Then I have to tap twice on the full screen button to get the nice track overview visible at the top of the screen

    Read this a couple of times but didn't get it. Are you saying the same as @branis in the comment above yours?

  • @sinosoidal said:

    @White said:

    @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    This is great 😊

    I found one thing:

    If the clips view is in full screen

    And I tap on the inspector button to open the pianoroll in full screen

    Then I have to tap twice on the full screen button to get the nice track overview visible at the top of the screen

    Read this a couple of times but didn't get it. Are you saying the same as @branis in the comment above yours?

    No I don't think so 😊

    What I'm trying to say is, that if I 'm in full screen in the clips view and then tap on the inspector button to go to the piano roll, then it opens in full screen view as expected, but I then have to tap twice on the full screen button to get it to show the track overview (In my 3rd picture, the one with the yellow "Chords", "Melody", "Drum", "Bass" at the top of the pianoroll)

  • @White said:

    @sinosoidal said:

    @White said:

    @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    This is great 😊

    I found one thing:

    If the clips view is in full screen

    And I tap on the inspector button to open the pianoroll in full screen

    Then I have to tap twice on the full screen button to get the nice track overview visible at the top of the screen

    Read this a couple of times but didn't get it. Are you saying the same as @branis in the comment above yours?

    No I don't think so 😊

    What I'm trying to say is, that if I 'm in full screen in the clips view and then tap on the inspector button to go to the piano roll, then it opens in full screen view as expected, but I then have to tap twice on the full screen button to get it to show the track overview (In my 3rd picture, the one with the yellow "Chords", "Melody", "Drum", "Bass" at the top of the pianoroll)

    I think we are talking about the same thing, but with different expectations :smile:

    @branis said:
    Also, if the composer is fully expanded (first case from above) and I press full screen twice, the composer won’t get back to being fully vertically stretched.

  • @branis said:

    @White said:

    @sinosoidal said:

    @White said:

    @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    This is great 😊

    I found one thing:

    If the clips view is in full screen

    And I tap on the inspector button to open the pianoroll in full screen

    Then I have to tap twice on the full screen button to get the nice track overview visible at the top of the screen

    Read this a couple of times but didn't get it. Are you saying the same as @branis in the comment above yours?

    No I don't think so 😊

    What I'm trying to say is, that if I 'm in full screen in the clips view and then tap on the inspector button to go to the piano roll, then it opens in full screen view as expected, but I then have to tap twice on the full screen button to get it to show the track overview (In my 3rd picture, the one with the yellow "Chords", "Melody", "Drum", "Bass" at the top of the pianoroll)

    I think we are talking about the same thing, but with different expectations :smile:

    @branis said:
    Also, if the composer is fully expanded (first case from above) and I press full screen twice, the composer won’t get back to being fully vertically stretched.

    I think you're right 😊

  • @White said:

    @branis said:

    @White said:

    @sinosoidal said:

    @White said:

    @sinosoidal said:
    I've just published a new build of version 1.9.3 which has the following two new features:

    • Added fullscreen mode button to bottom bar
    • Added inspector button button to bottom bar

    @branis, fullscreen mode should solve your spacing problems. Let me kmow how does it feel.

    The inspector button on the bottom bar allows to open/close the composer, on matrix, and the module settings panel on any other module page avoid the drag/tapping the dividing bar.

    I hope this small improvements contribute to improve your workflow. :blush:

    This is great 😊

    I found one thing:

    If the clips view is in full screen

    And I tap on the inspector button to open the pianoroll in full screen

    Then I have to tap twice on the full screen button to get the nice track overview visible at the top of the screen

    Read this a couple of times but didn't get it. Are you saying the same as @branis in the comment above yours?

    No I don't think so 😊

    What I'm trying to say is, that if I 'm in full screen in the clips view and then tap on the inspector button to go to the piano roll, then it opens in full screen view as expected, but I then have to tap twice on the full screen button to get it to show the track overview (In my 3rd picture, the one with the yellow "Chords", "Melody", "Drum", "Bass" at the top of the pianoroll)

    I think we are talking about the same thing, but with different expectations :smile:

    @branis said:
    Also, if the composer is fully expanded (first case from above) and I press full screen twice, the composer won’t get back to being fully vertically stretched.

    I think you're right 😊

    @White unfortunately, the nice track overview is an happy coincidence.

    Right now, the way the splitview open and close is implemented does not know when we have entered fullscreen or not. So, when you enter in fullscreen and then exit, what happens in that the clip composer height is less by "track label height".

    I believe what you are expecting to happen is an exception. If it is fullscreen, it is fullscreen, and not fullsceen minus "track label height". Do you know what I mean?

    If I have too choose here, I would probably choose over strict full screen, and fix the split view to fit that rule.

  • @sinosoidal said:
    If I have too choose here, I would probably choose over strict full screen, and fix the split view to fit that rule.

    Yes, I can see it now, that's the best choice 👍

  • edited January 2021

    @sinosoidal cant wait to try full screen and note fold. You’re killing it at the moment!

    As I do most of my initial ideas on iPhone I’m really grateful for the extra screen space and thought out into the layout. It feels generally so much better now than when I first got the app.

    Thank you

  • @RajahP said:
    Is it me, of is it difficult to just record to a clip? How do you do it, Thanks..

    How are you doing it?

  • @skrat said:
    With MIDI controller on current stable version it's virtually impossible, so it's not you, just wait for update 😉

    What do you mean with this?

  • @gregsmith said:
    @sinosoidal cant wait to try full screen and note fold. You’re killing it at the moment!

    As I do most of my initial ideas on iPhone I’m really grateful for the extra screen space and thought out into the layout. It feels generally so much better now than when I first got the app.

    Thank you

    Thanks for your feedback and support. Wanna join the TestFlight?

  • edited January 2021

    The full screen and note fold things looks like it’ll really change things, great stuff!

  • @sinosoidal said:

    @skrat said:
    With MIDI controller on current stable version it's virtually impossible, so it's not you, just wait for update 😉

    What do you mean with this?

    Sorry, I believed RajahP meant the bug with recording (afaik connected to MIDI controller recording but maybe just recording in general, honestly didn't tried that other way than over MIDI keyboard), but now I see the version with fix was released in stable version 6 days ago.
    So @RajahP, if you updated in last 6 days and the issue is still happening, you'd need to be more specifics about steps how to reproduce te bug.

  • I am trowing this question here :
    LK can record CC 64 sustain pedal from my keyboard (it is recorded in LK).
    However never played back to the Virtual Instrument. I have also routed a MIDI spy and indeed it is not there. No CC.

    Any clues ? Is it a known feature/bug ?

  • @Sylvain said:
    I am trowing this question here :
    LK can record CC 64 sustain pedal from my keyboard (it is recorded in LK).
    However never played back to the Virtual Instrument. I have also routed a MIDI spy and indeed it is not there. No CC.

    Any clues ? Is it a known feature/bug ?

    I don't have a sustain pedal, but I have a sustain button on my Korg nanoKey studio which sends CC64. I tested with Korg Module and it works fine.

    Could this be connected to the behavior when CCs are not transmitted if record is still engaged? Can you check if it works after you depress the track record button right after you record MIDI?

  • @branis said:

    @Sylvain said:
    I am trowing this question here :
    LK can record CC 64 sustain pedal from my keyboard (it is recorded in LK).
    However never played back to the Virtual Instrument. I have also routed a MIDI spy and indeed it is not there. No CC.

    Any clues ? Is it a known feature/bug ?

    I don't have a sustain pedal, but I have a sustain button on my Korg nanoKey studio which sends CC64. I tested with Korg Module and it works fine.

    Could this be connected to the behavior when CCs are not transmitted if record is still engaged? Can you check if it works after you depress the track record button right after you record MIDI?

    Thanks a lot, Indeed. As soon as I stopped the record button the CC 64 messages appeared.
    Ok then CC are not played back when recording, is it a wanted feature ?

  • @Sylvain said:

    @branis said:

    @Sylvain said:
    I am trowing this question here :
    LK can record CC 64 sustain pedal from my keyboard (it is recorded in LK).
    However never played back to the Virtual Instrument. I have also routed a MIDI spy and indeed it is not there. No CC.

    Any clues ? Is it a known feature/bug ?

    I don't have a sustain pedal, but I have a sustain button on my Korg nanoKey studio which sends CC64. I tested with Korg Module and it works fine.

    Could this be connected to the behavior when CCs are not transmitted if record is still engaged? Can you check if it works after you depress the track record button right after you record MIDI?

    Thanks a lot, Indeed. As soon as I stopped the record button the CC 64 messages appeared.
    Ok then CC are not played back when recording, is it a wanted feature ?

    I don't think so. I believe it's a bug

  • @sinosoidal said:

    @gregsmith said:
    @sinosoidal cant wait to try full screen and note fold. You’re killing it at the moment!

    As I do most of my initial ideas on iPhone I’m really grateful for the extra screen space and thought out into the layout. It feels generally so much better now than when I first got the app.

    Thank you

    Thanks for your feedback and support. Wanna join the TestFlight?

    Yes please! What do I do?

  • @sinosoidal said:

    @RajahP said:
    Is it me, of is it difficult to just record to a clip? How do you do it, Thanks..

    How are you doing it?

    Just placing a blank clip and setting record.. and hitting play in AUM... and it won’t record.. seems this is standard...

  • @RajahP said:

    @sinosoidal said:

    @RajahP said:
    Is it me, of is it difficult to just record to a clip? How do you do it, Thanks..

    How are you doing it?

    Just placing a blank clip and setting record.. and hitting play in AUM... and it won’t record.. seems this is standard...

    It is working for me . Perhaps you can post a video

Sign In or Register to comment.