I’d love it if Cubase Pro would automatically import Expression Maps from supported Virtual Instruments (e.g. HALion [Sonic] & Opus) like Studio One Pro does. I just load the instrument and the Articulation Sets are automatically imported. No manual step is required.
All that trouble to fix Menus and Window Management in Cubase, and the Cubase Hub Menu is missing standard Windows Menu and Window Decoration buttons. Have to mouse down to a [Quit Cubase] button to exit it, unless you use the Alt-F4 Key Command.
It’s weird, because they basically copied this from Dorico, but did it “incorrectly” despite Dorico having been doing it correctly for years:
I don’t think comparing generic application interface to skeuomorphic plug-ins interfaces is fair, though.
I also don’t think comparing Cubase to Visual Studio is fair. Visual Studio for Windows is not the same as Visual Studio for Mac (a later acquisition, rebranded and then recieving some code sharing from Microsoft).
Visual Studio for Windows is a mono-platform application built with Microsoft’s own Application Frameworks (e.g. WPF)… and possibly also some third-party extension libraries. Things like “Menus in the Title Bar” and Accented Title Bars are easier to implement on Windows when you use the platform’s native toolkits - particularly for applications built on .NET Framework libraries (but probably also MFC (if they still keep that up-to-date) or VCL (Delphi/C++Builder).
I am not sure how that goes with e.g. Qt. I’ve never developed an application with Qt with that being a requirement, so I’ve never bothered to check. I also haven’t developed an application with Qt since accented title bars became a thing on Windows.
Cubase cannot be developed in that way, because it’s actually a cross-platform, predominantly single code base application. Trying to make it the same on both platforms is what gifted us the awful window management on Windows before v13. It behaved on Windows as if it were a macOS application.
It’s also why most cross platform DAWs do not use standard Windows custom controls, iconography, etc. in many areas (and they even shuck some standard key commands). They use frameworks like Qt and then create their own overall design that they themselves keep consistent across the various ports of their application (macOS, Windows, Linux… whatever). If they didn’t, then the entire look and feel of the application would differ drastically from platform to platform.
I honestly don’t think these UI quibbles are big deals, personally. I think there are bigger workflow or functional considerations worth discussing.
Emphasis on I.
Keep in mind, Visual Studio went through 2 major rewrites of the UI:
- v5/6 Developers Tools → Visual Studio .NET 2002
MFC-> .NET WinForms - Windows XP Design Guidelines
- Visual Studio .NET 2003 → Visual Studio 2005
.NET WinForms → WPF - Windows Vista Design Guidelines
Later versions are basically iterations and optimizations on the Visual Studio 2005 User Experience.
The changes were extensive, but this happened during a time when Visual Studio was a $799+ Professional Developer Suite with a monopoly on the Education Market while also Overlording Windows development… Like Internet Explorer did the Browser Market (except… for an even longer period of time).
Microsoft’s developer tools division was (and is) also quite massive.