Autotune won't show up in my plugin List. Please help

Replies to This Discussion

Permalink Reply by mnml_music on January 25, 2010 at 11:08am

Try switching your iLok key to a different USB port and make sure you have the latest driver installed: http://www.ilok.com/download-ilok-software.html

Also make sure you are installing the correct version of Auto Tune. For instance, if you have Auto Tune 5 and have Auto Tune Evo installed, then you'll have issues with the licensing.

You can download the proper version from here: http://www.antarestech.com/download/update.shtml

• ▶ Reply

Permalink Reply by Anson Dawkins on February 5, 2010 at 9:14am

Having the same problem... yesterday got a message

validating Audio Unit Auto-Tune Evo by Antares: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * AU Validation Tool Version: 1.2.3a1 Copyright 2003-2007, Apple, Inc. All Rights Reserved. Specify -h (-help) for command options * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * -------------------------------------------------- VALIDATING AUDIO UNIT: 'aumf' - 'ATxE' - 'VST ' -------------------------------------------------- ERROR: Cannot get Component's Name strings ERROR: Error from retrieving Component Version: 4294967246 * * FAIL -------------------------------------------------- TESTING OPEN TIMES: FATAL ERROR: didn't find the component validation result: couldn't be opened updating properties of AU Auto-Tune Evo by Antares...FAILED! FAILED!


I have tried several things, update ilok driver, update auto tune, try different usb, to no avail. Should i buy new ilok?

• ▶ Reply

Permalink Reply by Anson Dawkins on February 5, 2010 at 9:15am

Did you find a solution?

• ▶ Reply

Permalink Reply by Jeff Andrews on April 27, 2010 at 3:16pm

I have essentially the same problem with Evo Duo. Installation and iLok registration went fine. I see the plug-in's DLL file in the right folder (c:\VST on a PC). I'm using Sonar 8.5 and Windows 7 64-bit. I've checked for the plug-in in both the FX list and the Soft Synth list, but it never shows anywhere. I've uninstalled & reinstalled - no difference. I've rescanned VST plug-ins many times and have also set it to rescan failed plug-ins. There's never any indication anything is wrong other than it just never shows up at all. I'm not new at this and have loads of other VST plug-ins which all work fine. What else can we do in this situation?

Regards,

Jeff Andrews
Chrome City Studios / FX Models

• ▶ Reply

Permalink Reply by Art Flanagan on April 27, 2010 at 3:34pm

Both of you issues seem to be different. Anson is definitely having an authorization problem which is probably due to a driver not being installed or not having the iLok key plugged in.

Your issue is due to Sonar not scanning the plug-in. Check Sonar's configuration to make sure (double check) it is looking in the correct directory. If you're certain it's looking in the right directory, try creating a new directory and moving the DUO .dll file to the new directory. Add the new directory in Sonar and have it rescan. See how that works for you.

There shouldn't be a reason to keep reinstalling the software. There is only one file that gets installed when installing DUO, and that is the .dll file. Other than that you're only installing the iLok driver again, which is unnecessary based on your description.

• ▶ Reply

Permalink Reply by Jeff Andrews on April 27, 2010 at 3:39pm

Hi Art. Thanks for the very quick reply. Since all of my VST's are in the same "C:\VST" folder (except a couple in the "C:\VST64" folder when Native-Instruments stipulated that they wanted a place for native 64-bit plug-ins), I'm pretty darn sure Sonar knows about that folder. Actually, I'm certain it knows about both those folders since they are the only ones in its list. However, I will perform the steps you outlined to put the DLL in yet another altogether different folder. I'll let you know how I fare. Of course, it shouldn't be necessary (that's the software developer in me speaking), but I'll be happy to find any work-around at this point. Thanks again.

• ▶ Reply

Permalink Reply by Art Flanagan on April 27, 2010 at 3:52pm

Yeah, it shouldn't matter logically (I agree) but it's just a trouble shooting idea. Sonar also has an option for blocking plug-ins. Make sure to check that list to make sure that DUO isn't blocked.

This can happen when Sonar scans the plug-in the first time and for one reason or another (usually the iLok not being plugged in) the plug-in gets placed on this list. There really isn't much else to it so hopefully one of these suggestions will help solve the problem.

• ▶ Reply

Permalink Reply by Jeff Andrews on April 27, 2010 at 4:30pm

Hi Art. Well, your work-around works very well - thank you very much. I don't know why, but Sonar sees the AVOX DUO plug-in just fine now that I put it in a folder all on its lonesome (C:\VST_Test). Guess it doesn't play well with others. Just kidding. But the one in the C:\VST folder doesn't get the time of day whereas copying it elsewhere works fine. As far as blocked plug-ins, that's why I've had Sonar set to rescan failed plug-ins, but it hasn't helped any. I need something more like rescan ignored plug-ins.

The bottom line is I get to use Duo now, so thanks a lot, Art. And eewwww does it sound weird on drums. :)

• ▶ Reply

Permalink Reply by Art Flanagan on April 27, 2010 at 4:46pm

Glad it works!

Hah. Yeah, drums have pitch, but are too punchy too offer any sustained variation. If you're trying to get DUO to work on drums, I would turn the Pitch Variation & Vocal Timbre to '0' so that the only thing being affected is the timing of the drums. This might be a cool effect to add some naturalization to sequenced drums.

• ▶ Reply