SF14 crash on openin / playing .WAV files

LordJarhead wrote on 8/27/2020, 2:04 AM

Hello,

 

I sometimes end up with a crash when I load a bunch of WAV files into SF and us some VST's and do things a tad too fast. I happened, not that often, but it was ok, I got used to it over time.

Now, I took a long break and wanted to get back at work today, only to find out that SF14 (Build111) 64Bit just crashes instantly on opening a .wav file in the explorer. Sometimes I can open them up, but as soon as I want to play the file in SF, it crashes immediately. I can't get a tone out of this program.

I do not know the version I had before, but I just had an update to Build 111, and it made it even worse by the fact that it crashed only by clicking a .wav file in the SF file explorer. I know it wasn't that stable of a program before but not like this. I can't do simple tasks, nor do my job. Maybe someone can help. Oh, and btw, since the Update the program keeps crashing without any report/log, it just closes.

Edit: I noticed that the issue seems to be related to specific folders. I can open and play files from one folder but crash on the other even if the files can all be played with WMP or VLC.

Edit2: I tracked it down to be a bunch of specific .wav files that keep crashing. Some work fine, some not. Maybe some files got corrupted, but I can't remember what I have done with them to have this drastic difference now. I can play both files with any player, iZotope RX7 can open all, showing no problem to operate them. When I run the files through a converter like Switch Plus and convert it into the same format, SF14 can open and manage them as usual.

 

Some OS information on the side:

Operating System: Windows 10 Home 64-bit (10.0, Build 19041) (19041.vb_release.191206-1406)
Language: German (Regional Setting: German)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 3003 (type: UEFI)
Processor: AMD Ryzen 9 3900X 12-Core Processor             (24 CPUs), ~3.8GHz
Memory: 16384MB RAM
Available OS Memory: 16314MB RAM
Page File: 9664MB used, 13305MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.0084 64bit Unicode

-------------
Sound Devices
-------------
Description: Beyerdynamics DT880 Pro (ASUS Xonar DGX Audio Device)
Default Sound Playback: Yes
Default Voice Playback: No
Hardware ID: PCI\VEN_13F6&DEV_8788&SUBSYS_85211043&REV_00
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: cmudaxp.sys
Driver Version: 8.1.8.1823 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 02.06.2015 02:00:00, 2735616 bytes
Other Files:
Driver Provider: ASUSTeK
HW Accel Level: Emulation Only
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

 

 

 

 

Comments

rraud wrote on 8/27/2020, 11:07 AM

Welcome to the Magix Sound Forge forum @LordJarhead.

Have you tried resetting SF which also clears the cache (file menu). I could not install the build 111 update at all... kept getting the message "must have Win 7 or 8" (duh, I have Win 10) and the update cancelled and SF closed). Ended up dong a repair install which worked w/o issue. May have somthing to do with fact that I have the 32 bit version of Pro 14 as well.. which updated ok. Thee 32 and 64 bit versions share a lot of the settings files.

Could be something in the file's header that SF does not like. Try changing the file extension to <.raw> and open in SF, if it opens 'Save as' a PCM Wave.

Can post one of the problem file(s) on DropBox, GoogleDrive, OneDrive or elsewhere?

jose-filipe8761 wrote on 8/27/2020, 11:50 AM

Sorry, for my English...

I have the same problem.

I think ".wav" files saved with "markers" or "regions" crashed in the SF14 buil 111 explorer.

If you clear the "markers" or "regions" of the file and save it, refresh the explorer and it is already possible to access without problems.

"Clean" files - Ok
Files with markers or regions - Crash

If you open the file in the "Open File" Menu, the file opens normally.

Jpf

rraud wrote on 8/27/2020, 1:13 PM

It is not uncommon to get an error message indicating corrupt "markers" or "regions" on files, usually written with other apps. The file usually opens normally though when 'Ignore' (or 'open anyway') is selected

jose-filipe8761 wrote on 8/27/2020, 1:32 PM

Yes.

In SFP12 and SFP14 build65 this message exists.
The same files are opened without any problem.

After the update to SFP14 build111, the message no longer appears and the application closes quickly (in SFP explorer).
It appears if you open the file from the "File-> Open file" menu.

Perhaps a problem with the SFP14 explorer after the update ...

LordJarhead wrote on 8/28/2020, 1:47 AM

Hey Rraud, thanks for the reply,

whenever I need to reinstall or clear a cache or anything with SF, I'm afraid to lose all my presets that I created. I use a lot of Plug-in Chains for my work and this allowed me mostly for automated workflows. I had to reinstall windows a couple of weeks ago and despite the fact that I tried this Preset Manager that did not really work, like, at all.

So I had to re-create all presets, which threw me back a couple of days behind scedules. Now this problem again, it makes me wonder why not switching to another tool. But I still love to work with SF too much.

I have converted some of my problematic sound folders and that worked, now SF works like a charm, for quite some hours by now. My sound libraries all work well, too. So it really was down to one single project folder.

I don't really know why that's affected, worked last time and after a few weeks of vacation, they just won't open. If I remember correctly there was an update in the meantime and these files were created with an older version of SF14. Wondering if that's the issue here.

rraud wrote on 8/28/2020, 10:45 AM

