It wonâtâŚItâll still be there in 10 with no acknowledgment and by 10.5 theyâll be like oh and we fixed the mixer GUI that a few users reportedâŚ
I have no GUI issues ???
Well the visual metering background is off when using win10 as a OS, but that has no consequence in functionality and can just be ignored.
Theyâve been able to reproduce it but those of us who do have the issue have been just left to deal with it. It causes real problems when you click and edit settings thinking youâre working on one channel, only to find out later that youâd changed settings on another channel because the mixer window had not redrawn. Not sure how you can call it professional when it does this. Itâs not professional when sat in front of clients and it happens. Not only do they see it too, but also it makes you look unprofessional. I mean, come on, Steinberg, this is version 9.5.
I would start looking for errors in your Windows system.
things to try
run sfc /scannow
run DISM command to try and find issues
full reinstall of Cubase (uninstall, delete /appdata Cubase folders (trash prefs)
update graphics drivers
In my support request, the head of support at Steinberg acknowldges it. Itâs related to the redraw reductions they did in 9.5. v9.5 uses a different graphics api in the code.
By the way, I went through all the stuff beerbong mentioned and a lot more months ago. Itâs not a system file corruption, it was a clean system to begin with and I even re-installed from scratch, including re-installing Windows.
If they (Steinberg) have reproduced it, and you received written conformation from Steinberg, ask for the specific issue number. The number will start with a C or B depending on the time it was entered. Or, ask Martin on this forum to confirm itâs an issue that was entered, and its current status.
Also, and not to diminish the issue, but this is not reproducible on very many systems. Obviously if it was, hell would be breaking loose everywhere. In the VI Control thread, you didnât give reproducible steps. Reproducible 100% of the time? Does it happen when opening a clean default project? List each step, starting with how you open the project to generate this.
Also list the operating system. Do you get the same issue with Windows 7 and 10? Running both Windows 10 and 7, as it shows in your signature, at the same time might not work very well.
It is still open with Steinberg, with the only reply being several âweâll get back to you on thisâ. Other people are getting the problem too, on Windows 10 and 7. I can recreate it from an empty project, just need to add tracks as per above.
Because of the nature of PCs, it is true it may not be reproduceable on all systems. As you say, I know people myself who do NOT have this issue with v9.5, and some who do. However, weâve not found any specific hardware setups with which the bug occurs. Iâve seen it on a colleagues studio PC that has an entirely different motherboard, architecture and brand of graphics card. But it is a bug nontheless, as Steinberg acknowledge.
The consistent thing those who I know who have this issue is that it is only with Cubase 9.5. It doesnât happen with 9 or 8.5 or 7.5 (or any other software of any kind on the computer).
Given this, and that theyâve reduced re-drawing in the code, and the fact Steinberg are using a different api on the graphics in 9.5 to previous versions, it is pretty obvious.
If you mouse over the parts that look corrupted, Cubase redraws, revealing what should be there. Some artifacts are left. Itâs definitely in the code, though. If you click on what you think is a plug-in for one track, because the mixer view is corrupted, you end up changing settings on that before you realize itâs actually a different track.