Community Forums Archive

Go Back

Subject:Hey What Gives? VSTi Problem w/ AcidPro5
Posted by: ExtraEcho
Date:11/11/2004 2:30:56 AM

First Off lemme say i'm finally happy you all decided to allow acid to act as a rewire slave. you finally have come to your senses. now onto my VSTi problem.

i had installed NI Elektrik Piano Instrument into my VST folder which AcidPro5 saw with no trouble. i started up Acid and checked to make sure that the plugin worked properly before i continued installing all my plugins and instruments (so that if i got a problem i'd know immediately) well i didnt get too far after that cus when i installed Spectrasonics StylusRMX and started up AcidPro5 again and authorized Stylus i no longer had my NI Elektrik piano as an available instrument. it was gone no where to be found. now when i started up VST stack it saw both the NI plugin and the Spectrasonics Plugin. What Gives? it makes no sense to me.

god i hope i aint the only one with this problem. this is why i've used AcidPro2 and refused to update to other versions until now.

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: JohnnyRoy
Date:11/11/2004 6:17:29 AM

Try keeping your VST Instruments and VST Effects in different folders. This is how I have my PC set up and I haven’t had any problems. I have my VST Instruments in C:\Program Files\VstPlugins and my VST Effects in C:\Program Files\Steinberg\VstPlugins. This is because some VST Instruments incorrectly expose themselves as FX when, in fact, they are NOT. This messes up the host program which is only going by what the VST is telling it that its capable of.

All of the Plug-ins are cataloged in the Registry under:

HKEY_CURRENT_USER\Software\Sony Media Software\ACID Pro\5.0\Metrics\VSTi Synth\Plugs

If you delete this entry, it will cause ACID to rescan for plug-ins. That may clear up your problem. I have more detailed instructions on how to do this in the ACID Tips section of my web site.

You must understand that Sony cannot be responsible for VST Instrument vendors that write buggy code. In many cases its not ACID’s fault. This is why Propellerhead Reason is a closed system. They didn’t want 3rd party code messing up their program. I think that’s a ridiculous decision which is why I would never buy Reason or any “closed” system.

~jr

Message last edited on5/7/2005 8:06:56 PM byJohnnyRoy.
Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: DKeenum
Date:11/11/2004 6:28:14 AM

I keep a shotcut to regedit on my desktop. When I add of delete an VSTi it would regularly screw things up.

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: ExtraEcho
Date:11/11/2004 12:59:09 PM

i really do not think that this is a case of VST Instrument Vendors writing buggy code cus i have both plugins running inside of VST stack with no problems. the buggy code is definitely caused by AcidPro5 and the fact that every software company nowadays releases buggy software figuring that they can update it as needed. this is why i've been an Acidpro2 user for such a long time.

i checked the registry and the plugin was there. like i said i can run it inside of other software. my problem is that acid5 doesnt want to see it at all. i'd rather have a solution to this problem instead of a defense of sony and acid and buggy code and who's fault it is. i'm going to try having acid rescan the plugins but i'm afraid that i know exactly how that will turn out although i hope i am wrong.

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: ExtraEcho
Date:11/11/2004 2:32:58 PM

alright this is just stupid. so i tried the registry thing and that worked. i had to reauthorize the NI plugin afterwards but it worked.....temporarily. the next time i started up acid after seeing the plugins there it was gone....again. so i tried everything all over again and ended up with the same result. i then tried seperating my vst and vsti into seperate folders and lo and behold it works. no problems whatsoever. i've never had to seperate vst's and vsti's before into their own seperate folders before. but the problem is solved although the solution is quite stupid.

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: drbam
Date:11/11/2004 4:00:04 PM

No offense, but why do you think its stupid to put instruments in one folder and efx in another? From an organizing perspective, this makes total sense to me . . . ;-)

drbam

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: JohnnyRoy
Date:11/11/2004 7:15:06 PM

> i'd rather have a solution to this problem instead of a defense of sony and acid and buggy code and who's fault it is.

In defense of myself defending Sony, I was careful to say. "In many cases its not ACID’s fault." Which means that in some cases it is ACID’s fault. I was just pointing out that I’ve seen my share of poorly written VSTi’s and so I would not be so quick to point the finger at ACID. I am a software developer myself so perhaps I’m more sensitive to defending other software developers that I know are just trying to implement the VST spec correctly.

I’m glad you got it working. Stupid or not. ;-)

~jr

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: ExtraEcho
Date:11/12/2004 12:00:21 AM

yeah. people never look at a program and say "man the code on this must be amazing!". so your defense is understandable. i just dont like spending a nice chunk of $$$ on something and then encounter problems and wait for an update. if i go buy a car i dont want to be driving it home and find out that the breaks are buggy and dont work properly. yes it's an extreme analogy but it works for me.

Subject:RE: Hey What Gives? VSTi Problem w/ AcidPro5
Reply by: drbam
Date:11/12/2004 6:26:23 AM

>> if i go buy a car i dont want to be driving it home and find out that the breaks are buggy and dont work properly. yes it's an extreme analogy but it works for me.<<

I don't think its an extreme analogy at all because this kind of thing happens a lot. In an attempt to remain competitive, every product manufacturer rushes new technology onto the market before its *fully* tested and thus the consumer is the ultimate beta-tester (definitely a pet peeve of mine).

drbam

Go Back