Anyway I grabbed an event from the Windows application event log which is below for any technical people.įaulting application name: acidnext.exe, version: 1.0.1.24, time stamp: 0x5ce7e4c4įaulting module name: acidnext.exe, version: 1.0.1.24, time stamp: 0x5ce7e4c4įaulting application start time: 0x01d55fec9870a889įaulting application path: D:\Program Files\ACID\ACID Pro Next 1.0\acidnext.exeįaulting module path: D:\Program Files\ACID\ACID Pro Next 1.0\acidnext.exe It just crashes at start up even though I've reinstalled, restarted, asked the cat for advice, but nope.
Acid Pro Next worked a couple of times on my Windows 10 Pro 32Gb box that runs anything else i throw at it. I signed up with 365 to learn music but this is nuts. (Thanks for allowing me to rant a bit :0) Have a soft spot for ACID but almost time for it to go bye bye. especially for someone like myself who works almost exclusively with MIDI, Kontakt, and Composer Cloud Play. I still love Vegas (use it for my audio mixdowns) but Sound Forge is virtually obsolete these days and Cakewalk has proven a reliable, solid, FREE DAW. And I spent a lot of money buying updates once they were released with 64bit architecture. prior to even Sony acquiring from the company Sound Forge. I've worked with the SF trilogy (Sound Forge, Acid, and Vegas) for years. Now I rarely have an issue, I'm just angry at the blatant disrespect Magix has for its paying customers. I NEVER had an issue with the prior build.
willing to send Build 17 install file? It gets saved in Documents folder. You can also add a "DisallowRun" key under currrent user explorer in the registry too.īTW anyone else.
It STILL doesn't fix the issue of ACID not loading all of your VST's and VSTi's but obviously Magix doesn't care about offering a quality build.
you say "good! it's the latest build, what's there to update? A patch to fix this? Stupid stupid idiotic program" and go about working with program.
UpS_updater_ACID_Pro_Next_圆4.exe (at least that's for pro next.)Įvery time you open the program a pop-up will say "important updates are being downloaded" Hit OK, another popup with the big red circle X will say your system admin is preventing the update program from running. Open the policy “Don’t run specified Windows applications“. This can be done via group policy editor - Press windows key = "R" type in gpedit.mscĮxpand “User Configuration” > “Administrative Templates“, then select “System“. Magix seems more interested in pumping out new $$$$ upgrades and addons rather than fix a product they clearly know is broken.Īnyway, the best workaround is to disallow the update program from running. If this were an open source freeware program I'd kinda (well, not really) understand but I paid $400 for a program that crashes constantly. Yes, Magix has proven they have no regard for their customers. I'm very curious, because I'm on an 8 year old HP laptop running the latest version of Windows 10. I have not had any problems with crashes either, and really the only issue I've had is with inconsistent loading of VSTs. Never had a problem installing any of the AP8 builds, and the same goes for AP9.
I'm looking forward to seeing what the problem may be, because unlike many others I have not experienced these issues. I also have Acid Music Studio 11 installed (the consumer cut down version) and it works perfectly, so there seems to be something specific about Acid Pro 9 and VSTs not being recognized correctly, which causes the crash. I will report back here as soon as I make some progress.
I am going to send a deep analysis of this problem to Magix Support on Monday and see if they can work out what the problem is. This is the exact same problem I am experiencing !!! I tried to delete everything in the user directories but still it won't start up. I could get it to run a couple of times after reinstalling it, then I'll fire it up only to have it stop loading and blank out after going about 50% through loading VST 's. Did a clean install from scratch, Deleted everything in the /user directories.