I still find the proofreading function needs work. I’ve written for bowed strings using the open 3rd string and then one stopped note on the 4th string, followed by the open 4th string. Proofreading is telling me that all of the notes on the 4th string are “too low.” But this is not true. The passage is full of playable notes like this, so I have to dismiss a large number of warnings. I do this because elsewhere proofreading is doing a good job.
Like this?
Proofreader isn’t giving me any issues. Can you upload the project or the relevant portion of it?
1 Like
I had the same problem with guitar harmonics and, sometimes, with fingerings but I think Soundproofing does a very helpul job, in genera
I have already taken care of all the issues presented by proofreading. I don’t want to hit that button that brings them all back! But here’s a snapshot of a passage for violin where proofreading claimed that the notes from middle C and below were “out of range.” Also in another passage low B and G#.
If you want specific help, you need to upload your project or a portion that illustrates the problem as @sjanssens asked.
2 Likes
Isn’t the playing range and « confortable range » as it is expressed in the proofreading comments linked to the ranges set in the instrument definition? If so one can change them if needed.
Certainly those notes are in the comfortable range of a Violin. If this was an XML import, it’s possible that the Violin instrument may be a “custom” one, rather than Dorico’s default. Or perhaps it’s a renamed other instrument.
But without seeing the actual document, this is just guesswork.
4 Likes