Thank you for a piece of software that seems to be able to grow into something really great. I’ve been a happy Finale user for decades, but what makes Dorico special is the Flows idea, being able to work on 30 songs/movements within one file. There are some issues, though:
Navigation: I spend most of my time in Write mode. I think it’s a pity that I can’t press Ctrl+1 (Setup) and navigate to another flow using the arrow keys, and then Enter will take me there in Write mode. Or a right-click context menu entry “GoToFlow” that also can hold a keyboard shortcut. In Setup we’ve got all the flows listed, and I’d think this is a natural place to go for eagle-view navigation.
General cleanup: I work in parallell between Dorico, Cubase and other programs. I want to export a Dorico voice as MusicXML from my tenth flow for use in Cubase. In Write mode I select the first note in the flow so that the title bar shows the name of the right flow. I export, and I think everything is fine, but it turns out that I’ve exported the twentyfourth flow, the last one I’ve entered so far. There’s probably some way to do this right, but I did it the wrong way. So I wonder: How does Dorico define the term “Active Flow”? If I think I’m working in the tenth flow, I’d like to be working in the tenth flow throughout the program.
Speed: I find myself entering lyrics too fast. This may not be a problem for most users, I don’t know, but I’m entering lyrics in a file that currently consists of 24 flows and 130 pages. I suspect that the lag is caused by a lot of unnecessary updating. Again, I’d like to mention the term “Active Flow”. When I’m in Write mode and Galley View, I want to be able to turn off updating of all flows except the one I’m working in.
Setup: When I make a change in Setup Mode I’ll have to wait. For each mouse click I make. I’d really like to have a modal dialog alternative here, where I can click around and make changes, and then postbone the lag until I click OK. Then I wouldn’t have to worry about clicking twice and then having to click a third time.
Again, I think the term “Active Flow” maybe should be more important than it is in Dorico so far. Would there be a performance boost if we had an option to “Update Inactive Flows” only on command?
Or maybe I’m wrong. I run Dorico inside Windows 8.1 from an SSD on an Intel i5 with 8gigs of RAM. Is the bottleneck in the hardware?