My project won't render

Raquela-Burt wrote on 7/19/2026, 5:12 PM

I have no trouble rendering my other projects except for this one. It just won't render. I tried doing an update... it says it's updated.

Is it because some of the audio files used in my project are wav's and some are mp3's?

Some of the wav's had questionable format settings, but it plays just fine. Still, that should never be a problem, right? For the sake of keeping up a work-flow.

But again, I do not have this trouble with my other projects.

A report was sent to Magix today, but I have no way of knowing if they got it of if they care. I wish I could have copied the report, but I forgot to after it was sent. If I see the report window pop up again. I'll be sure to copy-n-paste it here.

I would like to attach a picture of my problem, but unfortunately, I don't see anywhere here where I can do that.

Can anyone please help me with this?

 

ACID Pro Ver. 11.0.2 (Build 21) 64bit

Operating System
 Platform: Windows 10.0 (64-bit)
 Version: 10.00.26200
 Language: English
 System locale: English
 User locale: English

Processor
 Class: Intel(R) Core(TM) Ultra 7 265
 Identifier: GenuineIntel
 Number of processors: 20
 MMX available: Yes
 SSE available: Yes
 SSE2 available: Yes
 SSE3 available: Yes
 SSSE3 available: Yes
 SSE4.1 available: Yes
 SSE4.2 available: Yes

Display
 Primary: 2560x1440x32

Memory
 Physical memory: 32,133.0 MB
 Paging memory available: 71,045.2 MB

Application
   Path: C:\Program Files\ACID\ACID Pro 11.0\acidpro.exe

CD/DVD
   sfcd.cdd.dll version: 3.0.2.4681
   sfspti.dll version: 3.0.2.4681
   sfcdix.cfg version: 1.2.0
   sfcdix.cfg checksum: 185764

File I/O Plug-Ins
   aifplug.dll
     version: 1.2.2.10948
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\aifplug\aifplug.dll

   atracplug.dll
     version: 1.0.2.8860
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\atracplug\atracplug.dll

   aviplug.dll
     version: 1.2.2.13397
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\aviplug\aviplug.dll

   fhgaacplug2.dll
     version: 1.0.2.381
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\fhgaacplug2\fhgaacplug2.dll

   flacplug.dll
     version: 1.0.2.5496
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\flacplug\flacplug.dll

   mcmp4plug2.dll
     version: 1.0.2.8532
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\mcmp4plug2\mcmp4plug2.dll

   mcplug2.dll
     version: 2.0.2.6983
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\mcplug2\mcplug2.dll

   mp3plug2.dll
     version: 3.0.2.10369
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\mp3plug2\mp3plug2.dll

   oggplug.dll
     version: 1.2.2.11876
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\oggplug\oggplug.dll

   sfpaplug.dll
     version: 1.2.2.12188
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\sfpaplug\sfpaplug.dll

   stl2plg.dll
     version: 1.3.2.10564
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\stl2plg\stl2plg.dll

   wavplug.dll
     version: 1.2.2.13736
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\wavplug\wavplug.dll

   wmfplug4.dll
     version: 1.0.2.5349
     path: C:\Program Files\ACID\ACID Pro 11.0\FileIO Plug-Ins\wmfplug4\wmfplug4.dll

Comments

SP. wrote on 7/19/2026, 11:08 PM

@Raquela-Burt

A report was sent to Magix today, but I have no way of knowing if they got it of if they care. I wish I could have copied the report, but I forgot to after it was sent. If I see the report window pop up again. I'll be sure to copy-n-paste it here.

Are you talking about a crash report? I don't think that has any significance.

You can look up a detailed crash report in the Microsoft Windows Reliability Monitor (a tool included in Windows) and copy and paste it here. Inside the report is usually a fault module listed, which might help to find a solution.

Raquela-Burt wrote on 7/19/2026, 11:25 PM

Yes SP., that is exactly what I was referring to! I never knew about the Microsoft Windows Reliability Monitor. I typed "Reliability Monitor" into my start bar, and it popped right up... I believe there were two recorded from today.... I see other crash reports listed that could be relatable, but I'll start with these two...

 

FIRST ONE:

