Subject:Acid "Pro" 5c

Posted by: jasonjbundy

Date:12/10/2005 4:38:14 PM

Hello-

For several weeks, I have been having great difficulty with Acid Pro 5 when it scans for my VST's. I even updated my Pluggo product yesterday (this was having Acid problems in the previous version).

Acid is now crashing my ENTIRE system when I go to launch it rather than it just disappearing as before.

The tech support that emailed me to solve my problem was weak.

Ableton Live 5 can read all of my VST's, Sonar 4PE can read all of my VST's, FL Studio 5 can read all of my VST's, and Sound Forge 8 can read all of my VST FX with absolutely no problems.

Why Acid?

I want answers and a proper fix for this "PRO" product not some band-aid workaround, as these are currently the typical solutions from software manufacturers.

-Jason

Subject:RE: Acid "Pro" 5c

Reply by: pwppch

Date:12/10/2005 4:50:23 PM

Are you saying that you get a blue screen and complete reset of Windows when you launch ACID?

If so, this is not a VSTi problem, but a hardware problem. ACID cannot crash you out of Windows like this. Only hardware drivers or services can do this in Windows.

What did tech support suggest you try? I don't want to repeat what you have already tried.

Peter

Subject:RE: Acid "Pro" 5c

Reply by: jasonjbundy

Date:12/10/2005 6:07:42 PM

No blue screen. Acid causes a complete system reboot. It also caused a system handle error that kept cycling at start up and kept me out of Windows.

What hardware problem??? EVERYTHING is operating correctly as I checked statuses. All paths lead straight back to Acid.

Tech support suggested I rename my plugin folder. Which I did and it was a complete waste of time/effort (why should I anyways if everything else is working as it should???). They suggested I run a VST program that scans their properties, etc. Did that and found that Pluggo was maybe causing the problems. Downloaded their update yesterday.

But the kicker is that the rest of my DAW's are running smoothly and it is only Acid that has issues. ALSO, Acid was running just fine before and now it is not.

I had just a few issues with Ableton's VST scan because of the time change in October, but LIVE has been running like a champ since.

Jason

Subject:RE: Acid "Pro" 5c

Reply by: pwppch

Date:12/11/2005 1:23:24 AM

Didn't mean to offend you. Just trying to help as I am sure tech support was also. I am sorry that they couldn't help you .

I wont say any more, since you seem to know what you are doing and are sure of what the problem is.

I hope you get it sorted out. If you change your mind and want to work with me to help determine what the problems is, don't hesistate to ping me here.

Regards,
Peter

Subject:RE: Acid "Pro" 5c

Reply by: jasonjbundy

Date:12/11/2005 7:14:08 AM

Peter-

No offense taken.

I would really like some help but I do not have the time to sit around and introduce the hundreds of VST's I own (which work everywhere else) into Acid to pinpoint the ones that crash my system.

Since I am not a coder or software engineer, I did find a quick easy solution: removed all of Acid Pro 5 from my system.

Life is easier now.

Jason

Subject:RE: Acid "Pro" 5c

Reply by: JohnnyRoy

Date:12/11/2005 8:21:43 AM

> I would really like some help but I do not have the time to sit around and introduce the hundreds of VST's I own (which work everywhere else) into Acid to pinpoint the ones that crash my system.

Actually, it’s not that difficult. What you do is rename your vstplugins folder and start ACID to be sure that it is one of the VST’s giving you trouble. Then create a new Vstplugins folder and move half of the plug-ins back. So if you have 200 plug-ins, you move 100 back. If ACID works, that 100 is fine. Move them into a 3rd folder (for safe keeping) and move half of them again from your original folder into the plug-ins folder. Now you only have 50 to check out of 200. If these are OK you do the same thing with 25 from the original folder. If not, you remove half of the 50 in the new folder and see if that fixes it. If it does the bad plug-in is in the 25 you removed. If it doesn’t work the bad plug-in is in the 25 that remain.

You see, by working in halves (known as a binary search) you have narrowed 200 plug-ins down to the 25 that might be causing the problem in just 3 tests. That doesn’t take very long at all. Using the binary search method you can find a bad plug-in out of 200 in a maximum of 7 tests.

~jr

Subject:RE: Acid "Pro" 5c

Reply by: Illogical

Date:12/22/2005 10:45:59 AM

Yeah, but if you move Vst's that needed to be installed (rather than ones you can just paste into the folder), they get all screwy. Or at least that's been my experience...

Subject:RE: Acid "Pro" 5c

Reply by: Spectralis

Date:12/24/2005 3:38:04 AM

I think the VST implimentation has to improve. I would like the ability to troubleshoot plugins in ACID. If ACID could identify a plugin causing trouble and exclude it so that ACID will load then that would be a start.

ACID 6 will be here soon (I hope) so maybe things will improve.