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.
Bug with "Play tail in loop"?
I have a problem where, when I open Loopy Pro after not using it for a few hours, the "Play tail in loop" function causes the loop to jump up in level at the beginning of the loop every time during playback. This seems to happen with pre-recorded loops. I haven't experimented to see if this with live loops. Loading another project, playing it for a few seconds, and then reloading the original project seems to work.
My fear is that this will happen in a performance situation.
Has anyone else experienced this? Is there a way to fix this?
I'm not using multiroute audio, and it happens whether the iPad (8th gen) is connected to headphones, using the internal speaker, or connected to an interface.
Comments
Can you export, zip, and attach a simple example project?
Thanks for the reply.
I'll make a project, but then I'll leave it until the iPad has sat unused for a while, to make sure that it's a problem in the project I make. So, it'll be probably some 16 hours or so until I can upload something.
Meanwhile, I'll record a session if it happens while using the iPad today.
@moxamstudios : I haven’t heard of anything like this so it is a bit mysterious. A demonstration would be helpful. Are there any follow actions involved? Does it happen with internal audio or only if an interface is involved?
Great. Take your time. Unless @espiegel123 knows of some setting that might account for that, I think it's the only way to get to the bottom of it.
If I load and play another project, and then return to the original, that fixes it.
Also, it only seems to happen after the iPad has sat unused for a while. In my case, usually overnight.
I don't recall if it's happened while connected to an interface, but definitely, it happens with internal speakers or bluetooth headphones.
If I open a loop while it's playing, and turn off "Play tail in loop", the problem in that particular loop stops. But, it also reoccurs if I turn it back on.
The problem will happen consistently until I load a different project.
You mention it happening with pre-recorded loops? Can you clarify what you mean by that? 3rd party loops imported into Loopy? Loops you recorded previously in Loopy and imported? Loops previously recorded in the same project? Or ?
@moxamstudios : do you have multiroute audio turned on in the System Settings panel by any chance?
That one is answered in the OP.
Loops made by me, some using Apple loops, in Logic, imported into Loopy Pro; formatted 48 Khz M4A/AAC VBR. Pre-recorded, as in not recorded live, inside Loopy Pro, during a session.
I got it to happen today, though it's in an actual project and not something made just for demo purposes. I've made a screen recording of it happening. I'll see about making it available shortly.
What I've noticed is that the tail doesn't actually play, and that the volume of the clip returns to normal at the moment that the tail would have run out.
Woof. That's gonna be a fun one to try to run down 🥴. You might not need to attach the whole project if you have a video. The audio file may be enough.
Here's a link to a Proton Drive folder where I've uploaded the screen recording.
Loopy Pro glitch screen recording
Just to confirm - it's the first loop, the drum loop that's exhibiting the behavior, correct?
When you say "I have a problem where, when I open Loopy Pro after not using it for a few hours, ..." can you go into more detail? Is the iPad shut down? Is Loopy open in the foreground, or have you switched away from it, or have you force-closed it? Is
Play in Backgroundenabled in Loopy settings?Does it happen if only the loop in question is playing?
It's in every loop that has that feature turned on, which is pretty much all of them. That includes the pad that plays at the start.
I only heard it in the first one in the video. Are there others?
I think we will have to look at the project and see what is going. This is the only report we have had of anything like this.
Does this happen in any other projects?
Hmm… for the most part, I exit the app, and in this case, I am sure that I did return to the home page before turning off the iPad. However, I am not force-closing anything. Generally, I leave apps running and don't force-close things.
I did not hard shutdown the iPad, nor did I connect it to a charger. I just turned off the screen.
Play in Background is enabled.
There's a series of 8 projects which I'm working on currently. Each one was a copy of the previous, basically using the previous as a starting template. It has occurred with whichever of those 8 projects I've left as the open project.
The issue can be resolved by opening another project. If I return to the project where the problem was happening, it will now play normally.
@moxamstudios: does loopy stay open and in front the whole time?
Can you try making a copy of the project and delete all but one of two loops and see if it happens? That would help enormously.
I will do that, and leave it overnight as the open project. Tomorrow, I will report.
@wim @moxamstudios : does it happen even if loopy is left in the foreground overnight or only if Loopy Pro was in the background?
Last night's test, Loopy was in the background (background audio enabled). Interestingly, Loopy was restarted due to a TestFlight update at some time during the night, and it still occurred when I opened Loopy this morning. I will leave it overnight in the foreground tonight.
I hadn't removed any loops from the project, and won't tonight. That'll be the next test. Gonna take awhile at one day per test. 😉
What state was the project in when you started playing the loops after returning to it? Where some loops play enabled already?
There were six or eight loops play enabled. Tonight's test will only have one enabled and Loopy will be left open with the iPad screen turned off and the iPad powered.
btw, the project is fairly straightforward. I haven't found any actions that seem like they could contribute. Loopy's dynamics processor is the only FX in the project ... which is of course another thing to test with / without. I can't think of any reason it would do something like that, but it's a "person of interest" by association with the crime scene.
I left the project open over night with Loopy Pro in the foreground and only one clip armed. The problem didn't occur. I'll try the same test with Loopy in the background tonight.
I'll try to set up testing on another iPad I don't need to use during the day to hopefully speed up the testing.
I left it overnight in the background and unfortunately the problem didn’t happen
We'll probably get there eventually, but it's likely to be a long process finding repeatable steps. At least it's reproducible somehow. At least there's an easy workaround in the meantime.
@wim and @moxamstudios can you see if you slightly change the trim marker that creates the tail if it changes anything?
The first time I played the project, the tail didn’t play in the pad clip. But it hasn’t happened again for me even with a fresh project.
Someone had a clip that behaved funny and stopped doing so when they moved the marker.