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.
RC500 template freeze after last loopy pro update
Hi
I am using two RC 500 templates https://patchstorage.com/rc500-easque/ and https://patchstorage.com/rc500-esque-groove-edition/ in Loopy pro auv3 running in AUM. Before the last update they were running with no problems.
After the last update of Loopy Pro I run into this problem:
When I have recorded the first loop and want to switch to record the second loop the second records a small fragment and freezes. This does not happen all the time and it always happens after soem time using it. When I restart AUM it works fine again and then after soem time the same thing happens again.
I have been trying to solve this already for some weeks but I have no clue what is happening.
I am open to suggestions.
Kind regards,
Marc
Comments
If you use them standalone rather than in AUM, do they work correctly?
Can you make a screen recording of the problem and post a link to it?
Hi espiegel123
Thanks for responding
I will try both.
What complicates it that it is not clear when it will happen.
Cheers, marc
Hi espiegel123,
I just realized that these are your templates. Thanks for reacting and thanks for those templates! (as I am not using the effects I removed those, but it did not affect the rest untill the Loopy update)
I have made a screen recording in one of the rc500 templates in Loopy as Auv in AUM.
Here is a dropbox link, does that work for you https://dropbox.com/scl/fo/ctr11buonhpe44xml36ps/ACayvkPAHyQv3jemP5lLJJE?rlkey=62x6un7spti7vrzuyv55wvidh&st=u0q1u4eq&dl=0
In the screen recording I repeat the problem twice.
Can you try running them standalone and let me know if the problem happens if they are running that way?
@gitaar0 : it may take me a bit before I can investigate. In the meantime, try the Verse Chorus Looper found in the Sample Projects for quantized looping. Its functionality is more or less the same and it takes advantage of some 2.0 features that make it much simpler to modify.
Question: do you have the problem if you trigger by tapping the trigger button or only using a midi trigger?
@gitaar0 : I just spent about 15 minutes trying to get it to fail in AUM and wasn't able to.
Have you changed the project in any way besides removing the effects?
Have you edited the midi bindings in any way?
Hi,
I have been trying to get the same thing happening in Loopy pro standalone and for jow it still does not happen. With the auv version it sometimes takes awhile for it to happen, it can be running for an hour without problems or it will happen in 10 minutes. Never had the problem with the previous version of Loopy pro. (Which was the last update before the one that is out now)
I am using a midi pedal to trigger all the buttons in the template. Afaik I have not changed any binding. But to be sure I even downloaded a new instance of the template and used that. Same thing happened after a while.
I will try again with a new instance tomorrow, make all the transfers to the midi pedal I am using and keep track of what I do.
I will also check out the verse chorus
Thanks so much for trying to help me,
Cheers Marc
It has been a while that I responded. I have taken the time to try some things. I still have the same problem with Loopy pro as an auv in AUM freezing now and then. I have used the original RC500 templates that I did not change and they also have the same problem when I use them in Loopy pro auv. I can not replicate it in the standalone version. It happens also if I do not use a pedal to trigger the templates. It happens in both rc500 templates (unqauntized and quantized). But also not in the standalone version. Quiting AUM and starting it up again does not change the behaviour. Restarting my Ipad sometimes does. My setup is an ipad pro 12.9 5th generation, IOS 17.7 . Xsonic xtone audio interface, and a satechi usb interface. I am using an apple charger connected to the usb interface.
I am in the middle of a concert tour and this is something that I would like to solve.
I’ve not been able to reproduce the issue.
Do I understand correctly that the problem will happen by touch?
Have you tried the two projects I suggested as replacements for RC500esque to see if the issues happen?
The Verse Chorus Looper sample project is equivalent to the “Groove” (quantized) version.
An unquantized version is here:
https://wiki.loopypro.com/Templates:Verse/Chorus_Looper_Unquantized
The problem happens when I trigger either by hand or though midi. I have tried your suggestions, they do not seem to have the problem but they do have a slightly different functionality and for them to work gor me I would have to adjust some things. i would prefer to use the rc500 if possible.
It is a strange problem as sometimes it does not happen for a whole day and then it is persistently there. As I explained before I never had the problem before the second last update. I just updated Loopy to the latest version and it is the same regarding this problem.
Maybe it is not a Loopy problem but an AUM problem?
Since I have not been able to reproduce the problem, it would be tricky to modify the RC500 projects to solve whatever the issue is.
If you tell me specifically what changes you need to the more modern Verse Chorus loopers to work as you want, those will probably be easy for me to address for you. They are less likely to have issues as they make use of features that weren’t available when the RC500 projects were created.
The RC500 projects have a somewhat complicated internal design as they implemented some behaviors to make up for some features not yet available in Loopy when they were written.
Thanks for the offer. I have to see if I can write it down clearly.
In the meantime. The freeze only happens when switching from loop 1 to recording loop 2. It then records a very tiny bit on loop 2 and freezes. I do not know if that helps getting an idea of what goes wrong. Once it has frozen it keeps doing that untill I restart my Ipad (or at least that is what I think helps)
If you could take a little time using the verse chorus looper and when you find something to change, let me know.any difference should be pretty easy to accomplish.
I will do that. I will get back. Thanks
Hi Edward, I have sent you a PM. cheers, Marc
Edward asked me to post our PM conversation here so if I have other questions others can lear from it.
I followed up on Edwards advice to check out the verse chorus looper as an alternative for the RC500 with which I was having trouble. It appeared to be a good alternative . but I still had to make it work for my situation
This is the list of how I would like to use to verse chorus loopers within AUM . An Unquantized verse chorus looper and a quantized verse chorus looper.
1) Unquantized Verse Chorus loopy
How I would like to use it:
Footswitch A: Clip A (threshold recording) record - play - overdub hold: clear clip A Footswitch B: Clip B record - play - overdub hold: clear clip B FootswitchC: Fade and stop Footswitch D stop (after cycle of playing is complete) double tap: immediate stop hold: clear clip A and B
2)Quantized Verse Chorus loopy
Clip C?groove (threshold recording) records - play - overdub. hold: clear clip C
Footswitch 
stop (after cycle of playing is complete) double tap: immediate stop hold: clear clip A, B,C
How I would like to use it:
Loopy should always be in sync with AUM
Footswitch A: Clip A record - play - overdub hold: clear clip A Footswitch B: Clip B record - play - overdub hold: clear clip B Footswitch
Stopping loopy should not stop the main clock of AUM. I have percussion running in AUM that I want to keep running while I switch loopy loops on and of, always in phase with AUM.
So AUM keeps running and if I press a, clip A starts again in sync with AUM
In the current verse loop template there is a switch switching play to record mode. I do not want to have to use that as it is an extra step. Currently I would not be using the retro recording so I can use that footswitch for something else.
The following was Edwards respond to my list and his suggestions how to make it work:
Regarding:
“Footswitch A: Clip A (threshold recording) record - play - overdub hold: clear clip A
Footswitch B: Clip B record - play - overdub hold: clear clip B”
These are already implemented. Set the mode to Record. Transfer the existing bindings in the Record Mode profile to your controller. Adjust cc numbers as necessary
Footswitch C: Fade and stop
You can copy/paste the button from the RC500 project and bind to that
Footswitch D stop (after cycle of playing is complete) double tap: immediate stop hold: clear clip A and B
Add a button with the Play/Stop clip action with the target set to playing clips.
Add to the double-tap section to that button an action to stop playing clips with quantization set to None in the action.
Midi Learn pressing the button as tap (on)
Midi Learn the button’s double-tap action by double-tapping your pedal
Midi Learn the Clear button’s hold action.
I did this in the standalone version first and then transferred that to the Audio Unit Folder so I would be able to open it in the Loopy Pro AUV3 in AUM.
The only thing that did not work in the quantized verse chorus looper running in AUM was having my percussion running in AUM and have Loopy loops be switched on and off while the clock of AUM was still running.
My solution were two: 1) in the stop trigger I erased the ’stop clock’ binding and in the synchronization I chose Host Sync, making AUM the master and loopy the slave. This works for me now
In the unquantized version I have ableton link on in the synchronisation settings with master and start/stop on. This way Loopy is able to control AUM.
Thanks Edward
I was cheering too soon: i have, now and then, the same freeze with the verse-chorus looper templates as with the RC500 template and why I started my questions in the first place. I use the templates with loopy as an auv3 in AUM. I found out that it is somehow linked to using ableton link in AUM. If i do not use Ableton link it works fine. No problems if I use these templates in the standalone version btw.
If I disable ableton link in both AUM and in Loopy (within AUM), then it does not occur. In that way I can use both the quantized and the unquantized verse-chorus looper.
But I can only use the quantized version as a slave to AUM. If I want to use Loopy as the sync Master in AUM I have to use Ableton link to get AUM to follow Loopy.
Once I have Ableton link switched on and I choose another AUM preset in which I previously had Ableton switched off, Ableton will stay on and then I am back to my freeze problem.
Ableton link status is apperently saved as a global.
What am I doing wrong?
Cheers, Marc
Does this only happen if AUM is the host? Does it happen if Loopy Pro is hosting the Loopy Pro AUv3?
My main setup is in in AUM.
If I run the templates that I use in Loopy pro Auv3 in Loopy standalone they work fine. Is that what you are asking?
I am asking if you load the loopy pro auv3 with the project with loopy pro as the host instead of AUM as the host whether it happens.
@gitaar0 :
I’ve just spent 20 minutes running RC500 unquantized in AUM with Ableton Link on with no failures. I am trying to figure out what might be different.
Do you have the problem if the loopy pro AU is the only AU running and no other apps are running and you use only the on-screen interface rather than midi?
What do you mean by the freeze problem? In the video you posted, the issue seemed to be recording of loop B ended as soon as it started.
I did the same with the quantized verse chorus looper ableton on and seems ok.
Only in screen now, no midid.
As I explained before it does not always happen, but once it happens it is persistent.
I normally have helium, eucledian and octochron controlling percussion apps.
You are right that the issue seems that the recording of loop B ended as soon as it started. After that I cannot get loopy to play loop A (and of course loop B ). I am able to clear the loops but then the same thing happens again.
I’ve spent more than an hour without seeing it happen.
Possible things you might look at to narrow down the cause after rebooting your device:
Hi Edward,
I have again followed your suggestions and have set up loopy pro auv3 in AUM as the only app.
Ableton link is enabled. I worked with both verse chorus templates (unquantized and quantized) for a very long time (as in hours and restarts etc) with touch only and it worked fine. I added my midi pedal (paintaudio midi pedal via midi) and did the same for hours and it worked with no problems.
I added my percussion (helium/shaka, euclidian/things and octachron/external) and it kept working fine.
In my original setup AUM is the core app running effects (eventide/fabfilter/borderland/midiguitar etc) and I have several different AUM setups between which I switch.
I also have a setup with some backingtracks running in AUM’s file-player.
To start the AUM file-player in time, ableton link is switched of in those AUM presets. If I would turn ableton link on it would always wait for the next 1 beat of the ableton link tempo. I do need this to be exact and I cannot get that with ableton link. I read your answers to a thread on this subject: https://forum.loopypro.com/discussion/57092/please-help-me-understand-ableton-link
Now this is what I found out: I start from the perfectly working loopy/AUM setups that I created with loopy pro in AUM (the first ones above with Ableton Link on). Then i switch to my AUM setup with the AUM fileplayer and Ableton Link switched off. Everything works fine, but if I go back to my AUM/Loopy pro (with Ableton Link on) I get the same problem again that the second recorded loop almost immediately stops. Once that happens it keeps happening.
What i did next is: I added a midi channel in AUM with a midi Instance of Loopy Pro in my AUM setup with the fileplayer and switched on Ableton Link in the Loopy pro AUv. If I now switch AUM presets the problem is gone.
It seems that switching Ableton Link on and off in different presets in AUM is what is causing the problem in Loopy (if I am right).
I now have a different problem which is that I can not start the fileplayer immediately as the ableton link prevents that. Any suggestions?
Sorry for the elaborate writing.
I am now trying if it works to replace my fileplayer presets with loopy, which I gues should work
@gitaar0 : ableton link by design has an independent measure-based clock and all link clients follow it. When you start , a link-enabled app is supposed to start on the one of the next cycle.
When it is on, you will see a visualization of the link clock in both Loopy Pro and AUM.
If you aren’t using host capabilities Loopy Pro lacks, you might consider using loopy pro as the host so that you don’t need to use link.
Yes, I understand that. I have now changed my AUM presets in which I was using the fileplayer to using Loopy to play the files. It is a bit fiddely to set that up to works as direct as did the fileplayer in AUM (which reacted instantly) but I have it working.
Nevertheless I am still surprised that the problem I had with the second recorded loop stopping right after starting recording had anything to do with ableton link being turned on and of across AUM presets. (And I am still hoping that I now really solved it).
Yes, I am considering using loopy pro as a host when I have the time to sort that out.
I will keep you posted how it works out the coming days. Thanks so much for your help 🙏
And the problem doesn’t happen if you turn link on and off without changing the AUM preset?
No, only after changing to a preset in which ableton link is completely turned of in both loopy and Aum.
How are you changing them?