#CAN YOU USE UAD PLUGINS WITHOUT APOLLO DRIVERS#
Or on Windows there are even more variables, like video drivers and such. A change in hardware, OS, Mixbus version or plugin version can be the difference between working and not. Just because a plugin works on my system does not guarantee that it will work on yours. I'm not knocking the plugins, just pointing out that this is much harder than you probably think. Googling for " crashes" returns lots of results, and we aren't even in the top page. Regarding the other plugins you listed, I feel very confident that our support for those plugins is as good as other DAWs.
I'm sure we will get it sorted eventually.
#CAN YOU USE UAD PLUGINS WITHOUT APOLLO SOFTWARE#
I've started a discussion and exchanged software with them. We currently have a repeatable problem with SoundToys. And at the moment, no plugin manufacturers have spotted anything wrong in our implementation. In this respect we are FAR more open than any other host. Furthermore, our plugin-loading code is open-source and can be reviewed by any interested plugin developer. A few months ago, we were able to recognize and resolve some issues with the VST version of Plugin Alliance and other plugins. It's not my are always willing to fix Mixbus if it becomes clear that we are not following the spec. don't force me to find solutions for issues by contacting UA, Softube etc for the graphic glitch problem. CLEAR THINGS.ĭon't get me wrong, I have been and still I am a good supporter of mixbus because I like so much this daw and I recognise all the great job you have done and all the new goodies of 3.1. This already worked for VST versions of the plugins, so nothing was changed for those. Perhaps something like: "Mixbus 3.1 is not compatible with bla, blah blah 3nd party plugins". Re: UAD Apollo Twin & Plug Ins for FL Studio 20 Windows (PDC Issues) FL 20.5 fixes a problem when using the AudioUnit version of the UAD plugins in macOS: they wouldnt properly report their latency when the sample rate changed or when you rendered a project. I understand that there are surely serious technical reasons for these kind of issues but I would expect from Harrison's team a better statement. In my opinion this job is not to be done from the client.
Then, except UA, we have to contact Soundtoys, Softube, Plugin Alliance etc.
You will be best served by contacting UAD, I think. Even if it is our fault, we have no idea how UAD makes their plugin windows, or what libraries they use, or what might cause a "slowdown". Unfortunately we have very limited ability to troubleshoot a problem like that. (02-19-2016, 11:39 Wrote: Are you showing all the GUI windows, when this happens, or just one GUI?