Source
ACID Pro 11.0

Summary
Stopped responding and was closed

Date
‎7/‎19/‎2026 12:11 AM

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files\ACID\ACID Pro 11.0\acidpro.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    acidpro.exe
Application Version:    11.0.2.21
Application Timestamp:    639995d6
Hang Signature:    63cf
Hang Type:    134217728
OS Version:    10.0.26200.2.0.0.768.101
Locale ID:    1033
Additional Hang Signature 1:    63cf3813e9ab286c8c0e0ab7311914fd
Additional Hang Signature 2:    b135
Additional Hang Signature 3:    b13590ab48cfaf84eb742e1c1a146b5c
Additional Hang Signature 4:    63cf
Additional Hang Signature 5:    63cf3813e9ab286c8c0e0ab7311914fd
Additional Hang Signature 6:    b135
Additional Hang Signature 7:    b13590ab48cfaf84eb742e1c1a146b5c

Extra information about the problem
Bucket ID:    e86a7928780a2a7681e49c08e51484a5 (1289326955351803045)

 

SECOND ONE:

Source
ACID Pro 11.0

Summary
Stopped working

Date
‎7/‎19/‎2026 5:29 PM

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\ACID\ACID Pro 11.0\acidpro.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    acidpro.exe
Application Version:    11.0.2.21
Application Timestamp:    639995d6
Fault Module Name:    InnerProcessDictionary_x64.dll
Fault Module Version:    1.6.0.0
Fault Module Timestamp:    6159adfb
Exception Code:    c0000005
Exception Offset:    0000000000012848
OS Version:    10.0.26200.2.0.0.768.101
Locale ID:    1033
Additional Information 1:    5de6
Additional Information 2:    5de61729d9d575e3bb168fe650f90bd8
Additional Information 3:    7194
Additional Information 4:    719408a840bf65904e6e5fa544c187f2

Extra information about the problem
Bucket ID:    8e7951f36465aeb87c94e9e0dca9bd97 (2059528081599217047)

SP. wrote on 7/20/2026, 1:41 AM

@Raquela-Burt Are you using Waves plugins? It looks like InnerProcessDictionary_x64.dll is part of them. It could be that there is a Waves plugin that crashes Acid.

https://forums.steinberg.net/t/app-crash-on-close-innerprocessdictionary-x64-dll/

Raquela-Burt wrote on 7/20/2026, 3:39 PM

Yes I am SP., I use WAVES plugins for all my projects. I will check out that link you shared above 🙏

Raquela-Burt wrote on 7/20/2026, 10:40 PM

Unfortunately, that post at Steinberg, did not answer my question. I tried reposting my question there, but also unfortunately, Steinberg is not connected to ACIDpro or WAVES. Can anyone else help me here?

SP. wrote on 7/21/2026, 2:24 AM

@Raquela-Burt The link wasn't there to solve your problem, but just something I found about a crash caused by InnerProcessDictionary_x64.dll.

Generally, Waves is only compatible with DAWs listed on their website. So, if you'll ask them for help they will likely say, that they don't support Acid.

The last Acid update is currently from around 2020/2021. If it doesn't work with modern versions of Waves plugins there isn't much you can do, except maybe using much older versions of Waves or waiting until Boris FX releases a new version of Acid with additional bug fixes to the VST engine.

Maybe it will help if you reset the program settings of Acid back to its default. For this, press CTRL and SHIFT on your computer keyboard, then start Acid and keep holding both keys until a small window appears which will ask you to reset the program settings.

In the past, some users here could also solve VST plugin problems by changing the VST Scan Server exe files inside the Acid program folder against newer versions. For example, if you install the free 30 days trial version of Music Maker 2026 you'll find the same VST Scan Server executables in its program folder, but they are much newer and can load newer plugins. First, you need to backup the exe files in the Acid program folder and then you can copy and paste the files from Music Maker into the folder and overwrite them. Then start Acid and do a complete VST path rescan.

Another thing you can do, is to bypass all Waves plugins in your problematic project and try to export it again and see if it works. Then re-enable the plugins one-by-one until it crashes again. Then you found the plugin causing the crash.