The worst color management I've ever seen, the least natural

This can be done, actually, like this:



1 Like

Because the PLE, (which continues to see enhancements), the Color Tool and The Color menu on the toolbar took over those duties.

image image

There are probably some factory presets for track, event and parts colors.

It was not actually broken, the workflow changed.


The problem is that they don’t work consistently. I’ve changed computers three times since this first got broken and it still behaves as erratically as ever. Highlighting a group of tracks and then selecting a color in the color tool “sometimes” works. But other times it does nothing. So frustrating. Especially, for example, when I need to add 16 more tracks of backgrounds and I want to instantly colorize them differently so they’re easy to distinguish. It works sometimes and then it doesn’t. So I have to manually change the colors of multiple tracks, all the while telling the singers “I’ll be right there, gimme a few minutes”.

1 Like

100% agree. We can probably find the detail, the reason, the cause, and think hard about controlling our handling, taking courses and doing DAW-oriented yoga, but the truth is that it’s poorly designed to begin with. Period. In my opinion, we need to throw out everything in this function and start afresh.

I propose: an additional strip, at the bottom or top, which would be a strip of all colors (in a row). Anything selected - track, event, marker, single or multiple - could then be modified by a single click on a color.

That leaves the presentation of colors by name, a useful option that I like. If everything were better overall, at this point (which wouldn’t be difficult), seeing the name on mouse-over, while not ideal, would be acceptable. If, on the other hand, the list were vertical, color names could be added. I’m talking (if vertical) about a single universal window for all color management, always the same, with all options listed, including the project color set, of course with the option of saving the configuration file, with the choice of naming it.

The things I feel that could be improved a bit with colors are:

  • Ability to save different color palette presets in a named list. For example preset 1 named “Simple” is just 8 colors each named its name (blue is named blue, green is named green etc etc), preset 2 named “Hues” is 128 colors named for function (blue is “Bass”, green is “Guitar”, white is “FX”, pinks are “FX returns 1-8” etc etc).

Personally I wouldn’t use this feature since I use a 128 color palette for all projects, but if there are people that can work in this manner and want to work in this manner, I don’t see why they shouldn’t have the option to do so.

  • Some kind of PLE variable, so that when we use a track name for a filter on the top, we can also have it as a target in the action field.

For example. I have a color named Keys, it’s (let me ask my wife first…) turqoise. I have done this for many colors. Blue is Bass, red is Drums etc etc. If I could tell the PLE: "If a track name contains string ‘Key’, then use color ‘Key’, then I would only need 1 (one) PLE preset to colorize the whole project as planned. Now I need as many PLE presets as there are colors, which is a bit cumbersome to set up, and maintain. (sometimes I swear that bass is blue, but the next day I swear it should be yellow. Don’t judge, it’s all Scriabin’s fault.)


All wronG!!1!! Bass is brown, drums are blue, and FX returns have to be yellow!!! :rofl: I agree with the green guitars, though. :metal:


Drums are blue! Bass is green! FX returns are purple! Groups are orange! :rofl: I guess we all have our usual colors!

Thanks for the idea. I guess it’s a workaround, but doesn’t really have the same clarity for me - when you have your look you just want to be able to transfer it every time you update, which is what the profile is supposed to do. It was one of those things that worked perfectly and changed for no good reason that I can see.

Obviously, judging by the other ways people in this thread have been affected by the chaotic colour management in cubase, this is just the tip of the iceberg. I think maybe Steinberg just underestimates how important colour is in providing instant visual feedback when you’re working, and how important it is in organising layouts and arrangements in the various windows. It would be great if they targeted this for a major rethink.

Exactly that. I support you 100%. How do we get Steinberg to hear us?

Oh I think they ARE listening, but it’s a matter of how many things they can do simultaneously within a given timeframe.

(And I agree that color is important. Another thing that I would appreciate is if they checked how automation lines’ colors work because some times they don’t quite really stand out with some color combinations, and by extension ensuring general readability of data in both dark and light user color schemes is always guaranteed. Allowing even lighter user schemes is just a personal preference of mine, but it’s so trivial that I don’t really care either way. But automation data, I would really appreciate that improvement.)

1 Like

Hi @Ted_Perlman2

I think this video beautifully demonstrates the different pitfalls when trying to color multiple tracks.


  • make sure no events are selected
  • use the Select Color for Selected Tracks or Events tool, not the one in the inspector. Colorizing Selected Tracks

That’s the way it USED to work. But I’ve been complaining for four versions because it doesn’t ALWAYS work. SOMETIMES I highlight multiple tracks and select the color I want and…NOTHING happens. SOMETIMES it works properly like in this video. If it ALWAYS worked like that I wouldn’t be writing multiple posts about the SAME THING . Oy vey.

Are you talking about what the author is demonstrating here, at

When it doesn’t work, is it possible that even though you have tracks selected, there is also a part selected, thus coloring only the part, and not the tracks?

But you can use presets. Save them, recall them. See this post

Thank you - But saving individual color schemes as presets doesn’t even work as a workaround.
Because if you change something in your basic settings, you have to apply this change for each color preset. And that for several computers in the studio. There is no getting around a clean import of color schemes.

1 Like

I’m not clear on what you mean exactly.

But you can save a group of color settings, and if you change something in one of those, you can save the same group of settings again.

Also, you can use Profiles to pass the settings on to different computers.

This does not work for the color palette. The 32 colors from the palette cannot be saved with this method. In this way you only save the basic colors of Nuendo - but not the color palette.
I think we’re talking about importing this color palette with 16, 24 or 32 colors. The man from the video created a color project for this, which he saves as also as “default”.

Thanks @THambrecht for being specific.

It looks like the FR here is for being able to name presets for the color palette, which does make sense.

The best thing for to do, as everyone certainly knows, is to post a single request with a descriptive title and tag, so when dev team members browse the forum they can see it without reading gobs of text. Also opening a support ticket if you’re in a location where that is provided is a good idea.

In regard to changing track and part colors, and colorizing the mixer, and all the rest it would appear that all works okay.

If there are people who feel something is broken, a bug reproduction sequence would go a long way to revealing (or ruling out) the issue, as described in the Steinberg Support post: How to format a bug report

You’re right, Steve. As for the bug, yesterday, here, the Ctrl-click on the header didn’t work in the editor (but it did work in the Mixconsole with the corresponding function, on the same tracks). Then this morning, it worked everywhere. All without alcohol or drugs…-:). There’s some kind of bug. But it takes a long time to find the sequence. I can’t see anything conclusive. I’ll try to write to support as soon as I have time.

I don’t understand what exact function you refer to – ctrl-click doesn’t bring up a color list in the editors, as far as I know, and the mixconsole doesn’t use ctrl-click for this either, instead there’s the little arrow to the right of the track name. I might be missing something, but are you talking about something else?


Clearly, more is needed. Or less!!

Must be the translation. Ctrl-click, left on the track header in the editor (the main window), opens a color palette.

In the mixconsole, that’s what you say (I wrote: equivalent function, so arrow, etc.).