That’s not what I’m reading.
I’m reading people asking for specific scenarios so we can attempt to duplicate your issue. People are ‘trying’ to be helpful.
At this point we know very little about your situation. We don’t know if you’re working at 44.1k, 192, 16bit, or 64bit. We don’t know if you’re wired with coax, optical, wireless, ethernet, or none of the above.
All of the things people are listing…they do it because they’ve had experiences where ‘that was their issue’ at some point. It fixed it for me, no promise it’ll work for you, but here’s what “I” did.
I kid you not…I fought with a problem once for years…found out by total accident the problem was a specific make of SATA3 SSD drives I had been using (I bulk ordered several, and they ALL had the same issue with AV streaming). It was doing IRQ interrupts to Windows that caused hangs, slow downs, audio glitches, and none of the latency monitors reported that it should be a problem. The drives bench marked and stress tested like a freaking champ! By chance I discovered that pulling those drives meant I never had those problems again. Put one back in, even if it’s not being used/touched by Cubase for the session, and the problems return. There’s a 1 in a zillion chance that others will suffer from this exact same problem…but since it happened to me, I offer it up on the ‘try this’ list when fellow users are stumped with a problem that ‘seems’ similar to my experience.
I have found and reported a few bugs to Steinberg over the years that really were on them, and they were promptly fixed. Stuff nobody else had found and reported with enough details for the folks at Steinberg to duplicate, isolate, and correct the problem. In at least one case it involved uber obscure hardware dependent legacy features that few people ever used past or present.
With a good test project and instructions to follow, teams were able to duplicate it in the lab…every single time. It set off their debuggers and such…and they were able to promptly fix it.
Step ONE. I’m on windows, so I run dxdiag to get a print out of my system specs…it provides info about all of my hardware and how it’s configured at the BIOS/FIRMWARE levels, precise driver versions, IRQ assignments, memory addresses, and more.
Step 2. I craft a test project and document step by step what I am doing when the problem shows up. My preferred method over the years has been with screen shots and text in a word processor, but it’s fine to do full motion captures while talking in a mic if it works better for you.
Finally I zip up all the system and app logs I can find and include that in the report along with my sample project, docs, and dxdiag reports.
When somebody at Steinberg gets my project, they can load my specific project. They probably also have dev tools where they can examine every detail of my project files before they even attempt to load it. They follow my instructions and see if the bug shows up in their lab.
So many things can and do go wrong. In fact, once upon a time I had a corrupt starting template file in Cubase I was attempting to use. Trashed the template, built a new one, and never had a problem again. Perhaps a ‘Steinberg bug’ led to the corrupted template, but until it happens AGAIN, and can be reproduced on demand, nobody has a clue where to even begin searching for that ‘potential bug’.
Other times I’ve had various MIDI/MCU/OSC/MTC/ETC remote control scripts or sync settings that were duffed (my own fault), and they were chewing up enough of something important in the system to wreak havoc.
It’s a FACT that MICROSOFT has been making changes to the core MIDI services. LOTS of things MIDI were ‘broken’ in Windows 11 for a lot of folks doing MIDI on Windows machines (Virtual Port options, various drivers from different manufacturers that’d worked fine for decades, etc). Back in November of 2025, I had to go on Discord and grab a BETA KSA to fix Microsoft’s buggy MIDI server and get my rig going again. The official fix didn’t come out until MAY of 2026.
I don’t believe anyone means to insult you with these suggestions. People are just trying understand ‘exactly’ what you mean. If users know the steps you’re taking, and look at some of your projects, etc…then perhaps we can DUPLICATE the issue and help you fix it if it’s something other than the App, and the devs put a dart in the problem so they can fix it if it’s an app bug, test the fix, and get it in the next release.
For what it’s worth, I’ve used Wavelab 12 since the day it came out. My system is a snail compared to yours, and I’m not having the same issues as you describe. That doesn’t mean their aren’t ‘bugs’, it might simply mean I haven’t tried to do the things you’re doing. Maybe I’m using wav where you’re using aif. I don’t have the same plugins installed. I’m on AM4 with DDR4 my rig is so old…different ‘everything’ in my rig. I’m using PCI interfaces (through a PCIe bridge), so my audio drivers, system performance, etc, are going to be QUITE DIFFERENT from folks using cutting edge Intel Core or even newer AM5 rigs, folks using USB/Thunderbolt/PCIe interfaces. I’m routing everything through a dirty ASIO Link Pro back end, while most Cubase Users do not. I’m using a pretty old barely mid-range AMD Graphics Card, others out there are on something totally different.
Bugs are real…they can come from the apps, OS, drivers, hardware issues, and the list goes on.
To track down and fix them, specific information and example projects are critical.
You say it’s also giving you grief on a Mac. I believe you! Thing is, people can’t help sort it out if they can’t duplicate the problem. People will make ‘guesses’ and ‘suggestions’ on things to check…simply because they’ve ‘been there and got the T-Shirt’, the ‘suggestion’ happened to work for them.
