"Acid Pro 10.0 has stopped working"

Torrey-Zimmerman wrote on 11/21/2020, 2:03 PM

When I first launch Acid Pro 10, I typically receive an error screen. It contains the following information:

Extra Information
   File:                C:\Users\torre\AppData\Local\MAGIX\ACID Pro\10.0\dx_grovel_x64.log
   File:                C:\Users\torre\Documents\ACID Pro Projects\LBP_EPOSODES-ACID PRO\LBPodcast_Episode4_112220_Happy Holidays.acd-bak

Problem Description
   Application Name:    ACID Pro 10.0
   Application Version: Version 10.0.4 (Build 29)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\ACID\ACID Pro 10.0\sfvstwrap.dll
   Fault Address:       0x000000000CC63C1D
   Fault Offset:        0x0000000000203C1D

Fault Process Details
   Process Path:        C:\Program Files\ACID\ACID Pro 10.0\acidpro.exe
   Process Version:     Version 10.0.4 (Build 29)
   Process Description: ACID Pro 10.0
   Process Image Date:  2020-10-29 (Thu Oct 29) 16:00:18

 

After I clear the error screen and attempt to re-launch Acid Pro, the application will launch. But it does so with a blank project--not the last one I had open.

Is there a fix for this? Any assistance you can provide will be very much appreciated!

Comments

AmanSingh wrote on 11/21/2020, 5:45 PM

When I first launch Acid Pro 10, I typically receive an error screen. It contains the following information:

Extra Information
   File:                C:\Users\torre\AppData\Local\MAGIX\ACID Pro\10.0\dx_grovel_x64.log
   File:                C:\Users\torre\Documents\ACID Pro Projects\LBP_EPOSODES-ACID PRO\LBPodcast_Episode4_112220_Happy Holidays.acd-bak

Problem Description
   Application Name:    ACID Pro 10.0
   Application Version: Version 10.0.4 (Build 29)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\ACID\ACID Pro 10.0\sfvstwrap.dll
   Fault Address:       0x000000000CC63C1D
   Fault Offset:        0x0000000000203C1D

Fault Process Details
   Process Path:        C:\Program Files\ACID\ACID Pro 10.0\acidpro.exe
   Process Version:     Version 10.0.4 (Build 29)
   Process Description: ACID Pro 10.0
   Process Image Date:  2020-10-29 (Thu Oct 29) 16:00:18

 

After I clear the error screen and attempt to re-launch Acid Pro, the application will launch. But it does so with a blank project--not the last one I had open.

Is there a fix for this? Any assistance you can provide will be very much appreciated!

It could be that there is a plugin you are using in that project that Acid is conflicting with. When you are opening the project, Acid plays along but as soon as the part comes when the plugin is being used, Acid gives up. At least that is my guess. I too have a lot of 3rd party plugins which Acid comes un-glued with. In my case, I actually have turned off "open last project" in preference so it will at least open without these crash errors.

Edit: Once the project is re-openend, remove any major 3rd party plugins. If this is the case. If the plugin or a synth is not the culprit here, I am not sure. The only reason I think its a 3rd party plugin or synth is because in the error, I see "sfvstwrap". Just my guess. I hope it helps.

Torrey-Zimmerman wrote on 11/22/2020, 9:13 AM

Thanks so much for your help. I was able to trouble-shoot some of the plugins. And ultimately, I needed to Scan/Force rebuild the plugins, via the plugin manager. Now, Acid Pro seems to launch without error. I really appreciate your time!!!

AmanSingh wrote on 11/22/2020, 10:30 AM

Thanks so much for your help. I was able to trouble-shoot some of the plugins. And ultimately, I needed to Scan/Force rebuild the plugins, via the plugin manager. Now, Acid Pro seems to launch without error. I really appreciate your time!!!

Glad to hear. Acid Pro is great if it works! Have fun

LooneyBinJim wrote on 11/25/2020, 1:52 PM

Omg it works?

What were the plugins you removed ?did you add any back?if so can you share it would be cool...

Stephen-Hutchinson wrote on 11/28/2020, 12:09 PM

Since installing the latest update a few weeks ago, I can't open any projects made in ACID Pro 10 by double-clicking on the "acd.zip" file. Today I have dedicated some time to figure out why this is the case and having read this thread, I tried doing this "Scan/Force rebuild the plugins" suggestion, but to no avail. I just get the "ACID Pro 10.0 has stopped working" message over and over again. I get that message a lot when working with projects, and none of the updates have been of any help with the still constant random crashing of ACID while working in the middle of a project. After reading some other suggestions I have now tried opening the ACID 10 project in ACID Pro 9, but it's not compatible.

As a last ditch resort, I opened up ACID PRO 10 empty and then did File > Open and tried to load my project... that at least has worked but the program will still crash during working mid-project.

So at this point, after having tried several reboots, and seeing if that will fix the constant crashing, I've decided that upgrading to ACID Pro 10 was a huge mistake. So was 9.0 and 8.0 The last version that actually worked was 7.0 (which I still have a copy of thankfully.. but can't open newer projects with).

I am now faced with the daunting task of having to try and export all the individual tracks from each of my ACID 10 project files (Render As > Save each track as a separate file) and bring them into Ableton Live Suite. I tried Ableton Live Lite for a month and was so impressed at how much more modern and crash free it was (on both PC and Mac) that I bought the full Ableton Live Suite.

