Have you tried doing a "force Rebuild" from the VST Configuration dialog and rescanning? Make sure you have the proper 64bit plugin paths selected (AP8 will only use 64 bit plugins natively). I am able to scan and use all of my Izotope 64bit plugins.
Please post your question to the dedicated Vegas forum here.
Jeff Forum Moderator
First, it was not a question, it was a comment. Second, the purpose was to point out that Acid Pro is not the only Magix product that seems to have a problem with some Izotope plugins. In my personal opinion, that comment is more relevant here and less relevant in the Vegas forum.
All DAWs have problems with some plugins. And all plugins have problems with some DAWs. I doubt that there are very many exceptions to this.
... in view of what I wrote in the previous sentence, I still believe it is a comment more suited to the Vegas Pro forum.😀😀
Let me rephrase my comment. In my opinion, it would be helpful to both Magix users and Magix developers to be aware of the fact that a given problem affects multiple products. Is there a forum devoted to issues that affect more than one Magix product? If so then, that would be an appropriate place for this comment.
By the way, I have a hypothesis about the problem itself, based on experience with a non-Magix host. It's just a hypothesis at this point. Most (maybe all) Izotope plugins consist of two .DLL files. One is a VST format plugin and the other is not, but must be located in the same directory as the first. My guess is that some DAWs don't know what to do with files that have a .DLL extension but are not VSTs.
Hey guys I definitely found a solution and the problem was it was scanning the 32 bit version of the plugins so mostly I just redirected every 64 bit plugins to program files > Vstplugins and it definitely worked.. thank ya for all your support and appreciation