Not sure why it would wipe out all ASIO devices on my system, but struggling to work with ASIO after installing 11.0.4. Even some other applications no longer work after updating to 11.0.4. WASAPI is working fine still luckily. Unfortunately my main setup is Jack Audio and it can no longer connect to my main audio interface after 11.0.4 either. Very odd. Any ideas?
Mmm, what is SpectraLayers doing to my audio hardware. It was literally rock solid for over 2 years, now nothing is working anymore? No application will run ASIO anymore and SpectraLayers crashes when selecting ASIO.
1 Like
SpectraLayers is doing nothing special to your ASIO hardware, it’s just using the regular ASIO API. If other apps can’t use ASIO anymore then the common denominator is either an audio driver failure or a hardware failure.
1 Like
I’m perplexed then, I literally installed the update opened SpectraLayers it crashed when selecting ASIO, thought nothing of it, but then it wouldn’t connect and kept crashing. Tried connectingn other ASIO software, that no longer connects. Connected different ASIO interfaces, they can no longer be connected to. Literally 5 mins before everything has been rock solid for 2 years. Of course I got 2 albums to get through by Monday too, so that’s taught me hard lesson. Looks like i’m rebuilding the workstation now.
1 Like
This is the EventViewer logs when connecting to ASIO from SpectraLayers. Any ideas?
Faulting application name: SpectraLayers.exe, version: 11.0.40.395, time stamp: 0x6715296f
Faulting module name: MSVCP140.dll, version: 14.29.30147.0, time stamp: 0x63237c7a
Exception code: 0xc0000005
Fault offset: 0x0000000000013080
Faulting process id: 0x0x369C
Faulting application start time: 0x0x1DB3799B8980EDF
Faulting application path: C:\Program Files\Steinberg\SpectraLayers 11\Win64\SpectraLayers.exe
Faulting module path: C:\Program Files\Steinberg\SpectraLayers 11\Win64\MSVCP140.dll
Report Id: ef913402-91a2-4ab2-ac78-fe113b10632b
Faulting package full name:
Faulting package-relative application ID:
Reading up, it looks like Microsoft Visual C++ Redistributable package has got corrupted installing SpectraLayers maybe? I’ll try repairing Microsoft Visual C++ and see if that fixes the ASIO issue.
OK, managed to fix it. In case others have the same issue after installing I did this:
- Press
Win + R, typeappwiz.cpl, and press Enter to open the Programs and Features window. - Locate “Microsoft Visual C++ 2015-2019 Redistributable” in the list.
- Select it and click “Change” or “Modify.”
- In the setup window, choose “Repair” and follow the on-screen instructions.
- Repeat this process for both the x86 and x64 versions if they are installed.
- Restart
1 Like
Glad you resolved your issue. For the record, SpectraLayers doesn’t install or modify any Visual C++ redistributable package.
MSVCP140.dll inside SpectraLayers /win64 folder is a component from the Visual C++ redistributable though and that was crashing? I’ve no idea if MSVCP140.dll comes from my Visual C++ redistributable or the win64 build of the SpectraLayers update. Anyway, it’s’ resolved, thanks Robin!
1 Like
I think I spoke too soon, still experiencing lots of crashes post 11.0.4 update. Interacting with ASIO devices definitely fixed with the Visual C++ redistributable repair but now i’m seeing crashes when opening/using most modules, usually including MSVCP140.dll in the event log within SpectraLayers directory.
One of the frrst offenders is the VST3 module. It opens to a white box, but then crashes. Looking at the SpectraLayers log, for some reason it’s crashing scanning vst3 plugins. Not sure why it’s logging 0 files when it even shows a plugin it’s scanning and crashing on. Andrew Reeman plugins are not even the first folder in C:/Program Files/Common Files/VST3/ and I’ve never added that plugin to the current project i’m working on either, so i’m not sure why SpectraLayers is opening it yet??
13:33:18.600 23dc INFO scanning VST3 plugins… (0 files)
13:33:18.601 23dc INFO VST3 scan done
13:33:18.603 23dc INFO opening vst3 plugin file C:/Program Files/Common Files/VST3/Andrew Reeman/Spectral Gate.vst3 with effect Spectral Gate…
This is the Windows Application Event log:
Faulting application name: SpectraLayers.exe, version: 11.0.40.395, time stamp: 0x6715296f
Faulting module name: MSVCP140.dll, version: 14.29.30147.0, time stamp: 0x63237c7a
Exception code: 0xc0000005
Fault offset: 0x0000000000013080
Faulting process id: 0x0x2DC0
Faulting application start time: 0x0x1DB382919FEC7B5
Faulting application path: C:\Program Files\Steinberg\SpectraLayers 11\Win64\SpectraLayers.exe
Faulting module path: C:\Program Files\Steinberg\SpectraLayers 11\Win64\MSVCP140.dll
Report Id: 07e1d060-69ea-4d8b-b1be-3f5ff730d136
Faulting package full name:
Faulting package-relative application ID:
And crash info log:
Fault bucket 1810873168247759043, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: SpectraLayers.exe
P2: 11.0.40.395
P3: 6715296f
P4: MSVCP140.dll
P5: 14.29.30147.0
P6: 63237c7a
P7: c0000005
P8: 0000000000013080
P9:
P10:
And attached is the .wer (renamed .
Report.crash (42.8 KB)
)
Exception code: 0xc0000005 seems to be spectralayers MSVCP140.dll trying to access memory locations it shouldn’t?
What versions of Microsoft C++ Redistributable do I need to install for SpectraLayers? System currently has Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.40.33816
sfc /scannow didnt find any integrity issues so looks like Microsoft C++ Redistributable is still in order.
Some other side effects after updating is the recovery process launches when starting after a crash, does its thing, but the recovered project is then empty. I just lost several days work opening an old project. Is there a way to go back 2 versions of a file?
OK, I managed to force VST3 folder to get re-scanned by creating an Alias to the official steinberg VST3 folder where all the plugins are. This at least gets the dialogue open. This issue is despite a fresh install, SpectraLayers seems to default to loading Spectral Gate plugin. I don’t even have a project open yet, so this is definitely an issue. Why would it pre-loading a random plugin like this?
And removing a plugin now crashed SpectraLayers. Only way to load a new plugin is to temporarily rename the .vst3 plugin SpectraLayers keep loading on initialising to say .vst3.bypass, then load SpectraLayers, then I can load a different plugin. SpectraLayers still loads the last list of plugins for new projects though and then crashes??
I think i’m going to have to reinstall Windows to resolve these 11.0.4 update issues, it’s like half of SpectraLayers works fine as previous version did, but anything involving a popup window / GUI / SpectraLayers module / VST3 crashes it.
Here’s the SpectraLayers log leading up to crashing when trying to remove a plugin. In this case I’m trying to remove Spectral Compressor from Nih Plugs which I loaded.
16:07:58.623 43a8 INFO I/O: ASIO (Default System Input/Apogee USB ASIO Driver)
16:08:01.178 43a8 INFO scanning VST3 plugins… (0 files)
16:08:01.179 43a8 INFO VST3 scan done
16:08:01.180 43a8 INFO opening vst3 plugin file C:/Program Files/Common Files/VST3/Nih Plugs/Spectral Compressor.vst3 with effect Spectral Compressor…
Gets even stranger. I’ve literally deleted everything steinberg-related, removed every registry entry leftover from uninstalling SpectraLayers 10 and 11, removed Steinberg ASIO Driver, Steinberg Activation Manager and Steinberg Download Manager, removed every C++ redistributable, cleaned the registry, removed everything in users appdata, documents etc etc. Downloaded a new 11.0.4 installer and Activation Manager. Installed and it’s still crashing on every module opened and still is loading a random VST3 plugin before I’ve even created the first project? WTF is going on with 11.0.4? How can it be loading plugins when I have no project yet and deleted everything? Where is SpectraLayers still saving all this preference data to be loading vst3 plugins never requested in the first place?
All other audio software is working as normal, it’s only SpectraLayers after installing 11.0.4 is the problem now.
I can reliably reproduce the crashing in SpectraLayers VST3 management now for 11.0.4.
- Load Nih Plugs: Spectral Compressor plugin (works fine)
- Attempt to remove Nih Plugs: Spectral Compressor from the dialogue = Crashes SpectraLayers
- Load SpectraLayers again > Modules > VST3 Effect and the Spectral Compressor plugin is still in the plugin chain even though we haven’t created a new project yet, letalone opened the project that particular plugin was last used in.
- Attempt to remove Spectral Compressor = Crash and so it’s impossible to start a new project once in this cycle of loading and crashing.
Basically SpectraLayers needs to not load the plugin from the previous project by default, it needs to clear the entire chain of all plugins so that if one is causing an issue in a previous project, it doesn’t carry on causing the same issue in subsequent projects or even simply the initialization window after launching SpectraLayers.
Yes the crash with the Spectral Compressor was already reported here : VST3-Plugins crashes SL 11.40
It’s fixed in the upcoming patch 5: VST3-Plugins crashes SL 11.40 - #28 by Robin_Lobel
OK, cool. Will that patch stop loading plugin chains in new projects? It’s not just Spectral Compressor as this thread shows, it will be any plugin SpectraLayers crashes from using.
After 13 hours of fighting I’ve managed to get things rescued enough to work again, but I’m still facing the issue where recovered projects after a crash are not showing any layers or even history? e.g. PROJECT.slp here was rescued after a crash, it’s file size is 3.78GB and looks about right, yet it opens to be empty layers, no history. It weirdly adds 3 time markers not present in the project originally and labels them with the files first imported when the project was created. Very odd?
Yes, the VST3 Effects module will stop immediately loading the previous plugin chain from the previous session to avoid such scenario.
Recovering a crashed session can fail, but it’s independent from your .slp project which is left untouched. So if the recovery fails, you can still try loading your .slp project as when it was last saved by you.
1 Like
Sorry for double-reply, accidentally deleted the first.
This project was worked on all last week without issues, no crashes. Made some edits today, saved it and now when I open it, although it’s still the 5Gb file size it was originally, there’s no layers or stems in it. File size remains as it was.
Log from opening file here:
*20:51:13.480 85ac INFO C:\Program Files\Steinberg\SpectraLayers 11\Win64\SpectraLayers.exe *
*20:51:13.481 85ac INFO folder: C:\Program Files\Steinberg\SpectraLayers 11\Win64*
20:51:13.488 85ac INFO parent process: C:\Windows\explorer.exe
20:51:13.488 85ac INFO executable path: C:\Program Files\Steinberg\SpectraLayers 11\Win64\SpectraLayers.exe
20:51:13.488 85ac INFO early init done
20:51:13.488 85ac INFO creating app…
20:51:13.935 85ac INFO loading properties…
20:51:14.217 85ac INFO session SpectraLayers 2024.11.25-20.51.13.477 started - slp11srv
20:51:14.217 85ac INFO SpectraLayers Pro 11.0.40 Build 395 (x86_64 - Qt 6.6.3 - qtnamespace: SpectraLayers - MSVC 1929)
20:51:14.222 85ac INFO libpng warning: iCCP: known incorrect sRGB profile
20:51:14.457 85ac INFO ID: YzU5NjY5MjMtNWYxMy00OGMwLWE5MTctNWYzY2Y0NTFkYzk5
20:51:14.457 85ac INFO OS: Windows 11 Version 23H2 (Kernel: 10.0.22631) (en_GB)
20:51:14.457 85ac INFO CPU: 20 threads (AVX2)
20:51:14.457 85ac INFO RAM: 16 GB
20:51:14.458 85ac INFO HDD: 953 GB (29 GB free)
20:51:14.458 85ac INFO SCR0: 1920x1200x32@60.001Hz (device pixel ratio: 2) (primary)
20:51:14.458 85ac INFO SCR1: 1920x1080x32@60Hz (device pixel ratio: 1)
20:51:14.458 85ac INFO creating window…
20:51:14.459 85ac INFO loading plugins…
20:51:15.206 85ac INFO 40 external plugins loaded
20:51:15.221 85ac INFO initializing UI…
20:51:15.269 85ac INFO libpng warning: iCCP: known incorrect sRGB profile
20:51:15.343 85ac INFO layout and graphic objects initialized
20:51:15.375 85ac INFO setting shortcuts and properties
20:51:16.885 85ac INFO UI initialized
20:51:17.016 85ac INFO Ready
20:51:17.029 85ac INFO Show
20:51:17.059 85ac WARNING OpenType support missing for “Open Sans”, script 11
20:51:17.060 85ac WARNING OpenType support missing for “Tahoma”, script 11
20:51:17.060 85ac WARNING OpenType support missing for “Arial”, script 11
20:51:17.060 85ac WARNING OpenType support missing for “MS UI Gothic”, script 11
20:51:17.060 85ac WARNING OpenType support missing for “SimSun”, script 11
20:51:17.061 85ac WARNING OpenType support missing for “Segoe UI Emoji”, script 11
20:51:17.061 85ac WARNING OpenType support missing for “Segoe UI Symbol”, script 11
20:51:17.273 85ac INFO Accessibility enabled: true
20:51:17.287 85ac INFO checking ASIO…
20:51:17.653 85ac INFO scanning 11 devices…
20:51:17.654 85ac WARNING RtApiAsio::probeDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (Blackmagic Audio). RtApiAsio::probeDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (JackRouter).
20:51:17.654 85ac INFO Apogee USB ASIO Driver (0/2 channels, 48000 Hz) (default output)
20:51:17.654 85ac INFO Realtek ASIO (2/2 channels, 48000 Hz) (default input)
20:51:17.654 85ac INFO ReaRoute ASIO (x64) (16/16 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-128 (128/128 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-256A (256/256 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-256B (256/256 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-32 (32/32 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-512 (512/512 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-64A (64/64 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-64B (64/64 channels, 48000 Hz)
20:51:17.654 85ac INFO VB-Matrix VASIO-8 (8/8 channels, 48000 Hz)
20:51:17.654 85ac INFO I/O: ASIO (Default System Input/Apogee USB ASIO Driver)
20:51:17.965 4c38 INFO internet access:true
20:51:17.965 4c38 INFO setting helppath to Steinberg
20:51:18.018 85ac INFO accessibility enabled
20:51:18.107 4c38 INFO context help online:true
20:51:19.188 4c38 INFO help online:true
20:51:33.192 85ac INFO Read PROJECT-48.slp SamplingFormat(Real, 48000Hz, Audio, 2 channel(s), mapping: 11, order: custom) 0 layer(s))
20:51:33.311 85ac INFO GPU: D3D11 / NVIDIA GeForce RTX 3050 Ti Laptop GPU
20:51:33.554 85ac INFO Project Samplerate: 48000Hz Device Samplerate: 48000Hz
20:51:33.964 85ac WARNING RtApiAsio::probeDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (Blackmagic Audio). RtApiAsio::probeDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (JackRouter).
20:51:37.723 85ac INFO I/O: none
something similar happened to me a few weeks back on a project I had been working on for about 10 days…but my issue was after a crash and Recover Session dialog selection…which I’m not certain which I chose
Yeah, that issue is resolved with the vst crashes and I thought that was the end of this opening blank projects after recovery issue. I’ll try the latest patch tonight, but this a scary bug as I’ve basically lost a week of work already simply opening a file, didn’t even crash, didn’t have any vst on it either. Doesn’t help I’m a Bitwig user, we simply don’t crash the DAW so I get out of the habit of continually making two copies of everything.
1 Like