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.
Comments
@DMan @_ki
Thank you. I will pass this on to the lead developer on the project.
@_ki
If the audio unit host app were to set a filter gain setting very near but not equal to zero, like +0.0001 dB of gain. That could cause a problem like the one you described. We will try rounding near-zero gain settings to exactly zero and see if that stops these issues.
@Blue_Mangoo
Hi, concerning nice Stereo Modulator, can you consider adding bpm synced LFO modulation option? This is truly a must have for that kind of effect and currently misses. We have some options in AUM/apeMatrix to use assignable bpm synced LFO, but in GarageBand for example there are no possibility to make a perfect sync. Thanks
Sure. Thanks for the suggestion
Glad you consider that feature, thanks!
@Blue_Mangoo , @tja
After some experimentation i have found a reproducable, minimal setup for the ‚audio fading out‘ problem.
0) Download my sample drumloop to the iPad
https://drive.google.com/file/d/1ny0BSdpBExWuFd0ai26jZqCRQ2PnwfrL/view
unzip and store the wav
1) Open AUM, add a file-player to channel 1 with the given drum-loop, set loop-play
2) Add Blue Mangoo EQ, and do the following steps
2a) Move low-cut to fully left (off), move high-cut to fully right (off)
2b) Set low-shelf to 100hz, -21db exactly
2c) Set bell 1 to 2500hz, 7db exactly
3) Use AUMs save AU preset function (left in the AUs window title bar)
4) Load the just saved AUM AU preset by tapping its name
You will notice, that the curve now shows a new dip on the left side, as
if low-cut is set to 20hz, but the low-cut icon itself is disabled
5) After startings AUMs play, it takes about 25 seconds for one of the channels on the AUM meter to become red and rise, it falls back to a lower level and slowly rises, after 35seconds both meters are red and audio starts to fade away. The spectrum display of the EQ takes a lot longer to disappear.
.
One gets the same effect as saving/reloading the preset by saving the AUM
session, and reloading the session. You also will get the additional low-cut dip.
If one initially sets the low-cut to 20hz in the EQ, the problem seems not occur - only
when loading a preset where low-cut was initially set to be off.
.
I suspect that the drum-loop and redshrike synth (used in my inital bug report) both are quit hot in the gain and have lots of low freq parts in it. The reloaded preset might have a wrong interpretion of the low-cut off setting (as seen in the different curve, but inactive icon) and this might cause a buildup of an DC offset or even a resonance in the lower and higher frequencies.
@_ki
Thank you so much for this.
@_ki we used the information in your bug reports to make corrections. The update went live on the App Store today. Hopefully that fixes the problems you were having.
@Blue_Mangoo Thanks for the update - i have retested for both reported bugs.
BUG 1: AU parameter automation no longer crashes AUM to desktop - but still kills the whole audio-system and the curve and spectrum of the EQ.
As you can see, i also tried to limit the received parameter value to ‚50-60‘ to be shure that the bell 2 freq will be positioned in the center
After enabling the LFO to midi control connection in the midi routing matrix, audio crashes and the UI of the EQ no longer shows graph or curve.
If one touches the bell 2 icon, it jump to 20hz - even though the CC received should have positioned it in the center...
BUG 2: The fading-audio glitch is fixed, the settings get reloaded correctly
I am also currenlty doing some tests about several EQs (of different vendors) performance and number of instances.
Of the Blue Mangoo EQ, i can currently instantiate 26 of them, but only reload 24 without a AU crash. And even then about 7-9 of these 24 lost their setting and revert to the default.
How to reproduce:
Just setup several AUM channels, each with a file player and the EQ and on each EQ just dial in a bell1 or bell2 peak.
For each of the reload tests, better use a fresh start of AUM - so quit, restart AUM and then reload one of the saved settings.
BTW for my evaluation i have an AUM project with 44 tracks and 5 sub-groups (no other AUs used) and can instantiate and reload 49 ZMors EQ AUs without problems.
@_ki sorry for the trouble and thanks for testing again. I’ll s nd this back to the dev team
@Blue_Mangoo Don‘t worry, i am really happy and content with your EQ. It offers a very nice spectrum graph and easy controls, intuitive UI, doesn’t use much CPU and mostly works great.
Others seem to get the AU automation running, at least i saw messages that they did with the old version. I startet with a newer version, where the parameters got logarhytmic scaling which IMHO is better for filter sweep automation.
That's interesting. I wonder what is the limiting factor: CPU or RAM, or something else? What happens when you reach the limit?
I think its a memory limit - as far as i have read, all instances of an AU only get 360MB total on 64bit devices.
For the 24 Blue Mangoo EQ instances, i get only 27-43% CPU - without any EQs the project already uses ~28%, so from the CPU performance one probably could do 60-70 instances of your EQ before hitting 100% CPU.
.
If one adds one instance too many, all instances of the AU crash - this is a real problem with big sample based AUs like Syntronic where one can open only a few instances because each needs a lot of memory.
When coming near the cpu limit, you start to get crackles when the UI does ists redraw for instance when scrolling AUMs channels. When reaching the CPU limit, you get crackles - but no crash of the system.
@_ki that makes sense. I think we are using ram on drawing graphics with metal. I’ll look into it and see if the RAM footprint can be cut down somehow.
Perhaps only allocate the extra memory for the spectrum graphics if the AU is opened and deallocate it when closed. This would probabbly help lot with the total footprint.