I've used ACID Pro since ACID Music came out in 1999/2000. This is it for me. 20 years later, I'm done with ACID as a DAW. I've created hundreds of projects over the last couple decades and little by little I'll have to port over the tracks from each of the best mixes I've created, and note the plugins used. It is going to be a difficult journey, but constantly paying for upgrades for a software in hopes that the crashing will be fixed is just a pipe dream. It is such a pain in the ass to use that it is no longer a viable avenue of music creation. I just hope I can salvage the work I've already done in ACID, export all my tracks out, and be done with the current iteration of ACID for good.

AmanSingh wrote on 11/28/2020, 5:44 PM

Since installing the latest update a few weeks ago, I can't open any projects made in ACID Pro 10 by double-clicking on the "acd.zip" file. Today I have dedicated some time to figure out why this is the case and having read this thread, I tried doing this "Scan/Force rebuild the plugins" suggestion, but to no avail. I just get the "ACID Pro 10.0 has stopped working" message over and over again. I get that message a lot when working with projects, and none of the updates have been of any help with the still constant random crashing of ACID while working in the middle of a project. After reading some other suggestions I have now tried opening the ACID 10 project in ACID Pro 9, but it's not compatible.

As a last ditch resort, I opened up ACID PRO 10 empty and then did File > Open and tried to load my project... that at least has worked but the program will still crash during working mid-project.

So at this point, after having tried several reboots, and seeing if that will fix the constant crashing, I've decided that upgrading to ACID Pro 10 was a huge mistake. So was 9.0 and 8.0 The last version that actually worked was 7.0 (which I still have a copy of thankfully.. but can't open newer projects with).

I am now faced with the daunting task of having to try and export all the individual tracks from each of my ACID 10 project files (Render As > Save each track as a separate file) and bring them into Ableton Live Suite. I tried Ableton Live Lite for a month and was so impressed at how much more modern and crash free it was (on both PC and Mac) that I bought the full Ableton Live Suite.

I've used ACID Pro since ACID Music came out in 1999/2000. This is it for me. 20 years later, I'm done with ACID as a DAW. I've created hundreds of projects over the last couple decades and little by little I'll have to port over the tracks from each of the best mixes I've created, and note the plugins used. It is going to be a difficult journey, but constantly paying for upgrades for a software in hopes that the crashing will be fixed is just a pipe dream. It is such a pain in the ass to use that it is no longer a viable avenue of music creation. I just hope I can salvage the work I've already done in ACID, export all my tracks out, and be done with the current iteration of ACID for good.

I understand your frustration, stephen. I left Acidpro back in 2007 due to sony ruining it. Came back to it after version 8 came out, again, went back to ableton as the dark GUI ruined it. kept upgrading all the way to version 10, still full of bugs but at least they added a better (not same as ver 7) GUI so I could start seeing the loops I am working with. Full of freezes, crashes, Mp3 not working, this and that, I didn't give up this time. Magix doesn't really help, they just come up with the next upgrade and want more money.

However, I think most of us here in forums are those long term acid pro users who are extremely frustrated that acid pro came back to life but the only positive change it came back with, was going from 32bit 64bit but also came with a lot of bugs either un-fixed from previous life or just got added on due to all the unnecessary bells and whistles. Anyway, it is what it is.

My question is this, when you were having all of these problems, did you do a clean un-install of acid pro 10 and re-installed it to see if stopped crashing? In my case, that was the solution alongside adding exceptions in windows defender. acid pro has minimal crashes now but "render as" is still buggy. and mind you, this was mostly from my own troubleshooting as Acid pro is my choice of DAW for over 20 years. There was absolutely zero help from Magix in any of my issues.

Torrey-Zimmerman wrote on 1/13/2021, 3:40 PM

So far, I haven't heard back from MAGIX. And I'm hearing that others have been disappointed by the lack of support they've received from the company.

Since force-rebuilding my effects, and experiencing some short-term success, Acid 10 Pro has begun freezing and crashing again. I never thought about the possible interaction between Acid and Windows Defender. I'll have to explore that a bit more. AmanSingh, can you share any more information about the exceptions you put in place to get Acid and Defender playing nice?

AmanSingh wrote on 1/13/2021, 5:07 PM

Hi Torrey, I am sorry to hear that you are still having problems. About the Win defender, I still think that Acid has something to do with it but about the exceptions, I am sorry to say, that failed as well. Meaning adding exceptions did not work. I went in circles with that, win defender would remove the exceptions in the next startup. So its really hard to tell where exactly is the problem.

So, about the effects, I would highly recommend NOT to use any new Magix effects in your projects. Do not use side-chaining as that is buggy (confirmed by other users). About magix not replying, I am one of the few lucky ones who they did reply to. According to Magix, acid pro's bugs will be worked on in January 2021 so that should be Now. In my case, I don't have crashes anymore mainly due to not using the following: Morph pads, Magix effects, Midi stuff and MP3 files. I use acid pro strictly for audio and for it's simple layout. Later mix the songs in Studio One as I ended up buying that as I needed side-chaining.

Acid is a great tool, just hang in there and lets all hope the bug-fixes are coming soon.

Kip-Johnson wrote on 1/23/2021, 1:03 AM

This is well know bug that will never be fixed. It has to do with the time it takes to load a large project with lots of plugins to load. Its a timing issue where if you load the project by double clicking the project file it try's to load or scan all the plugins in a certain amount of time before the ACID software gets loaded. It blows up on the ACID initialization process while loading the software while scanning the plugins. It probably has to do with the new code the programmers added to run the VST loader concurrently (asynchronous) while loading the ACID software. If you load the ACID software first then open your project after ACID loads first it won't blow up.