I think you are taking two people for one.
The person that made the video is @Kenn_Michael
Yeah, I’m clearly not up to the task this morning :). I didn’t see the message break between your post and the video from another person. Now it all makes sense. /bows.
1 Like
Make the best of it?? What kind of statement is that? It is very clear @Fredo: Many Nuendo users were used to, and happy with the way it was. Cubase users were also happy with the way it was. I understand that there were technical reasons for changing it in Nuendo, but as you may have noticed, many Nuendo users are NOT happy with it. You even say you don’t like the color inversion at all yourself! 
Sure, it all depends on everybody’s preferences in GUI settings (dark / bright etc). Which is one of the great things in Nuendo that you can customize. PLEASE, don’t use the argument of "I really can’t understand why people use bright colors that burn your eyes within hours". Everybody should set it up the way they like, especially since Steinberg has implemented this option. Don’t judge users!
What really bothers me is the attitude you are showing here: You don’t seem to have any understanding of what people are saying here, and even claiming that users are stubborn.
PLEASE, PLEASE, try to understand that users are NOT happy with this change in design. PLEASE, see if you can have some empathy for this, and not treat use like we are stubborn, and that the problem is in the way WE use it.
The problem is simply that Steinberg decided to change something, which they think it is the best solution, and that we should simply put up with this and “Make the best of it”.
Please tell me this: Does this look acceptable to you:?
2 Likes
You are taking this way out of context.
For a variety of reasons, Steinberg had to change this.
AFAIK, they are not coming back on this.
I try to offer solutions, that’s all.
Fredo
I’m sorry you feel that way. To me the context is simple: I feel that Steinberg is not listening to this complaint. Since you (@fredo) are actively involved in this forum / post (which is highly appreciated), you are sort of representing our link to the Steinberg team. To me, many aspects of your response give me the impression that Steinberg is not willing to take our complaints into account.
The solutions you offer are appreciated as well, of course. But still, It feels as if the root of the problem is placed by the users who are (seemingly) unwilling to adapt their view on this, and not with Steinberg who changed something which obviously has a great impact on how users experience using Nuendo.
It would really suit Steinberg if they (or you) would say: “Okay, we hear you. We will at least see if there is something we can do here”. Instead of “We don’t see what the problem is, we are not coming back on this, get used to it”.
3 Likes
I guess you missed my very first anwer:
Best regards
Fredo
I didn’t miss your first answer. In fact, I follow the entire thread very closely. In this post you only state why SB decided they had to change the GUI, (technical reasons), and that we have to get used to it. But what I am saying is that, although many Nuendo users have complained about this change, SB doesn’t seem to acknowledge this, or are willing to revise their decision.
I am convinced that SB did their best to find the best solution to their technical problem. But many users obviously disagree.
Sure, if there is absolutely nothing the SB programmers can do to please both Nuendo and Cubase users , at least to some degree, then so be it… But it in my opinion, is not a very elegant way of dealing with this issue by Steinberg.
2 Likes
Well, if this is really the case, then my statement from two weeks ago is more valid than ever. A real shame, if you ask me.
3 Likes
Does anyone know any way for us users to officially make a group complaint in Steinberg about this feature?
I have been watching this thread from its beginning, and the only person that can have a word with an official Steinberg member is @Fredo .
As we all see, @Fredo is not willing to help us - the users, consumers and buyers of Nuendo 14 - in order for Steinberg to make an update with a fix to this matter.
I personally am getting tired of paying for a software that downgrades instead of upgrading, and that makes my workload slower and more tiring instead of faster and easier.
I got tired of reading excuses such as “get used to it”, or “you are not using the correct color pallette”.
If I wanted to work in an environment that is Pro Tools friendly, I wouldn’t spent my money on Nuendo and I would have payed for Pro Tools.
As a consumer and audio professional I would want to officially make my complaint to the company and not lose my time listening to excuses and reading arrogant answers.
Does anyone know how can we achieve that as a group?
Thank you.
1 Like
FWIW, I am not a Steinberg Member, I am not on the Payroll.
At best I am part of the furniture.
Fredo
I’ve been thinking about this as well. I’d love to find out if it is possible send an open letter of complaint to Steinberg about this policy. I’ have no idea how, or who to contact about this.
2 Likes
I have mentioned you as the only person in this thread that could speak somehow directly with someone inside the company. I did not in any way mentioned you as an official member.
Best,
Thanos
1 Like
Didn’t you just say:
Also, you’re conflating the “Cubase users” input with the inversion of the selected event it seems. That was just about the “red box” border (which you can turn off).
Or are you looking for someone else to tell you “this is the way it is?”
@Fredo : My apologies for assuming you were a (payed) member of the Steinberg team. But since you are an active member on this forum, you appear to be a spokesperson of Steinberg, and the only one “inside” who actually responds to our posts.
Perhaps you could inform us how or who to contact within Steinberg regarding making an official complaint on behalf of a group of (professional) users.
Thanks.
2 Likes
I’ll have to see how well I can line up dialogue edits with the new Cubase-like inverted/black event highlight. I know the Cubase users hated the red outline version we had in Nuendo, ha ha. It seems like such a trivial thing that I think it should just be a preference setting at this point. Can’t say I love the black folder icons on the folder tracks either, but whatever - not a deal breaker for me. I’d still vote for full-on themes in future versions, like Reaper supports.
What I mean to say is:
- If SB absolutely refuse to change their mind about the color inversion issue, then I guess I’d have to live with that (regrettably). But I’d like to see if we can contact SB as a group about this policy.
- Not sure what you mean. But as I understand correctly, Cubase has had color inversion for a long time, and Nuendo didn’t. I know about the red border complaints in the past and Nuendo has a nice option to disable it. But I got the feeling that, for technical reasons, the team decided to go with the color inversion way and tell the Nuendo users to get used to it.
1 Like
It is - you can toggle Highlight Borders of Selected Events in both C14/N14 
Well, yes…that’s still there…but this is more about the entire event turning black that is in question (I recently updated from Nuendo 12, so it’s new for me).
1 Like
Thanks for the reply, and yes, fair enough here. As long as the end result would be something like a toggle between inversion or not, then that’s fine with me personally. There’s more to this change though, and I didn’t think it was fair at all the way Fredo’s comments were being mischaracterized (in my opinion). But hey, I thought dude was an SB employee too
I think that’s it, actually. I have some history in development (I was a security principal for a rather large software vendor) and these changes are not made flippantly. There are dependancies involved, and (according to others) this was arrived at by both beta testers and the dev team. Maybe you guys should get on the beta team so your voice is better represented? I think that would be far better than some “open letter” to the devs (you actually want the program manager, not the devs I think). While people like to be “heard,” I found Fredo’s response quite refreshing - “Extensive discussions were had, and this was the conclusion. It is now the way it is, and as I understand it they will not go back.” I mean, I’d much rather be told the hard truth than some mushy “We hear you and feel your pain; thoughts and prayers” kind of thing.
I’m sure there’s some level of disconnect on what is considered “impact” here, but that’s just my opinion. I saw references to people with ADHD in loud environments as some manner of design dependency and was left scratching my head on that one.
I’ve been trying to understand the fervor here, and can’t. It seems absolutely trivial to me, but that’s not the point and it doesn’t matter what I think. I trust people are having a hard time. I even went so far as to create a macro/PLE (thanks to @mlib for prompting me to get more into PLE) to change the color of the selected track, and that has merit too. The PLE actually allows color changes by increments, so I can see an “up/down” key combo to alter the color for the select track if it’s really an issue for folks.
Thanks.
1 Like
It would be nice to be on the beta team, but unfortunately I wouldn’t have enough time to do any testing. I run a postproduction facility with multiple Nuendo setups and it would be impossible to implement beta versions in our daily workflow. But I’d love to contact beta testers and hear them out.