They can’t. Or if they can, could you show me how to solve the problem with the green arrangement button color if I’m using the mid-gray UI color preset (it’s not visible on mid-gray)? I use that preset so that my track color/automation colors have high enough contrast.
I don’t think we are really understanding each other, sorry.
I’m trying to say that I don’t see the need to glance at selections because I always keep what I need front and center very clearly and work with intent.
So I don’t care to “find out” what is selected. If I need to, I just select what I need.
I wouldn’t be asking this is we were talking about toggle states across the interface, for example.
But well, it’s fine as it is AFAIC.
@Fredo Here’s a link to my earlier post - N14 - How can I turn off selected event colour change? - #69 by estevancarlos
The scenario I imagine is that someone has selected an event. They zoom out to show LOTS of events. Then they have to go back and carefully observe their screen in order to see the selected event within the context of other events. Why did they zoom out? Maybe they need to see more information. Why can’t they focus? Maybe people around them are talking and asking them questions. Etc.
If you’re interested there are lots of books/courses/tutorials on user interface design and user experience which go into depth about what myself and others have briefly alluded to here. It’s a large topic and if you’re not aware of what you might be looking at or understanding the problem it might not seem like a problem at all.
I too work with intent but am often switching between mixer window, project window, different monitors, interacting with clients etc. Steinberg’s interfaces are now pretty poor for the “at a glance” information.
I do wish we had some kind of full ‘theme’ support the way Reaper does. It would be so nice to fully-customize Nuendo’s color palette, though most of what Steinberg does and offers is fine, at least for me.
Yeah, that is why there is a key command called “Zoom to selection”. 
I’m describing a scenario where someone might want to see it zoomed out for context. It may require several seconds to find an event in that context.
Oh sorry, I misread you.
I know you are right from a technical/theoretical point of view. But to me this is a non-issue.
If on top of all the serious, uncircunventable problems that really get on the way of getting work done in Nuendo, I still had to deal with not being able to find events on the timeline I would be using something else a long time ago.
But somehow I always know where things are in my sessions, so I never need to look for lost events for some reason.
Lucky me!
edit: please mind you that I’m not talking about people with disabilities, etc. I’m talking about this supposed need inside of a workflow. I don’t buy it.
ok bye
Something Steinberg wants to reflect on is the phrase, “death by a thousand cuts”. Replace “cuts” with “user experience friction”.
One small cut may mean nothing. A hundred may bother someone enough that they won’t buy the software. 200 cuts may convince someone the software is too complex and they won’t recommend it to a friend… etc
Okay, we can have an endless discussion about everybody’s personal preferences regarding GUI’s. But the question remains: Is the Steinberg dev team going to address this issue?
I am convinced that there are valid (technical) reasons for the team to implement the color inversion for clip selection, and that they think this is the best solution. But judging by the comments in this forum, many users disagree with this decision.
So, I would strongly recommend the Steinberg team to take this in serious consideration for future updates. I personally would like to see a simple option to disable / enable the color inversion, and have a border (with optional color adjustment, just like the play cursor has). The audio waveform has to be clearly visible at all times! I hope you agree that this example is unacceptable:
(Yes, there is a waveform somewhere in there…)
Personally, I will stick to N13 for now, regrettably, because I think N14 is a great release. So, PLEASE Steinberg (@Fredo): take this issue seriously! Listen to the community of loyal (professional) users, and see if there is anything you can do here. Thank you.
All of the above ^
I will say one thing to add to this because there are a few here who don’t quite understand still what the issue is were trying to convey. Last night I spent a good hour messing with the waveform view settings to get the right balance with the inverted selection. I could not find a compromise where my eyes weren’t straining looking at the events flashing between bright and dark. I found myself often looking at the screen squinting, it felt a bit like those awful optical illusions which play with colour and contrast and if you look too long it becomes quite disorientating. I’m personally sensitive in this way.
In addition to this, if you have white waveforms with black outlines (which is my choice), when moving a range selection across the waveform, the size and shape of the waveform changes which makes it more difficult for precise edits without zooming in way more than necessary. This just slows me down.
Black waveforms on events seems to be the most bearable for the eyes, but I really can’t stand black waveforms on coloured events. Can’t really tell what’s going on in the waveform at a glance.
Just please consider giving us an “accessibility” option to turn it off and have it like it was before.
We do appreciate the 99% of other great features we got with this update. So great job!
Thank you for listening.
… Steinberg has a strange tradition of products with groundbreaking, innovative ideas and over-complete feature sets, but clumsy UI (and especially unfortunate GUI) decisions.
Absolutely right.
I hope they can properly refine the user interface. They can refer to the layout of other software and use the same color scheme. Steinberg’s interface is too glaring and hard to read. Additionally, they should fix the bugs exist the long time ago.
Fredo,
It certainly seems like that’s what you implied - Steinberg felt the need to make technical changes to this latest iteration of Nuendo that would not only remove expected and long-established interface behaviors (in favor of something starkly different), but that the focus in the end appeared to be about needing to primarily satisfy your Cubase users wants, as that’s pretty much the UI behavior Steinberg implemented. (inverted colors).
You also mentioned:
“All kinds of configurations have been tested and…it broke the workflow of the Post Production users.”
Well, the configuration Steinberg landed on has definitely undermined the workflow efficiency for many of us.
(I’m still baffled at what technical limitations prevent a preference setting for one, or the other, type of behavior? Hopefully it’s something that can be solved and implemented in an update to rectify such a drastic mandatory change).
I understand some people prefer inverted colors. That said, I’d hope those same people take the time to understand many of us don’t. It’s not on me to explain why my preference is my preference - if I tell another user I find the new UI behavior decidedly less efficient, and they tell me “you shouldn’t”, that’s an incredibly unhelpful interaction.
Finally, to diminish and brush aside the idea that a change like this for LONGTIME Nuendo users is minimal and nothing more than a “you’ll have to get used to it.” certainly comes off as cold and uncaring to your paying customers, quite frankly.
- DE
Yeah, hopefully get used it is not an official position. However, as users we may have to assume and expect glacial changes. The UI solution is not immediately obvious because their UI system is a house of cards. One thing changes and other elements “break”.
The real UI solution would require going against established Cubase user expectations and companies sometimes want to do that cautiously. I’ve had experience at a company where the users complained a lot when sensible changes were made not because they were “bad” but because they were different and unfamiliar.
Edit:
My biggest concern is that the inverted color decision is not actually a sensible decision and not a direction we should go in.
Very true.
But that burden shouldn’t fall on the customers - i would’ve rather they delayed Nuendo 14 and took even more time testing to sort something like this out properly, as they knew where they landed would be a “compromise” (a.k.a. a detriment and workflow underminer for some customers. Personally, I would never consider “after all these years in Nuendo, now you get MANDATORY inverted colors” a “solution”)
I def understand that scenario - unfortunately, this doesn’t feel like a “sensible” change, but rather to your earlier point, their UI system is a house of cards, so here we are with an unapologetic, unrequested change like that forced upon us; a change that’s frustrating a number of users (and making some of us stick with Nuendo 13 while perhaps regretting the purchase of 14. Which is sad, because there appear to be some interesting new [and sensible] features in it).
For me, the biggest issue is the (IMO all-too-frequent) dismissive attitude from SB when it comes to baffled, exasperated customers simply expressing their frustration, hoping for helpful insight, accountability and actual support; customers that have paid for this company’s product (including every subsequent update), and depend on that product for their livelihood, only to have significant unexpected (less efficient) changes thrust upon them without warning.
And the SB feedback - “you’ll have to get used to it”
Reminds me of back in the day working with Quark (page layout software) and their “just deal with it” attitude when it came to bugs and frustrations.