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
WHYYYY????????
Things have been fine, using Drambo here and there. Yesterday made a cool start to a song, just a great flow. Thinking "I love this!" This could be my main setup. then today--- AUv3 fx Koala FX reset, and Zeeon reset. The error message reset to init, as I explained above. I turned off background audio like suggested. It sounds like only a few people experience this and I have no idea why it happens to me. There has to be a solution! The feeling of not being able to depend on a tool just really sucks as a musician.
i Made sure to save it. And printed the tracks luckily. Just odd that others don’t have the same issue or can’t reproduce it.
should I delete and redownload the app. ?Wondering what specific thing about my iPad , settings, or whatever is causing this.
the only thing i can think of is if leaving the app open and the iPad cover off somehow messes it up. thanks so much for thinking it through. hoping to figure it out!
Not sure if this makes any sense, but going to the "hamburger"/menu >Open> (choose song) doesn't work. The AUv3 issue remains. But going to the "hamburger"/menu > Files>Documents> (choose song) does work. Everything resets to the correct parameters and works fine then.
Opening from documents worked for me and recovered what I thought were lost Zeeon instruments. Definitely guilty of switching over to safari with Drambo in background (doing it right now). So I’ll be mindful of that and try turning off background audio.
Just came to post what you just recently figured out.For me, occasionally my TB Equalizer Pros crap out immediately upon opening a project. Thankfully simply reloading the project has always reloaded properly with my saved eq curves.
I also often had the same issues with Auv3s in the past and I think it was always due to leaving Drambo running in the background and coming back to the project later. What I then started doing was to always save the project and then load some factory project template (usually the default 8 track with MIDI to CV) when I was done for the day. I would usually also close Drambo completely. When I wanted to work on it again I was then forced to open the project from the documents. It seems that, as you guys also mentioned, that is the uncorrupted project version, whereas the auto-saved one can get the Auv3 states corrupted. Koala sampler inside Drambo ‘errored’ for me very often and I lost everything that was in there so later when I applied this above-mentioned workaround I also made sure to save a project inside the Koala Auv3 too before exiting. It was cumbersome but it seemed to work.
I think that Drambo running in the background and having those Auv3s loaded is the most likely issue. I never really tried to intentionally recreate the issue for a proper bug report however due to frustration 😅 I also dont’t think it’s quite easy to recreate it since it seems to occur while not using the app.
Yesterday, after I wrote the post above, I intentionally tried to recreate the issue and it seems I did it. Will test it some more though.
Here are the steps:
This was done on an iPhone 11, running iOS 18.7.1, running v 2.48 (6) of Drambo.
I'll try to test some more.
I used to get that problem with drambo, and it was always after leaving drambo. So as per @giku suggestion I disabled background entirely, and since then I never had that problem again. So if you don’t need drambo to run in background maybe try that and see if it helps
'Background audio' in settings, if that is what you were referring to, was already set to 'OFF'.
Did another test right after my last post. This time I did it a bit differently.
This confirms that the issue is with the auto-saved state of the project and not the project which was manually saved.
Thanks for reporting, I'm on this.
Thank you for looking into it!
Thank you for looking into it!
I noticed the following issue causing errors in apps.
I've been streaming on my iPad for quite some time now, using an external mirrorless camera. I connect it through a hub or directly to the iPad via USB-C.
Occasionally, something happens and AUV3 apps won't load, displaying an error.
Restarting Drambo doesn't help. A full iPad restart is the only solution.
What could be causing this issue, and why does it affect AUV3 apps?