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

1103104106108109130

Comments

  • edited December 2021

    @Janosax said:
    Yeah colors does a lot to get inspired IMO, first app contact is with eyes.

    100% agree. I like LK’s flat and minimal design, doesn’t get in the way. I love the way ApeSoft apps are laid out, very inspiring. FAC is always nice and to the point, BLEASS is clean and unobtrusive. Fabfilter very useful friendly… On the other side of the spectrum Auria and 4pockets I find very off putting. Do we need designs to resemble analog mixers, all the 3d glory and shiny metal?.

  • @Janosax

    The new beta (build 270) tries to fix the issue you've reported regarding the pitch bend. If there is still any problem please let me know.

  • This is becoming very frustrating for me, I can’t figure this out no matter where I look in the manual so I hope someone here can help me

    I’m trying to use this as a drum machine sequencer but it chokes notes if I have more than one note triggered on the piano roll. I tried this with other apps and it did the same thing. How I get it to be able to play more than one note? Sorry if this sounds like a dumb question…but it’s making me mad and once someone gets mad, well…let’s just say I’m not thinking clearly anymore. Hopefully it’s just a simple solution…

    Thanks in advance for whoever might be able to point me in the right direction

  • @ambrosiajam said:
    This is becoming very frustrating for me, I can’t figure this out no matter where I look in the manual so I hope someone here can help me

    I’m trying to use this as a drum machine sequencer but it chokes notes if I have more than one note triggered on the piano roll. I tried this with other apps and it did the same thing. How I get it to be able to play more than one note? Sorry if this sounds like a dumb question…but it’s making me mad and once someone gets mad, well…let’s just say I’m not thinking clearly anymore. Hopefully it’s just a simple solution…

    Thanks in advance for whoever might be able to point me in the right direction

    It sounds like you need to figure out how your drum machine is set up. This doesn't sound like it has to do with the sequencer.

  • I don’t have any choke groups set up and never had this issue before with other programs. But I also can’t find any choke settings in LK. Maybe there’s an issue with the midi settings that I overlooked or accidentally turned on/off or something. I don’t think AUM has any settings like this either. I’m admittedly new to using LK, but not new to triggering my machine with midi or routing/etc. I’ll keep messing around with it.

  • @ambrosiajam said:
    I don’t have any choke groups set up and never had this issue before with other programs. But I also can’t find any choke settings in LK. Maybe there’s an issue with the midi settings that I overlooked or accidentally turned on/off or something. I don’t think AUM has any settings like this either. I’m admittedly new to using LK, but not new to triggering my machine with midi or routing/etc. I’ll keep messing around with it.

    You could use a MIDI monitor app to confirm that LK is sending all the notes. Are they maybe on different channels?

  • LK was able to send multi-notes to other apps, like Model 15 for example.

    It’s a problem with the Roland tr-8s. For some reason it is acting ‘monophonic’ instead of ‘polyphonic’, but only in regards to midi messages sent via my midi/usb adapter cable. I can still play it and run the on-board sequencer like normal. But not the other way around, regardless of choke settings or after adjusting the equipment’s midi settings. It used to work, but now it’s not. and I cannot for the life of of me find any info about this. It seems like it’s normally a non-issue (but everything I’ve found is just people who control the tr-8s with their daw are using a desktop)

    Seems like an issue for another thread or even just something I should just forget about.

    And here I thought the awkward little boundaries between iOS and hardware were finally over…there’s always some little bugs! Yaghr!

    I’m liking LK though…it’s like the closest thing to getting Gadget in AUM as an AU imo 🙃

  • @ambrosiajam : why do you attribute this to LK. What happens when you send notes to your drum machine from another sequencer or keyboard app?

  • edited December 2021

    @espiegel123 said:
    @ambrosiajam : why do you attribute this to LK. What happens when you send notes to your drum machine from another sequencer or keyboard app?

    I just said in my last post that it’s a problem with my Roland tr-8s, as far as I can tell, and I DID send the notes to other apps with LK and it worked fine.

    It was not an issue in the past, so whether it came up with the recent firmware update, software updates, or some other issue - I don’t know, Like I said, I’ll just keep messing around with it and if it’s not something I can do, then it’s fine. I am new to using LK and it also never happened before, although it’s been a while since I had my tr-8s sync’d to the iPad.
    I only thought it was LK at first because I saw in someone’s tutorial video one time that certain note groups will choke the notes, but that was actually regarding a different app, and they were triggering it with LK.

  • @ambrosiajam said:

    @espiegel123 said:
    @ambrosiajam : why do you attribute this to LK. What happens when you send notes to your drum machine from another sequencer or keyboard app?

    I just said in my last post that it’s a problem with my Roland tr-8s, as far as I can tell, and I DID send the notes to other apps with LK and it worked fine.

    It was not an issue in the past, so whether it came up with the recent firmware update, software updates, or some other issue - I don’t know, Like I said, I’ll just keep messing around with it and if it’s not something I can do, then it’s fine. I am new to using LK and it also never happened before, although it’s been a while since I had my tr-8s sync’d to the iPad.
    I only thought it was LK at first because I saw in someone’s tutorial video one time that certain note groups will choke the notes, but that was actually regarding a different app, and they were triggering it with LK.

    Could you try it with something neutral, like the AUM screen keyboard?

    I wonder if the TR-8S has trouble with notes at exactly the same time?

  • Hello folks!

    I have a problem regarding triggering of clips with "irregular" bar lenghts. A simple example: "Trigger Quantization" in LK is set to 1 bar, global "Signature" to 4/4. I have two scenes, each containing one clip. The first has a length of 4 bars of 4/4. The second has a length of 3x 4/4 plus one bar of 3/4. The second one I get to loop seamlessly by setting the loop end marker to the desired position. So far, so good.

    Now if I have clip 2 playing and trigger clip 1 during the last bar of clip 2 (the 3/4 bar), the switch to clip 1 will always occur after a bar of 4/4, causing 1/4 of silence. LK seems to assume "a bar" to always be of the length specified by the global "Signature" parameter, so it doesn't help to change the length and individual signature of clip 2 to be 1 bar of 15/4 either. (I can get around that problem by setting Trigger Quantization to 1/4, but that leads to another issue, because, well, 1/4 often is too short a time for comfortably switching between scenes/clips.)

    Could one of several possible solutions to this be a clip parameter like "switch to next triggered clip on loop end" (that becomes effective when the triggering occurs within that last "shortened" bar in which the loop end resides)? (And it would then be important that the beginning of this next triggered clip is seen as the new 1 or downbeat. I add this because I don't know if the shortened clip 2 in some way would mess with LK's idea where the 1/downbeat from then on should be, which could lead to further issues.)

    If I should be missing a simple or already existing solution please feel free to set me straight! ;)

  • @xglax said:
    @Janosax

    The new beta (build 270) tries to fix the issue you've reported regarding the pitch bend. If there is still any problem please let me know.

    It seems that it works perfectly now, thanks great job 👏

  • @Janosax said:

    @xglax said:
    @Janosax

    The new beta (build 270) tries to fix the issue you've reported regarding the pitch bend. If there is still any problem please let me know.

    It seems that it works perfectly now, thanks great job 👏

    Awesome news!

  • I’m trying to get my setup in Aum with LK as a sequencer.
    Problems:
    when switching “scenes”

    1.there’s overlap kick
    2. no note off so stuck notes on loops

    https://www.dropbox.com/s/0exwipiu65n7tow/final.MOV?dl=0

  • edited December 2021

    @Tamir_Raz_Mataz said:
    I’m trying to get my setup in Aum with LK as a sequencer.
    Problems:
    when switching “scenes”

    1.there’s overlap kick
    2. no note off so stuck notes on loops

    https://www.dropbox.com/s/0exwipiu65n7tow/final.MOV?dl=0

    I guess update didn’t fix hanging notes/no note off when jumping through scene.

    Still double notes when jumping through scenes only when host running.
    Hear it on video attached on the kick and on percussion loop

  • @sinosoidal I’ve been playing with LK in loopy recently and it’s mostly working, but I’m getting this quite often in the au window.

    Might be worth talking to @Michael

  • @gregsmith said:
    @sinosoidal I’ve been playing with LK in loopy recently and it’s mostly working, but I’m getting this quite often in the au window.

    Might be worth talking to @Michael

    @Michael are you able to give any kind of insight from a dev perspective? Thanks!

  • @gregsmith said:
    @sinosoidal I’ve been playing with LK in loopy recently and it’s mostly working, but I’m getting this quite often in the au window.

    Might be worth talking to @Michael

    I am seeing this a lot, too. If the clips were set up, LK will play them but there is no u.I.

  • @sinosoidal said:

    @gregsmith said:
    @sinosoidal I’ve been playing with LK in loopy recently and it’s mostly working, but I’m getting this quite often in the au window.

    Might be worth talking to @Michael

    @Michael are you able to give any kind of insight from a dev perspective? Thanks!

    We’d have to ask LK’s developers, I think

  • @Michael said:

    @sinosoidal said:

    @gregsmith said:
    @sinosoidal I’ve been playing with LK in loopy recently and it’s mostly working, but I’m getting this quite often in the au window.

    Might be worth talking to @Michael

    @Michael are you able to give any kind of insight from a dev perspective? Thanks!

    We’d have to ask LK’s developers, I think

    That is the LK developer @sinosoidal :sunglasses:

  • @Samu said:

    @Michael said:

    @sinosoidal said:

    @gregsmith said:
    @sinosoidal I’ve been playing with LK in loopy recently and it’s mostly working, but I’m getting this quite often in the au window.

    Might be worth talking to @Michael

    @Michael are you able to give any kind of insight from a dev perspective? Thanks!

    We’d have to ask LK’s developers, I think

    That is the LK developer @sinosoidal :sunglasses:

    Oh that’s you Nuno! Haha. I was thrown by the “from a dev perspective“ 😄

    Yeah, I really have no idea I’m afraid – I think I’d have to have a look at the codebase. Happy to do that if it would help.

  • edited December 2021

    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

  • @Samu said:
    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

    It happens regardless. And happens even if ui was already drawn successfully. Once triggered nothing fixes it except reboot

  • @espiegel123 said:

    @Samu said:
    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

    It happens regardless. And happens even if ui was already drawn successfully. Once triggered nothing fixes it except reboot

    I’ve found a quick way to get it back. If you have the LK au window open, then nudge up from the bottom as if you’re going to switch apps, but don’t actually switch, the interface shows again.

    This works on the phone anyway. Not tried iPad yet.

  • @gregsmith said:

    @espiegel123 said:

    @Samu said:
    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

    It happens regardless. And happens even if ui was already drawn successfully. Once triggered nothing fixes it except reboot

    I’ve found a quick way to get it back. If you have the LK au window open, then nudge up from the bottom as if you’re going to switch apps, but don’t actually switch, the interface shows again.

    This works on the phone anyway. Not tried iPad yet.

    @Michael I have never been reported of such similar behavior before. I didn't tried myself to reproduce the problem on our side yet but there must be some awkard interaction happening.

  • @gregsmith said:

    @espiegel123 said:

    @Samu said:
    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

    It happens regardless. And happens even if ui was already drawn successfully. Once triggered nothing fixes it except reboot

    I’ve found a quick way to get it back. If you have the LK au window open, then nudge up from the bottom as if you’re going to switch apps, but don’t actually switch, the interface shows again.

    This works on the phone anyway. Not tried iPad yet.

    Unfortunately, that doesn't work for me.

    @sinosoidal @Michael : while this can get triggered by a number of things seemingly at random. One 100% reproducible way for me is to have the LK window be open in Loopy Pro, switch out of Loopy Pro and then back. No amount of resizing (even to maximum size) or nudging will bring back the u.i.

    Even opening a new Loopy Project and reopening the project with LK doesn't solve it -- so it seems like the LK AU is referencing something left over that persists when reinstantiating.

  • @espiegel123 said:

    @gregsmith said:

    @espiegel123 said:

    @Samu said:
    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

    It happens regardless. And happens even if ui was already drawn successfully. Once triggered nothing fixes it except reboot

    I’ve found a quick way to get it back. If you have the LK au window open, then nudge up from the bottom as if you’re going to switch apps, but don’t actually switch, the interface shows again.

    This works on the phone anyway. Not tried iPad yet.

    Unfortunately, that doesn't work for me.

    @sinosoidal @Michael : while this can get triggered by a number of things seemingly at random. One 100% reproducible way for me is to have the LK window be open in Loopy Pro, switch out of Loopy Pro and then back. No amount of resizing (even to maximum size) or nudging will bring back the u.i.

    Even opening a new Loopy Project and reopening the project with LK doesn't solve it -- so it seems like the LK AU is referencing something left over that persists when reinstantiating.

    Just after posting this, I found something that fixes it and made gives a clue. If I double-click the home button while in Loopy Pro which brings up the system's thumbnails of recent apps (maybe this is what Greg Smith meant by nudging up) then LK redraws it window.

  • @espiegel123 said:

    @espiegel123 said:

    @gregsmith said:

    @espiegel123 said:

    @Samu said:
    Could it be a simple thing like maxing the plug-in window?
    I've seen some plug-ins fail on the iPhone 8 (with other hosts) when there's not enough room on the screen/window.

    It happens regardless. And happens even if ui was already drawn successfully. Once triggered nothing fixes it except reboot

    I’ve found a quick way to get it back. If you have the LK au window open, then nudge up from the bottom as if you’re going to switch apps, but don’t actually switch, the interface shows again.

    This works on the phone anyway. Not tried iPad yet.

    Unfortunately, that doesn't work for me.

    @sinosoidal @Michael : while this can get triggered by a number of things seemingly at random. One 100% reproducible way for me is to have the LK window be open in Loopy Pro, switch out of Loopy Pro and then back. No amount of resizing (even to maximum size) or nudging will bring back the u.i.

    Even opening a new Loopy Project and reopening the project with LK doesn't solve it -- so it seems like the LK AU is referencing something left over that persists when reinstantiating.

    Just after posting this, I found something that fixes it and made gives a clue. If I double-click the home button while in Loopy Pro which brings up the system's thumbnails of recent apps (maybe this is what Greg Smith meant by nudging up) then LK redraws it window.

    Yes, that’s exactly what I meant - my phone doesn’t have a home button but nudging up is the equivalent.

  • Oh, another LK Loopy Pro issue I had today…

    I have a loopy project on my iPhone with LK in it. I saved it and airdropped to my iPad. When i reopened it, all the LK stuff was gone, as if I’d only just added it to loopy.

    LK is fine if I reopen the project locally on my iPhone.

    Not sure what’s happening here @Michael - not sure if it’s just state saving issues.

    This doesn’t happen in AUM.

  • @gregsmith said:
    Oh, another LK Loopy Pro issue I had today…

    I have a loopy project on my iPhone with LK in it. I saved it and airdropped to my iPad. When i reopened it, all the LK stuff was gone, as if I’d only just added it to loopy.

    LK is fine if I reopen the project locally on my iPhone.

    Not sure what’s happening here @Michael - not sure if it’s just state saving issues.

    This doesn’t happen in AUM.

    Interesting. Would you mind sending me that airdropped version?

Sign In or Register to comment.