Sometimes surprising (and disappointing) the extent to which some, as soon as a new capability appears, tend to “look a gift horse in the mouth.”
3 Likes
Can you say if cc data gets imported as well like cc 11 for expression?
Midi data does not get imported at all. The import only transfers what you see in the score.
1 Like
Thank you for clarifying.
Yeah, I’m wondering if there is any obvious advantage to importing a Dorico project over the prior method (I just export the flow as midi and import that into Cubase. It’s pretty fast and consistent). I already do it that way, which gives me specific control over selecting which flow I import - helpful with individual film cues separated out by flows. If there isn’t much of a difference otherwise in terms of the data which gets imported, re-saving a flow as a separate Dorico project would be an extra unnecessary step for no advantage when I could just stick with the midi file method for now.
1 Like
I think it is a step in the right direction. The main difference will be (once midi data will be in the project), that you don’t have to open Dorico first. I imagine the goal will be to enable users to open and save a project in either Dorico or cubase. In my case the piano work and drum programming would be done in cubase. Arrangements for everything else in Dorico and back to cubase for audio. No exporting
1 Like
Unless, of course, it is the second flow you wish to import 
Don’t get me wrong, I think it’s great, but it does feel like it was taken out of the oven before it was finished cooking. But I am happy to see moves being made in this direction, no doubt.
Many features in Dorico have been introduced with an approach similar to “successive approximation” in math, starting with the basic feature and then revisiting it to add more capabilities.
Maybe that’s why it wasn’t „advertised“ in the Dorico forum. And it’s an maintenance update
They did a big video on YouTube with Dom Sigalas featuring it I’m mostly playing devil’s advocate at this point – I’m not mad about anything, I am fine with Steinberg’s direction and trust in the team. I was just agreeing with others above that projects tend to have more than one flow, so in that case I’ll stick with midi import for now, since it works fine. But glad to see it’s progressing in the right direction. 
Also being Devil’s Advocaat – Dorico only exports MIDI one flow at a time, so having to export separate flows is no slower nor more effort.
Sure. Effort-wise might be the same as deleting other flows in your Dorico project and re-saving as another Dorico project. But to me from an organizational standpoint I prefer to keep things contained in one project file rather than splintering them off into separate projects per flow. Just feels more tidy to me, and if you need to make changes to several flows it’s nice to have them all in one place. But that’s just a workflow preference, others may like the separate project file approach, and I respect that.
File > Export > Flows. Tick the box to Export each flow as a separate file.
Yes, but if you’re exporting to MIDI, those are still all separate files.
Anyway, I’m sure that Cubase will handle multi-flow documents in due course.
1 Like
Thanks, I forgot you can do it that way (since I rarely do).
Of course, but I view those more as intermediary outputs for roundtrip purposes only. Of course you can view Dorico projects this way, too. I reckon I would find multiple Dorico projects to get confusing if I look at a folder many months later, just how my brain likes to organize things.
I look forward to seeing the features develop. I will reiterate I am happy to see progress in this direction!
Well, the Dorico import gets the lyrics imported too, Midi does’nt, does it?
1 Like
Personally, I wouldn’t want it to. If implemented, I hope there’s a way to just get the midi tracks - a checkbox toggle? - so I can apply my own instrumentation to the tracks in Cubase. I can see, though, where many would find instrument import to be useful.
1 Like
Will midi CCs (data) within a Dorico import be in a future maintenance update perhaps? Or will this have to wait for a major release?
cheers,
JDTune
1 Like
The latest version of Nuendo does not seem to support this. Am I right?
For Cubase 14, this is unlikely to change substantially.
Nuendo 14 is a superset of Cubase Pro 14.0.20, and as such also includes the feature to import the notation from Dorico project files. As indicated by Timo in the Nuendo forum, you’ll be able to find out more from today!
1 Like
Thank you very much for reply Stefan. 
Here is a link re: requesting any help with logical editors to extract midi data and some import processes in Cubase forum.
I’ve been playing around with the logical editors so hopefully I can come up some with workarounds.
cheers,
JDTune