In the score for my Brass Quintet the automatic quantization is inconsistent. Some triplets are shown properly, others divided into weird 16th note/rest combinations (see attachment - the 2 staves above are correct, the 2 below it are wrong). Sometimes i can solve this with score settings, but more often when I correct the notes I marked by selecting the instrument in the list on the left, it changes all the notes I’d corrected earlier on that staff. I set “Auto Quantize” and uncheck “Adapt” and “Deviate”, as it suggests in the manuel. Is there a way to JUST correct the notes you mark in the score without changing all the notes in the staff? I’m sure I’m missing some simple step…sometimes I get the results i want, mostly I mess up the parts I’d already corrected and lose hours of work. Thanks for any tips.
To state the problem more clearly, when I use the Score Settings panel to correct problems like these falsely displayed triplets and click “apply”, it will then also turn all the passages that aren’t triplets on that instrument’s stave into senseless triplets, and vice versa. It seems like an utterly useless tool for notation editing if you can’t perform this function on individual passages without messing up the whole stave.
Well, it does help to dig in to learning the functions that are available in the Score Editor because the settings window is only one aspect.
I suggest you read the beginning of the Score Manual if you haven’t already, so you get the basic idea of what you’re working with, and after trying things out it will be easier to formulate questions.
See especially, Inserting Display Quantize Exceptions
Thanks, that does help. I’ve been using Score for decades in Cubase, but haven’t used Display Quantize in a while, as I don’t recall Cubase ever having so many problems with just recognizing triplets and straight notes, or being so inconsistent about it between parts.
The info you’ve provided is not sufficient to understand precisely how to help.
Strangely enough, I described exactly what I was trying to do, what the problems were when I did it, and your answer did help. So there’s that.
Lucky!