![dorico for ipad dorico for ipad](https://misc-burns.s3.us-east-1.amazonaws.com/Blog%20Photos/Dorico%20for%20iPad%20Review/omniOutlinerfiles.png)
In the meantime, I have one big tip for getting your own Music XML transfers to work as well as possible: Match up instrument names between your programs exactly.
![dorico for ipad dorico for ipad](https://cdm.link/app/uploads/2021/07/8.-Share-your-music-1536x1117.png)
2 Alas, switching between them is clearly a non-starter. 1 So now I need to decide whether Dorico or StaffPad will be my source of truth for the course of this particular composing effort. With the complexity of the scores I’m writing, it’s honestly more effort than it’s worth to try to go back and forth this way: I will spend more time than I can justify just trying to match up the exports from the one in the import to the other.
Dorico for ipad software#
Unfortunately, as every software developer who has ever worked with interchange formats like this knows, this is an incredibly hard problem, and it simply won’t work 100% of the time. That is the dream: to be able to use whichever tool is “right for the job” at any given moment, and have them seamlessly hand the relevant data between each other. I hoped, then, that Music XML would let me have the best of both worlds: working quickly in random contexts with StaffPad, but taking that work back into Dorico regularly.
Dorico for ipad full#
Perhaps a future version with the equivalent of the full Dorico Pro feature set will give me everything I need in that regard: I’m by no means married to handwriting-based input. For example: my Fanfare for a New Era of American Spaceflight has 33 “players” in the Dorico project. In particular, its 12-player limit is simply a non-starter for the kinds of large-scale orchestral works which are what I’m spending my time on right now.
![dorico for ipad dorico for ipad](https://blog.dorico.com/wp-content/uploads/5_Guided_tutorials.jpg)
Combine that with StaffPad’s good - if very imperfect - handwriting recognition, and that was a great way to work this month.ĭorico’s just-released iPad version might seem to fit the bill - but unfortunately does not (yet?) work for the kind of things I mostly compose. An iPad is a fantastic tool for that kind of thing: it is far more versatile than a laptop. I have done a lot of my work this month just chilling on a couch or even lying abed. However, I cannot use it in some of the contexts where StaffPad is particularly useful to me: or at least, not as easily. That makes me want to lean in and just use it as my digital sole tool (alongside a piano and paper and pen). The net is that I want Dorico to be the source of truth for my work. Dorico’s notion of what music is and how music works is much better, and the documents it generates as output are much better as well. However, while I find StaffPad to be a pretty great piece of software for quickly entering ideas as I think of them, I really prefer Dorico as a source of truth for my scores. Over the course of the mini-sabbatical I have been on throughout July, I have spent a bunch of time composing in StaffPad. People who care about music composition and notation software.