Releasing a version where you haven’t tested it enough to discover a bug this bad is just extremely disrespectful as a company. For example, it had a major bug where all of your edits would go lost upon reopening a project after closing it, as well as deactivating a track with an AT Pro X instance on it. Hence, I want to inform speculators of AT Pro X before making a decision on buying or not, and I also want to hear about others experiences of Antares.įirstly, the graph mode (which ”improved functionality” was one of the new Pro X’s main selling points) is just covered in different sorts of bugs. Having used it since november, my conclusion is that Auto-tune Pro X is the worst plugin I’ve ever purchased, and Antares is the worst company I’ve ever come across.
When forcing Logic into Rosetta mode it works as it did before the update to V10.0, but this kinda defeats the whole purpose of all plugins and Console being M1 native now.Okay, this will be a long post, but I am just so frustrated. The DSP load does not exceed the limits and the plugin is authorized. I tried reinstalling the whole UAD package (clean reinstall), reauthorizing all plugins through the control panel and rescanning all plugins in Logic (after manually deleting the AU cache), but when trying to use AutoTune Advanced as an insert effect it just says "Disabled" in red letters at the bottom. The plugin works just fine when running it as an insert in Console. I'm encountering this issue where after installing UAD V10.0 the AutoTune Realtime Advanced Plugin (the one that is supposed to be M1 native now, not the one with the white and blue interface) stopped working in Logic when running the DAW in the regular native mode (I'm using an M1 Mac with Monterey 12.3.1).
0 kommentar(er)
