Hi @PG1
I hope you are well.
i’ve updated WL12.0.51.15 yesterday,
and now experiment crash on crash etc.
config details are in the crash repports
i’ve made a new project from the one i was working on,
remove all plug from the master section, and it still crashes.
audio config is a merging Hapi, up to date runing various AD / DA via AES, configurated as it should etc.
here are the crash reports
The problem seems related to your audio connection settings.
I recommend doing them again in the WaveLab preferences.
thanks @PG1
so i just re-do exactly the same connections and it should work?
I would erase this setting folder beforehand:
\Steinberg\WaveLab Pro 12\Presets\Audio Connections\
Hi @PG1
just to let you know,
a lot less crashes so far.
2 in a week.
redo the audio connections folder supr and connection remaking
and no crash yet 
thanks a lot for the help.
Hi @PG1 i hope you are well
i’ve experimented many crashes those last time.
i’ve reinstalled WL, updated all pluggin.
i’m on an intel mac.
i though about an ARM process crashing everything.
but no ARM processes anywhere.
also updated the OS. the convertors drivers.
an i’m still crashing all the time.
it seems something goes wrong with the Playback Audio Queue.
i’ve redo the audio config.
and i have a lot of latency, like 4 seconds.
please let me know your thoughs.
These are indeed crashes inside the playback part of WaveLab. But I cannot see the origin of the problem.
Why do you have such long latency of four seconds? Maybe this is a sign that somewhere there is too much stress for WaveLab. Just a guess.
i’ve always had latency.
but those time it’s really massive.
i don’t use that much plugins, i ve deseable oversampling to save CPU.
i’ve pushed my buffer a bit to try to reduce crashed and prevent CPU spikes that make audio crackle and audio bounce impossible.
I recommend to use 512 as block size, rather than 384.
Or even 1024.
But the best is usually a multiple of 512.
Thanks @PG1 i’ll try that and let you know.
i guess idealy the best would be to buy a new powerfull computeur.
but it’s not for this year
i’ve switched to 512,
and Sadly it crashes again unfortunaltly :
GPT says and ive got no idea what it exactly means to be honest :
”crashes with WaveLab Pro 12.0.51.15 on macOS 15.7.2 (Intel, x86_64).
On the latest crash, WaveLab terminates with EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS at 0x0000000000000008in thread “Playback Audio Queue”. The entire call stack at the top is inside the WaveLab Pro 12 binary (no third-party plug-ins and no baios or CoreAudio2ASIO frames at the top), which suggests a null pointer dereference in WaveLab’s internal audio playback queue.
Earlier the same day, I had another crash with the same low-level signature (EXC_BAD_ACCESS, invalid address 0x8), but this time in thread “BAIOS”, with the stack going through baios.bundle. In another previous crash, the “Playback Audio Queue” thread was running through TDR Infrasonic before returning into WaveLab, again with the same kind of invalid address error.
Taken together, these crash logs seem to point to an instability in WaveLab’s audio engine / playback scheduling on my system (WaveLab 12.0.51 + macOS 15.7.2), sometimes surfacing in the BAIOS thread and sometimes directly in the “Playback Audio Queue” thread in the WaveLab binary.”
Hi @PG1
Just to let you know.
It’s better.
I’ve reinstalled Mac OS sequoia, and merging drivers (+6ms). Remade all merging patches.
Updated pluggins.
Choose 1024 buffer + 100ms asio Gard
we’re arround 1600ms on the playback delay
Still not perfect but not crashing anymore.
Thanks for the help.
The part that would be great to improve is the delay on analog return.
I m on the a similar layout as Justin; in a montage
Play clip with plugs on ref track, out on analog loop,
return on stereo track. A limiter dither et. On out slots.
Monitor with 3 pluggins.
Do you have suggestions on tweaks to get less delay on the loops back ?
