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.
FAC Maxima seems to have broken…
A recent’ish update to FAC maxima seems to have broken something in AUM…
1) I always have the mix knob mapped as the exposed AU param in AUM, and now it never remembers it.
2) worse, it’s causing all kinds of static/noise. Like if the dsp limit is reached, but it’s only at 40%…
Ive reset ipad, etc… still happening. Remove it and issue goes away. Seems to have something to do with using more than one instance in a project.
Never had this issue until very recently. I’m 100% positive it’s a Maxima issue.
Anyone else seeing/hearing this issue?
Comments
Maxima hasn't been updated for three years.
If that's the case, it would be an AUM problem, not a Maxima problem. Which parameter that's exposed in AUM is controlled solely by AUM. The plugin has nothing to do with it.
How many instances? I'll try some tests.
And what iPad and iOS version?
Actually, I believe an app can specify that parameter in the AUv3 parameter data it supplies to AUM. If the app does not specify one, AUM does not display one (this may have changed in AUM). For example, I loaded DRC and it displays Osc 2 Sync, which is far down its list of AUv3 parameters.
If the user changes that selection, that would only apply to that specific instance of the AUv3. It won't be remembered by either the app or the host for future instances.
I've got 4 instances running here at 53% utilization on iPad 9th gen, iPadOS 17.3.1. Buffers set to 64. No audio problems.
I'm not not seeing the exposed AU parameter either. I can set each instance to whichever parameter I want and what it is set to is saved with the AUM session. The default parameter for new instances will be whatever I set it to last though, but that's reasonable to expect.
I can make the session sound garbled by setting buffers to 2048. Could that be it @MonkeyDrummer?
AUM does remember the last parameter set as the default per plugin. Change it and exit the session. Start a new session and add the plugin. The parameter last selected to show will be the default to show for the new instance.
That is correct. I didn't realize, since I never use them. So AUM should be remembering whatever the user has set for Maxima.
And it should be saving it for each instance in the session. I set up four instances of Maxima, each with a different parameter as the exposed one. The session restored each plugin properly. The default for new instances was whatever parameter I last set as the displayed one. I'm puzzled at what @MonkeyDrummer is seeing.
Could you show us a couple screenshots and/or video mate?
This could help.
Weird… your right… something else changed then that is only now impacting Maxima on my ipad… very weird.
If you post a screen recording showing the setup details and demonstrating what is happening that would probably be helpful.
I think I figured it out based on a comment above. Somehow AUM was operating at a buffer size of 2048 even though the checkmark was on 1024…? 🤔
Pressed the 1024 and the distortion went away… So lots of weirdness…
How or why was AUM doing the wrong sample rate?
Why was Maxima the only thing that seemed to care?
If you started another standalone app earlier that had the buffer size set to 2048, it could force AUM to it. If that app didn't shut down cleanly it could have "grabbed" the buffer size setting even though not running. However, you say you tried a reboot. That should have cleared anything like that out. so 🤷🏼♂️
As for Maxima acting up at that buffer size - sometimes developers overlook that buffer sizes can sometimes set to more than 1024. Most apps have been corrected for that due to bug reports by now, but apps often slip through because not very many people use that high of buffer settings, and of the ones that do, even fewer report the problem to the developer.
I got an immediate response from Fred. 😎