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.
Hot battery with LaGrange or DLYM?
I’ve begun an exploration of LaGrange. and I find the battery on my 12.9 Pro2 getting extremely hot. LaGrange only using 1% but DLYM has used 14%!
Haven’t tried with other synths yet. I’ll experiment eliminating DLYM, of course. Anybody have any input on this? CPU is running around 25%. Might I have a problem with the iPad? Thanks
Comments
Were you using them in AUM?
I don’t have a pro, but also not getting any overheating, although some of the DLYM presets caused spikes up to 60% for a moment or two.
Hope that help a little.
@SNystrom, nope, CB3. I disabled it and the battery cooled down. One more iOS mystery!
Are you sure it’s the battery and not the processor getting hot?
@Edward_Alexander.... duh, hadn’t thought of that. .... but the cpu is around 25%.
It can be juicy with its processor use. With iOS's more processor-intensive music apps it's a good idea to have your iPad on a stand. That way at least it's being air-cooled, and that can make a lot of difference in a composition with multiple channel strips of instruments/fx.
Not sure if this would be helpful but DLYM has a new update with some bug fixes, try updating maybe.
@jonmoore and @eylvy, thanks for the thoughts. I’ll probably just avoid DLYM. Plenty of delays out there.
Do you remember the settings you had for DLYM? I was trying it in AUM and barely had it register on the CPU load. That could be a difference in the way CB3 and AUM measure and report.
Were the UI's for the AU's open when you noticed the heat?
@NeonSilicon, It was probably the default setting, but I don’t remember. UI was not open.
Well, that takes out any of my theories then.