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…4041434546…50

Comments

  • MichaelMichael

    @lukesleepwalker said:

    @hat_cake said:

    @wim said:

    @wim said:

    @hat_cake said:
    Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

    Sorry, no.

    I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

    ooh, thanks! thats a clever workaround idea :)
    either that, or something along those lines, should be quite powerful..

    This feature request has been made several times so here’s hoping the master can fit it in.

    Yep, that’s coming soon, both as a clip target for actions and also as a feature of play groups

  • lukesleepwalkerlukesleepwalker

    @Michael said:

    @lukesleepwalker said:

    @hat_cake said:

    @wim said:

    @wim said:

    @hat_cake said:
    Is it currently possible to configure a button to play a random loop, and on every button press, it'd randomise again?

    Sorry, no.

    I suppose you could set up midi note bindings to launch clips, then use something like the Rounder Robin Mozaic script to send random notes to trigger them.

    ooh, thanks! thats a clever workaround idea :)
    either that, or something along those lines, should be quite powerful..

    This feature request has been made several times so here’s hoping the master can fit it in.

    Yep, that’s coming soon, both as a clip target for actions and also as a feature of play groups

    HUZZAH! And the clouds did part and heavenly beams of light doth shine upon us.

  • MichaelMichael

    Yea and verily, for I am a beneficent developer

  • wimwim

    Verily! And we the recipients of thy bounty do revere thee.

  • gregsmithgregsmith

    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

  • wimwim
    edited January 2022

    @gregsmith said:
    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

    Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

  • espiegel123espiegel123

    @wim said:

    @gregsmith said:
    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

    Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

    I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

  • gregsmithgregsmith
    edited January 2022

    @espiegel123 said:

    @wim said:

    @gregsmith said:
    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

    Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

    I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

    On closer inspection, it seems to have something to do with the order of the donut group.

    In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

    If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

    However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

    I hope this makes sense to someone! 😂
    Hopefully @Michael will understand my rambling and can confirm my suspicions.

    If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

  • GLaceyGLacey

    Question. I imported a sample into a 2 bars loop. The sample is somewhat shorter than 2 bars. The problem is that the sample is getting retriggered immediately at its end not just the beginning of the next loop.
    Can you please advise how to setup the loop to trigger the sample only at the beginning of each loop?

  • JumpercollinsJumpercollins

    @gregsmith said:

    @espiegel123 said:

    @wim said:

    @gregsmith said:
    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

    Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

    I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

    On closer inspection, it seems to have something to do with the order of the donut group.

    In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

    If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

    However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

    I hope this makes sense to someone! 😂
    Hopefully @Michael will understand my rambling and can confirm my suspicions.

    If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

    @gregsmith You may find StreamByter Nimble Midi Looper and TF Visual Swift Music new TX/RX Midi and Audio Modules if you can grab the beta from @Jorge come in handy for experimenting with midi connections and combining midi and audio with Loopy Pro at least until we get the midi update.

  • Doc_TDoc_T
    edited January 2022

    Two questions. I MIDI map a Korg NanoStudio controller to LP. The faders control the volume of the colors. The Hardware fader sends value 127 but the fader in LP does not go beyond 0dB. Is this correct? How can I set the controller to cover the whole range of the LP slider?

    I know that current launchpads (mk3) get automapped with corresponding colors etc. I have a Launchpad mk2 and would like to map this like the newer models. Is this possible from the UI of LP? Or does this require some deep dive into the app and some obscure MIDI sysex commands to work properly? How is the binding of the automapped Launchpads done?

    I hope this was not covered before.

  • gregsmithgregsmith

    @Jumpercollins said:

    @gregsmith said:

    @espiegel123 said:

    @wim said:

    @gregsmith said:
    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

    Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

    I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

    On closer inspection, it seems to have something to do with the order of the donut group.

    In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

    If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

    However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

    I hope this makes sense to someone! 😂
    Hopefully @Michael will understand my rambling and can confirm my suspicions.

    If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

    @gregsmith You may find StreamByter Nimble Midi Looper and TF Visual Swift Music new TX/RX Midi and Audio Modules if you can grab the beta from @Jorge come in handy for experimenting with midi connections and combining midi and audio with Loopy Pro at least until we get the midi update.

    Thanks @Jumpercollins I’ll have a look.

    I’ve actually got a really good working solution triggering atom2 clips with empty donuts. It’s working great. Will make a video soon.

    Thing is, this is the only thing holding back using LK which would give us automation as well as midi. It’s completely working apart from this one detail which I think will be easy for @Michael to sort if my theory is correct.

  • JumpercollinsJumpercollins

    @gregsmith said:

    @Jumpercollins said:

    @gregsmith said:

    @espiegel123 said:

    @wim said:

    @gregsmith said:
    @Michael I'm experimenting with using donut follow actions to trigger LK clips on and off. It's working really well except for one thing. When I have a group of donuts set so only 1 will play at a time, and go from one to the other, sometimes the stop follow action from first one will trigger before the play follow action from the next one, and sometimes the other way round. Is there any logic to this? It'd be good if the stop action of donut one always fires before the play action of donut two for my purposes. Not sure about other scenarios.

    Could it possibly have something to do with FX tails? I wonder when the stop action fires if the loop is set to play the tail on stop.

    I think I reported a bug a while ago that was the result of something like this. It prevents one from implementing the equivalent of record and select next.

    On closer inspection, it seems to have something to do with the order of the donut group.

    In this screenshot, the empty donuts in the grid trigger the corresponding grid positions in the LK instance. Because of the way LK works, the stop action on all the blue donuts triggers the stop at the bottom of the blue column in LK. The donut groups are set so that only one donut will play at a time.

    If I tap blue 1, then blue 2, then blue 3 working downwards, it works as intended with the stop action stopping the LK column, then the start action of the next donut starting the next LK clip.

    However, if I go upwards, from blue 3 to blue 2 for instance, blue 3 stops in LK, but blue 2 doesn’t start. I think this is because the stop action of blue 3 donut is firing after the stop action of the blue 2 donut.

    I hope this makes sense to someone! 😂
    Hopefully @Michael will understand my rambling and can confirm my suspicions.

    If anyone’s wondering why I’m bothering with all this, I reckon if I can get this working, we have midi donuts and automation donuts that can be arranged on the loopy timeline along with normal audio donuts.

    @gregsmith You may find StreamByter Nimble Midi Looper and TF Visual Swift Music new TX/RX Midi and Audio Modules if you can grab the beta from @Jorge come in handy for experimenting with midi connections and combining midi and audio with Loopy Pro at least until we get the midi update.

    Thanks @Jumpercollins I’ll have a look.

    I’ve actually got a really good working solution triggering atom2 clips with empty donuts. It’s working great. Will make a video soon.

    Thing is, this is the only thing holding back using LK which would give us automation as well as midi. It’s completely working apart from this one detail which I think will be easy for @Michael to sort if my theory is correct.

    @gregsmith
    Looking forward to seeing how your achieving everything on your video once you get time to post it.

  • sisterkatesisterkate
    edited January 2022

    @robosardine said:

    Talking about making another Loopy Pro @Michael. I was wondering if you would ever consider making a Loopy Pro ‘Lite’ at some time in the future - which would only have the basic functionality of importing and looping audio with a few more useful select features thrown in? I’m about to purchase Loopy Pro when my trial runs out shortly (and a work of art it truly is) - but I won’t be using many the features - like live looping etc
    I’m thinking along the lines that you would sell a real barrowload of them at a smaller price, and it could act as a gateway to the bigger one.
    iOS needed a good AU clip launcher up until now, a Lite version would fill that space and be a lot less complex to work with, it would also be a real challenge to any other budget clip launchers out there and so would likely occupy a considerable chunk of that market. There’s maybe a lot of folk that are reluctant to shell out for the big Pro one when they only want to have a bit of fun launching off some clips.
    It’s not going to affect me like I say as I’m getting it anyway (though funnily enough I would probably buy a Lite version as well).
    Just a curious thought. I z

    • 1
  • Doc_TDoc_T
    edited January 2022

    @Doc_T said:
    I know that current launchpads (mk3) get automapped with corresponding colors etc. I have a Launchpad mk2 and would like to map this like the newer models. Is this possible from the UI of LP? Or does this need some deep dive into the app and some obscure MIDI sysex commands to work properly? How is the binding of the automapped launchkeys done?

    Interesting is, that I can load LK as a MIDI source in LP and the Launchpad will connect to LK instead of LP. I guess I could make a grid in LK that would mirror the LP grid and MIDIlearn the Launchpad to LP. That way I could have a colored layout on the Launchpad mkII - similar to a 'native' automapped device. Interestingly the Launchpad could than also act as a MIDI Looper with Ableton like MIDI loops in LK to drive AUs in LP. Sounds somehow smart - but maybe take to much time to develop a workflow.

  • shponglethedogshponglethedog

    @espiegel123 said:

    @MisplacedDevelopment said:
    Has anyone managed to get MIDI Guitar 2 working inside Loopy? I think I have it wired up correctly with MG added as an effect on mic input then the “A” instance added as a MIDI lane but it does not send any MIDI out to the destinations I have selected (tried a few synths and MIDI monitor). The internal MG synths respond OK to input so that part is working correctly but LP is not seeing the MIDI out.

    Odd…just restarted Loopy and now MG in the MIDI lane is labelled as “B” version and it and is sending MIDI out correctly. I can reproduce the original problem though by removing MG and adding it back in again.

    I have the same issue.

    Ditto here. Sent a message to Michael, he said it's fixed in the next update. Awesome!

  • mbncpmbncp

    I have my iPad connected to the Mac and I'm using the usb connection (audio in + midi in/out) and my problem is when restarting Loopy pro (most of the time) it will loose the connection, I need to add that midi input again, reassigning connections.

    Any idea ? The port name is IDAM MIDI host and it has always the same name

  • cuberoo_cuberoo_

    @mbncp said:
    I have my iPad connected to the Mac and I'm using the usb connection (audio in + midi in/out) and my problem is when restarting Loopy pro (most of the time) it will loose the connection, I need to add that midi input again, reassigning connections.

    Any idea ? The port name is IDAM MIDI host and it has always the same name

    I’ve had the same problem and the only workaround I’ve found so far is to use Audiobus in the middle. Set Lp to send and receive from AB and setup Audiobus to route to and from idam.

  • mbncpmbncp

    @cuberoo_ said:

    @mbncp said:
    I have my iPad connected to the Mac and I'm using the usb connection (audio in + midi in/out) and my problem is when restarting Loopy pro (most of the time) it will loose the connection, I need to add that midi input again, reassigning connections.

    Any idea ? The port name is IDAM MIDI host and it has always the same name

    I’ve had the same problem and the only workaround I’ve found so far is to use Audiobus in the middle. Set Lp to send and receive from AB and setup Audiobus to route to and from idam.

    !
    Good idea but I'm wondering if it's not adding an extra buffer latency, will try !

    What I did was to add atom in the middle but within loopy, I still have to add the track but just have to send to atom instead of 20+ synth :p

  • cuberoo_cuberoo_

    @mbncp said:

    @cuberoo_ said:

    @mbncp said:
    I have my iPad connected to the Mac and I'm using the usb connection (audio in + midi in/out) and my problem is when restarting Loopy pro (most of the time) it will loose the connection, I need to add that midi input again, reassigning connections.

    Any idea ? The port name is IDAM MIDI host and it has always the same name

    I’ve had the same problem and the only workaround I’ve found so far is to use Audiobus in the middle. Set Lp to send and receive from AB and setup Audiobus to route to and from idam.

    !
    Good idea but I'm wondering if it's not adding an extra buffer latency, will try !

    What I did was to add atom in the middle but within loopy, I still have to add the track but just have to send to atom instead of 20+ synth :pensive:

    I would not expect Ab to add much latency, if any in real terms, certainly in the case of just passing through one port to another.

  • JohnInBostonJohnInBoston

    Latest update is out!

  • RajahPRajahP

    @JohnInBoston said:
    Latest update is out!

    Yep

  • Edward_AlexanderEdward_Alexander

    Nice! Thanks for the update @Michael we appreciate all of your hard work!

  • Doc_TDoc_T

    My Launchpad mkII shows signs of life which is very good! Thanks for the update and this absolutely great app!

  • MichaelMichael

    Thank you!

  • ambrosiajamambrosiajam
    edited January 2022

    I can’t seem to grant access to the microphone in standalone mode? I tap the ‘open settings’ option and it doesn’t show up…

    Any help would be appreciated, I can’t seem to find the info I need. It seems simple, I can’t understand what I’m doing wrong here. Using a behringer u-phoria um-2 audio interface…


  • espiegel123espiegel123

    @ambrosiajam said:
    I can’t seem to grant access to the microphone in standalone mode? I tap the ‘open settings’ option and it doesn’t show up…

    Any help would be appreciated, I can’t seem to find the info I need. It seems simple, I can’t understand what I’m doing wrong here. Using a behringer u-phoria um-2 audio interface…


    What OS?

    Disconnect everything . Reboot your device and look in Microphone settings. then reconnect your device.

  • ambrosiajamambrosiajam

    I am Using iOS 15.1 on a 2017 12.9” pro

    I did disconnect, hard reboot, no change. Will try again and delete/reinstall the app if it continues

  • HmtxHmtx

    @ambrosiajam said:
    I can’t seem to grant access to the microphone in standalone mode? I tap the ‘open settings’ option and it doesn’t show up…

    Any help would be appreciated, I can’t seem to find the info I need. It seems simple…

    Your settings screenshot shows that you are looking in Settings>Loopy Pro and you won’t find it there.

    You’ll need to go to Settings>Privacy>Microphone and then find Loopy Pro on the list and turn on for access.

  • ambrosiajamambrosiajam

    @Hmtx said:

    @ambrosiajam said:
    I can’t seem to grant access to the microphone in standalone mode? I tap the ‘open settings’ option and it doesn’t show up…

    Any help would be appreciated, I can’t seem to find the info I need. It seems simple…

    Your settings screenshot shows that you are looking in Settings>Loopy Pro and you won’t find it there.

    You’ll need to go to Settings>Privacy>Microphone and then find Loopy Pro on the list and turn on for access.

    That’s what pops up when I hit the prompt in loopy pro. Anyhow, I checked the privacy->mic settings and loopy pro doesn’t even show up on that list of apps, nor does it show up on the list of apps that recently requested access. I might try deleting and reinstalling the app, I can’t see any other way to get this to work?

    The audio interface inputs and outputs are showing up in loopy, however:

Sign In or Register to comment.