I’ve been complaining about the white fonts for 3 years nonstop and nothing, you love the white fonts is good but at least let us change it in the preferences for example a green color like pro tools where you can work for 10 hours no problem
4 Likes
UAD - LUNA is wonderful when it comes to GUI. LUNA wins the race.
1 Like
The GUI is also just unfinished…
why are there little boxes around my buttons now? (C12 top, C13 bottom)
4 Likes
Yes, not as clean or polished as yet is it…
Still, we had around seven updates to C12 along the way… no doubt there’ll be similar opportunities with C13 to improve things 
.
Always a question of how/when; which are directly in proportion to levels (reserves) of patience left in folk - especially on those ‘bigger ticket’ features so long asked for, yet to be delivered…
Can’t quite tell, what OS are you on.?
Windows 11.
Cubase has never has this many gui issues on a new version before.
1 Like
There was a version where the middle mouse button function was missing on the MAC. Guess how long it takes them to fix it? A whole version, CUBASE7-8.
1 Like
The question is, does the development team read this forum, and do they take any cognizance of it? Certainly they do for Dorico., but so far I see no evidence of any Cubase product manager taking an interest in this category. I hope I am wrong! One would expect with a thread over 300 posts long somebody from Cubase would comment, but I see zip.
9 Likes
That’s a good question. Most of the complaints, at least those accompanied by screenshots, are fairly obvious. For example:
- Mismatched M and S in project window and mixconsole. That’s obvious straight away.
- White text remaining white even with the preference to highlight a selected track, completely washing away the track name. Obvious.
- Screen too busy due to heavy letters. Obvious.
There are many other things too, that fall in this “extremely small detail” category, which, to be fair, I’m hesitant to bring up. Because it’s so graceless. I mean, I don’t know if a developer is following this thread or if they have despaired and left due to the sheer volume of posts, but posting another set of pictures to show that “ah, some pixels of the dB readout poke through the meters depending on the zoom setting”, I mean, that’s borderline petty. It makes us all look bad, us users in the sense that we’re hunting for the slightest flaws for the sake of some perverse pleasure, and the developers for not responding to stuff that they probably already know. But on the other hand, if they DON’T know about it, then it’s good information, right? So, which issues are already known, and which aren’t? So that we can stop bringing up the same points again and again?
I don’t know which of all these issues are known. Maybe they’ve been fixed the third day after the release. Maybe they haven’t been fixed yet, but the developers know about all of them, and more. I don’t know.
Maybe they really like what they have done, or perhaps they would not have done it. No users asked for any of the GUI changes as far as I can see.
5 Likes
Maybe better for steinberg to invest some time and resources to implement some font choices(type,size,color etc…) in preferences, on various areas of the program like menu, track name, parameter’s values etc… so users can set it to there satisfaction , and wont complain so much about it
6 Likes
Here’s mine.
1: Prioritise readability
2: Create distinct separation between elements with borders or good colour contrast.
3: Don’t create an Interface that requires unnecessary mouse clicks.
… you know, kind of like they did about 20 years ago when common sense favoured pretty pastel colours. I’m not against modern - I’m just against madness.
12 Likes
AND not or, please. We need both of these changes.
And, by borders, I mean that as empty space around elements on the screen. Right now, on the Track list with multple tracks, we have a long line of M and S that blend together top and bottom because there isn’t enough empty space between them.
1 Like
Somebody call Karl Steinberg and tell him about this disaster of a GUI, maybe he will pay a visit to the headquarters and kick some asses… you know, for old times’ sake.
Hi @Andro,
Having in mind the previous experience of mine in the Cubase topic… well, no one from the Cubase team, doesn’t care about what the users here ask for, and their opinion on “improvements” that no one asked for. There are so many important features to be integrated, which are missing, and improvements to be made… but they decided to waste time destroying the fine looking GUI.
The team behind Dorico, on the other side, is a completely different story… They should serve as an example for the entire company. The guys by Daniel’s side really know how deal with the users on the forum. They really love Dorico, while the guys behind Cubase probably don’t and would like to destroy it…
Best wishes
4 Likes
Many users have been begging for the GUI to be overhauled.
Some things are much better. Some things are worse.
As a Dorico user I concur, and I am always impressed how active and helpful the Dorico lead product manager is on the Discourse forum. What I don’t comprehend is why there appears to be a 1000 foot high wall between the Dorico and the Cubase team, even though Dorico uses Cubase audio technology and both products are owned and developed by Steinberg. This is an extreme example of siloing.
I’m not convinced the Cubase team wants to destroy their own product as you suggest, but I can’t understand how any product manager let the current debacle out as a release. Nor why they take no interest in the users that they sell to, and who effectively pay their salary,
3 Likes
It’s funny because Ableton just presented a new Live 12 with… GUI updates 
Opposed to C13, they even added accessibility options for visually impaired people (I hope that this is the proper name).
I wonder if their forum will also be full of complaints about changes 
Live is not my main DAW so I don’t know if those changes are good or bad.
3 Likes
Interesting - as they say on Ableton’s site:
“Toggle the visibility of each Mixer section to fit your needs, and benefit from improved readability and feedback.”
And the dark mode visual does look more soothing on the eyes than the current Cubase 13 UI design.
It’s all in how the fonts are implemented!
They are good changes with regard to the Ableton Faders which used to be the same colour as the background and tiny. They have been like that for years. I sometimes have to lean across my desk to see them at times. Often i would just move them to find out where exactly there were.
It’s only taken them about 10 years to do that small change but it’s welcome lol.
1 Like
I think claiming the Cubase team is trying to destroy Cubase is a bit much. While I’m greatly disappointed in the new UI as it stands today, I strongly doubt the team working on this is intentionally trying to do harm.
If C13 release 1 is a big bother, one can just keep working in previous versions of their choosing and wait for version 13 to bake a bit longer (if the batter is not firm enough to your liking).
I doubt we’re going to get a hug session with the Cubase development team as they have more important things to do, such as working on point updates.
I think the larger issue here is in individuals having a different view for Cubase. We can’t all get what we want, because some of those things are in opposite directions. I don’t mean the GUI but in features. Everyone has their ‘important’ features they want added and sometimes those ‘important’ features aren’t so important for other users. And even if they are there is clashing on how they should be implemented.
Plus Cubase is already large and relatively old. The code base has to be massive. Dorico, on the other hand, is still relatively young. The code base is much fresher, first release in 2016. It’s a child. And their team seems to have started from members of the original Sibeleus team set up shop in London.
So I don’t think the comparison is fair. And we should probably take a breath and calm down. It was a month before the first maintenance update came to C12. So it is unrealistic to expect anything sooner than that if not a bit longer.
If I was a developer for Cubase, I wouldn’t want to communicate either. Look at how we behave.
4 Likes