![]() ![]() Some of the customer workers are uneducated as well, which creates misunderstandings. ![]() Getting a reply back takes multiple working days, and all replies that are tech-related are totally unhelpful. Also, using Melodyne I can have a session full of Melodyne instances without it affecting my CPU noticeably.įourthly, Antares customer support is just dreadful. I also really feel like the graph mode on Auto-tune Pro X shouldn’t be a CPU-heavy process, since it’s working with audio that’s been recorded into the plugin, and not doing real-time edits. To make this error dialog appear on the same buffer size without using Auto-tune Pro X, I usually have to have something like a 100 track session using multiple CPU-heavy plugins on multiple of the tracks (like soothe and IR-reverbs). In Pro Tools, I can get the audio processing error window using one instance of Auto-Tune Pro X doing some gentle stretching and tuning in graph mode, on maximum buffer size. Thirdly, the CPU-handling of that thing is awful. Those two plugins do the same thing, so the difference definitely shouldn’t be that big. It’s painful to use Auto-Tune Pro X’s graph mode alongside Melodyne, since the latter is extremely smooth working in, while Pro X’s graph mode is just a laggy mess. I’m using a basically maxed out MacBook Pro that handles all other plugins with minimal effort, including very CPU-heavy ones. ![]() Most stuff in graph mode, like creating notes, stretching audio and dragging all of the knobs are processes that are very laggy, and it looks like you're using the software with an extremely low FPS value on your screen. It seems like the glitches depend on where you start playing from, and that is definitely something that the playback isn't supposed to be dependent of. Not like detected an octave down, but actually played out an octave down, which is super annoying and happens not to rarely. Also, at random times you don't only get glitches, but also that a note is played out an octave down. I understand that bugs may appear in a plugin, but a bug this big is unnacceptable, let alone the fact that it took months for Antares to fix this bug.Īlso, another major bug is that the playback isn't consistant, so that AT gives off weird glitches when pressing play sometimes, but the next second the same part can be played completely free of glitches. 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. Okay, this will be a long post, but I am just so frustrated. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |