Why are system AUv3s disabled by default?
The system AUv3s provide convenient capabilities (graphical peak limiting, parametric/band EQ, etc) beyond Drambo's built-in modules. But it's now necessary to enable a setting to show them in the browser/search, and I didn't catch why.
Are system AUv3s disabled by default in order to avoid potential performance/stability issues, to keep the AUv3 list looking tidy, or some other reason?
Comments
I think it is about the tidy list. You wouldn’t believe it, but there were grumpy users in the past who found the app horrible to use because you had to scroll past these system AUv3 every time.
Apparently some users didn't want them to be at the top of the list or some other weird excuses?!
They were also a bit shaky under older iPadOS versions...
The Apple AUv3's became somewhat stable under iPadOS17 and under iPadOS18 I've had no issues all with them.
I did ask for the option. At the time I thought that if it could be done then great for the tidy list, but if not then it wasn't a big deal. If it goes away because it's a nuisance to others it wouldn't be a big loss really.
Apple created its own labyrinth again and didn’t do its homework.
apple AUs on iOS are not compatible with apple AUs on Mac … 😱
means if you create drambo projects with apple AUs your projects are not crossplatform compatible anymore …(won’t work on Mac or the other way around)
Apple really fucked this up. 🤦🏻♂️
it could have been nice … if it just works. But no it doesn’t. Let’s better hide that for now. 😕
(the apple AUs are nice utilities and they cost zero cpu, but as long as they dont work on both platforms (Mac and iPad) ,just like that, its a no go 🤕)
this is one of drambos best features
I can continue to work on my projects and it doesn't really matter what computer I have at hand. 😍
get your ass up, apple, and fix your own APPLE AU plugins to your new standard that is crossplatform.
If beepstreet can do it, apple can do it too. 😫