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

1…3536384041…50

Comments

  • espiegel123espiegel123

    @Skyblazer said:
    I'm trying to set up a retrospective looping template. In the metronome area, where it says "bars", I'm setting that to 1 bar...hopefully that's okay, as I would like that visual indicator surrounding the BPM readout to display the beat. Beat 1 is in the top right quadrant, like the face of a clock.

    I'm also using a 1 bar blank loop to keep the metronome running.

    It looks like when "Retrospective Quantization" is set to "Quantized", it grabs the correct portion of the audio (only the bars which have finished recording, and not the current bar) when I'm using 2 bars or fewer.

    And when it's set to "Immediate", it grabs the correct portion of the audio when I'm using 4 or 5 bars, and probably more. Haven't tried it with 8 bars yet. But when I set it to 32 bars, there seems to be a glitch. Doesn't seem to work with 32.

    The donut just glows without showing a waveform when I tap it, and then becomes unresponsive...if I pause the playhead, and then tap the donut, it records non-retrospectively.

    Am I doing anything incorrectly? Are these known bugs?

    @skyblazer: retrospective immediate with a clock of 32 is working for me (though quantized is behaving strange).

    @Michael : i just tried this out and at 32 bars things behave funny for me when retro is quantized. If i make sure that at least 32 cycles have played, retro quantized seems to start a count out rather than capture what is in the buffer. immediate is working ok for me. I tried this both with a widget that retro records next tap and by setting clip settings to retro quantized.

  • MichaelMichael

    @espiegel123 said:

    @Skyblazer said:
    I'm trying to set up a retrospective looping template. In the metronome area, where it says "bars", I'm setting that to 1 bar...hopefully that's okay, as I would like that visual indicator surrounding the BPM readout to display the beat. Beat 1 is in the top right quadrant, like the face of a clock.

    I'm also using a 1 bar blank loop to keep the metronome running.

    It looks like when "Retrospective Quantization" is set to "Quantized", it grabs the correct portion of the audio (only the bars which have finished recording, and not the current bar) when I'm using 2 bars or fewer.

    And when it's set to "Immediate", it grabs the correct portion of the audio when I'm using 4 or 5 bars, and probably more. Haven't tried it with 8 bars yet. But when I set it to 32 bars, there seems to be a glitch. Doesn't seem to work with 32.

    The donut just glows without showing a waveform when I tap it, and then becomes unresponsive...if I pause the playhead, and then tap the donut, it records non-retrospectively.

    Am I doing anything incorrectly? Are these known bugs?

    @skyblazer: retrospective immediate with a clock of 32 is working for me (though quantized is behaving strange).

    @Michael : i just tried this out and at 32 bars things behave funny for me when retro is quantized. If i make sure that at least 32 cycles have played, retro quantized seems to start a count out rather than capture what is in the buffer. immediate is working ok for me. I tried this both with a widget that retro records next tap and by setting clip settings to retro quantized.

    Interesting. I wonder if perhaps it failed to allocate enough memory. Can’t remember if I actually report the allocation failure to the user or just fail silently. If it can’t allocate the buffer, it will continue to use the smaller size, which would explain the behaviour that you’re seeing

  • wimwim

    @Michael said:

    @espiegel123 said:

    @Skyblazer said:
    I'm trying to set up a retrospective looping template. In the metronome area, where it says "bars", I'm setting that to 1 bar...hopefully that's okay, as I would like that visual indicator surrounding the BPM readout to display the beat. Beat 1 is in the top right quadrant, like the face of a clock.

    I'm also using a 1 bar blank loop to keep the metronome running.

    It looks like when "Retrospective Quantization" is set to "Quantized", it grabs the correct portion of the audio (only the bars which have finished recording, and not the current bar) when I'm using 2 bars or fewer.

    And when it's set to "Immediate", it grabs the correct portion of the audio when I'm using 4 or 5 bars, and probably more. Haven't tried it with 8 bars yet. But when I set it to 32 bars, there seems to be a glitch. Doesn't seem to work with 32.

    The donut just glows without showing a waveform when I tap it, and then becomes unresponsive...if I pause the playhead, and then tap the donut, it records non-retrospectively.

    Am I doing anything incorrectly? Are these known bugs?

    @skyblazer: retrospective immediate with a clock of 32 is working for me (though quantized is behaving strange).

    @Michael : i just tried this out and at 32 bars things behave funny for me when retro is quantized. If i make sure that at least 32 cycles have played, retro quantized seems to start a count out rather than capture what is in the buffer. immediate is working ok for me. I tried this both with a widget that retro records next tap and by setting clip settings to retro quantized.

    Interesting. I wonder if perhaps it failed to allocate enough memory. Can’t remember if I actually report the allocation failure to the user or just fail silently. If it can’t allocate the buffer, it will continue to use the smaller size, which would explain the behaviour that you’re seeing

    That could maybe relate to it behaving better after I stopped and started the transport. Maybe it re-allocated the buffer or something.

  • MichaelMichael

    @wim said:

    @Michael said:

    @espiegel123 said:

    @Skyblazer said:
    I'm trying to set up a retrospective looping template. In the metronome area, where it says "bars", I'm setting that to 1 bar...hopefully that's okay, as I would like that visual indicator surrounding the BPM readout to display the beat. Beat 1 is in the top right quadrant, like the face of a clock.

    I'm also using a 1 bar blank loop to keep the metronome running.

    It looks like when "Retrospective Quantization" is set to "Quantized", it grabs the correct portion of the audio (only the bars which have finished recording, and not the current bar) when I'm using 2 bars or fewer.

    And when it's set to "Immediate", it grabs the correct portion of the audio when I'm using 4 or 5 bars, and probably more. Haven't tried it with 8 bars yet. But when I set it to 32 bars, there seems to be a glitch. Doesn't seem to work with 32.

    The donut just glows without showing a waveform when I tap it, and then becomes unresponsive...if I pause the playhead, and then tap the donut, it records non-retrospectively.

    Am I doing anything incorrectly? Are these known bugs?

    @skyblazer: retrospective immediate with a clock of 32 is working for me (though quantized is behaving strange).

    @Michael : i just tried this out and at 32 bars things behave funny for me when retro is quantized. If i make sure that at least 32 cycles have played, retro quantized seems to start a count out rather than capture what is in the buffer. immediate is working ok for me. I tried this both with a widget that retro records next tap and by setting clip settings to retro quantized.

    Interesting. I wonder if perhaps it failed to allocate enough memory. Can’t remember if I actually report the allocation failure to the user or just fail silently. If it can’t allocate the buffer, it will continue to use the smaller size, which would explain the behaviour that you’re seeing

    That could maybe relate to it behaving better after I stopped and started the transport. Maybe it re-allocated the buffer or something.

    Could be.

    It’s the downside of working with 32 bit stereo audio – tends to take up rather a lot of room

  • SpidericemidasSpidericemidas

    @audiblevideo said:

    @Spidericemidas said:
    It’s a totally new way of working for me, and I’m really loving it! I’m still very fond of using AUM but I’m now recording perfect loops of my tracks in AUM and transferring them into Loopy where it’s so much easier and more fun to perform them. Instant satisfaction touching combos of loops on and off for jamming.
    Much gratitude to @Michael for updating Loopy to run on iOS13!

    Get off my use case! It’s my use case and no one else’s ;P

    Haha! It’s great, isn’t it?! I haven’t even looked at the other functions like widgets and the timeline thing yet. So much fun!

  • JumpercollinsJumpercollins
    edited January 2022

    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

  • JanosaxJanosax

    ..

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Nice video thanks for sharing.

  • JojoJojo

    I’ve had some issues getting consistent performance from a couple foot pedals sending MIDI info. I tried an Airturn BT-200 S-4 (Bluetooth) and my voicelive 3 plugged in via USB. Both registered midi input when I was assigning MIDI…however, only one button on my Airturn pedal seemed to actually trigger when not in assign mode and my Voicelive 3 wouldn’t trigger either. Are there certain CCs that don’t work? I was able to get my IK Blueboard Bluetooth pedal to connect and trigger, but I wasn’t as happy with the soft pedals for looping (foot tactile experience).
    Any ideas?? Help? Thank you so much…I’ve been setting up a huge looping template for a few days, but I’m getting hung up on this hinge point…

  • espiegel123espiegel123

    @Jojo said:
    I’ve had some issues getting consistent performance from a couple foot pedals sending MIDI info. I tried an Airturn BT-200 S-4 (Bluetooth) and my voicelive 3 plugged in via USB. Both registered midi input when I was assigning MIDI…however, only one button on my Airturn pedal seemed to actually trigger when not in assign mode and my Voicelive 3 wouldn’t trigger either. Are there certain CCs that don’t work? I was able to get my IK Blueboard Bluetooth pedal to connect and trigger, but I wasn’t as happy with the soft pedals for looping (foot tactile experience).
    Any ideas?? Help? Thank you so much…I’ve been setting up a huge looping template for a few days, but I’m getting hung up on this hinge point…

    Check with a MIDI Monitor in Loopy to see what MIDI is being received. If you MIDI learn from the pedal, it is sometimes necessary to manually change the learned trigger (on, on/off, hold, double-tap). Sometimes Loopy will guess that you want Hold when you really want On or On/Off.

    There are notes about how to insert a Midi Monitor in Loopy Pro here:
    https://wiki.audiob.us/doku.php?id=loopy_pro_troubleshooting

  • JojoJojo

    Thanks for the recommendation! Unfortunately, it’s still not working.

    I don’t think it allowed me to upload the above image, but basically, that’s what I did. I changed it to on/off from ‘hold’(and tried it the other way too). I put a midi monitor in to view what was passing. It shows the MIDI info and it’s assigned to a button(which works), but the pedal won’t trigger it.

  • wimwim
    edited January 2022

    @Jojo, how did you get to that point? I don't see any action such as "Press" and I don't see any CC type such as "On CC 16" or "Hold CC 16". I haven't figured out any way to get to a button setting that looks like what you show.

  • celtic_elkceltic_elk

    @wim said:
    @Jojo, how did you get to that point? I don't see any action such as "Press" and I don't see any CC type such as "On CC 15" or "Hold CC 16". I haven't figured out any way to get to a button setting that looks like what you show.

    Yeah, I think what’s missing here is that you have to specify which widget action is supposed to be activated by your MIDI message.

  • espiegel123espiegel123

    @Jojo said:
    Thanks for the recommendation! Unfortunately, it’s still not working.
    I don’t think it allowed me to upload the above image, but basically, that’s what I did. I changed it to on/off from ‘hold’(and tried it the other way too). I put a midi monitor in to view what was passing. It shows the MIDI info and it’s assigned to a button(which works), but the pedal won’t trigger it.

    In case @wim's clue wasn't enough. Do you see the '>' next to Action. You need to tap that and assign an action to tell Loopy which action. Normally, it automatically chooses 'Press'. I am not sure why it didn't.

  • JojoJojo

    Hmm, it seems to be accurate…

  • wimwim

    @jojo, it would be super helpful if you could state the steps you went through to get to those two screenshots. Particularly that first one. I just haven't seen a path to getting to what you're seeing in that first screenshot.

  • raindroraindro
    edited January 2022

    Any one have an opinion for best AU sequencer to use with this?

    (I wish Bram made a piano roll sequencer! Hammerhead works so well in LP)

  • mjm1138mjm1138

    @raindro said:
    Any one have an opinion for best AU sequencer to use with this?

    I'll just throw out there that I've been playing around with LK and Polybeat and they're both a bit crash-prone in Loopy Pro. Don't know if it's those two sequencers or midi plugins generally. Crashes seem a bit random, hard to reproduce but usually happen upon interacting with a UI element in the plugin. How are midi plugins performing for everyone else?

  • HalftoneHalftone

    Little update just came out I see...

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • JumpercollinsJumpercollins

    Nice combo.

  • KitesKites

    Hey guys, I wasn’t able to find anything through forums search, but is there any talk of QWERTY keyboard shortcuts?

    Also, I’m currently testing the beta sidecar. Wonder if anyones paired it with Loopy Pro yet. :wink:

  • [Deleted User][Deleted User]

    Im excited to try update on my rme card (big hope for all outputs). Thank you for this all!!

  • dobbsdobbs

    Hm… ipad mini 5, ipadOS 14.8
    When the app asked me to do the echo calibration during first startup, nothing happened, it just skipped the process. When I trigger the calibration manually, I see a never ending rotating icon and again nothing happens. Is this a known bug?

  • [Deleted User][Deleted User]


    Ok. No more BM3 in the background for LoopyPro to have multioutputs.
    If only Drambo would have such update, I will be in heaven.
    Thank you for this update!
    and Im glad for all midi improovements in mapping.

  • [Deleted User][Deleted User]

    LoopyPro in background (Launched first) open all outputs in other app like Drambo (which dont let me use of all outputs without additional app like BM3 or LP).

  • FoleslawFoleslaw

    @raindro said:
    Any one have an opinion for best AU sequencer to use with this?

    (I wish Bram made a piano roll sequencer! Hammerhead works so well in LP)

    +1 for Bram’s piano roll!

  • espiegel123espiegel123

    @dobbs said:
    Hm… ipad mini 5, ipadOS 14.8
    When the app asked me to do the echo calibration during first startup, nothing happened, it just skipped the process. When I trigger the calibration manually, I see a never ending rotating icon and again nothing happens. Is this a known bug?

    Not a known problem. Can you power your device down and restart or do a hard reset and see if it still happens after you restart?

  • HmtxHmtx

    @dobbs said:
    Hm… ipad mini 5, ipadOS 14.8
    When the app asked me to do the echo calibration during first startup, nothing happened, it just skipped the process. When I trigger the calibration manually, I see a never ending rotating icon and again nothing happens. Is this a known bug?

    Also might be the old didn’t-click-yes-when-music-app-asks-for-microphone-access problem. Not assuming you’re a noob, I’ve done it too. Every music app on iOS will ask for permission to access the microphone, its essential to give permission so the app can access iOS audio. Go to settings > privacy > microphone and scroll down the list to make sure Loopy Pro is turned on to grant microphone access.

  • ervinervin

    @espiegel123 said:

    @dobbs said:
    Hm… ipad mini 5, ipadOS 14.8
    When the app asked me to do the echo calibration during first startup, nothing happened, it just skipped the process. When I trigger the calibration manually, I see a never ending rotating icon and again nothing happens. Is this a known bug?

    Not a known problem. Can you power your device down and restart or do a hard reset and see if it still happens after you restart?

    I never fails to impress me how ios troubleshooting in 2021 is still based on The Windows Method from the 1990's. 😊

  • espiegel123espiegel123

    @ervin said:

    @espiegel123 said:

    @dobbs said:
    Hm… ipad mini 5, ipadOS 14.8
    When the app asked me to do the echo calibration during first startup, nothing happened, it just skipped the process. When I trigger the calibration manually, I see a never ending rotating icon and again nothing happens. Is this a known bug?

    Not a known problem. Can you power your device down and restart or do a hard reset and see if it still happens after you restart?

    I never fails to impress me how ios troubleshooting in 2021 is still based on The Windows Method from the 1990's. 😊

    True of any hardware/software system, not just iOS. Nor is it a method that particularly relates to Windows or the 90s.

    Power-cycling and resetting give one a known (or semi-known state).

Sign In or Register to comment.