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.
AUM / Model D crackling and DSP spikes
Just noticed I can’t seem to run 2 instances of Model D without massive spikes when I open the AU and sporadic crackling other times, no other apps open, iPad Pro 10, iOS 11.3, latest app versions. Anyone else seeing this? I just updated to 11.3 so hoping it’s not this!
Comments
I think they added some settings to the system settings area for Model D. There are settings for Preferred Buffer Size and Preferred Sample Rate. They are in the iOS Settings app.
Try checking to see if these match what you have AUM set for, as well as your audio device if you are using one. Set them all the same and see if that helps. If the audio buffer size keeps changing when app switching, you will get crackles. Also changing samplrates will require processing and can cause crackles as well, so avoid that too by setting those all the same rate.
Hope this helps.
@CracklePot thanks for the info, unfortunately the settings are already the same. It seems when I open the AU I get a DSP spike of around 40%, so weird!
My Air 2 is running 2 AU instances ok. DSP peaks in the 90% range but not going red. You should be fine it seems. I used 256 44.1 and even had BeatHawk open in the BG.
What are you using to monitor? Built in speaker, headphones out, USB device, etc. The built in speaker is also known to crackle, but it goes away if you use other monitoring methods.
better contact @MoogMusicInc and see if they can replicate it. I'm still on 11.2.1 and don't want to update yet if that's true
I'm having the same problem on my ipad pro 9.7". iOS 11.3 running two instances of Model D in AUM, 44100, buffer at 256, DSP hovers around 40% even while both are being triggered by an external sequencer. two monophonic patches, sans fx. As soon as I open the GUI, DSP shoots up to 106+% and everything goes crackly/haywire until the window is closed.
Same thing happens when I use one instance of Model D alongside most any other AU instrument.
same here as what @palm describes, but with iPad Pro 10.5.
The thing I’m seeing with this app under AUM on an iPad Pro with latest IOS, is how very loud it is. I have to turn down the volume to very low on the fader in order to stop it completely overwhelming everything else.
Wonderful app, and getting better with every update, but loud, man, too loud.
Yea it is pretty loud. I noticed that too. Amazing app though! By far my fav synth on iOS. I can only describe it like this - it feels like an instrument.
>
Coming from you, quite a compliment.
This is the same problem I was having with Model 15. The GUI causes spikes, and it happens to me with only one instance at 128.
AU gui causing cpu jump is definitely a thing on iOS not restricted to the Moog apps. I think it’s more noticeable with them as they are the most cpu intensive synths. I wonder if 11.3 has made it worse though. I know it’s a bit better if you turn off the 120hz mode in settings.
I’m only using AUM mainly to host AUs right now, is it happening the same in all hosts?
Exact how it feels too for me.
But the volume is important since it drives the feedback/saturation. Also maybe one of the few synths where the OSC and the main output has an effect here.
I like to gain stage ot full but then put a limiter or compressor behind it to get a controlled wonderful saturation no other app can do yet.
Especially now with velocity and aftertouch control. Thought that was the only thing lacking if anything.
Oh yeah. I’m getting my share of crackling as well. Seems to come with the territory.
Model 15 did/does it too. Air2, latest update.
It seemes weird to me that a lot of the crackle-plagued are on Pro models. I looked up screen sizes and the Pros are significantly higher resolution than my iPad Air2. I now wonder if the screen is taking up too much processor for you Pro users, and you need a low res mode to optimize for Audio rather than Video, or something along those lines.
This is weird indeed, and seems to indicate that the issue not directly related to available CPU power. I'm getting the feeling something is borked in the way iOS handles thread priorities (i.e. erroneously giving higher priority to graphics-related threads over the sytem audio thread).
@brambos or anyone - any idea who I should contact regarding this bug? Moog / J Liljedahl / Apple?!
I suggest Moog and Apple both, as you're a customer of both, and Moog is a customer of Apple - and a "known" brand. You could add AUM in there, as well.
It sure seems like this to me. Crackles whenever interacting with UI in a number of different apps and combinations. Air 1 11.3
I swear it started with iOS 11 because I’m pretty sure it wasn’t doing this prior. I thought it was certain apps but that doesn’t seem to be the case.
I haven't read this thread very closely to see which version of ios everyone is using but I just found this article.
It appears iOS 11.3 is causing a lot of audio issues.
https://www.forbes.com/forbes/welcome/?toURL=https://www.forbes.com/sites/gordonkelly/2018/04/15/apple-ios-11-3-problem-apple-music-facetime-skipping-iphone-ipad/&refURL=https://www.google.com/&referrer=https://www.google.com/
Moog are certainly aware of the issue. I would report to Apple and mention that Model 15 and Model D are performing very differently between past and recent iOS versions and that graphics-heavy operations (opening the UI, task-switching between apps, etc.) interfere with audio performance - and that the issues seem to be extra noticeable when the apps are hosted as AUv3.
working ok here....
ha, was going to post whether you'd checked that button, easy to forget though
There's a nice patch setting for Model D in new Geoshred update, it works great on headphones but.....
If I use my Audio interface iconnectAudio4 I get stuck notes in Model D after using it. then I have to restart GeoShred and AUM as weirdly the AUM midi port disappears from all apps.
Not sure what's going on there
edit: ok it seems Geoshred enables all midi out ports by default, so switching all off but AUM port and all is more stable
Yea this has been a thing for a while. Hard to tell because sometimes it seems to function better than others which might be updates? Also I've heard when your battery is over 50% it seems to occur less. I had my battery replaced and its still not entirely gone tho. Definitely seems like a thread priority thing. Opening the UI usually seems to help while minimizing seems to cause the spike