Well I don’t like the idea of separation of the score editor from Cubase so we would think of it as about Dorico. I still think that it should move towards being part of Cubase as fast as possible. For now when working in it I feel like finding myself in a different world. That’s about how modifier keys work, how mouse works (selection, right click, wheel) and so on… The new score editor is based on Dorico, that’s nice, but now it should live it’s own life being a part of Cubase. And I would like to discuss its features here, not on Dorico forum)
1 Like
And those are things I’m sure are on the list where they would like to improve the behaviour there. Dorico is written in a different UI framework than Cubase - pretty much all of Steinberg’s products are written in the industry standard Qt framework, except for Cubase/Nuendo which is made with its own framework. A lot of the behaviour of selections not necessarily working as expected etc likely has to do with the mixture of UI frameworks in place here, as the Score Editor seems to function more or less like a Dorico “plugin” inside Cubase, the way you might integrate Wavelab within Cubase or some such thing (like ARA). When performing certain operations in the score itself, it is visibly Dorico/Qt handling these inside the “plugin” rather than Cubase (ex. the font dialog that appears when you add system text, and likely a lot of the selection/navigation stuff). Hopefully it is possible to get these things sorted out better even given the differences. I’m pretty sure that if Cubase/Nuendo were newly developed today instead of being existing products, they would likely have used Qt for them instead of a custom framework. I’ve also wondered whether Cubase/Nuendo might eventually be moved to the same Qt framework as Dorico in the future, to avoid Steinberg having to maintain its own different framework only for Cubase/Nuendo and potentially to improve compatibility, but I’m not sure how viable this would be in reality due to the large number of changes it might require in the Cubase/Nuendo code.
The main reason I’m suggesting asking on the Dorico forum in this case is because it is more likely to get directly to the developer familiar with and responsible for that part of the code.
1 Like