Acid Pro 9.0.30 Crashes When Loading Waves Plugins 5.2

Gamerat328 wrote on 12/3/2019, 2:44 PM

When i Open any waves plugin acid pro 9 crashes,but when i open them with acid pro 7.0 they work fine,i have waves diamond bundle 5.2,so what is the error?i have an amd 5650 card in my laptop,i heard that amd cards are the problem,When i open any waves plugin It says exception 0x0000005 something like this

Comments

Tinus72 wrote on 12/5/2019, 2:44 PM

after updating to Acid Pro 9.0.30 all waves 9.7 vst plugs gone, seems waveshell not loading

Frank_Fader wrote on 12/6/2019, 2:35 AM

ACID now only supports WAVES as VST3 plugins. WAVES assured us that all of their plugins are available as VST3, too. When loading older projects containing VST2 WAVES, these should be automatically replaced with their VST3 counterpart during loading.

Gamerat328 wrote on 12/6/2019, 5:30 AM

But i want to use these version of plugins because of stability and other reasons,and my pc isnt that powerful to run the latest waves,they were working in windows 7 but after i upgraded to windows 10 they crash when i load them,i also have acid pro 7 and acid pro 4 and music studio 10,they work in acid pro 7 and 4 but also crash in music studio 10,maybe because i have an amd card?by the way it is 1gb vram if that helps....

Gamerat328 wrote on 12/6/2019, 5:38 AM

The exception log is here (I loaded c1 gate):

ACID Pro
Version 9.0.3 (Build 30)
Exception 0xC0000005 (access violation) READ:0x000003DC IP:0x156C13B0
In Module 'Waves5.0.DLL' at Address 0x15680000 + 0x000413B0
Thread: GUI ID=0xDBC Stack=0x0019F000-0x001A0000
Registers:
 EAX=09ee6358 CS=0023 EIP=156c13b0 EFLGS=00210216
 EBX=0de41948 SS=002b ESP=0019f704 EBP=0019f718
 ECX=00000000 DS=002b ESI=00000000 FS=0053
 EDX=09ee89dc ES=002b EDI=0fc466b8 GS=002b
Bytes at CS:EIP:
 156C13B0: 8B 91 DC 03 00 00 85 D2 ........
 156C13B8: 75 05 33 C0 C2 04 00 8B u.3.....
Stack Dump:
 0019F704: 1C423687  1C400000 + 23687 (C1.dll)
 0019F708: 0019F710  000A0000 + FF710 
 0019F70C: 00000000 
 0019F710: 09EE6358  09EE0000 + 6358 
 0019F714: 00000019 
 0019F718: 0019FD8C  000A0000 + FFD8C 
 0019F71C: 05C4CBF1  058D0000 + 37CBF1 (acidk.dll)
 0019F720: 09EE89DC  09EE0000 + 89DC 
 0019F724: 0019F730  000A0000 + FF730 
 0019F728: 7568BB20  75670000 + 1BB20 (USER32.dll)
 0019F72C: 0DEB87A8  0DD40000 + 1787A8 
 0019F730: 00000000 
 0019F734: 0019FD8C  000A0000 + FFD8C 
 0019F738: 05AF8D1E  058D0000 + 228D1E (acidk.dll)
 0019F73C: 00AAE7DC  00400000 + 6AE7DC (acidpro.exe)
 0019F740: 0DEB87A8  0DD40000 + 1787A8 
> 0019F76C: 0063053A  00400000 + 23053A (acidpro.exe)
> 0019F770: 760F6962  760F0000 + 6962 (GDI32.dll)
  0019F774: 00000000 
  0019F778: 00000000 
> 0019F77C: 0049414E  00400000 + 9414E (acidpro.exe)
  0019F780: 0019F800  000A0000 + FF800 
> 0019F784: 756A6898  75670000 + 36898 (USER32.dll)
  0019F788: 1E010E70 
  0019F78C: 0019FD3C  000A0000 + FFD3C 
