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.
Crackling/Popping only while UI is visible
Back to the well of knowledge. Just made a project with electric vintage, DRC, Magellan 1 IAA, audio guitar sample, audio drum samples: kick, snare, hats. 2 au fx on guitar sample, no other fx. 8 bars looped.
On a 1st gen 9.7 iPad Pro. Sometimes I have similar loops with 3-4 more AU’s, more samples and more fx and no issues. With this loop, getting crazy pops and crackles in BM3, but only when UI open, if I hit the home button to collapse the app, the loop plays perfectly. Any visual settings I can adjust or any other ideas on why this happens and how to fix?
Also when I reopen loop, Magellan 1 arp and bpm is gone and returned to 120 in Magellan with no arp even though I’m setting it to track tempo before saving and have bpm lock engaged. What gives?
Comments
IAA apps don't save their state like AUv3 apps do. Some return to the last settings they had when you closed them down, some don't. None save the state within the host project.
(except in Audiobus if they support Audiobus state saving.)
The only way to find out is to remove one app at a time until the problem goes away.
The number of apps you can get away with varies with the apps, the complexity of the patches used, sample rate, buffers, the polyphony, the size of the samples, whether or not you have disk streaming and/or real-time time stretch, and probably a dozen other factors. There's no formula for predicting what you can get away with. Using IAA apps is generally going to cause more issues than AUv3 though in my experience.
What are the AU fx? The CPU varies widely from effect to effect. What are your buffers set to?
@wim thanks, i do notice the most issues with audiokit apps so I found it strange it happened on this track without Bass 808, retro piano etc.
@espiegel123 dual vcf and kosmonaut. I did notice on a track a little while ago that I put the free cassette effect, think it was version 2, the whole track and mixer screen started stuttering so bad I couldn’t even play the track anymore. 44100 128 16 bits background audio on and measurement mode on. I took everything down except recording bit depth and it was still crackling. So weird that it stops when I play it with the BM3 UI collapsed. Right now the track is stopped and my cpu is hitting 28%.
128 is a pretty small buffer . Try 256 or 512 and see if it improves.
Also rebooting can make a difference.
Thanks @espiegel123 i’ll try that. Is it normal for CPU to jump to 30% and hover around 24% when the track is stopped?
CPU % isn't very meaningful until you get into very high numbers. Search the wiki for throttling for an explanation .
I found that limiting the frame rate on my ipads helped a bit ... a while back Apple reset things to accommodate video streaming and the like - increased the rate at which graphic displays are refreshed - effectively doubling it to 120hz. Not exactly essential for musicians.
If you have graphic intensive apps - FX with lots of pretty wiggling knobs and complex automations for example - they can add significantly to sudden CPU spikes. But I haven't noticed any problems or arkwardness with running them at 60hz.
You limit the refresh rate by going to settings - accessibility - motion - tick the "limit frame rate" box. Worth a try.
@Soundscaper I think you are onto something with the frame rates since the crackling stops completely when playing the track with the iPad screen blacked out/not showing visuals.
@espiegel123 changing the buffer size helped some after I rebooted. I made another track with a bunch of au’s, an IAA, some samples, more than the original track with the problems and no crackling.
I’ll change the frame rate too, seems like that would help as well.
In ipadOS 14 audio processing will not be limited to one processorcore is what I heard. That will expand possibilities for older devices too I think.
That's good news. Will only new apps can use this new feature, or do the present apps profit also?
I also have a 9.7" 1st gen iPad Pro.
When apps have a lot of graphics going on, it tends to
crackle and crash a lot at lower latency settings.
With some of my configurations I cannot use my iPad at anything other than 1024.
My recommendation is to play in notes at 256 and then as
you add more effects increase the buffer to 1024.
Apps have to be specially written and use a new set of routines to take advantage of this. It might be a lot of work for developers to modify their existing apps.