Since I installed Wavelab 13.010 I have the following problem: Only in dolbi atmos projects, even in some with a small number of tracks, a strange noise like glitch and pop is heard next to the music, and the image in the phasescope and loudness meter freezes. If I try to open Dolby atmos 3D view, its volume meter freezes instantly and the balls no longer spin but freeze too. I use Windows 11, SteinbergUR24C, Intel cofee blake, 32 GB Ram, and Gigabyte aorusZ 390 Pro Wifi. Any advice would be welcome. I have tried many settings that did not solve the problem.
This looks like a performance issue. Atmos requires a lot of power.
You mention your processor’s family, but you do not specify what your processor is.
Thank you! Is Intel I7 Cofee lake. I also have Nuendo 15. In Nuendo I don thave this problem. When I installed WL 13.00 I didn’t experience this. I did when I installed 13.010. then I uninstalled and went back to 13.00 but unfortunately the problem persists so I went back to 13.010. Anyway, I noticed that this happened shortly after I installed I think the last update from Sonarworks. I took it out of the common file to see if it still does it and it still does it. I don’t know if it’s Sonarworks’ fault or it was just a coincidence. I would really like, I don’t know if it’s possible, that with the next update I no longer have noise on Dolby Atmos projects. Otherwise I have absolutely no problems. However, it wasn’t like this the first time. That’s why I’m asking for help. My processor and 32 GB RAM should handle an Atmos project that only has 4 beds and 1 object! I loaded the same project into Nuendo 15 and there is no noise there! The sound is very clean and the processor is somewhere around 20%.
There were very few changes between WaveLab 13.0.0 and WaveLab 13.0.10.
Then Sonarworks is more likely involved, though I ignore how.
If you do a re-render from WaveLab, does it play with the same noise as when you play it from the audio montage?
The render is perfect. I did binaural render, 7.1.4 render and 9.1.4 render. Everything sounds perfect! The problem is only when playing in dolby atmos mastering editing and what is seen, that is, the image freezes. Otherwise, the final result is ok. But.. it’s very difficult to work when you hear something that flows next to the music.
Someone replied to your post.
| PG1
April 27 |
- | - |
There were very few changes between WaveLab 13.0.0 and WaveLab 13.0.10.
Then Sonarworks is more likely involved, though I ignore how.
If you do a re-render from WaveLab, does it play with the same noise as when you play it from the audio montage?
Do you have a powerful graphic card? Displaying the 3D view is resource-demanding.
By the way, what is the CPU consumption as displayed in the transport bar of WaveLab? This only concerns the audio part, not the graphics.
The Audio Processing Load in the transport bar remains very low, between 3% and 5%.
Even with the Dolby Atmos 3D window closed, the rhythmic noise persists. However, the noise only appears when the Atmos renderer is active in the montage. If I perform an offline render, the result is perfect.
This suggests that the issue isn’t just about GPU drawing, but rather how WaveLab 13 manages the real-time ASIO buffer and metadata synchronization when the Atmos engine is engaged, causing DPC spikes even without the GUI visible.
My graphics card is an NVIDIA GeForce GTX 1050.
I have set it to ‘Prefer maximum performance’ and disabled all 3D enhancements (AA, Lighting).
Despite the very low Audio Processing Load (3-5%), the rhythmic noise persists even with the plugin window closed, which suggests the 1050 driver might be causing DPC latency spikes when WaveLab’s 13 immersive engine is running
I have applied all Windows and NVIDIA optimizations (Background Services, Max Performance, HAGS Off, 3D features Off). The Audio Load is still only 3-5%, but the freezing and rhythmic noise are identical. The issue persists even on a native USB-C connection direct to the motherboard.
Do you have the possibility to test with another audio device?
Did you close the 3D View tool window? (I’m not speaking about the 3D view, but about the tool window.)
I tried it on a dell laptop and an audient evo 4 sound card and everything worked perfectly! I took the evo home and put it on the computer with the problem. Same situation, noises and frozen graphics and with audient just like on the UR 24C. Even on High Performance power plan and with the Audient Evo 4, the desktop still freezes while the Dell laptop works perfectly. I have confirmed that both systems have similar power settings in Windows, yet only the desktop suffers from this rhythmic noise at 3-5% CPU load. I am now forced to go into the BIOS to disable C-States and Intel SpeedStep to see if a hardware-level clock stabilization fixes the Atmos engine sync.
The audio starts to accelerate (tempo increases without pitch change) after a few seconds of playback. I tried forcing a constant platform clock (HPET) via CMD, but it made the whole OS sluggish without fixing the WaveLab issue.
Since the offline render is perfect and the issue exists on my desktop (Z390) but not on my laptop, it seems WaveLab 13’s real-time engine is failing to sync its internal timeline with the ASIO clock on this specific hardware, causing the audio to ‘run away’ while the GUI freezes.
This cannot be the explanation. At the same time, I have no explanation for your case!
New discovery: The issue is not specific to Atmos. It happens in any Audio Montage, even a simple stereo one. After 8 seconds, the noise starts, and after another 8 seconds, the meters freeze.
However, playing a standalone Audio File (even 7.1.4) in the Audio Editor works perfectly with no noise and fluid graphics. The problem is strictly isolated to the Audio Montage engine. It seems like a buffer management issue between the Montage’s real-time processing and the ASIO driver on my system.
I have a very important technical update: The noise that appears after a few seconds sounds like a short, distorted feedback delay of the original signal (observed clearly on a kick drum). It’s like a buffer wrap-around or a recycling of the audio buffer.
This happens ONLY in the Audio Montage (even in stereo), while the Audio Editor plays perfectly. This confirms that the Montage’s real-time buffer management is failing to sync or clear correctly on my Z390 system, causing audio to repeat and eventually freeze the GUI.
Well, I am sorry for what you experience, and I have no clue about what’s going on in your computer.
WaveLab is being tested on various hardware, some of which are not powerful, and what you observe was never reported. This looks like some interaction between your media, the graphic card and your audio device. But I know that saying this won’t help you.
Just in case, make sure do not use the following option, which is very demanding on the hardware.
First of all, thank you for the answer and please believe me that I would not waste your time or mine if I did not have this problem. By default I keep the view follow cursor but whatever I put it does the same thing. Probably the least resource consuming would be static view. Here’s what I did. I reinstalled Wavelab12 PRO. I made an ambisonic 30A montage (16 channels) It sounds perfect without any additional noise. I saved it and opened it in Wavelab 13 PRO. The same noise is heard as in all other montage projects. In conclusion, on my system it works perfectly on 12 and with background noise on 13. I bought the wavelab 13 update the first day it came out. From wavelab 6 until now I have been a loyal customer. My system, processor, 32GB of RAM and aorus Z390 PRO motherboard are not found on equipment with which Steinberg programs would not work. As proof, Nuendo 15 works perfectly, wavelab 12 the same, 13 also worked for the first two weeks then this problem appeared. I am not to blame for this. I am just a customer who constantly pays money for the software I work with. I would really like it to work as it should. I have no one to ask for help except you because you made this program. Please solve the problem. Thank you in advance.
Then at this stage, it is absolutely necessary to try to remove all preferences:
While WaveLab is not running, clear this folder (make a backup to preserve your presets).
\AppData\Roaming\Steinberg\WaveLab Pro 13
I have conducted a thorough test with LatencyMon while the Montage was noise-glitching.
The results are 100% GREEN.
LatencyMon concludes: ‘Your system appears to be suitable for handling real-time audio and other tasks without dropouts.’
This is a definitive proof. Since the system latency is perfectly fine (confirmed by LatencyMon and the fact that WaveLab 12 works flawlessly), the rhythmic noise and GUI freezing in WaveLab 13.0.10 are strictly caused by an internal bug in the new Montage engine. It is not a hardware, driver, or Windows configuration issue.