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

16970727475130

Comments

  • edited March 2021

    @tahiche said:

    @RajahP said:

    @tahiche said:

    @krassmann said:
    I have some great news for the LK users that are searching for a solution for audio clips. Earlier in this thread I described an idea for the @4Pockets MultiTrack plugin to have a better integration with a scene based sequencer. I also wrote that to Paul the developer and he did it. The soon to be released version 1.14 of MultiTrack will contain an experimental snapshot feature. These snapshots store the loop region or playhead position and can be triggered by MIDI.

    I know this might not be helpful for a totally freestyle clip launching workflow - you must wait for Loopy Pro 😊 But I think it’s great for a workflow that is based on scenes in LK.

    Here is the help text for that new feature that Paul sent me.

    You can configure MultiTrack with up to 12 sets of loop points and remotely trigger these loops using incoming midi notes. This is useful when you want to trigger different parts of your song and move from one loop to another. This feature is only available when 'Remote' mode is enabled. You also need to disable 'Host Sync' as these loops are running independently of the host application. To configure the loops TAP and HOLD the 'Remote' button, and a 'Remote Loop Points' window will appear. This window can be dragged above the timeline if you wish and remain in view while you configure all your loop points

    In this window you will see a snapshot button and 12 buttons labelled 1-12. To store a loop point first drag a selection on the ruler, press the Snapshot button, then quickly press one of the 12 slot buttons to store the loop. Once a slot is used it will turn yellow. Pressing a yellow slot will preview that loop on the timeline. You can also snapshot a cursor positions without an associated loop. Triggering these will simply move the play-head to this position and play continuously from that position

    Once configured these loop points are saved with your song, and can be triggered using incoming MIDI notes so long as 'Remote' is enabled. Also be sure the MIDI version of the MultiTrack plugin is loaded, and a suitable MIDI keyboard connected and routed to the plugin.

    MIDI notes in the range 48-59 schedule a loop. The loop will only be triggered once the current loop is completed. Notes 60-71 trigger the loop immediately and do not wait for the current note to complete.

    Many Kudos to Paul for such a quick response to a feature idea

    I’m beginning to think Paul is a robot, or rather a legion of robots.
    This looks like a great feature!. So significant it deserves its own button, I wouldn’t put it under a “tap an hold”. I hate “tap and holds” they make you press stuff for seconds when that wasn’t the one... Looking forward to the update. I don’t think Muktitrack would fit the bill for very complex audio-heavy projects in LK but it’d certainly work well to record and lay out ideas.

    Seems the MultiTrack update is out.. Will love to see a video of this...

    I just tested it, looks good!. This feature coupled with multi-out audio seems like a very promising option for LK audio. You could have different tracks in Multitrack (bass, guitar, etc) routed to different AUM tracks and use loop snapshots for song parts corresponding to LK clips.
    Made a quick video demonstrating how the looping works, both the C3 octave trigger that waits for loop to finish or C4 octave that immediately triggers. Here I’m just using a simple loop and aum keys to show the basics. Like it!.

    I’m eager to try it out with Lk and see how it behaves and what kind of issues will come up. But I really appreciate the effort on this one. Out of the box it looks like the most straightforward and useful solution to do audio stems from LK. A lot better than samplers or any makeshift audio clip launching techniques, which are tedious and problematic (tried them all 🙃), well see how it goes but it looks very promising!. 👏

    Thanks.. seems the midi part of the modular setup is ‘almost complete’.. now it time to give audio some attention (Auv3)..
    I’m looking forward to ‘snapshots’ of entire states...morphing etc.. like this.

  • edited March 2021

    @sinosoidal said:

    @auxmux said:
    That's great @sinosoidal regarding the Controller module, been wanting custom mappings for a long time. It'll go a long way to making LK an even more awesome performance tool. I agree with the change your suggesting.

    It would be cool if the the controls in Controller view itself could be midi mapped to work with external controllers.

    It is not the first we have that request. Why would you want to control a CONTROLLER module parameter with an external controller? Why don't you map the external controller directly to the target? What's the advantage of that possibility? Can you please explain?

    Sure, the scenario i'm thinking of is LK in standalone mode. Let's say I'm using LK to sequence hardware. Controller in LK would be mapped to midi cc of the hardware, and the controls in LK would be mapped to a midi hardware controller.

    This way it would be a handy way of mapping controls quickly without having to update Midi CCs on the midi controller itself. It's almost like having a midi translator built into LK itself, without a third party app like MidiFlow.

  • @auxmux said:

    @sinosoidal said:

    @auxmux said:
    That's great @sinosoidal regarding the Controller module, been wanting custom mappings for a long time. It'll go a long way to making LK an even more awesome performance tool. I agree with the change your suggesting.

    It would be cool if the the controls in Controller view itself could be midi mapped to work with external controllers.

    It is not the first we have that request. Why would you want to control a CONTROLLER module parameter with an external controller? Why don't you map the external controller directly to the target? What's the advantage of that possibility? Can you please explain?

    Sure, the scenario i'm thinking of is LK in standalone mode. Let's say I'm using LK to sequence hardware. Controller in LK would be mapped to midi cc of the hardware, and the controls in LK would be mapped to a midi hardware controller.

    This way it would be a handy way of mapping controls quickly without having to update Midi CCs on the midi controller itself. It's almost like having a midi translator built into LK itself, without a third party app like MidiFlow.

    Thanks for explaining. I see. I will add this to our feature suggestion list (low priority). :blush:

  • @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @auxmux said:
    That's great @sinosoidal regarding the Controller module, been wanting custom mappings for a long time. It'll go a long way to making LK an even more awesome performance tool. I agree with the change your suggesting.

    It would be cool if the the controls in Controller view itself could be midi mapped to work with external controllers.

    It is not the first we have that request. Why would you want to control a CONTROLLER module parameter with an external controller? Why don't you map the external controller directly to the target? What's the advantage of that possibility? Can you please explain?

    Sure, the scenario i'm thinking of is LK in standalone mode. Let's say I'm using LK to sequence hardware. Controller in LK would be mapped to midi cc of the hardware, and the controls in LK would be mapped to a midi hardware controller.

    This way it would be a handy way of mapping controls quickly without having to update Midi CCs on the midi controller itself. It's almost like having a midi translator built into LK itself, without a third party app like MidiFlow.

    Thanks for explaining. I see. I will add this to our feature suggestion list (low priority). :blush:

    No worries. Thanks, agreed, it's a nice to have.

  • @sinosoidal I have these annoying timing issues when I try to record from the Launchpad sequencer to LK. There is always some steps off beat. It doesn’t matter if I record quatized or unquantized. I tried in AUM and Drambo. Any help on how to get the midi from the LP to LK unchanged is greatly appreciated.

  • @Artvarg said:
    @sinosoidal I have these annoying timing issues when I try to record from the Launchpad sequencer to LK. There is always some steps off beat. It doesn’t matter if I record quatized or unquantized. I tried in AUM and Drambo. Any help on how to get the midi from the LP to LK unchanged is greatly appreciated.

    We have that bug in our todo list. We haven't been able to look at it yet. Sorry! :disappointed:

  • @sinosoidal said:

    @Artvarg said:
    @sinosoidal I have these annoying timing issues when I try to record from the Launchpad sequencer to LK. There is always some steps off beat. It doesn’t matter if I record quatized or unquantized. I tried in AUM and Drambo. Any help on how to get the midi from the LP to LK unchanged is greatly appreciated.

    We have that bug in our todo list. We haven't been able to look at it yet. Sorry! :disappointed:

    It‘s OK. You got lots of stuff that probably affects more people. I just managed to record into drambo and then back to LK, which worked. I‘ll try that for now.

  • Is there a way to filter midi learned messages. I use midi keys to trigger clips and my synth is receiving them.
    LK is even recording them .. weird

  • @mbncp said:
    Is there a way to filter midi learned messages. I use midi keys to trigger clips and my synth is receiving them.
    LK is even recording them .. weird

    What happens if you unarm the track?

  • edited March 2021

    @wim said:

    @mbncp said:
    Is there a way to filter midi learned messages. I use midi keys to trigger clips and my synth is receiving them.
    LK is even recording them .. weird

    What happens if you unarm the track?

    Well, then there is no midi at all going thru. IMO these midi learn events should be filtered, first time I see an app behaving this way :o I could filter them but it's annoying that they get recorded in LK

  • wimwim
    edited March 2021

    @mbncp said:

    @wim said:

    @mbncp said:
    Is there a way to filter midi learned messages. I use midi keys to trigger clips and my synth is receiving them.
    LK is even recording them .. weird

    What happens if you unarm the track?

    Well, then there is no midi at all going thru. IMO these midi learn events should be filtered, first time I see an app behaving this way :o I could filter them but it's annoying that they get recorded in LK

    So ... the app needs to remember all the notes that you've used for mapping and exclude them from pass-through and recording? I guess I never ran into that because I would always use a midi CC's or a separate midi channel for automation. I typically use channel 16 for automation. That's not always an option for controllers that can't change channels, I know.

    Each track can be told to listen to a single midi channel rather than All. I don't know if that helps but is the method I use.

  • @wim said:

    @mbncp said:

    @wim said:

    @mbncp said:
    Is there a way to filter midi learned messages. I use midi keys to trigger clips and my synth is receiving them.
    LK is even recording them .. weird

    What happens if you unarm the track?

    Well, then there is no midi at all going thru. IMO these midi learn events should be filtered, first time I see an app behaving this way :o I could filter them but it's annoying that they get recorded in LK

    So ... the app needs to remember all the notes that you've used for mapping and exclude them from pass-through and recording? I guess I never ran into that because I would always use a midi CC's or a separate midi channel for automation.

    The app already knows if a midi message is a binding or not, so filtering that event isn't a big deal.
    In Drambo if I assign a midi event to some function, it won't be recorded or sent any further.
    Btw in LK, even a CC gets recorded and will go thru, the only way is to assign a different channel, set the track to a single specific channel, so every time I'll need a new binding I have to re-channelize it before it hits LK ? Not the greatest workflow.

  • I’m getting stuck notes when I hit the undo button. Anyone else?

  • Trigger quantize and record quantize don’t seem to be saving to project correctly. When reopening it shows as they were saved but functions in a buggy/glitchy manner requiring those two parameters to be reset. Anyone else?

  • @hibjshop said:
    Trigger quantize and record quantize don’t seem to be saving to project correctly. When reopening it shows as they were saved but functions in a buggy/glitchy manner requiring those two parameters to be reset. Anyone else?

    Record quantize seems to capture some unquantized notes. I set record quantize to 1/4 in a one bar clip and played four quarter notes. The first note I play shows up on the grid simultaneously at the very end of bar 1 and on measure one. Happens every time. I am probably playing the note a hair early.

    That last note in the picture below shows up on screen at the same t8me as the first note

  • @sinosoidal Thanks for all your hard work in bringing this great app. I'd like to add two small suggestions into the mix (unless there is already a way to do it?)

    1. Ability to use generate controls for a) selected notes or b) notes in loop brace instead of all notes in whole clip
    2. Ability to hide arm and stop controls which would reveal an extra 4 scenes. We can typically stop a clip in any empty slot and only need one armed track.

  • @hibjshop said:
    I’m getting stuck notes when I hit the undo button. Anyone else?

    Old bug. Not solved yet. It's on our list. Sorry! :disappointed:

  • @hibjshop said:
    Trigger quantize and record quantize don’t seem to be saving to project correctly. When reopening it shows as they were saved but functions in a buggy/glitchy manner requiring those two parameters to be reset. Anyone else?

    We will take a look.

  • I don't know if this had already bern requested... I would like to have some more functions to draw automation. A line tool for example. Yesterday I wanted to apply a growing probability to an 8 bar clip with many 16th notes - that was quite impossible without zooming in, but then it’s hard to keep the line straight over 8 bars.

  • @krassmann said:
    I don't know if this had already bern requested... I would like to have some more functions to draw automation. A line tool for example. Yesterday I wanted to apply a growing probability to an 8 bar clip with many 16th notes - that was quite impossible without zooming in, but then it’s hard to keep the line straight over 8 bars.

    It has been requested before. We will eventually get there. :wink:

  • edited March 2021

    Midi mapping on clips is a bit weird, if I have a single track with cc_1, cc_2, cc_3,.. then add a new Track, the mapping is rearranged horizontally, cc_2 will now trigger clip 1 on track 2, cc_3 will trigger clip 2 on track 1, ...
    Any special reason for that ?

  • @mbncp said:
    Midi mapping on clips is a bit weird, if I have a single track with cc_1, cc_2, cc_3,.. then add a new Track, the mapping is rearranged horizontally, cc_2 will now trigger clip 1 on track 2, cc_3 will trigger clip 2 on track 1, ...
    Any special reason for that ?

    Does the mapping change when adding new tracks? Can you make us a short video on how to reproduce the problem?

  • @sinosoidal said:

    @mbncp said:
    Midi mapping on clips is a bit weird, if I have a single track with cc_1, cc_2, cc_3,.. then add a new Track, the mapping is rearranged horizontally, cc_2 will now trigger clip 1 on track 2, cc_3 will trigger clip 2 on track 1, ...
    Any special reason for that ?

    Does the mapping change when adding new tracks? Can you make us a short video on how to reproduce the problem?

    Between the 2 pics I just added the new track

  • @mbncp said:

    @sinosoidal said:

    @mbncp said:
    Midi mapping on clips is a bit weird, if I have a single track with cc_1, cc_2, cc_3,.. then add a new Track, the mapping is rearranged horizontally, cc_2 will now trigger clip 1 on track 2, cc_3 will trigger clip 2 on track 1, ...
    Any special reason for that ?

    Does the mapping change when adding new tracks? Can you make us a short video on how to reproduce the problem?

    Between the 2 pics I just added the new track

    This is definitely a bug. We need to look at this. Thanks for reporting.

  • edited March 2021

    @krassmann said:
    I don't know if this had already bern requested... I would like to have some more functions to draw automation. A line tool for example. Yesterday I wanted to apply a growing probability to an 8 bar clip with many 16th notes - that was quite impossible without zooming in, but then it’s hard to keep the line straight over 8 bars.

    Yep.. I requested the 'Draw' mode for Prob/Vel, as CC does... Doubling down on that request.. could be really nice..

    Thanks..

  • @sinosoidal said:

    @hibjshop said:
    Trigger quantize and record quantize don’t seem to be saving to project correctly. When reopening it shows as they were saved but functions in a buggy/glitchy manner requiring those two parameters to be reset. Anyone else?

    We will take a look.

    Thanks. Being able to run smooth from the get go is a big plus with workflow and getting started.
    Really getting into this app, its fantastic, thanks so much!

  • @sinosoidal if it helps I have trigger quant and rec quant both set to none when state saved (for ambient jams). Both have to be pressed when opening the project (aum) to fuction properly.

  • I really like the app but it crashes really too often for my taste, using it with Drambo, just one instance of LK (using MIDI Bus app for routing), on an iPad Air 4 th gen.
    Rebooting doesn't help and the crash is very random, also sometimes the GUI is all black although the plug seems still working. Removing LK and trying to reload doesn't work, only way is to restart Drambo.
    Recovery state prevents from loosing all my work, but not always.
    Any idea ?

  • @mbncp said:
    I really like the app but it crashes really too often for my taste, using it with Drambo, just one instance of LK (using MIDI Bus app for routing), on an iPad Air 4 th gen.
    Rebooting doesn't help and the crash is very random, also sometimes the GUI is all black although the plug seems still working. Removing LK and trying to reload doesn't work, only way is to restart Drambo.
    Recovery state prevents from loosing all my work, but not always.
    Any idea ?

    Are other users having this experience? We have the lowest crash rate in 90 days.

    Maybe there is something particular about your setup that is triggering those crashes.

    Can you please make the simplest project that replicates the crashes very easily? Maybe that would help us finding the problem.

    Thanks!

  • @sinosoidal said:

    @mbncp said:
    I really like the app but it crashes really too often for my taste, using it with Drambo, just one instance of LK (using MIDI Bus app for routing), on an iPad Air 4 th gen.
    Rebooting doesn't help and the crash is very random, also sometimes the GUI is all black although the plug seems still working. Removing LK and trying to reload doesn't work, only way is to restart Drambo.
    Recovery state prevents from loosing all my work, but not always.
    Any idea ?

    Are other users having this experience? We have the lowest crash rate in 90 days.

    Maybe there is something particular about your setup that is triggering those crashes.

    Can you please make the simplest project that replicates the crashes very easily? Maybe that would help us finding the problem.

    Thanks!

    I get the odd crash here and there but nothing to write home about. I save very regularly in AUM anyway as presets are generally tiny.

    I’m on iPad Pro (2019 I think) and iPhone 11 Pro

Sign In or Register to comment.