What I think would be ideal is having cubase allow you to make those new folders and then hide the ones it couldn’t seperate the metadata to form the correct tree. Ie Valhalla in other. Creating customs is great. Not if there’s doubles tho. Pretty much just the hide button. But for folders…
I too find that Alt-F4 not exiting any more is an annoying quirk.
I really hope this happens
I see that competitors are spreading, developing and succeeding at a rapid pace
Thank you for the amendments you mentioned, as they are really important for the company, the users, and the competition in the market again in a strong way.
I’m starting to feel that the developers don’t have a good research team to look at and research what the important features are instead of releasing a new set of plugins and adding some things that were supposed to be present in previous versions.
Nothing new for me. The company should think about fixing the problems and fixing the user interface, which is considered bad compared to any interface.
And also working on creating something new that distinguishes the company to maintain its position
I also do not know how difficult it is to implement, but I see that it is already present in some programs, including the Mozilla browser
And Visual Code and jet Brain
And DaVinci Resolve
And others
It is definitely considered something unimportant, and there are many problems that must be fixed and things that must be improved
But perhaps if they actually started implementing simple steps and provided us with maintenance updates gradually, it would be very welcomed by users.
…
I personally prefer dark colors, as I usually work in a low-light environment
I find that dark colors are comfortable for my eyes
Perhaps the solution is more customization options for windows, colors, and fonts
1 Like
What is also very very important to realise is a lot of the new features companies are touting like Live 12 are not new. Live 12 is a huge let down and a missed opportunity. That’s if your an intermediate to advanced producer. But these companies are nailing features that are super shiny to beginners. It feels like the pre established market where some more innovation is required for more advanced users is being swept to the side for new doe eyed ones.
A mpe soft synth and multi distortion is the last thing established people want. But everyone I know just starting is music is hyped.
As I said though. Cubase 13 is the first we’re I have thought. “They have a chance”. They’re starting to change the perception. Which is half the battle….its always going to be a little hard.
1 Like
Do you realize Live 12 allows for further integration of Max For Live including the ability to generate and transform MIDI directly in the editor? This means more people can develop brand new features more directly into Live 12. That’s huge.
1 Like
I truly love ableton and max for live. That and the piano roll features are really all cool. In fact I’m teaching a class on AI integration at liveschool in Sydney in December so it’s not lost on me the power of max. I think that and the Piano roll and a few other things are the final pillars preventing a steamroll from bitwig.
The gap between S1 and cubase for me is larger.
But as someone whose had a chance to play with live 12 and has moved to bitwig these are my gripes.
The new browser. Awesome but unlike bitwig does not currently incorporate AI meaning that aside from those inbuilt to live. Everything else must be tagged the first time and then can be searched.
The ability to edit audio in the bottom section as well as arrangement.
Something akin to bitwigs operators as well would be welcome.
The new midi generation stuff brings it close if not in line with fl’S but again a huge missed opportunity to go above and incorporate artificial regeneration.
Bounce in place
Ara
Overall I’m not unhappy. But with the success of push which is a powerhouse it has diversified where the attention is.
One things for sure. Without max for live and the community innovating it. Ableton would have a hard time.
I give bitwig 2 years before they become a major player against ableton.
Although a little bird from ableton inferred that they actually might have some private sort of rnd investment role in bitwig 
who knows what’s really going on
How is that an issue? Do you always work on only one project at a time? While I open and close Nuendo once or twice a week, it’s dozens of times for projects.
The behavior you described is not desireable at all.
I close Cubase many times a day. Cubase & Nuendo also “close” themself quite a lot. Happening little bit less with v13 than previous versions.
I thought first that the Hub opens when closing project but its lurking at background forever.
Only UI grievance for me is that I need sun glases when opening Audio Pool. All other windows are dark or gray but Audio Pool is brighter than sun.
Oh, this pool window, how annoying it is to the eyes
Also, the menu in general is white old Win95 Style ,Alert and loading Messages
I prefer dark colors,
The bold fonts are white color,
These are all things that seem insignificant but when used for long hours they are really annoying
4 Likes
I really try to give developers the benefit of the doubt, but telling me the Command is Ctrl-Q has to be one of the most dismissive things I’ve seen on a forum from a developer.
I have about 10 different applications with Ctrl-Q as the exit shortcut, and I never knew that was the case because I never had to. I only found out because I went and checked after commenting here, because I know for a fact that I have never used that shortcut to exit a Windows application before… until now.
Alt-F4 is the system wide shortcut for Exiting an application since the 1980s on Windows, and it sends the current in focus application an Application Exit message, which triggers that event. The Exit/Quit procedure in a Windows application is generally set to respond to that message, so it generally didn’t matter if the exit command was Ctrl-Alt-Shift-Numpad 4… it would still exit the application with Alt-F4.
You can compile a Win32 or .NET application with no procedure set up to exit the application, and it will still exit with Alt-F4. That’s how fundamental this key bind is.
In order for this to not work, Steinberg had to have gone in and intentionally coded the application to catch this message and send it to a different event and prevent it from exiting the application - which is why the window closes momentarily and then pops up. The system tries to force the exit, but the application intercepts and decides… “I’d rather not.”
It’s something they intentionally broke, and it’s something they should intentionally fix.
What key command is used for Exit/Quit/whatever is not something any Windows user should have to ever be concerned with. It’s a non-factor. Alt-F4 works for everything, anywhere, regardless of what combination is set there.
Short circuiting a system-wide key command like that has to be one of the dumbest things I’ve ever seen an application developer do. And for what benefit to the user?
EDIT: Actually, the second dumbest. The dumbest is DP locking the Windows Key and using it for all manner of key commands in their DAW - so you can’t even Press the Windows Key and search while DP has focus.
1 Like
You certainly do not give the benefit of the doubt. You’re making a mountain out of a molehill, and you’re doing precisely what condemn as dismissive.
As is well-known you can have any keystroke you want for any command.
Simple provocation. You are trolling the dev. Speaking as moderator, this goes against the forum guidelines and simple courtesy.
1 Like
Out of everything one can concern oneself with I’d never have guessed what key command to use to exit the app would be one.
Here’s what I did:
I decided that in order to memorize key commands each function mapped to a ‘unmodified’ key would have related functions on the same key with the modifier keys. In other words, if opening mixer 1 is F3, then I would make SHIFT+F3 open mixer 2, ALT+F3 open mixer 3, and so on. If F4 does X then ALT+F4 will do something related. I see absolutely zero benefit in having “quit” there. Instead I reassigned that to a completely different key combination (SHIFT+ALT+PAUSE/BREAK).
How often do I exit the app? Not that often every day. How often would I use F4 in some capacity? Possibly many times during a normal 8-10hr work day.
1 Like
Exactly how I do/did it.
Because when moving fast, and especially when I have to open up another DAW, I want the application to close when the last document is closed. Alt-F4. Voila. No disappearing-reappearing windows. No Hub pop-ups (not sure why anyone thought that even sounded like a good idea). Just done, over and gone.
If Cubase doesn’t exit fully, it still has all Control Surfaces and MIDI Controllers locked to it, so they cannot be used in the other application.
The fact that we still have to “double exit” the software because of this stupid Steinberg hub is already infuriating enough… after getting our hopes up and insinuating they had “addressed” that issue. They just replaced that stupid Desktop Menu Bar with a Hub Menu… and made it even worse.
The window also does not exit the application when the Close Button is pressed in the title bar. Lol.
And no window on this OS behaves that way by default, so yes… intentionally broken is 100% fact.
1 Like
Are you talking about the exit-functionality or the key(s) that triggers it?
I don’t understand what this has to do with what I was talking about. The window pops up when you close the last document window. If you have multiple open, then closing one project will simply place application focus on a different project. It has literally no affect whatsoever on how you use the application.
I work with people who use other DAWs, sometimes I have to close one and open another one. Not all projects reside in Cubase. Sometimes, I have to use Studio One or Pro Tools. If Cubase doesn’t exit when I assume it has, it has all Control Surfaces and Controllers Locked to itself. These are things that I generally don’t have to think about when using a Windows PC.
Additionally, everything I’ve stated is what Dorico does, and it also has an option in Settings to not open the Hub when the last document window is closed, so that application is fine as far as that is concerned. No one who works on multiple scores in Dorico is seeing problems with this behavior.
It also exits the Hub and Application properly when the on display and I Alt-F4 or click the Close button on the Title Bar.
Nothing about this behavior I have described makes sense. Not even Steinberg’s other products that basically function in the same way behave this way.
1 Like
When I quit Nuendo using the (by me) assigned key command Nuendo closes completely. What am I missing?
@Ehabmxd nice post and very well thought out. I would definitely financially support a cubase and nuendo merger into one program and wholeheartedly agree to the improvements you mentioned. Thanks for posting.
Local Undo
-More Cuemix (4 is not enough The other Daws they Can Add Unlimit)
-Cpu Improve
-Audio Engine Improve
-Update Expresion Map
Of course it has an effect on how you use the apllication.
I work mainly in Nuendo and don’t need to close it when using other daws, but I only work with one project at a time. If it shuts down when I close the only open project, I will have to open it again, which takes longer and, as I said, is an undesireable behaviour.
Now, if they put it as optional, I have no objections.