The new Settings is terrible for our studio

I think the Settings window is so well organized that it’s worth upgrading for that alone!

Hi @csurieux,

exactly. Had a similar thought, even involving some more flexible window handling, or toggles between “simple” and “advanced” settings for some things, since to me the new preset window feels a bit unfinished and in parts impractical. Yet I appreciate its concept.

Basically I’m convinced that it’s a good idea to have all the program settings inside one “unified” preferences window. But then more than one instance of that window might sometimes be more practical (like having the independent Key bindings window) - so why not make sort of a “Lego set” out of the preferences window, and integrate its individual setup into the user profile?

In Cubase, there are now so many intelligent ways to save user presets for parts of an individual workflow, so why not here? Just one (perhaps weird) example: if my workflow involved absolutely no track color changes, why can’t there be a way to just make the preference’s color section invisible, so that there would be less stuff to scroll - upon opening the preferences? A similar concept already exists in Cubase (track visibility). Or why not have a function to prioritize most often used parts of the preferences window by letting the user move them upwards / downwards?

Cheers,
Markus

hehe

You know whats even funnier…look up AREXX…implemented from IBM mainframe. Sounds boring right?

Well AREXX was a system wide script where (good programs) inherited the api stuff with the OS and any program spoke to another via ipc. If this was around today…we would not be having this conversation about automation/workflows. We use to have a company database that drove a paint program to automatically image clients houses

Like applescript or wscript that actually worked and you didnt drive the gui you spoke to the program via a masthead which spoke to everything else including the os

Just a thought

BTW I think the new Electronic Arts (ie James) should be integrated into Cubase and stop all this piecemeal candy like instrument stacking etc…seriously.

Um $323 for that…just NO :slight_smile: IF no filesystem update…DEFINITELY NO NO

Its a nice touch…but half baked re: the op and…have you ever tried to patch settings between projects hehe. You need a database just to find which file a setting belongs to and the mystery of whether it will be exposed ie xml or binary locked

I agree too but it comes down to a more fundamental abstract that no longer seems to be important to the dev at Steinberg

Workflow tiering in manufacturing is a good illustration (and obvious; I owned a factory and manufactured masonry for 7 years)
There is a limited amount of “real estate” to a workers space. Its helpful to break it down to 3 areas. .

  1. Direct contact; Constant access tools are assigned here so the user literally has these in hand reach
  2. 3 Step: High use but ordered for next tier of use
  3. Stored: Outside the core zone of 1 & 2, organised and store for easy access though
  4. Anything else is considered deep store and low use

This was revolutionary to me and when applied to audio production environment…it actually makes work feel great and creativity is so good.
I have friends in China…they sent some of their peeps to Germany for 6 months where they learnt this and took it back to the factories there…mind blowing change.

My hardware and software machinery relies on this.
The point is the OP is actually about this refinement. It relies on granular access to the tools…modular windows allow flexibility for users and
tabbed/tear off ui widgets are the best (in this design context)
satisfying nearly all of the points listed above and in this day and age of dev IDE doing most of the heavy lifting is the reason why I say half baked.

thanks for your thorough demonstration!

i am in a similar boat. using Cubase since it’s inception in Hamburg on Commodore64 up to now.

Steinberg/Yamaha is NOT really interested in professional users (except maybe Hans Zimmer). its constant changing of the GUI and symbol/color variations is totally counterproductive to a honed workflow.

the new Settings require a considerable re-learning of the workflow.

(although my programmed keyboard shortcuts to: Preferences/Device setup/plugins/connections etc. still get me directly into the new Settings and the corresponding tab there!)

also the last couple of updates provide, with very few exceptions, only features for the kids playing with a bit of recording. dumping bunches of “new” plugins which do basically the same basic thing.

but I have to face the reality that i’m a dinosaur of a different recording era.

the future does belong to the kids on the laptops and the “AI-1-button-composing-mixing-mastering” applications.

bummer!

I suppose if it’s not too restrictive, yes. I have a feeling a lot of tweaks will take place about this, including the option to use separate and consolidated windows.

I really love the new settings menu for many reasons. It’ so much more readable, finally the setting items are grouped to those areas where they belong since ever. Search is working very well. We do not need to click save or apply. We see all the changes in realtime and can work in the other/main window(s).

So: what we discuss here, are opinions and points-of-views. In mine: someone really invested time to improve that a lot. Those who struggle with it might in some cases rather have general issues with change.

We discuss pros and cons, which are subjectively weighted by each one with bias.

It must be difficult for “onepostonly” to be not coming back to make another post to reply to this, after writing out what, 4 or 5 pages of thorough logical and metrical analysis likely done to avoid being brushed off as, “having general issues with change”

:rofl:

I mean, they couldn’t have been more exact and thorough. :rofl:

I don’t think this thread was really meant for those who love the new settings to come defend them, hence the OP proclaimed in second paragraph that the changes make sense.

The thread is about development overlooking how some people utilized individual windows to their benefit, perhaps unbeknownst to the developers, and for 20 years.

The average user will benefit from the change, but also, the average user probably hasn’t developed commercial workflow strategies/habits to begin with… It would be like a car company removing a high gear that 99% of the people who drive that car don’t use… But then the people who use that car for racing not being able to drive as fast anymore against other competitors.

