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.
Apps bypassed in AUM do they still use memory?
If an app is bypassed in AUM does it use less memory?
Just experimenting since my ipad Air 3rd gen some times throws a dicky fit, but then I do often throw too many tasks its way.
Comments
If I remember correctly, AUM makes the call to the AU instance to allocate memory and other resources when the AU is first put in the slot. It doesn't call the deallocate method until the AU instance is ejected. So bypassing won't free any memory.
Some hosts don't make the call to allocate until the play button is engaged. But since AUM is always "live," this really wouldn't make sense with the way it works.
That is correct.
I think that things like free-running oscillators, timers, etc. may continue to run as well.
Thanks @NeonSilicon and @ wim.
Does this effect the dsp? or is that different?
I know well I am risking it since I have 2 beatcutters working a midi lfo bypassing and switching them in and out, both of these are being effectived by a Mix Box and Bram Boss perforator. Then 3 colullums containing 2 Ensos in each. Another collum with Hammerhead. All this is triggered by an SL Mixface working in Bluetooth sounds bloody amazing but it sometimes as the odd hickup. Sorry about the spelling rerrors dsylexia and too many pain killers.
I know there is still some DSP consumption even when bypassed. How much or why or how it varies from app to app, I can't say. All I know is when I was experimenting with "freezing" tracks using Enso, the only way to completely free up the DSP was to completely remove the apps.
Hmmm… sounds interesting. How do you freeze Enso tracks in AUM. Must be done in Cubasis?
I put "freeze" in quotation marks because it's not a true host freeze, but a substitute for it. TBH I don't use it much because I don't trust Enso's stability. Here's a wiki article and video showing the process in Audiobus, but the idea is basically the same in AUM.
https://wiki.audiob.us/doku.php?id=tutorial_lower_session_cpu_usage_with_enso
Note: This is a destructive freeze. The only way back from it is to restore a version of the session saved before any plugins are removed.
Yes I agree Enso is brilliant since it imediately captures the moment but is stability is still dodgy.
Thanks @wim for the link. It is pretty much what I am doing already since my Eno’s are capturing the output from 2 Beatcutters, but since that is random sampling of section live I cannot release the Beatcutters.
Yeh, it was just to demonstrate that plugins can still consume CPU when bypassed.
Yeah thanks for that, I sometimes think the animation of Enso’s sample is the straw that brooke the camels back, since when I sample into Enso live from midi it seems to consumme less power than when its window is open with waveform running
That’s just iOS allocating more CPU power because of the additional processing needed for the UI. It’s an oddity of iOS that when an app works the device harder CPU meters can go down. They’re a reflection of the percentage of available CPU power, not total CPU power at any one time. IOS throttles the CPU available to save battery and heat, then kicks in more when needed.
CPU meters don’t always provide useful information on iOS. The only real indicator is how far you can push things before getting dropouts or UI sluggishness.