Tank you. I’m going to delete the preferences and I’ll keep you updated on what happens next.
I deleted the preferences folder. Unfortunately this did not solve the problem. The noise did not go away. If you want I can send you the driver report from Latencymon but I don’t know how because it is a text file and not a jpeg. If you want I will try to simply copy it but it is very long
This cannot be useful to me.
Do you have another audio device to try with?
I tried with an Audient EVO 4. Same situation. On the desktop it works and on the laptop it doesn’t. The funny thing is that the two have almost the same components. Same video card and I tested the same sound cards on both. Here’s how I see the situation. It seems logical that way. I have another system, a Dell Laptop with the same NVIDIA GTX 1050 chip, and WaveLab 13.0.10 works PERFECTLY there.Both systems run Windows 11. This proves that the software is not inherently broken, but it has a critical incompatibility with the desktop architecture (Z390 PCIe bus/NVIDIA driver combo) that was not present in WaveLab 12. Version 13 is failing where version 12 and Nuendo succeed on the exact same desktop hardware.
I have compared two systems with NVIDIA GTX 1050:Dell Laptop (Intel HM370 chipset): WaveLab 13.0.10 works perfectly. Fluid graphics, no noise.Desktop (Gigabyte Z390 Pro): WaveLab 13.0.10 freezes and crackles, while WaveLab 12 and Nuendo work fine.Both have 32GB RAM and run Windows 11. This is a clear indication that the new v13 engine has a synchronization bug specifically with the Z390 desktop bus/NVIDIA combo, which was not present in previous versions. My laptop proves the software can work, but my desktop proves the new engine is regressive on certain hardware architectures.
Do you mean that on your desktop machine, you have the same problem using two different audio devices, from two different manufacturers?
It does not do any synchronization: WaveLab sends the audio to the driver, then audio device driver is in charge of playing the audio in a steady sample rate. WaveLab is totally hardware agnostic. I mean, WaveLabt does not behave differently according to the hardware.
That’s what I said. Like two different audio hardware produce the same noise on my dextop. Probably if I test another one but I only have two the same thing happens. On the laptop both work perfectly. So in conclusion it’s not about the sound hardware.
If you have the opportunity to test on a system identical to mine, i.e. motherboard, processor, video card, RAM, you would hear exactly the noise that I hear. It is best heard on a single channel, even mono, in the simplest stereo audio montage, not atmos or ambisonic. After a few seconds, maximum four, a distortion delay appears that imitates the real audio file but is its distortion. If I have two channels, each distortion repeats exactly what happens on that channel. If I play your demo project called Demo Adm for Dolby atmos mastering, I hear hundreds of repetitive distortions simultaneously, depending on how many tracks there are. Initially I thought it was only on atmos montage projects, but it appears on any audio montage project, even on stereo.
I don’t have such a system. There are many of thousands of WaveLab 13 out there, and the Steinberg technical support has not received a single case like yours so far.
Therefore, there is something very special on your system. This is not necessarily hardware, but I have no clue, unfortunately.
The fact that it does not happen on WaveLab 12 is even more strange because the playback engine, apart Atmos, is really almost the same in WaveLab 13.
I might be wrong, but independent of the bad quality, the music seems to play a bit faster than the original. This is like if some low-quality time stretch were applied to it.
What are the exact references of the two audio devices you have tried with?
What ASIO block size are you using?
-
512 or 1024 or more but usually 512
-
Sreinberg UR 24C and Audient EVO 4
-
You noticed well but I already wrote this to you. I wrote that the project apart from the noise tends to accelerate the tempo without changing the pitch of the sound. Look, now that you also have a movie in which you saw exactly what happens I’m not writing to you anymore because I know you’re busy. I just ask you to put my problem on a list of possible problems of the program and maybe in the not too distant future you can find a solution for me too (an advice or an update that would also include the solution to this problem). Until then I won’t bother you anymore but I want you to try to put yourself in my situation. Thank you in advance!
Obviously, if you ask me anything technical about my system, motherboard, installed software, etc., I will answer you immediately.
I solved the problem! I had a driver installed called VB-Audio driver. I never kept it open but it seems to be working in the background even though I didn’t open it. I used it before for zoom meetings where I was viewing audio projects. I uninstalled it, restarted the system and wavelab 13.010 works flawlessly now. Thank you very much for your support and time.
Indeed, this is a low-level driver that can manage system audio streams.
I am happy you found the problem 
Thank you for all and for 13.020!