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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Loopy Pro Questions
This discussion has been closed.
Comments
@robosardine : the email didn't reach me. I'll check that account's spam folder in case it got tapped there.
Checked my sent box - it’s there. Anyway I’m on YouTube now 😃 see above. Thanks to my daughter Laura and everyone else that knows me.
@robosardine : what happened between the case where it worked and when it stopped. that looks like a bug...the trigger might have something to do with what happened between recording the first sequence and starting the second recording.
@robosardine @Michael : i am seeing similar behavior.
record sequence. delete the recorded events. record sequence again. playback stops unexpectedly after the number of bars originally recorded.
It’s not just meeeee! 😃
I've gone back and forth on Loopy Pro for a while now. I wish the 7-day trial were a bit longer, but alas, mine has ended. With that said, I do have a question since I realized Gauss colors the sounds too much for my needs and can't be used at the moment.
I am running a full live hardware set through my iPad with AUM as a mixer. I have all my channels sending to a buss that will have a looper for transitions. However, AUM is never running in play mode, nor does the BPM ever match the hardware - there's no need for either of those things in my current flow. If I want to use Loopy Pro to capture the end of a song loop to play as I switch projects/patterns/whatever on my hardware, does transport need to be running, or can the loops play independently? Also, since all my songs are different BPMs, do I need to somehow clear and change the loop length for the next song? Basically, I want to be able to hit RECORD via a MIDI controller, have LP record a loop until I hit stop, then immediately start playing it. Then later on, I want to do the same thing in the same recorder with a different song of different tempo/length/etc., without having to do more than press one or two physical buttons.
With Gauss, it always sets the length to when you start/stop it, and I have a MIDI controller setup to erase the Gauss loop and then set the record time to max, which then gets changed when I actually record the loop.
I really hope this makes sense.
Loopy does not need the host transport to be running.
Depending on what you are doing and how you have things set up, Loopy’s loops don’t need to be related to loopy’s tempo settings. If you turn quantization and time-stretching off, each loop can have its own length and be totally independent other loops’ lengths.
So that's a yes? Haha. Basically, I should be able to just have one looper setup on an AUM channel that will record, and then play immediately when I stop? Also, can LP be synced to external hardware if it's being hosted as an AU? If so, that'd make all this a lot easier, actually.
As an AU, Loopy can be synced to Ableton link or the host or nothing.
So, you could run something that bridges link and midi clock. You would probably be want AUM to ignore them if I understand your use case. OR you could run Loopy standalone and AUM in parallel and bus audio between them as needed.
Here’s another thing that has been bugging me with my occasional forays. Why do I find it so difficult to move the play head in the sequencer? I can populate the timeline with some clips, set some loop points - but then when I try to drag about the play head it jitters about like crazy then pings back to where it started. Occasionally I have control over it - but I’ve no idea how I managed to get it to work.
Why drag? It's much easier just to tap on the ruler where you want the playhead to be.
During playback or when the transport is stopped?
Also, could it be that you're synchronizing the playhead with Xequence 2? That would cause some arguing between apps, with X2 asserting itself when playing (and maybe when not playing).
@robosardine : can you make a screen recording and post a link to it? i just tried playing back a sequence and tapping in the timeline during playback and it was working. I was tapping as @wim mentioned where i want the head to move.
@espiegel123 @wim It’s both - when it’s playing and when it’s stopped. I can have nothing else at all with it. Just AUM and Loopy Pro in the effects slot and nothing else. I find it slightly strange that this might seem new to you both 😄 it’s happened to me for as long as I can remember and on different iPads. It can’t be just me that this phenomenon is happening to - I assumed it would be a well recognised thing - being that it’s such a common action on a timeline to do. Maybe it is just me 🤷🏻♂️
Maybe the difference is I don't swipe. I tap in the ruler area. I wouldn't be likely to run into that issue.
What happens if you tap where you want the playhead to move to?
I will post up a video - I’ll be back with this in several days. Problem is I’m in London at the moment and my mobile has been lost or stolen. YouTube want to verify it’s me by sending a phone link before they will publish it as I’m a new client to them. It’s going to take up to 5 days for a new sim to arrive so I will post it then when I get a new phone set up. It won’t be returned to me as someone has already been using it before I had it blocked. Stupidly I had no password on it.
I have the screen recording so that will be fine.
In the meantime I can send it to either or both of you in an email if you would like. I have a recording of the tapping attempt as well - it just jumps to the tap point then rebounds back to the same point. If you want to send me an address I will post them to you, otherwise I will post a link to the video I several days time when the pain of my lost phone has eased and I’m all set up again.
@wim @espiegel123
Before sending it, are you sure that you don’t have some sort of sync turned on? Are you in timeline loop mode where there is a timeline selection set to loop?
How big is the file?
That seems to be it! 😀 I had it synced to AUM and not Link. It’s moving along sweetly now. So it’s not possible then to have it synced to AUM and reliably move the playhead along? I think I had just been taking sync to AUM as a non deviating norm. It didn’t even occur to me to consider this. If you sync it to AUM you will see exactly the issue I was having. Am I the only dimwit to be caught out by this? Whoops!
I notice it will count in now to the sync quantum bar on AUM and keep nice and neat which is great.
Thank you both again.
When you say syncing to AUM, do you mean receiving MIDI Clock from AUM?
It might be inherently tricky to be able to arbitrarily move the play position of the sequencer while slaving to a clock. I am not sure what is supposed to happen. Not many apps with timelines on iOS can run as slaves. I am curious what they do. Is there anything other than Beatmaker 3 and Loopy that will slave to MIDI Clock?
@robosardine : check your AUM settings. Try turning off Send Song Position Pointer -- if you send that and clock, Loopy Pro will want to jump the playhead to the song position that AUM is sending.
I bet that is your issue. I just tried it and if you turn song position pointer off things seem fine.
I was meaning having ‘host sync’ enabled in the Loopy Pro Settings - which seems to rule out syncing to Link at the same time - even though AUM is itself synced to Link. Unless this is referring to syncing start and stop as opposed to bpm which I always thought it was. I see that Loopy Pro will not now start with the starting of AUM though it will of course play in time.
Thought I had pressed ‘post comment’ on this but it’s still here. I’ll press it in a second because I’ve just seen your comment above. Where/how do I turn off Son Position Pointer?
Are you running Loopy as a standalone or as an AU? If you are using it as an AU and using the sequencer, the sequencer is going to try to stay in sync with AUM's timeline. If that is the case, use Link rather than host sync. Link doesn't have a timeline the way that AUM and Loopy do.
I’ll be back. I’m off to bed now - a long journey awaits me tomorrow and we’re leaving early as the missus is well unimpressed as to what Booking.com seen fit to advertise as accommodation fit for a classy bird to enjoy. You know how it is. It’s not so bad - but irritatingly crap in many aspects - so I’m with her on this one. How can you really tell what you are getting with accommodation? They get your money then you get the keys…. meh
I’m running it as an AU. Yes I’m thinking at the moment that this will be the best option at the moment. I’ll get back into it when I get home. Cheers!
Back home - bliss. And the phone is back in my possession and it can be unblocked - double bliss.
I can’t see how to switch off the send song position pointer - I would like to give that a go but I see that you were advising to run Loopy Pro synced to Link - after the song position idea you mentioned @espiegel123 indicating it was the best option. It does seem to work out in a sense doing it this way though it does seem to interfere a bit with my experiments - when the pointer jumps backwards to align itself with Link it plays anything that is behind it before starting at the intended point.
Where do you switch off the song position pointer? I’d like to have a puddle about with it.
Song position pointer is only relevant sending MIDI Clock from AUM to other apps -- when I mentioned that I thought you were using Loopy Pro standalone receiving clock from AUM. I didn't realize until after I posted that you were using Loopy as an AU inside AUM. Host sync always has the equivalent of song position pointer -- so when using the AU with host sync you are out of luck with that.
If you don't need sync with AUM and are just using Loopy as an AUv3 plugin, then you can turn off both host sync and Link in Loopy. Loopy will run freely with it's own tempo controls then.
If you do need sync with AUM, then you could try leaving host sync on and instead positioning the playhead using AUM. To do that you drag left and right over the transport controls.
.> @espiegel123 said:
OK - thank you. Everything is a lot clearer now. I should have asked about this a while ago 🤔