Thanks Steinberg and two observations about Cubase 15

[Tomateck]

Thanks because you finally heard the voice that was shouting from the end of the tunnel and asking for:

• full native zoom and UI scaling;

• Native MacOS dialogue windows that are perfectly conforme when macOS switch automatically in dark mode;

• A better UI color customization experience;

• A more comprensive Audio settings location menu;

Now I want suggest/request:

• A more modern Pool window with a consistent look as the others in Cubase, it’s time to replace that 90s look

• Native plugins graphic that do not destroy the details with bad pixels when zoomed at 50% or more;

And yes, Thanks for this version 15!

[gstar82]

Scaling of the channel eq window would be great too.

[estevancarlos]

@Tomateck

A more modern Pool window with a consistent look as the others in Cubase, it’s time to replace that 90s look

I propose that the Pool be integrated with the Media window. They provide a lot of overlapping functionality and I think it would simplify things. If you need to find media local to a project OR on your computer, you should use the same window.

I created an interactive Mockup (a few years ago)

Figma

[estevancarlos]

And this gray empty box on the left hand side was always a head scratcher. I know it represents where an image is supposed to go but it’s an odd UI decision to leave it there when not in use.

[Evgeny_Brodsky]

obviously you know that you can turn it off. i dont know anyone who use it

[bnz]

I couldn’t resist looking this up.

Cubase VST 5.1 (2001):

SX 1 (2002):

Cubase 15 (2025):

[bnz]

Result: you can’t say 90s. It’s clearly 2000’s

[antic604]

@estevancarlos

And this gray empty box on the left hand side was always a head scratcher. I know it represents where an image is supposed to go but it’s an odd UI decision to leave it there when not in use.

You know you can right-click on a channel and disable the pictures altogether?

[bnz]

By the way, personally, I’d prefer it not to be integrated with the mediabay. The one thing is project specific, the other thing is a database across all projects. Mixing these up would be rather confusing for me. However, I do think that a unified project data window could make sense, like with project setup, project colors, project notes, project pool etc.

I don’t think there is something inherently broken with the pool window. But it needs a visual overhaul with the unified dark design, some reworked buttons and so on. Along with the preferences which are also quite old now. Especially the preferences need an overhaul like searchable settings, better organization, better saving and setting sharing mechanisms etc. It is in my opinion much worse than the pool window. But then again, both are parts of the software you usually don’t touch once they are set up.

[Tomateck]

@bnz

Result: you can’t say 90s. It’s clearly 2000’s

ahahahah, sorry!!!

@bnz

I don’t think there is something inherently broken with the pool window. But it needs a visual overhaul with the unified dark design, some reworked buttons and so on. Along with the preferences which are also quite old now. Especially the preferences need an overhaul like searchable settings, better organization, better saving and setting sharing mechanisms etc. It is in my opinion much worse than the pool window. But then again, both are parts of the software you usually don’t touch once they are set up.

Totally agree with you

[estevancarlos]

I’m just remarking on the UI design. It’s usual to leave an empty box.

[antic604]

You mean there shouldn’t be a frame around it?

[estevancarlos]

If a user is not placing an image there, the empty box is no longer needed. The UI should assume that if they don’t place an image there, it means they don’t want to use it at the moment. So it should remain empty. Same approach in Studio One and Logic.