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.

Loopy Pro Questions

1101113151634

Comments

  • The user and all related content has been deleted.
  • Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

  • edited January 2022

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Yes, I’ve experienced this, especially when it re-loops. And with no regularity as such. It doesn’t happen a lot, but it’s very bad when it does, especially if it’s a drum track that suddenly falls silent for a beat. I’m a bit worried about using it for a performance, but I think a fix is part of the next update if I understand Michael correctly on Discord.
    (Other than that I just need to say: it’s a f****** great app, especially for setting up a live performance, but also for creating songs and ideas. I’m totally in love!)

  • Thanks again for the epic product and prompt support. Since LP doesn’t yet support midi loops, what is the proper workflow to trigger a midi loop, so that it remains in sync with your audio loops in LP?

    I’ve loaded Helium inside LP and can get it to send midi data to an AUV3 instrument or a hardware instrument if I open the plugin and press play in the plugin window. However I’m struggling to figure out the best was to trigger helium, and keep heliums tempo in sync with LPs clock. Do I need an intermediary widget? Can such widget be quantized? Do I need a different instance of Helium for each midi loop?

    A related questions is what is the timeline for midi looping in LP? If it’s coming soon maybe I just wait :)

  • @GreedySpark, enable Host Sync in Helium, then create a timeline loop that matches your loop length in LP.

  • @GRiker Excellent! that allows me to trigger one midi loop by pressing play in loopy and it is synced to the clock length. We are off to a good start.

    Suppose I want to trigger a midi loop during the middle of a performance or I have more that one midi loop of different lengths? I can imagine some workarounds. Multiple different instances of Helium constantly running different midi loops in the background with all midi faders initially set to off. Turn up the applicable fader to “launch” the applicable midi loop.

    Is there an easier approach or a better auv3 plugin that would serve this purpose within LP?

  • @galmandsværk said:

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Yes, I’ve experienced this, especially when it re-loops. And with no regularity as such. It doesn’t happen a lot, but it’s very bad when it does, especially if it’s a drum track that suddenly falls silent for a beat. I’m a bit worried about using it for a performance, but I think a fix is part of the next update if I understand Michael correctly on Discord.
    (Other than that I just need to say: it’s a f****** great app, especially for setting up a live performance, but also for creating songs and ideas. I’m totally in love!)

    Ok good, then it’s not just me, and by the sound of it, @Michael is aware.

    I’m totally in love as well!

  • @GreedySpark said:
    @GRiker Excellent! that allows me to trigger one midi loop by pressing play in loopy and it is synced to the clock length. We are off to a good start.

    Suppose I want to trigger a midi loop during the middle of a performance or I have more that one midi loop of different lengths? I can imagine some workarounds. Multiple different instances of Helium constantly running different midi loops in the background with all midi faders initially set to off. Turn up the applicable fader to “launch” the applicable midi loop.

    Is there an easier approach or a better auv3 plugin that would serve this purpose within LP?

    Atom 2 and LK also work well within Loopy. I don't know Helium's feature set. But with either LK or Atom you can set MIDI loops to be triggered by the MIDI event of your choice. And you could send them from a MIDI controller or a widget you set up in Loopy or midi sent by a follow action. There are many ways to accomplish that goal.

  • @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Do you mean playing loops fall silent or an input channel falls silent? The more detail that you can provide the better.

  • @espiegel123 said:

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Do you mean playing loops fall silent or an input channel falls silent? The more detail that you can provide the better.

    I want to say everything goes silent for a brief second, but now that I think of it, it might be just a single channel.

    I’ll have to keep playing with it and try to pay attention to what it’s doing when it does it again.

  • edited January 2022

    @Edward_Alexander said:

    @espiegel123 said:

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Do you mean playing loops fall silent or an input channel falls silent? The more detail that you can provide the better.

    I want to say everything goes silent for a brief second, but now that I think of it, it might be just a single channel.

    I’ll have to keep playing with it and try to pay attention to what it’s doing when it does it again.

    If it is a single channel, see if there is a delay or reverb or sampler effect on it, in case it is an issue of an AU not being un-idled instantly.

  • @espiegel123 said:

    @Edward_Alexander said:

    @espiegel123 said:

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Do you mean playing loops fall silent or an input channel falls silent? The more detail that you can provide the better.

    I want to say everything goes silent for a brief second, but now that I think of it, it might be just a single channel.

    I’ll have to keep playing with it and try to pay attention to what it’s doing when it does it again.

    If it is a single channel, see if there is a delay or reverb or sampler effect on it, in case it is an issue of an AU not being un-idled instantly.

    My experience is that a single donut will cut out (but keep playing in time) when it re-loops, and then be back shortly after. It’s only a matter of half a second or so, but clearly audible. I can’t point out a pattern, but I feel that it happens more often with donuts that have just been recorded, as if the project needs to “get acquainted” to it. I know that probably makes no sense :)
    I’ll try to screen record a session and see if I can catch it on tape.

  • @espiegel123 said:

    @GreedySpark said:
    @GRiker Excellent! that allows me to trigger one midi loop by pressing play in loopy and it is synced to the clock length. We are off to a good start.

    Suppose I want to trigger a midi loop during the middle of a performance or I have more that one midi loop of different lengths? I can imagine some workarounds. Multiple different instances of Helium constantly running different midi loops in the background with all midi faders initially set to off. Turn up the applicable fader to “launch” the applicable midi loop.

    Is there an easier approach or a better auv3 plugin that would serve this purpose within LP?

    Atom 2 and LK also work well within Loopy. I don't know Helium's feature set. But with either LK or Atom you can set MIDI loops to be triggered by the MIDI event of your choice. And you could send them from a MIDI controller or a widget you set up in Loopy or midi sent by a follow action. There are many ways to accomplish that goal.

    Thanks! It looks like LK is a good solution for triggering various midi loops throughout a performance.

  • @galmandsværk said:

    @espiegel123 said:

    @Edward_Alexander said:

    @espiegel123 said:

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Do you mean playing loops fall silent or an input channel falls silent? The more detail that you can provide the better.

    I want to say everything goes silent for a brief second, but now that I think of it, it might be just a single channel.

    I’ll have to keep playing with it and try to pay attention to what it’s doing when it does it again.

    If it is a single channel, see if there is a delay or reverb or sampler effect on it, in case it is an issue of an AU not being un-idled instantly.

    My experience is that a single donut will cut out (but keep playing in time) when it re-loops, and then be back shortly after. It’s only a matter of half a second or so, but clearly audible. I can’t point out a pattern, but I feel that it happens more often with donuts that have just been recorded, as if the project needs to “get acquainted” to it. I know that probably makes no sense :)
    I’ll try to screen record a session and see if I can catch it on tape.

    The only time when I have experienced something like that is if a trim has been made to a loop or if playing with time-stretching. Please try to get some screen recordings that capture the issue.

  • edited January 2022

    @Edward_Alexander said:
    Does Loopy Pro ever just randomly go silent for a beat or two for you guys?

    It doesn’t happen regularly. Only every now and then.

    Yes, it happens occasionally and I haven’t worked out whether it’s some combination of settings or a bug. I posted a video on the Slack, though. I had recorded long notes in a loop and the last one ended right at the end… the plan was that it would loop seamlessly. But what actually happened was that the recorded loop cut off for a second at the end before the loop restarted. I 100% held the final note to the end of the loop, it was recorded from Animoog Z and the waveform in clip settings clearly showed that it had been held correctly.

  • edited January 2022

    The going silent issue is fixed in the next update, coming in the next couple of days

  • @Michael would it be possible/feasible to use the apc 40 protocol as a general protocol for talking to controllers? This would allow it to be selected in a menu along with its associated ports and as such it would the be possible to write a midi effect that translated between the protocol and a particular device, for me the push 2 and xone k2.

  • @GreedySpark said:
    @GRiker Excellent! that allows me to trigger one midi loop by pressing play in loopy and it is synced to the clock length. We are off to a good start.

    Suppose I want to trigger a midi loop during the middle of a performance or I have more that one midi loop of different lengths? I can imagine some workarounds. Multiple different instances of Helium constantly running different midi loops in the background with all midi faders initially set to off. Turn up the applicable fader to “launch” the applicable midi loop.

    Is there an easier approach or a better auv3 plugin that would serve this purpose within LP?

    Here’s a YT video demonstrating Helium’s clip launching capabilities.

  • @Michael said:
    The going silent issue is fixed in the next update, coming in the next couple of days

    Thank you Michael!

  • @cuberoo_ said:
    @Michael would it be possible/feasible to use the apc 40 protocol as a general protocol for talking to controllers? This would allow it to be selected in a menu along with its associated ports and as such it would the be possible to write a midi effect that translated between the protocol and a particular device, for me the push 2 and xone k2.

    I'm working on that

  • @Michael said:

    @cuberoo_ said:
    @Michael would it be possible/feasible to use the apc 40 protocol as a general protocol for talking to controllers? This would allow it to be selected in a menu along with its associated ports and as such it would the be possible to write a midi effect that translated between the protocol and a particular device, for me the push 2 and xone k2.

    I'm working on that

    amazing, thanks :blush:

  • @Michael said:

    @cuberoo_ said:
    @Michael would it be possible/feasible to use the apc 40 protocol as a general protocol for talking to controllers? This would allow it to be selected in a menu along with its associated ports and as such it would the be possible to write a midi effect that translated between the protocol and a particular device, for me the push 2 and xone k2.

    I'm working on that

    Being able to use Push 2 with Loopy Pro would be so amazing!

  • @Michael_R_Grant
    Or for the poor people like me the push 1

  • edited January 2022

    When a loop is synced count in/count out, a single tap trigger cue play/stop then a second tap trigger immediate play/stop. I want to avoid that because with a pedalboard/midi controller it’s risky to have that behavior in live. Can’t find any setting for this? Do I miss something?

  • Apologies if this has been mentioned on this or the other LP megathreads (and it is not in the manual):
    Is it possible to duplicate an AU Input track in the mixer? Or is it in the cards for future updates?

    Thanks.

  • @Janosax said:
    When a loop is synced count in/count out, a single tap trigger cue play/stop then a second tap trigger immediate play/stop. I want to avoid that because with a pedalboard/midi controller it’s risky to have that behavior in live. Can’t find any setting for this? Do I miss something?

    What is the behavior you want?

  • edited January 2022

    @espiegel123 said:

    @Janosax said:
    When a loop is synced count in/count out, a single tap trigger cue play/stop then a second tap trigger immediate play/stop. I want to avoid that because with a pedalboard/midi controller it’s risky to have that behavior in live. Can’t find any setting for this? Do I miss something?

    What is the behavior you want?

    I made a template to replicate Ableton session triggering system, with scenes widgets triggering horizontal loops while stoping all other ones, all loops staying individually free of scenes triggers. If I trigger a scene one time, correspondant loops are play/stop scheduled, if I trigger a second time, it will play immediately. This can happen by mistake very easily with a pedalboard in real live situation, I want to avoid this, a second tap should do nothing. Grouptheloop or Ableton Live for example don’t allow for this. See video, first part is single tap desired behavior, second part is double tap immediate trigger which could happen accidentally:

  • @Janosax said:

    @espiegel123 said:

    @Janosax said:
    When a loop is synced count in/count out, a single tap trigger cue play/stop then a second tap trigger immediate play/stop. I want to avoid that because with a pedalboard/midi controller it’s risky to have that behavior in live. Can’t find any setting for this? Do I miss something?

    What is the behavior you want?

    I made a template to replicate Ableton session triggering system, with scenes widgets triggering horizontal loops while stoping all other ones, all loops staying individually free of scenes triggers. If I trigger a scene one time, correspondant loops are play/stop scheduled, if I trigger a second time, it will play immediately. This can happen by mistake very easily with a pedalboard in real live situation, I want to avoid this, a second tap should do nothing. Grouptheloop or Ableton Live for example don’t allow for this. See video, first part is single tap desired behavior, second part is double tap immediate trigger which could happen accidentally:

    I personally wouldn’t want to lose the ability for a second tap to override (I use it all the time) . I can see that a preference about it could be handy.

  • edited January 2022

    I made a request on Discord: add ability to trigger other clips to single clip gesture. This is another thing not easily doable in Loopy Pro as I try to replicate Ableton Live session view system, scene widgets triggers loops on horizontal lines and loops should be able to be triggered inside vertical column while stop other same colored loops. Loopy pro groups don’t allow for proper system, so I had to also use widgets especially for this, with loops triggering those widgets just to stop other loops vertically. Adding ability to trigger other clips to single clip gesture could make that more simple. See video and screenshots (see also LK sync, all in AUM :-)):

    Ableton Live is not the only way of doing things, but it has set standards also for the way its session view works, for good reasons :) We find this in LK, GarageBand, Launchpad, Grouptheloop… it’s much more difficult to achieve in Loopy Pro but there are just « basics ».

  • edited January 2022

    @espiegel123 said:

    @Janosax said:

    @espiegel123 said:

    @Janosax said:
    When a loop is synced count in/count out, a single tap trigger cue play/stop then a second tap trigger immediate play/stop. I want to avoid that because with a pedalboard/midi controller it’s risky to have that behavior in live. Can’t find any setting for this? Do I miss something?

    What is the behavior you want?

    I made a template to replicate Ableton session triggering system, with scenes widgets triggering horizontal loops while stoping all other ones, all loops staying individually free of scenes triggers. If I trigger a scene one time, correspondant loops are play/stop scheduled, if I trigger a second time, it will play immediately. This can happen by mistake very easily with a pedalboard in real live situation, I want to avoid this, a second tap should do nothing. Grouptheloop or Ableton Live for example don’t allow for this. See video, first part is single tap desired behavior, second part is double tap immediate trigger which could happen accidentally:

    I personally wouldn’t want to lose the ability for a second tap to override (I use it all the time) . I can see that a preference about it could be handy.

    This is why I’m asking for a new setting for this 🙂 This is really bad in front of people playing your music to make that second foot tap by mistake and having this other scene playing immediately. There is a reason other apps don’t allow it. So a setting to toggle it like all other settings we found in Loopy Pro could make lot of sense. Without it I will never use LPP on stage but only for production. Not pure truth just my need, I’m sure other users will realize this in true live situation.

This discussion has been closed.