Every time I try to start the Acid Pro 10 audio daw that I have recently purchased I keep getting this error message, when I click on OK the program shuts down:
ACID Pro
Version 10.0.4 (Build 29) 64-bit
Exception 0xC0000005 (access violation) READ:0x0000000000000000 IP:0x0000000008923C15
In Module 'sfvstwrap.dll' at Address 0x0000000008720000 + 0x0000000000203C15
Thread: GUI ID=0x23D4 Stack=
does anyone know how to resolve this
thanks
graeme
graeme-mchugh, unfortunately, AP is still full of glitches and bugs. But there are plugins that acidpro is most probably having trouble with as most likely this is happening at vst scan. Try the following methods:
First method which has always worked for me, un-install acid pro completely. use revo-uninstaller (free version) and do a deep scan to remove all magix files from PC and then do a clean Re-install.
If that doesn't work, Go to
C:\Users\User\AppData\Local\MAGIX\ACID Pro\10
Locate this file:
acidpro_bridgeaware_plugincache_x64.xml
Delete that file. Upon next startup, Acid should reset the scan. If you are able to get into Acid, do a force rescan of vst plugins in plugin explorer.
Good Luck
Hi AmanSingh
I did notice that it was happening when I was trying to load in a saved project... When I begin a completely new project from scratch I was able to use the software. When I went to save the new project as another take of the previous project in the same folder I saw that there were quite a few temp folders created... I deleted these but haven't tried to open the new saved file yet... so it may well still work but if it doesn't then I'll give your suggestion a try
thanks for your help
Hi AmanSingh
I followed your instructions and managed to get the program working, however whenever I try to start a saved project I have to keep deleting this "acidpro_bridgeaware_plugincache_x64.xml" file before each start up, and that included the rescan of the plugins in plugin explorer. Any idea if there is a further fix for this?
Graeme, I am unclear on a few things. First of all, did you try to un-install/re-install as the first method first? Secondly, is this happening with any project you start/save and then re-open and it gives you problems? If so, there is definitely a plugin that is being the problem here. Can you list the 3rd party plugins being used with AcidPro?
Do another thing, start a project, but don't use ANY 3rd party plugins, then save. close ap10, and re-open, see if it gives you problems then. If all goes well, we will have to target your 3rd party plugins and find which one is conflicting with AP10.
Hi AmanSingh
Sorry for taking long to reply to you as I was working on an acid project and wanted to get a bit done on it before uninstalling and reinstalling the software... I have just done this but it seems to not have made any difference to the problem that I am having... I think it may be one of the plugins that may be causing the problem but which one I'm not sure... The plugins I have installed and using with Acid Pro 10 are: Superior Drummer 3, EZ drummer 2, EZbass and Guitar Rigg 5...
I need these plugins to work with Acid as it is the only Daw I have on this laptop and for some reason Superior drummer 3 wont save my work as a wave file in stand alone mode... I can use Acid Pro 10 as long as I delete the "acidpro_bridgeaware_plugincache_x64.xml" file before each session.... How do I start a project, but not use ANY 3rd party plugins?
I can use Acid Pro 10 as long as I delete the "acidpro_bridgeaware_plugincache_x64.xml" file before each session.... How do I start a project, but not use ANY 3rd party plugins?
Hello Graeme, you can go into plugin manager and remove the folders which contain those 3rd party plugins. Now, before you do any of that, since I don't own these plugins or know enough about them, are these 32bit format? Do you know? If so, there is a VSTwrapper available called jBridge. You might want to get that and see if that fixes this issue. You will have to look at the instructions on how to bring 32bit plugins into a 64 bit DAW. I am only going this route as I know very little about excatly whats going on other than I am now sure that it is happening due to your plugins. Sorry, I am not being much help. I hope someone else is reading our thread and might have a better solution.