#GUI COLOR SCHEMES FULL#

#GUI COLOR SCHEMES FULL#

…there’s no entirely free choice of picking colors from a full RGB color band(s), whereas the color pickers in all other (“lower level”) parts of Cubase’s GUI color choices still enable the full RGB / hue / saturation / value ranges. “ Preferences” → “ User Interface-Color Schemes” → “ Focus Color” In ' Preferences' → “ User Interface-Color Schemes” → “ Custom Color Scheme” Strangely enough, one can still completely mess up the custom GUI coloring by choosing bright red or ultramarine blue main GUI color values, but never bright yellow or orange, or white. Nowadays, only four relatively dull and dark main color schemes can either be picked as such, or they can be adapted by picking some rather dark pastel colors, but nothing too light, or even white (as in “inverted contrast”). Or even something with a rather unconventional touch of pastel color choices. However, I still think that it wasn’t the best design decision by Steinberg to restrict the main GUI color scheme customisation as much when Cubase 11 got introduced.įor example with Cubase 10 and 10.5 (and earlier versions), eye sight impaired users could still create their own high contrast color schemes, even a more or less white Cubase GUI with dark system fonts could be configured. Hi think that you and all the others in this thread have quite a few valid points regarding Cubase and the current GUI, while speaking from different angles. It might be really good for sound design, doing EDM music using a bunch of VSTi’s…but then suck for straight up composing a song, doing a symphonic score for a gaming engine, syncing to film, or connecting to a 128 input mixing bus and recording a live band.Ĭubase is pretty good at many things but it’s not going to match every product on the planet for every specific need/task. Sometimes I go take a look at the stuff people claim ‘looks so cool, modern, and fresh’…then learn pretty quickly that it sucks with multiple monitors or big screens. It’s just that…surface level changes tend to take enough priority as it is. I personally don’t have a problem with fresh looks and work flow improvements. The last several years instead of getting more ‘little things’ that save time and improve work-flow, we get new skins, UIs, and the trade off getting some ‘cool new looking stuff’ while breaking things that worked really well for decades. Unlimited versions of takes in VST automation lanes (and easy to swap among them…cut and paste the best bits of the various takes into a new lane). More/better tools for working with the automation lanes…powerful Logic Editors devoted to batch script changes to those lanes. Improvements and updates to the expression map system. More track types to automate more things. Improved logical editors…with more event types and abilities. If we must choose, I’d rather have useful stuff added, bugs fixed, etc…than too much time being spent on the paint job. Like that one doesn’t have to ‘relearn the whole DAW’ every time a new version release hits the streets.

Like the way it looks, and how it’s laid out.

Gui color schemes