Steinberg has released Dorico 6.2.40, a free update to Dorico 6 that rebuilds a large part of MusicXML import, according to Scoring Notes. The work came out of musical theatre projects moving shows from Finale and from Sibelius (via Dolet) into Dorico, and out of publishers moving Sibelius material across for new editions. The release also includes engraving refinements, better MusicXML export and more than 80 bug fixes, fourteen of them in import. For anyone who uses music transcription software to get a part out of a recording and then opens it in a notation program, this is the part of the update that matters.
Why this matters if you want a score out of a recording
Every automatic transcription ends up in a notation program eventually. We export MusicXML, you open it in MuseScore, Sibelius, Dorico or Finale, and you fix what the machine got wrong. The import step is where a lot of that work either gets easier or gets thrown away.
MusicXML is a description of a score, not the score itself. It carries notes, durations, text, dynamics and some layout, but it does not always say what a piece of text is for, and it does not describe every aspect of a page. The importing program has to guess. Dorico 6.2.40 makes fewer guesses wrong.
The changes that matter most at the desk:
| What changed | What it means for an imported transcription |
|---|---|
| Text formatting | Font family, size, bold, italic and underline survive, including changes within one instruction |
| Musical markings | Tempos, dynamics and playing techniques keep their wording, including qualifiers, and become native Dorico items |
| Gradual dynamics and tempos | A "cresc." or "dim." with a dashed line becomes a real gradual dynamic; dashed lines after "rall." and "accel." set how long the change lasts |
| Page layout | Page dimensions kept exactly rather than rounded to the nearest paper size; odd and even margins imported |
| Instrument changes | A part with several instruments becomes one player holding all of them |
| Error recovery | Invalid durations or tuplets no longer push later music out of place; Dorico recovers at a bar boundary and adds a comment |
Two of these are quietly important. First, dynamics and tempo text now become native items with playback behavior, so a crescendo you imported actually does something in playback rather than sitting there as a text box. Second, the error recovery. A transcription that has one bad tuplet in bar 12 used to risk displacing everything after it. Now Dorico tries to pick up at a reliable bar line and tells you where it did.
What it changes in practice, and what it does not
It changes the round trip. If you transcribe a busy arrangement, separate the stems first with the stem splitter, export MusicXML and open it in Dorico, the first page should look closer to what you heard: the tempo marking reads "poco meno mosso" instead of "poco", the page is the size you set, and the drum part is a kit built from the instruments actually in it rather than a generic set.
It does not change the notes. This is worth being blunt about. Dorico 6.2.40 interprets a file better. It does not make the file more correct. If the transcription missed a ghost note on the snare, or heard a triplet where the drummer played straight eighths, that error arrives in Dorico exactly as it left us. The update moves the editing work from "fixing what the importer broke" to "fixing what the transcription missed", which is the work a musician should be doing anyway.
It also does not fix everything, and Steinberg says so. MusicXML does not always say what a piece of text is for, and Dorico still has to infer some things from formatting and position. The results depend on what the source application exported. A file from Finale may import better than a file from a program that writes a thinner MusicXML. And the recovery from rhythmic errors can still leave missing or incorrect music: Dorico adds comments and warnings, but those passages need checking against the original.
The new import preferences are worth knowing about. There are five, in the Import section of the MusicXML page of Preferences. Four are on by default: import page text and templates, import layout settings, import engraving defaults, and recognize musical markings in text. The fifth, importing chord symbols as local to individual instruments, is off by default. Turn it on when the guitar and keyboard parts have different chords at the same position, so each keeps its own instead of being merged. All five apply to subsequent imports only, so existing projects are unaffected.
Our view
The honest trade-off is between fidelity and control. A Dorico that preserves more of the source file is a Dorico that overrides its own defaults more often. If you have a house style, a template, or a set of engraving rules you apply to everything, some of these new import behaviors will fight you. That is why the four on-by-default options can be turned off: you can choose to keep musical instructions as text, or use Dorico's defaults instead of the file's. Learn where those switches are before you import a 40-page chart.
The second trade-off is trust. Error recovery is a good thing until it hides a problem. A comment in the score saying a passage was repaired is only useful if you read it. Build a habit of checking the comments panel and the first and last bars of every imported part against the recording before you print anything.
The open question is the one Scoring Notes raises: results depend on the source. We can tell you what our MusicXML contains. We cannot promise it will import as cleanly as a file exported from Finale, because the two files are not the same kind of document. If you hit a systematic import problem with our output, tell support and include the file. That is how this gets fixed on our side.
Who should care most: arrangers and copyists moving theatre or commercial charts between programs, teachers preparing parts for students, and anyone who transcribes regularly and has been correcting the same import mistakes by hand. If you write straight into Dorico and never import, this update is mostly bug fixes and engraving polish.
What to do next
- If you have a recording you need notated, transcribe a song and export MusicXML rather than MIDI. MusicXML carries the text, dynamics and layout that this update now preserves. MIDI carries pitches and timing, which is what you want in a DAW, not on a page.
- Separate the mix first. A clean drum stem transcribes better than a full mix, and a better file imports better. The stem splitter is the first step for anything dense.
- If you work in a DAW and only need the notes, the audio to MIDI converter is the shorter path. If you need a page, stay with MusicXML.
- Check what your plan includes before you start a long project: pricing and plans describes the shape of the offer, and the numbers there are the current ones.
- Before you import, read Notation Files: Diagnose Before You Edit. Most import problems are visible in the first ten seconds if you know where to look.
- If you are moving old Finale or Sibelius material rather than new transcriptions, our notes on Maestro Imports Finale Files cover where layout still slips.
One last thing. A transcription of a copyrighted song is a derivative work. Importing it into Dorico, cleaning it up and printing it for your own practice is one thing. Distributing, selling or performing it is another, and the rules differ by country. Check with the rights holder or your local licensing body before you share a score.
