I’m super happy about the new proofreading feature in Dorico 6. Now that this feature is in place, I hope to see lyric proofreading in future updates, specifically, an alert when there is a melisma that is missing a slur, and when there are lyric extensions that are either missing or unnecessary. (When copying/pasting lyrics, as well as importing files, sometimes there are issues with lyric extensions.) Adding these to the proofreading function would help speed up the work in choral music.
What I love about the proofreading feature : it will improve (as chords have) and I am quite confident that it will be impossible to work without it in a very short time, in many areas of the work. It needs a lot of fine tuning to lower the noise floor (those indications that take room and are not really relevant), and many areas are not covered yet, but the Team has been clear about it: it’s going to improve. As this is a feature that none other have, how couldn’t they make it so much better that anyone could see how valuable Dorico is?
The most advanced music notation software has done it again, and twice in this update: proofreading and cutaway scores.
We have plenty of ideas for further things to warn about via the new Proofreading panel, but we welcome all suggestions, so please let us have them.
(We have so many ideas that we could easily occupy the entire team working only on proofreading features, but there are other things we also need to do!)
While I’m happy to accept the proofreading as “warnings of possible problems”, there’s plenty of vocal music that doesn’t bother with slurs on melismas.
But for missing extensions lines – or worse, extension lines extending where they shouldn’t – I’m all for circling in thick red pen, and having David Hemmings screaming in your face.
+1 for this! I love the proofreading feature, but for lyrics it would be superduper helpful.
As posted in another proofreading thread; here’s an example of extension lines that happen daily (or maybe even hourly) with me when copy-pasting lyrics
Yes, this look familiar!
No, Anthony Hughes himself talks about it in the little video where he presents this feature.
I think this is the most sought after correction ever, five days after an major update