Yes , you can actually tame the graphics quite a bit , i haven’t checked out all options but there two areas that needs change Font , brightness of font , oh three sorry and those … that i’m not allowed to speak about because someone’s thrown a rattle out of the pram … (cough cough ) , two words , first one begins with F , second one begins with C
Over all i like the changes , the auto hidden in sections not being used saves space , a bit more tinkering from both sides and a little 3dness it could be a beautiful concept
Hi, Sebastian.
I’m really sorry that you didn’t get my point right. Perhaps it’s my mistake and I should have put it more carefully, but I thought that the second part of my post would clearly show that the first part was just sarcasm.
Actually that list from 1 to 6 is just an example of the standard behavior of a soft wear developing companies or big companies who sells their stuff across the whole world. They always blame the user.
There are a lot of pictures with C12 and C13 side by side in this thread which clearly show that the new design went the wrong way and not because its flatness but because of wrong deсisions. But I still think that “absolute flatness” is the wrong way, bad style and bad taste.
There was a time when I was trying to try Studio One and I couldn’t force myself to work with it at least a one whole day because of that cheap flat UI. They have some great ideas that implemented much more wisely than Cubase but anyway I can’t work with it. And I will not switch to it even today after Steinberg’s great fail because I see no reason to waste my time changing one poorly made thing to another of the same style.
Poorly educated new generation of designers, engineers, musicians with bad taste is trying to make a revolution in every area and they have no idea that we’ve been there already 20 years ago.
Some of the examples of the comparison between 12 & 13 for the GUI differences, the new version actually looks better to me. But with so many horror stories of peoples actual experiences, I need the demo before I upgrade.
you are absolutely right. The new graphics are definitely unclear and will hurt your eyes within half an hour. It’s a mystery to me how anyone can prefer this loud GUI over the much calmer graphics of Cubase 12?
The new look goes exactly the right way:
straightforward and fast, contrasts instead of pretentious shades, without all the unnecessary frills. A DAW is a workhorse.
If you want to see art, you should look at a painting.
I think C13 and GUI is on the right way to. Yes there is alot work to do, but its mutch better then C12. smal steps are better then big steps there. Just fixt the monitor settings and its mutch cleaner. Am waiting for vector based GUI and where everything is rezisable.
Havent test and Max out C13 yet on my PC but there is alot of new stuf that lower cpu on every track now. But my feeling is i can save minimum 20%cpu power if i use C13 the correct way in bigger projects.
C13 is a monster for programers to work with, and to make everything to work. DAW is hard to make.
And there is other daw to work in before put stems in to C13
I just tried doing normal work today with the new Cubase 13. So far, no harsh interruptions to the workflow. That’s most important. My eyesight is still 20/20 though, so I can’t speak for those who need more forgiving contrasts.
I have no gripes about “too much white”. Too much black would also have the same effect. Too much of any color has the same effect.
Plus, given the fact that I think almost most of us prefer the backgrounds to be dark, the fonts should be “bright”. Can you imagine working with black fonts with a bright background? Sheesh.
Plus, I have more important things to do, like music to make. So far, it’s been pleasant. 13 feels more “tactile” than 12.
I think the C13 GUI is an improvement over C12. But I’m not surprised by the comments from people who don’t like it. If you stare at something all day, it’s going to impact people and they’ll have strong opinions.
But overall, I’m fine with it, I’m focusing on the positive workflow improvements, which are good. I do think the GUI is a little more consistent now, especially the updates to various options and screens throughout the app. Glad to see even MIDI plugins got a more consistent look.
But it’s far from perfect. It would be impossible to please everyone.
You just said you have 20/20 vision so I don’t expect you to have issues with “too much white.” Are you just attempting to counteract others who have visual disabilities and issues with cubase 13?
How hard is it to make two or three presets - dark (white letters), light (black letters), and something inbetween.
This way it is possible to please most people.
This I’m not so sure of… but to your larger point, I do think having some very thoughtfully considered presets would be good.
Accessibility for people who have actual visual issues or visual disabilities is a real problem for some people BTW, and it’s not something most developers care about, unfortunately. In my earlier response, I did not mention this, and I apologize, since that is a big part of this thread.
So knowing that there is a real science behind this, I would have to agree that having an accessibility compliance consultant work with Steinberg to address color and contrast issues, and other accessibility options, would be a wonderful thing for Steinberg to do.
So I support that idea. I know of a number of artists (composers, musicians, performers, producers) who have real, actual visual disabilities and I can see that they would probably have a hard time using part or all of Cubase TBH. So you’ve got my vote for awareness that visual disabilities are a real thing and some consideration should be paid by developers to this issue.
BTW, in the US, there is a thing called “508 compliance” - which is, in practice, a set of standards for accessibility of information and communications technology. This applies to federal agencies, and is obviously NOT a commercial enterprise standard. But the general ideas as they have evolved over the years is that colors, font sizes, contrast, and various other features can be made to help people with various kinds of impairments. It’s usually applied to content like documents and websites, etc., but the ideas can be applied to apps, including something like Cubase.
This is a GOOD idea to incorporate these general design concepts into products because it actually can help overall design for everyone too. And there are a bunch of 508 compliance experts who have studied these issues, and Steinberg could hire one of these guys to analyze Steinberg products and provide some recommendations. It would be up to Steinberg to decide to implement any of them of course, but I guarantee some of the recommendations would be very simple to execute and would help people in this thread who have real accessibility concerns. Some of the recommendations would of course be way too expensive to implement in Cubase though, but again, some tweaks could go a long way to helping some people.
I totally agree that vector based GUI is the right way.
Steinberg should also listen to their clients at the same time, since the present design is still lack of tweaking.
Now having been in Cubase 13 for four days, I still find that it is getting my eyes tired far earlier than Cubase 12.
The bars in the Inspector are much thinner, forcing me to find and stare at the thing that I want to click on. It is just faster working in the Inspector in Cubase 12.
The new MixConsole needs further tweaking as well IMO (I am saying about gui elements that can’t be tweaked in preference, etc., by user).
However, I am really quicker in getting my mouse cursor onto solo / mute /… buttons (but yes they’re somehow too bright. Could be a little bit darker maybe).