> 0019F798: 756A68B2  75670000 + 368B2 (USER32.dll)
> 0019F7C0: 71A1336F  719F0000 + 2336F (UxTheme.dll)
> 0019F7C4: 71A13290  719F0000 + 23290 (UxTheme.dll)
> 0019F7CC: 71A1337E  719F0000 + 2337E (UxTheme.dll)
> 0019F7F4: 71A13F80  719F0000 + 23F80 (UxTheme.dll)
> 0019F804: 75697F57  75670000 + 27F57 (USER32.dll)
> 0019F820: 75709DE8  75670000 + 99DE8 (USER32.dll)
> 0019F828: 75689E97  75670000 + 19E97 (USER32.dll)
> 0019F834: 75691879  75670000 + 21879 (USER32.dll)
> 0019F844: 7569188A  75670000 + 2188A (USER32.dll)
> 0019F854: 756918A4  75670000 + 218A4 (USER32.dll)
> 0019F868: 1C431370  1C400000 + 31370 (C1.dll)
> 0019F874: 756ADBD0  75670000 + 3DBD0 (USER32.dll)
> 0019F884: 756A630E  75670000 + 3630E (USER32.dll)
> 0019F89C: 7568972C  75670000 + 1972C (USER32.dll)
> 0019F8C0: 756896C1  75670000 + 196C1 (USER32.dll)
> 0019F8E0: 771E213C  771A0000 + 4213C (ntdll.dll)
> 0019F8F4: 75687695  75670000 + 17695 (USER32.dll)
> 0019F914: 756ABE6B  75670000 + 3BE6B (USER32.dll)
> 0019F970: 04008002  00400000 + 3C08002 (acidpro.exe)
- - -
 0019FFF0: 00000000 
 0019FFF4: 00D30679  00400000 + 930679 (acidpro.exe)
 0019FFF8: 003A2000  00200000 + 1A2000 
 0019FFFC: 00000000 

Gamerat328 wrote on 12/6/2019, 5:39 AM

This time its in music studio 10 (Also Loaded C1 Gate)

Problem Description
   Application Name:    ACID Music Studio 10.0
   Application Version: Version 10.0 (Build 108)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files (x86)\Waves\Plug-Ins\Waves5.0.DLL
   Fault Address:       0x0DEB13B0
   Fault Offset:        0x000413B0

Fault Process Details
   Process Path:        C:\Program Files (x86)\Sony\ACID Music Studio 10.0\musicstudio100.exe
   Process Version:     Version 10.0 (Build 108)
   Process Description: ACID Music Studio 10.0
 

Gamerat328 wrote on 12/6/2019, 5:41 AM

In Acid pro 7 it loads just fine

Its really sad to see that the older versions of a program can load a plugin while the latest version can't....

Trensharo wrote on 12/7/2019, 6:33 PM

In Acid pro 7 it loads just fine

Its really sad to see that the older versions of a program can load a plugin while the latest version can't....


ACID Pro 7 uses a completely different VST Engine, which is 32-Bit only and doesn't support VST3. If that's what you want, then just use ACID Pro 7 and call it a day. It's not like you're going to be missing a ton of functionality by doing that. Just the benefits of going 64-Bit (Memory usage, mainly) and some garbo Vita 2 instruments (eFX is ignorable if you have Waves plugins).

Trensharo wrote on 12/7/2019, 6:34 PM

But i want to use these version of plugins because of stability and other reasons,and my pc isnt that powerful to run the latest waves,they were working in windows 7 but after i upgraded to windows 10 they crash when i load them,i also have acid pro 7 and acid pro 4 and music studio 10,they work in acid pro 7 and 4 but also crash in music studio 10,maybe because i have an amd card?by the way it is 1gb vram if that helps....


Windows 10 runs more efficiently than Windows 7, so that's not a reason for this. You have to have issues elsewhere in your system for this to be the case. I'd investigate that.

Beyond that, if your system is too weak to handle some Audio Plugins, then I questions if it's strong enough to handle a DAW at all...

Gamerat328 wrote on 6/19/2020, 4:31 PM

After a long period i found the solution 2 weeks ago. its to run the program as an adminstrator.

johnebaker wrote on 6/20/2020, 3:07 AM

@Gamerat328

Hi

Does this solution refer to loading an old project in this topic if so, please post there that the issue is resolved.?

I will close this topic as resolved.

John EB
Forum Moderator

Lateral thinking can get things done!

VPX 12, MEP Premium 2020, and earlier versions 2015 and 2016, Music Maker Premium 2021 and Music Maker 2020.

Running Windows 10 2004 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.