That is indeed odd. Does this only happen for Cubase 14? What happens if you run Cubase 13, or even Cubase 12?
This is what you do to cause those extreme graphics glitches? If you un-maximize a window using the window button top right it doesn’t? Is it repeatable, as in does it happen every single time?
PS
I can’t remember if you could move a maximized window by grabbing the title bar in Windows 7, but in Windows 10 you can.
That seems unlikely.
I just tested it in Nuendo 13 and it works as expected. I pull the window from the title bar to make it not maximized and it gets a certain size. I resize the window and then snap it back to full screen. Drag it down again and it perfectly remembers the previous re-sizing. Same if I use the icons in the upper right corner.
Since Cubase and Nuendo share most of the code I doubt you would have that problem because the code was “old” and I wouldn’t.
The problem with resizing is something I could see just in general being a problem with the program, but the problem you’re having with the window being “smeared” / “repeated” (last image) to me looks like something outside of the DAW. It really does. That is what I was referring to when I said I’ve never seen anything like that coming from a problem with a DAW. And if that happens for a reason outside of Cubase then perhaps solving that will solve the resize problem.
Last time I had something like that happen it was either a driver issue or a hardware conflict. If it was a hardware conflict the way I did troubleshooting was to strip the computer down by removing hardware from the motherboard and then adding things one item at a time. Adjusting BIOS settings was a part of that.
I think when that happened to me last the problem was a driver being corrupted for some reason because the system got unstable, and the system got unstable because a “splitter” / chip on the motherboard couldn’t handle a UAD-2 Quad card I had inserted. The lanes should have gone from PCIe x16 to x8/x4/x4 and the system just wouldn’t do some things with that configuration. Take the card out, reinstall drivers, no problem.
For troubleshooting if I were you I would probably look at the board to see if there is any PCIe sharing going on and if there is stop that sharing. Additionally maybe test the memory to verify it’s good.
1 Like
Guys, there is absolutely no CPU or GPU hardware glitch that cause a window to become gigantic once it’s pulled down from maximized state. It simply doesn’t make any sense, because in 30 years of using computers, I have never come across anything like it, even with the crappiest of computers that had a terrible CPU and GPU.
I’m not going to do any of that, because I know this is NOT caused by the CPU. The only Intel utility I have is that one that you download to see if your 14900 series CPU was in one of the batches that had that overheating problem, so it checks your CPU and tells you if it was. In my case, it told me it’s perfectly fine.
Added to that, I set the BIOS to not do any overclocking of any kind, setting all the options to the Intel profiles, not the Asus ones, which are known to cause overheating. The CPU is more than fast enough without needing to shorten its life by overclocking it, I don’t understand why would anyone want to do that when these days there’s barely anything that is done by the CPU, and for the things that do, this CPU is insanely fast without OC.
I built this machine in January, when I already had Cubase Pro 14, so I never installed 12 or 13 in it.
Good question, but just now I tried that and it sent the window to another monitor that is on but not in that input, which is the TV set. When I brought it back to the main monitor with shortcuts, I tried it again and I couldn’t get the glitch. So I wouldn’t say it happens every single time, but it happens about 95% of the time, because every tine I start working on a project and I start opening the key editor frequently, I get this bug all the time.
Sure, I also just tested Nuendo 13 briefly and it works just fine.
Whatever it is, this is a problem with the windowing system, whether Microsoft changed something that messed up the API that Steinberg is using for Cubase 14, or anything else, I don’t know, and it’s not my problem. But I’m sure this is something they need to fix.
The window being smeared or repeated would lead me to think there’s a problem with the GPU only IF the same problem manifested itself in other programs as well. Guys, this is simple logic: if there’s a bug happening in just one program, the problem is THAT program, not the hardware, not the OS, not anything else. It’s that specific program that has that specific bug.
Whatever was that problem you described, it has nothing to do with mine. As far as PCIe sharing, the reason I have four NVMe drives and not five is because if I install the fifth, I would have to share that PCIe slot with the graphic card, because that slot is Gen 5, so if you only have the card, which is my case, it works at x16 but if I install the NVMe Gen 5 and the graphics card, they share the same PCIe bus, so I left that NVMe slot empty, and all the SSDs are installed in the rest of the NVMe slots.
Also, this past Monday I opened the machine, used an electric blower that blew every tiny spec of dust from inside the machine and installed the 5080 card. So there’s nothing wrong with my machine, it’s the code in Cubase that has some kind of incompatibility with perhaps just Windows 11, I have no idea. But again, when something happens in just ONE program, it’s not the hardware, it’s not the OS, it’s not user error, or anything else you can imagine. It’s a bug in that specific program.
I stress tested the hell out of this machine even before I installed Windows in it, and then afterwards. I still do sometimes, and almost every night, this machine is left rendering from Blender all night long, then it’s being used almost all day long. That’s why I built it with expensive and high quality components, because I needed a machine that could take very heavy use.
But you can use the same logic also like this: “if there’s a bug happening on just one computer, the problem is THAT computer, not the software, not the OS, not anything else. It’s that specific computer that has that specific bug.”
See what I’m saying? You isolated Cubase specifically but only on your machine, meanwhile unless I’m missing it nobody else has the same problem while using the same software.
I think all of us are just trying to give you as many parameters as possible to look at to troubleshoot this. I don’t think anyone is blaming you for anything, so hopefully you take it as such; an effort to find what’s wrong.
Thought: Have you tried uninstalling Cubase and then reinstalling it? Because it would seem to me that if the problem is Cubase and nobody else has a problem then a screwed up install would explain that.
3 Likes
looking at those screen shots that’s definitely a GFX card/Hardware issue.
I’ve run Cubase since Atari days and never seen anything like this.
M
1 Like
Okay, I understand. But would you mind trying it out? Then it would either show the same behavior for Cubase 13 or 12 (bad to figure out the real cause) or if not, you can point the finger on Cubase 14. But without trying it, it’s a hard time guessing what’s and where it’s going wrong.
I can see that, except that I know that at least one other person, who posted above, has a problem that is at least in the same vicinity, meaning, GUI chaos when he pulls down the key editor window that was maximized:
Added to this, I have no way of knowing if anyone else in the whole Cubase Pro 14 on Windows user base has this problem or not. There may be plenty of people that have it and didn’t post about it.
But I do know one thing for sure: in my machine, this doesn’t happen with any other program that I have installed. And I have quite a lot.
That’s fine, and I appreciate it, but you guys keep going around in circles, trying to pin on anything BUT Cubase, when simple logic indicates that it is Cubase. Steinberg support just replied to me about an hour ago, now trying to blame it on my cables and my connections. What the hell does that have to do with anything? Sure, if I was having this problem with everything else, or even if the screen went off and on when I touch the cables that go from the computer to the monitors, I would replace the cables. But the cables are perfectly fine. I don’t buy the cheapest stuff for anything. I don’t buy grossly overpriced cables because everyone knows they’re a scam, but I buy good cables. And cables will never cause the kinds of things that you see in my screenshots and photos.
If a monitor cable is partially broken, the signal would go off and on, especially if you move the cable around. It wouldn’t cause a window that you de-maximize to enlarge horizontally to the width of three monitors.
I don’t have any problem saying that my there’s something wrong with my machine if there is. I don’t have special feelings for my PC, it’s a thing, a tool. But if I repeat, over and over, this ONLY happens in Cubase, and not anything else, and everybody else keeps saying, it might be this or that in your machine, well, it’s gets old.
Not yet, I’ll try that this weekend. I installed Cubase Pro 14 when I built the computer, and then every update that came after that.
I could be wrong but I believe the glitch issue and issue of overly large windows are separate and should be addressed and approached as such.
But this logic doesn’t hold water due to the simple fact that this forum isn’t flooded with accounts of problems identical to yours.
If I were you and experienced the graphical glitches you have shown using 3 different graphics cards, I would bite the bullet and reinstall everything fresh.
1 Like
Like I said, to me it’s not simple logic that it’s Cubase if nobody else is having exactly your issue.
More importantly though I’m not pointing the finger at Steinberg simply because they already engaged with you and are apparently dismissing that it’s their fault, so like I said I’m just trying to give you as many things to investigate as possible. And ‘yes’, blaming cables seems like bs.
Hopefully a re-install could solve the problem.
Which is not enough proof that nobody else is having this problem, and like I showed above, at least one more person is having this problem or at least something extremely similar.
You mean reinstalling everything Steinberg fresh, or a drive wipe and clean install of Windows? The Steinberg cleanup I’m willing to do, the other, I’m not. It would take weeks because of the amount of software and VSTi libraries I have, and unless there’s irrefutable proof that it would solve this problem, no chance I’m going to go through all that.
If you missed my reply, we know that at least one more person (that we know of) is having this problem. The fact that nobody else has posted here doesn’t mean that nobody else has it.
Well, to me it’s very disappointing that a company like Steinberg, which in my short experience until recently, makes very stable software (Cubase on Mac is more stable than Apple’s own Logic Pro), and instead of asking me for the Sysinfo report and taking a good look at it, they dismiss it as “it’s your graphics card”. I would never do that. That’s terrible customer service. I would work with the customer, asking him for the Sysinfo report and other reports from other similar programs, and tell my software engineers to take a look at the part of the code that deals with interfacing with the windowing system, and see if anything catches their attention.
The worst thing you can do to any customer that has a problem, is try to blame it on them. That has never worked for any company in the history of the world. The only thing that it accomplishes is to leave a customer unhappy with your brand. Do it more than a few times, and the customer takes their business to your competition.
And I can tell you one thing I just realized about Cubase 14. Steinberg did something to the GUI, and I’m not talking about minor details here and there, but a big one. While I never installed Cubase Pro 13 on this PC, I did install Nuendo 13, because I don’t have Nuendo 14, and probably won’t get it. But Nuendo 13 is Cubase Pro 13 with several things on top, but they share most of the code. And Nuendo 13 on PC has two things that are very different from Cubase Pro 14. The title bar and menus don’t abide to the dark theme in the OS. They are white, or soft white. I’m really glad that Steinberg changed that in Cubase 14, because I’m used to work on macOS for several years, and macOS doesn’t do the half assed dark theme that Windows does. In macOS, if you choose dark theme, everything is dark.
So there is a big change there, and my guess is that there’s something in the GUI code that was left from Cubase 13 and doesn’t abide to the current Windows 10/11 internals. I know that Cubase has a skin, because if you take a look at one of my photos:
you can see that the GUI mess somehow removed the skin from that window, and what you see is the basic old GUI that started with Windows 95 and NT. So Cubase 14 doesn’t have the same GUI code than the previous versions.
Wow, if the Steinberg team did this for every user that had a problem with a PC component (example a graphic card) the whole thing would grind to a halt. More staff would have to be employed and the cost of the software would jump through the roof.
Maybe test a different graphic card, cables and even monitor set-up. Does the problem persist if you only use one of your monitors? These are the areas I would be looking at.
I don’t think we imagine that happening the same way. The way I see it, the software engineers at Steinberg are very familiar with the code, so any of them would know where to look, it wouldn’t take that long. It’s not like giving the entire Cubase Pro 14 code to some new coder and tell him “Here, find out what’s wrong with the GUI”
What, three cards are not enough for you?
Sarcasm or not the more you insist on blaming Steinberg for your issue the less chance you’ll have of ever getting it sorted.
You expect Steinberg to put their resources into your computer problem but can’t be bothered to try your own trouble shooting.
Does it happen with one monitor connected, does it happen with all versions of Cubase 14. Have you bothered to download and test Cubase 13, 12.
Why does nobody else including myself with three different PC set-ups have this issue.
Yes I have seen this type of graphic glitch before and it’s always been down to a graphic card or graphic card software.
Rant, pass blame and attack all you want but that’s not going to resolve your computer graphic issue.
I honestly hope you get it resolved. Take care.
It’s not sarcasm. I said this happens with three different cards, and you say “Maybe test a different graphic card”. That’s why I’m asking how many cards do you want me to test before you realize it has nothing to do with the card?
I expect Steinberg to write code that is stable, like the macOS versions of Cubase Pro 12 and 13 that I used on my Mac Studio for years, and I don’t know if 14 is just as stable in macOS as 12 and 13. So maybe I’m used to Cubase being very stable, and when I come across this, it’s very disappointing.
And as far as not bothering to try my own troubleshooting, I don’t know why you say that. I already said that this weekend I’m going to uninstall every piece of Steinberg software, clean the leftover folders, and reinstall again. Also, before that, I’m going to take some steps that Steinberg support asked me to do and report back to them.
I don’t blame you for not reading the whole thread because it’s long, but like I already said, there’s another person in this thread that has the same problem, or at least close enough. In his case it’s worse because it requires him to restart the PC.
It’s not a rant, it’s just fact. It is NOT my graphics card, this is NOT a graphics card issue, or it would happen in other programs. That is simple logic, I don’t know how else to explain it.
Wow, I’ve never seen anything like this with Cubase before, and I’ve used Cubase Pro on Windows from 7 - 14, Windows 7 - 11. I’ve always run 3 or 4 monitors too (albeit older ones that max out around 1920x1080).
I have seen screen tears and such on cards with bad memory, duff cables/connectors, borked drivers, when they get too hot, or simply demand more power than the supply can provide…but never with Cubase like in your screen shots above.
If Steinberg can’t replicate that issue in the lab, there’s no way they can offer support or fix it.
It does this same thing to you with only one screen? Different graphics cards? What about a larger power supply? Have you ever seen it act like that on any other system before? Could the Windows installation itself, or perhaps one of the zillions of ‘extra libraries’ different software might install be borked?
I apologize for being yet another, “It works fine for me.” forum dork. I could make some suggestions on how to trouble shoot the system, but it seems like you’ve tried that already.
Would you mind posting a DXdiag report for forum browsers to check out?
You could be CORRECT. It might be an issue with the code, or perhaps a compiler/driver thing deep in the developer’s tool box.
Thing is, to find a fix, it’s essential to discover the exact point of failure through a process of elimination.
I.E. Start with a fresh system drive with a fresh OS install…take things away until it works properly, add things back with minimal features enabled at first, enabling features and such in each bit of hardware one bit at a time until it breaks again, etc…
Some graphics cards have a zillion little features and sub-features that can be toggled about. Some require specific settings on the motherboard BIOS (that also might require bios firmware updates). CPUs and GPUs themselves often require micro-code updates to get everything intended working properly. It might well be that yours is properly set up to support something that Cubase isn’t handling properly.
Who knows…but it’s hard to ‘fix it’ without loads of tests.
I HAVE seen and reported GUI issues in Cubase before (12 had quite a few when it was first released), but never the screen tears, reverting back to XP windows/elements, etc. That’s seriously messed up! It ‘might’ be Steinberg’s fault…but it’s going to take some ‘digging’ to find a way to make a report that they can replicate in the lab.
Is your Cubase installation (or anything relating to the graphics drivers and such) setup to attempt to run some things in ‘Windows Compatibly’ mode? If native Cubase GUI elements are reverting back to XP libraries, that’s truly odd…what might cause that? I have seen some ‘plugins’ do stuff like that, but I can’t say I’ve seen Cubase native elements, nor any Steinberg plugins do it in a very long time. I have to roll all the way back to Cubase 3 or so, and put it in Windows Compatibility mode to get XP looking GUI stuff.
OK, I just saw that…
So you get this with a single screen on three different cards? That would suggest that the point of failure may well be with something else. Perhaps a BIOS setting in the motherboard? Corrupted Windows/Driver Installation? Power supply? Monitor/Cable?
You say it never happens with any other software, only Cubase. What other software do you use that manages multiple windows over multiple monitors at the same time?
I understand your frustration, and maybe it could be Cubase. But here’s the thing - don’t underestimate how screwed up some 14th gen Intel CPUs can be. I’m just tackling this particular corner - if you feel it really isn’t, then fine.
Try updating your Intel Management Engine drivers, if they’re not already updated. DO NOT UPDATE BIOS - just the IME drivers. They are the key ingredient for your graphics hardware to interact with your CPU and all software.
1 Like
Your problem is such a biggy that if this was a Cubase problem this forum and the FB Cubase pages would be inundated with angry costumers.
The fact it only happens with Cubase doesn’t mean it’s the software, your logic is wrong.
And certainly one other person in the whole of Cubase world having (not even the same) graphic issues means it’s a bug.
Did I read in this very wordy thread that you built this PC yourself?
I wonder how many PC Cubase users have very stable graphic set-ups .. compared to your one user on this thread with a SIMILAR issue.
It’s a issue with your set-up.
I don’t know how else to explain it to you.
Well, then that says everything about the way you see things, or you do understand that this is common sense, and you’re just trying to argue for the sake of arguing.
Yes, and I’ve built many PCs in the last 20 years, and I know how to build them well. The ones that I know off still work fine to this day, with the exception of the hard drives of course, because those can stop working from a moment to the next.
In fact, a PC I built in 2012 is in another room as a render node, rendering from Blender almost 24/7 and it works as fine as the first day.
Most definitely it’s not, and I think you know it, but you’re one of those people that only want to tell others that they’re wrong to feel good about themselves, so I’ll just ignore you.
That’s not a bad suggestion, but it’s not going to happen. For one thing, just installing all the virtual libraries I have would take over a week, especially when not all companies are known for having the best servers. Spitfire is downright terrible, at least for people in the US, Native Instruments is great for their own instruments, but they cap the download for their 3rd party libraries quite a lot, and Orchestral Tools is not terrible, but tends to stall at certain times. Since I have about 2 or 3 TBs of OT libraries, another 2 of Eastwest, and many more, that’s an amount of time I’m not willing to waste.
Now, if this was a widespread problem, meaning, if there were at least 5 programs on my PC that when I detach the maximized window, that window becomes gigantic and goes farther than the edges of the screen, then I would think about it. If it happened with all the programs, I would have done that a long time ago, and I would have never though Cubase had anything to do with it.
However, this issue happens ONLY on Cubase Pro 14 and Nuendo 13. I bet that if I were to install Cubase Pro 13, it would also happen with it, since it happens with Nuendo 13. Now, despite the bold statement of some people that don’t see this logically and just want to aggravate me, my logic is sound. I couldn’t care less whether I’m right or wrong. I always said that I’d rather be wrong but find a solution to the problem. If this happens ONLY in the two programs that share the same code from the same company, pure logic is that the problem with that software, not drivers, not my PC, not user error, etc, etc.
Perhaps, if this didn’t happen with any other programs, but my computer was a mess that tends to do crazy stuff all the time because the OS has become corrupt, I’d be willing to entertain that. But it works as flawlessly as a Windows 11 PC can work. I don’t have constant crashes. Some programs crash, sometimes, and usually when I push them to the limit. For example, Blender tends to crash when I try to render a frame from the GUI in a small section that has a motion blur value of 100 (for anyone who doesn’t know Blender, that is a rather crazy and unusual value, the default is usually 0.5), and rendering at 30000 samples (which is about 7 times what is considered a decent amount of samples. Now these values are for a specific purpose in a small section, so I’m not going to bore anyone with the why. But that tends to crash Blender about 20% of the time I try rendering from the GUI, never from the CLI.
And speaking of Blender, that window detaching thing I do with Cubase, I do it with Blender several times, much more than with Cubase, and it never ever resulted in that window becoming larger than the edges of the monitor it was in. Not one single time. And it’s not just Blender, I have three computer monitors (the TV is also connected, but I never use it as a computer monitor because it’s an OLED), so I tend to detach and attach windows to different monitors all the time, with many different programs. This bug doesn’t show on any other program.
So yeah, this is a bug in Cubase, period.