Error- AUv3 app resets to Init setting
This is driving me crazy. I don't build things in Drambo but I love the sequencer and possibilities for P-Locks. However, when I use an app like Tal-Uno, Korg Gadget, and even Zeeon-- I will come back to a project only to find the error message and I have to reset the audio unit instrument. I'm hoping there's a simple solution, because this is making Drambo unusable for me. Thanks in advance!
Comments
I just tried to reproduce with Zeeon but everything worked fine.
What exactly are you doing to make this happen?
Thanks for responding. Apps and iOs are up to date... I just make a song come back later and then I get these error messages. I was hoping there is an obvious solution. But I don't think I'm doing anything weird. I make a song in Drambo with a couple AUv3 plugins, come back a day or two later and it's this error message.
OK let me try projects with more AUv3 plugins...
I'm sure I'm not above "user error", if it's something as simple as not saving properly, or file management, idk?
I remember a similar issue long ago that only applied to Virsyn's Teraverse which did not behave correctly in communication with the host.
Your issue must be different because I haven't had any of these recently.
Which iPad model and "up to date" iOS version are you running?
iPad 9th generation. Was at 18.3.2 updated to 18.4.1
is it worth it to delete and redownload Drambo?
If AUV3 plug-ins are large in size/contain a lot of samples, they hit OS AU memory limit.
That’s at least why my Drambo in Loopy wouldn’t load. I’d get exactly the same symptoms. Since I’ve diminished the number of samples I’ve stopped having these issues.
Actually, my Drambo project was only like 150mb so nothing crazy big.
@seenbread Does it also happen if you load a project with only 1 or 2 Zeeons loaded?
But if I have multiple AUv3 tracks in Grooverider 2 it's fine.
I'll create a project with only 2 Zeeon tracks and report back.
I have a very similar problems. Many of my Auv3 plugins fall into 'error' state when I keep drambo in the background while doing other stuff, others seem to go back to default parameters. In any case drambo is not showing a reliable behavior with these plugins. this can be a real dealbreaker when it comes to live performances and such
Interesting, I was wondering what caused it. So I can avoid it. It sucks to lose what you've worked on, makes you lose trust in the process. But in the past couple weeks I have not had the error, but I have no idea why. I have a song with like 6 Mariana Bass which is CPU heavy and it crackles but I haven't lost any settings. Then the one with just Zeeon and sampler is fine.... so, I don't know.
It may be, like you said, if I keep it open while doing other things on the iPad. So maybe close Drambo when not using?
Even if an app is meant to run in the background, iOS can sometimes shut it down. The host should handle that gracefully, but some plugins may not. Moral of the Story? An iPad is not a PC, all bets are off if you leave it sitting around for long periods of time or if you go to other programs that may need those resources (especially memory). Saving your work before doing other things or leaving an iOS device running is the only defense.
Drambo has Settings - Background Audio, and there are timeout options. If you haven't checked those it's worth doing.
BUT. That is no guarantee an app won't be unloaded. Just visiting a large, web page that needs lots of memory can be enough.
@number37 Yep. I fully agree to all points. Safari is the memory eating bad guy on an iPadOS that in fact is an unnecessarily restrictive iPhoneOS. And while it unloads tabs' content at will, it doesn't seem to free the respective memory to the extent one would expect.
Might be worth a try to disable background audio.
I'll try that. Thanks