It’s the same problem on other resolutions. I also had the problem on my 20" (can’t remember the exact resolution - maybe 1280x?). I have no idea if it’s a memory problem or not. And frankly I don’t think it should be my (or other users) problem to know/fix such things. Yes - if ONLY I had the problem, due to something in my system. But it is a VERY common problem, as the vast number of threads on the subject the last couple of years show.
Yes they sure do seem reluctant. I’m pretty sure they are well aware of the problem though, since people have been complaining about it for years now. And they have tried coming of with workarounds (e.g. not maximizing any windows and/or using the - not working properly - workspaces) as well as they’ve used the windows API as an excuse for the way the windows react in the past.
The big question though is if they’re going to do something about it? Either with a fix (like suggested in this thread) - or a more current redesign of the basic GUI?
I’m not a programmer - just a user who knows good user interfaces from the bad - so maybe a fix isn’t so simple as already suggested - or you’d think they’d already done something about it.
I can live with a fix (at least for know), I would LOVE a redesign of the whole windows structure as already stated (which I think is about time to keep up with the superior workflow options presented in other DAWs), but I’m having a hard time with total silence from the Steinberg devs after so many years with people complaining about this issue.
I also work on a single screen and problem occurs all the time when I open a Key Editor or a Sample editor.
The project window get resized beyond the maximum resolution of my screen.
Also, the knowledge base article posted by Chris has no effect here as it refers to multiple screen setups. This problem happens on single screen setup.
I know, but the problem still exists. And unfortunately, this article does not provide a solution. I love Cubase but this problem is there for too long. I remember showing this to a Steinberg rep in Musikmesse and he told me he was aware of it.
It would be really great if you could report this issue as a priority to the development team. It is such a shame, really it is irritating and time consuming having to resize windows all the time.
sorry, but I do not (and many others) have this problem on my computers. So something is “strange” on your computer. Did you got in contact with our support department ?
Cheers,
Unfortunately, my country is not supported from your direct support and the best way would be to contact Steinberg directly, not through my dealer for this matter.
I can assure you, I have four machines, with different specifications , and I work in various studios that use Cubase. All of them have the same problem.
I guess the only way to get this solved once and for all is if someone would create a video so that the support team can see for themselves what we are talking about and how to resolve it.
It is no coincidence that this issue has been reported from so many people in this and the previous forum.
I believe the thing is that some people may identify this as a “problem” and some as a “normal behaviour”. It is something that definitely happens on all machines.
Post a video. please someone!
And yes. It is not a “bug” Just a design choice that many people dont like (including me). And that windows choice is old.
No it does not work as designed. Maximize both the project window and the key editor. Toggle key editor on and off for a while. The vertical zoom will start to drift to a bigger value. This makes no sense in any UI paradigm whatsoever.
Cubase has the standard MDI limitations that Steinberg can do nothing about until they abandon MDI (have to use “always on top” for floating windows on top of maximized windows etc.), but stuff like that is simply broken.
If you mean open and close by ‘on and off’ (otherwise I have no idea what you mean by ‘on and off’) I’ve just been doing it for 10 minutes, no vertical zoom issues here. Or any other issue that I can see.
I don’t have anything set to always on top and get along just fine. I maximise the main app window and keep the project window on the left hand monitor with the main mixer below it. I only maximise the project win (or other) for very specific reasons and restore them once I’ve finished. All plugs etc opening on the right hand monitor. Absolutely no problems and very easy to work (have fun) with.
Tabs and docking windows would get very irratating very quickly as far as I’m concerned.
I’m finding myself agreeing almost entirely with MarkE’s post above. I too cannot see/get the window re-sizing ‘drift’ (described by paaltio) to happen here.
Oh, and while I’m at it, I DON’T want a clone S1, Ableton, Cakewalk, or Adobe Audition/CS software UI for Cubase thanks; they’re all good, they’re all fine. I use them when needed/occasion suits. I’m happy with Cubase, right now…! Have been for a number of years (certainly since SX days). Don’t want to unlearn all my workflow/shortcuts thanks.
But, then again I suppose I don’t have to upgrade if that’s the way SB heads; on the contrary, neither do the unhappy folk here if they don’t. Cakewalk or S1 beckons.
I also agree with someone else’s post about nailing down a reliable repro or video for SB to seriously look into this (obviously real and VERY horrible) windows randomness that’s being reported. Its the only way.
Right now, they just don’t see it; agreed, several/lots of posts by folk reporting ‘issues’ with windows handling - but a lot of those are probably down to maximising (which SB say if you wish to avoid problems, you shouldn’t - as that is the WAY CUBASE IS DESIGNED…!). The random windows sizing ‘creep’ or ‘drift’ is something bad and different and needs looking into.
Now, proper VCA’s, better routing, full view of inserts/sends in the mixer anyone…?
Ok. This more lika a real bug. God job with the video!
I think thee are too issues in this discussion. This bug i one and the other one is the windows who cant have always on top (pool window, some midi windows, media bay mr816 hardware window. maybe som more) and therefore the project not staying maximed because of that. Anyhow should both this issues be fixed. I dont talk about a new GUI. Just everything “always on top” as a option.
Firstly, if there is a bug here, it’s got nothing to do with windowing system. It’s something else.
Secondly, when I was doing it yesterday, I was using the mouse to open/close the editor. Double clicking the midi part to open and clicking the editors close button to close. I’m a mouse person.
I’ve just tried using the keyboard and being a mouse person I don’t actually know what the keyboard shortcuts are for this. So I guessed which keys should do this. I found that with the midi part selected hitting return opens the Key Editor and hitting Alt+F4 closes it, which are the standard Windows keys for doing such an operation. Again, no problems.
So, I opened the Key Commands dialog to see what other keyboard shortcuts might be assigned for this and under Edit - Open Key Editor there is nothing set by default. Being a mouser rather than a keyboardist, what I’ve got here must be the defaults 'cause I’ve never changed anything in the Key Commands.
I could be wrong here of course but I assume you’ve set up your own key commands to handle this operation. If so, are you sure that whatever you’ve set doesn’t clash with something else? Not sure if that’s possible not having mucked about with Key Commands.
What Key Command are you using exactly?
But, as I said earlier whatever the problem is here, it’s nothing to do with the windowing system.
At least the following windows unmaximize the Main Window
Devices->Mixer 1,2,3
Devices->Midi Devices
Devices->Plugin Information
…
What they dit is not a correct MDI-implementation, i could live with a MDI interface if it were implemented correctly…
They fail on their own limitations, not on those of Windows…
Mink
When all’s said and done, I think it sucks, that maximizing any window in Cubase fucks everything up so bad!
In working with a client in a 10 hours session, it should not be an issue, you’d need to consider, that if you by mistake maximize a window, you have to spend the next half an hour re-dragging and resizing everything again to fit the screen because your mediabay is half out the screen and your midi and audio windows suddenly think your screen resolution is 7080x5060 or something like that.
Not if Steinberg want to make Cubase a professional DAW that meets todays demands in terms of features and workflow that is!
But maybe this is why so many pros use a combination of Protools and Logic and not Cubase. Cubase might still (for a little while) be the mostly wide used sequencer worldwide - but 80-90 % of those are properbly teenagers who doesn’t own a Mac and is just starting out.
It’s just so sad, because I really LOVE Cubase for the most parts - in fact I think it is an excellent sequencer - but the windows issue and the lack of will to do anything about it is just SO unprofessional IMO.
I dont think this problem exits on apple computers. Maybe Steinberg sees in the feature most of cubase users have macbook, imac, pro. U sincerely hope not. Cause PC is getting more consumer friendly and with style. If Microsoft Phone 7.5 (mango) become a hith with nokia phones more people will keep on bying great, good looking, easy pc. Steinberg should make the gui as easy on pc as on mac.
Not discounting your complaint at all, but why wouldn’t you simply click again to unmaximize the window? It would go back to exactly what it was prior to the accidental click. It does for me at least. When simply stretching the main window all the way and stretching the project window and mixers to my dual displays everything stays fine afterward unless I accidentally click/drag the window which does indeed become a major PITA. I wish I could lock windows in their places. People have mentioned workspaces but I’ve not yet tried them. I should give them a look. Anyhow, my first thread on here was complaining about the window issue as I was getting scroll bars when not even fully at the boundary edge. But it’s since resolved itself with some tweaks, which may or may not have resolved it but it’s good now and always was for me in SX3.