Preset Manager works if (all) the Fx and chains file paths have not been changed,
Otherwise, the individual presets can be copied from:
C:\Users\USER NAME\AppData\Local\MAGIX\Sound Forge Pro\ (#)
Keyboard shortcuts and layouts:
C:\Users\Rick\AppData\Roaming\Magix\Sound Forge Pro\ (#)

As you are probably know, 'AppData' is normally a hidden system folder.

LordJarhead wrote on 9/2/2020, 3:16 AM

Ok, so I found out that all .wav files I save with SF14 tend to crash SF14 when trying to open them again. So I changed the extension to .raw, could only drag&drop it in SF14, it wasn't shown up in the SF explorer, I saved it as .wav PCM, and trying to open that files again crashed SF14 again. I can Drag&Drop the .wav file in, it opens and plays it, but if I try to use the SF Explorer and only click on the file it crashes. I usually only work with that explorer tho.

LordJarhead wrote on 9/2/2020, 3:27 AM

I finally got a report window showing following Log;

 

Extra Information
   File:                C:\Users\kahld\AppData\Local\MAGIX\SOUND FORGE Pro\14.0\dx_grovel_x64.log
   File:                C:\Users\kahld\AppData\Local\MAGIX\SOUND FORGE Pro\14.0\vst_grovel.log

Problem Description
   Application Name:    SOUND FORGE Pro
   Application Version: Version 14.0 (Build 111) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\forgek.dll
   Fault Address:       0x0000000000B9DBF5
   Fault Offset:        0x00000000001CDBF5

Fault Process Details
   Process Path:        C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\Forge140.exe
   Process Version:     Version 14.0 (Build 111) 64-bit
   Process Description: SOUND FORGE Pro
   Process Image Date:  2020-08-12 (Wed Aug 12) 17:57:42

The dx_groval_x64.log file is empty, vst_groval.log shows:

 

INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\Analogue Modelling Suite\AM-Munition1.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\Analogue Modelling Suite\AM-Phibia.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\Analogue Modelling Suite\Am-Pulse.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\Analogue Modelling Suite\AM-Track.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_ChorusFlanger.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_Compressor.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_DeEsser.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_Gate.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_Limiter.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_Phaser.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_Reverb.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_StereoDelay.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_TremoloPan.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_TubeStage.dll.
INFO 2020-09-02 10:25:27 ignored and skipped C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\essentialFX\eFX_VocalStrip.dll.
INFO 2020-09-02 10:25:27 **** Writing search paths to registry ****
INFO 2020-09-02 10:25:27 Adding path "C:\Program Files\SOUND FORGE\SOUND FORGE Pro 14.0\MAGIX Plugins\"...
INFO 2020-09-02 10:25:27 Adding path "C:\Program Files\Common Files\VST3\"...
INFO 2020-09-02 10:25:27 **** Writing mappings to registry ****
INFO 2020-09-02 10:25:27 **** Grovel completed with no critical errors ****

I uninstalled and reinstalled SF14 completely only to find out the same exact problem as before. No difference.

LordJarhead wrote on 9/2/2020, 3:39 AM

Ok so I noticed that when I can open a wav file, put some markers in it (M) and save it, the markers disappear, which never happened before in .wav files. When I load an old file that I KNOW has markers, SF14 crashes. I can only open files that have no markers in them.... the Markers seem to be the problem here... wtf

 

rraud wrote on 9/2/2020, 11:24 AM

In the "Save" (or 'Save as') window there is a "Save metadata with file" check box. Unchecked will not save markers, regions and such.

FYI, in "Options> Preferences> General", there also is a "Warn when metadata cannot be saved with the file" option..

LordJarhead wrote on 9/3/2020, 3:15 AM

Yes, I have these selected, but that won't make me able to open files that I've saved with markers before the updated Build 111. So I can not open my project files unless I use a converter or another tool to clean the markers/regions. That is a nightmare; I've made these markers for a reason.

rraud wrote on 9/3/2020, 10:36 AM

I cannot not duplicate that behavior in Pro 14 (build 111) Can you post a file that has the problem on DropBox, GoogleDrive, ect.

According tp the error report, there are a lot of plug-ins trying to load. Select the Fx icon on the toolbar and remove them.

Try uninstalling Sound Forge with a third-party uninstaller that can remove leftover register entries, folders and other pertinent data files the OS uninstall leaves behind.... then reinstall.
I recommend Revo Uninstall which is highly regarded among folk here and elsewhere. There is a freeware version as well as a pro version. The freeware version is adequate for most folks

TRM wrote on 9/20/2020, 10:51 AM

Sorry, for my English...

I have the same problem.

I think ".wav" files saved with "markers" or "regions" crashed in the SF14 buil 111 explorer.

If you clear the "markers" or "regions" of the file and save it, refresh the explorer and it is already possible to access without problems.

"Clean" files - Ok
Files with markers or regions - Crash

If you open the file in the "Open File" Menu, the file opens normally.

Jpf

 

I am having similar problems. Attempting to open an audio file from SF14's Explorer panel will cause the program to crash. Even highlighting the file will crash the program. Note that the crash occurs only when the file contains a marker and only if attempting to open it from within the program. Dragging and dropping the same file externally from Windows Explorers does not cause a crash. Uninstalled/Reinstalled program. It did not fix the problem. I am using the latest build (111), and also on a brand new PC build (new mobo/pcu/ram/ssd etc).

BTW How do I add my PC stats to my comments like you did?

TRM wrote on 9/28/2020, 1:52 PM

I activated a support ticket with MAGIX regarding this issue, and they confirmed the bug, specifically audio files containing markers crashing the program whenever they're opened from the file explorer module. It seems to be specific to the latest build. They have forwarded the issue to their technical department, and will hopefully issue an update soon. The current workaround seems to be dragging and dropping the file from Windows Explorer, as well as using the File > Open command to open the file,