The pros is that everything is in one place and people have a search bar, that was established in paragraph 2 and 4. The cons are little more complicated and of which, power/pro users haven’t had trouble finding anything since Cubase 4.

I think if you look at the first video, the OP does a good job of displaying a metrical need for multi-window workflow. Metrics aren’t really an opinion… Unless we are going to get into some deep discussions about the universe and existence :rofl:

Ok, I can agree with that :slight_smile:

It actually is progressive development because everything having its own separate window is a UX trend from the mid 90s, which is not that desirable because of the many issues it has like windows becoming “lost” under others due to improper priorities, which is a common problem for Cubase.

Except for things like the workspaces window, right? If a user needs to have that open “all the time” then this is clearly a regression. And it’s a regression every time you prefer to have multiple windows open that are now consolidated, for example when setting up new templates. You may want to be able to see both workspaces and i/o simultaneously.

In general this change is probably a net positive once (if) they get rid of the wasted space in the window, but for sure there are regressions for some people. Looks like a case where having the cake and eating it would have been both possible and preferred.

I think the OP was implying that the change with the new settings is progressive development, and that there are innate failures within that… sort of like the phrase, “if it’s not broken don’t fix it”.

Another issue here is, there is always going to be “wasted space” or maybe rather, more space taken… Because of the left tab column of which wasn’t there before for individual windows.

How they go about fixing the wasted space per tab size requirements? size recall memory per tab I suppose.

From my perspective it was broken and they have fixed it.

‘Broken’ is a strange term to describe this. Everything has been operational and working just fine prior to V16… All that was required maybe, is that people read the manual/study.

I would consider it more broken now, because there is a mismatch of Global Settings vs Project Settings, a mismatch of useability needs, software preferences vs hardware connections/networking, passive set-and-forget settings vs actively used features, etc, etc, and conflicting UI needs/useability/workflow.

There are more problems now, than there were before - apart from people simply needing to learn the program - which isn’t really a problem or broken component.

As a newbie, perhaps your perspective of learnability is valid, but I’m not sure your perspective on what is “broken” and what is not, would outweigh someone who has been using every aspect of the software for 20 years.

OH come on don’t use that as an argument, my opinion is just as valid as yours. BTW I spent six months wrestling with this area of Cubase 15 before I just gave up.

I can see and respect the argument from the initial poster in this thread and I don’t wish to belittle him/her at all. There is undoubtedly room to improve what is currently in C16 and I do hope that Steinberg take those comments onboard.

However, your argument just comes across as trying to belittle me. Please don’t.

This is a turning point, where old habits will inevitably die hard, which is likely why the OP has their forum name set as such.

By default your opinion is just as valid as mine? Just because you have one? Is that how that works? Is that the case in all industries?

You can voice your opinion… That doesn’t mean it’s more valid.

You’re coming in here as someone who has barely used the software and are speaking to people who have used it for 20 years. At what point do you read a room and know where you stand in it?

I gave clear credit to and acknowledged your perspective on useability and learnability as a new user, but in regards to whether something should be considered “broken”… if I am the head engineer at the studio that has been around for 20 years using a piece of software for 20 years, and you are the intern that just showed up… I’m going to put more stock in my “opinion.”, especially if we are having an important discussion that affects the efficiency of the studio, and thus the profitability, and thus the stability of the jobs of the people employed there.

It’s nothing personal, but you came in here proclaiming something is “broken” to some very experienced users of the software, who make money with it.

You can give your perspective, but be prepared for your perspective to be critiqued as well if you’re proclaiming something like that to professionals. Again, read the room and where you stand in it… If it’s a kitchen and you’re doing the dishes, then you probably aren’t the head chef / if you can’t take the heat…

Anyways, no hard feelings, take it easy.

Yes, it is.

Let’s please stay respectful to one another, no matter how long someone’s been using Cubase.

So I can’t have the opinion that someone’s opinion isn’t as valid as mine?

It’s just not a philosophy I have experienced in any job I have ever worked from the time I am a teenager.

There’s a difference between everyone being allowed to give their opinion vs every opinion being equally valid. At some point, we start measuring validity and or viability… otherwise we get nowhere… whether we are building a bridge, or baking a cake, or developing DAW software.

The thread is a lobby towards Steinberg to rethink their development.

This user has, after proclaiming their happiness with the change as a new user and having that opinion received and accepted by everyone here, has now made an unnecessary addendum which comes across as “lobbying against the lobby” by referring to the software as being “broken” prior to version 16.

As someone who supports the OPs efforts, I am now lobbying against the counter-lobby with an opinion that their opinion is in fact not so valid that they can just start calling things “broken”, because broken is a serious word typically reserved for parts of the program that have a bug or are not functioning as intended.

So it is my opinion, that metrically, we can say that this is not the case, and I am using my experience and others of 20+ years, and the fact that they themself acknowledged that there are components of this Settings change they had zero awareness of (Workspaces) which means it would be metrically impossible for them to understand what is broken more or less.

My opinion is that they didn’t need to come back into thread after already having been accepted by everyone here as a newbie liking the change, and adding the “broken” part,

So with all due respect, and a tint of montypythonesque humour… I stand by my position.