Community Forums Archive

Go Back

Subject:Failed vst
Posted by: MichaelK
Date:1/23/2010 6:12:02 AM

Hello;

I recently purchased the Symphonic Choirs software. It works well in stand-alone mode, but ACID puts it into the Failed vst folder.

Can you give me any info that may either fix the problem in ACID (if, indeed there IS one) - OR- something I can forward to the vendor's tech support group?

Thanks

Subject:RE: Failed vst
Reply by: pwppch
Date:1/23/2010 10:04:29 AM

In ACID 7.0d, there is a new scan option to force a complete rebuild. Have you tried this?

Also, you can right click on the failed plug-in to force ACID to rescan.

Failed plug-ins are typically caused by the plug-in taking to long to intialize during our start up scan. These alternate methods may solve the problem with the Symphonic Choirs. (We don't have that one in house, so I don't know if there is a specific problem with it and ACID. I would recommend you contact the vendor to see if they are aware of any issues.)

Peter

Subject:RE: Failed vst
Reply by: raskiefilm
Date:1/25/2010 12:10:02 PM

@ MichaelL

Are you trying to run the 32-bit or 64-bit plugin? Be sure to run the 32-bit version (I know that seems obvious to some but I'm stating just in case).

64-bit is just for stand-alone Symphonic Choirs Play.

To confirm, the Symphonic Choirs 32-bit plugin works on Acid for me.

Subject:RE: Failed vst
Reply by: MichaelK
Date:1/26/2010 8:51:06 AM

I'm encouraged that SC works for you, raskiefilm... it gives me hope. I can run Wordbuilder/Symphonic choir as a stand-alone (using the samples, not the WB Choirs) on my Windows XP (32-bit) PC which leads me to believe I have installed the correct vst. However, neither module will open in ACID even after a rescan.

How do you load SC into ACID, and do you also use Wordbuilder?

Thanks!

Subject:RE: Failed vst
Reply by: MichaelK
Date:1/26/2010 11:53:34 AM

Thanks, Peter. I tried the rescan with no success. I also contacted the vendors' support and am awaiting answers from them.

Subject:RE: Failed vst
Reply by: raskiefilm
Date:1/26/2010 12:19:56 PM

@ MichaelK

To clarify, when you say "neither module will open in ACID even after a rescan", does that mean the PLAY module (as you cannot physically see it)?

I load SC as a soft synth. The explorer opens and I select the PLAY VSTi. When that module opens, I select SC and configure accordingly.

I do not use Word Builder that often as I'm still having difficulty loading the WB words/construct to play on my keyboard.

raskiefilm

Subject:RE: Failed vst
Reply by: MichaelK
Date:1/27/2010 4:55:15 AM

Actually, I discovered that I did not have the Play vst in the plug-ins directory. I copied it there and when I tried to Insert Soft Synth from ACID, I received an error dialog box with the message "That product does not exist (productld-1). The vst icon displays with a 'lock' image imposed on it and also appears in the 'ignored' sub-folder.

The vendor (EastWest) replies that ACID is not supported... but they are 'working on it'

Nice.

Also, in an (apparently) unrelated problem, I had trouble with Media Manager after asking it to scan drive C: in hopes of finding/fixing the vst issue.
Now MM hangs on open from within ACID and/or on reinstall. Any suggestions... ?

Subject:RE: Failed vst
Reply by: pwppch
Date:1/27/2010 8:10:10 AM

lso, in an (apparently) unrelated problem, I had trouble with Media Manager after asking it to scan drive C: in hopes of finding/fixing the vst issue.
Now MM hangs on open from within ACID and/or on reinstall. Any suggestions... ?


Scanning the "C" or any root drive will cause all kinds of havoc. You as asking the VST scanning code to look at every dll on your system in the case of your system drive.

Check out these two threads for solutions:

A7P-VST scans

A Pro loading massive .dll files on start up

Peter


Message last edited on1/27/2010 8:10:58 AM bypwppch.
Subject:RE: Failed vst
Reply by: raskiefilm
Date:1/27/2010 8:42:26 AM

@ MichaelK

That is the same response I received from EW. Is your default plug-ins folder named VST? Just curious.

With regards to Media Manager, in my experience, it is a resource hog. My suggestion would be to uninstall it unless you find a lasting benefit to keep it installed.

raskiefilm

Subject:RE: Failed vst
Reply by: MichaelK
Date:1/27/2010 1:19:40 PM

""My suggestion... uninstall it"

Good idea. Done!

Go Back