Understood.! Good to know.
Looking forward to seeing others’ responses here, to your reports.!
And this exactly shows what respect you have against other users. If they do not fit into your scheme they have no experience.
There is more in the world than forums and social media… there is a real world.
Anyway, you made your point and I’m tired of reading all these completely off-topic and continusly repeated, not ending responses. To avoid that I put you on ignore from now.
4 Likes
Well, it’s your right to ignore me, since you feel it.
But the Janus’ comment:
I really wish you would stop your constant patronising of the Dorico/Steinberg Team(s).
Made me think that he has no previous experience with Steinberg, and he didn’t noticed how the things changed after the Dorico team came to the company. Then I decided to check if my assumption is correct. So, my assumption was proved from what I’ve seen on his profile here.
I’m not disrespectful! I apologized to him, in case I’m wrong.
I agree with you that the discussion went a way too off-topic.
Would be better to move back to the original discussion here.
Best wishes,
Thurisaz
To answer that part of the post.
The surveys about the user expectations and wishes about certain features won’t ruin the privacy of the development process. Many successful companies do surveys among their customers.
Best wishes,
Thurisaz
Perhaps the collected nay-sayers here should start their own software company. Doubtless, in no time at all, they could whip together the ideal Notation/DAW program, given their conviction that “programming is easy.”
5 Likes
This survey was made some years ago, back when the old forums where active. I’m sure they took that in consideration, along with all the feedback from the forum since and other sources, and that’s the path they’re following. I’m pretty sure this is the result of those market studies.
3 Likes
Well, we all know how reliable polls are. 
Even the questions in a public survey can expose data. Sometimes I think there are reasons why it’s extra tricky. There can be benign secrets or confidences on both sides. Projects, plans, associations…
I worked for a company where we participated closely with certain vendors and were allowed to speak with them privately pretty freely. But when those same vendors asked us to share publicly for them at conferences or in certain materials - it got complicated. Sensitivity and regulatory concerns I can’t describe. Lots of vetting of content if it was approved.
However they’re doing it now has certainly worked for me. As far as opportunities to give input, we know they read everything here carefully.
A very big thumbs up from Guy Michelmore on Dorico and Cubase 14.
3:20 and 16:16 into the video.
3 Likes
Thanks for listening to the wishes of the user base. I personally think that the expression maps has been implemented very well and intuitively in Dorico. If you need time to get this properly running in Cubase, that’s totally understandable - we don’t know how complex this is.
Nonetheless, this is the most requested feature at least on this forum. Nobody of us knows what is going on “behind the scenes” at Steinberg regarding expression maps, but I can understand that this discrepancy between “we hear you and have prioritized it higher” and the yearly disappointment is increasingly frustrating for some.
Apart from all of that, I’m very excited what Cubase will bring to the table in regards to Dorico integration!
Don’t skip past the first minute though!
2 Likes
Congratulations on all the work so far. I tried a trial export from Cubase to Dorico yesterday and the result looked good. I imagine if one is canny about instrument naming in Cubase then Dorico will try to intelligently assign similar instruments. I was using a noteperformer template with my trial attempt and did not get this result but will give it another go at some point.
I am certainly even more excited if we eventually get Cubase import options for both Music XML AND Dorico project files. Bet that would be a real workflow revolutioniser in things like Score to Daw or Daw to Score 
Well done again to you and the rest of the Cubase/Dorico team. As a Nuendo (and Dorico 5) user these days I guess all these new features will come through to Nuendo 14 in good time.
3 Likes
He was having a field day. I don’t think I have ever seen him so excited before, and that is saying a lot.
Can any Dorico document file (*.dorico) be read in Cubase Score Editor?
1 Like
No, and XML import is gone now as well.
To port projects from Dorico > Cubase, export from Dorico as MIDI.
If you need to import XML stuff into Cubase, roll back to Cubase 13 or 12 (You can have multiple versions of Cubase installed at the same time)…import your stuff and save it as a Cubase project. Now you can bring those projects into Cubase 14, but the ‘score layout’ data from the older Cubase versions will be lost. At least you can still get pure performance tracks from XML this way.
2 Likes
Ya gotta love some “frisky” software!
1 Like
Thank you! Then this is a good new feature for Cubase users who do not have Dorico.
Was there any clarification as to why this was done? I can’t seem to find anything. Thanks.
It’s just a matter of priority. We are never able to do everything we plan to do in a single release, even when the project takes multiple years, as this one has done. We will add the ability to import MusicXML and Dorico projects in future releases, though I can’t say when.
14 Likes
Hi Daniel,
Yes, no doubt the new Cubase Score Editor needs time to evolve and move feature to be implemented.
The import of MusicXML and Dorico Project files is an important thing, but something else would be even more useful to those of us, who are using both Dorico and Cubase.
- Project Transfer and Project Transfer Update function.
It will allow us to directly transfer projects between both app, and update them, if additional changes were made either in Dorico, or Cubase. - Still the best scenario will be when Dorico and Cubase are deeply enough integrated, that Dorico could be used as a real-time Score Editor and Cubase as real-time MIDI and Audio Editor simultaneously for the very same project. Of course this needs a lot work and effort.
Of course the import of Dorico Projects, or the Transfer of Projects forth and back need additional major changes to be made in Cubase - Expression/Percussion Maps, Independent Voice Playback, Playing Techniques, probably the Playback Templates as an optional feature for the transfer / transfer update process (in case we are using NotePerformer in Dorico, we cannot transfer the playback template to Cubase. We’ll need another one for Cubase. In case we are using the very same VI instruments setup in both apps, then would be nice if we could just transfer everything as it is for further adjustment, mixing and mastering).
Best regards,
Thurisaz
1 Like
@Thurisaz , although the recent Dorification of Cubase’s Score Editor is a big first step, it’s obviously not the end station by far. I’m pretty sure much of what you’re suggesting is already planned.
3 Likes