Hi all, I have yet to hear from Sony technical support so I'm hoping someone here may had a similar experience to help solve my problem. I upgraded to Acid Pro 7a. In the Plugin Manager I set the Add path to C: thinking that it would load only the plugins on my harddrive that I have in various folders. It was a bad thing to do. Acid cannot tell the difference between vst.dlls and system.dlls. When I launch the application it attempts to load every.dll on the computer. After many minutes it locks up and the cell windows never load.
Then I kill the process in the Task Manager to get back to the desktop. The hidieous thing about this is that some of the system.dlls activate and strange things happen like icons being deleted off the desktop. My error turned this program into malware. Re-installing Acid does not solve this problem. I have spent much time looking through the registry for starup information to alter but no success.
So that is my thinking at the moment - to find where the startup config is stored on the computer so that I can reset the program to it's startup defaults. Reformating and re-installing Windows is not an option. I'm using WinXP Pro Service Pack 3. The only way to determine whether a dll is a VST plug-in is to load it. This is a limitation of the VST technology.
Jun 06, 2011 VST plugins are generally run within a Digital Audio Workstation (like Sony Acid Pro; Audcacity; Cubase; etc.), providing the host application with additional functionality. Most VST plugins can be classified as either instruments (VSTi) or effects, although other categories exist.
You should definitely not scan your entire system for VSTs. By default ACID looks at a registry entry HKEYLOCALMACHINE SOFTWARE VST for the default VST search path. This registry entry is defined byt the VST SDK. If this key does not exist, then ACID defaults to C: Program Files VSTPlugins To correct your problem: 1. Locate the following directory on your system: C: Documents and Settings Local Settings Application Data Sony ACID Pro 7.0 3. Delete the file acidpro.plugincache.xml 4. This will force ACID to rescan the default directory paths.
You can then manually add additional directories where you believe plug-ins are installed. Avoid large search paths like c: Program Files as any number of dll's that are scanned can cause the problems you experianced. We are looking at solutions to prevent this from happening, but there is only so much that can be done given the way VST enumeration works. Yeah, My bad assuming Acid would know the difference between vst and system.dlls. Believe me, I wish we could.
We do have an interal 'don't ever scan this file' list, but it could never be made 100% complete. We are looking for a solution to prevent - even if it is just a warning - the use of large search paths like C:, C: Windows, C: Program Files. Out of curiousity, does the Acid.exe have any old school type command line switches? Nothing that would be useful to end users. Is there something you are interested in?