It’d be nice if there were a fast way of cleaning up passages like this. The problem with the “filter by lowest note” feature is that if there’s a single note on the stem it unhelpfully grabs that too.
That results in a decent workflow for splitting out the bottom notes:
Filter bottom note, paste into lower staff
Filter 3rd from bottom note, reduce into lower staff
Change the rhythm to quarter notes → all the unnecessary high notes are gone because they were on the off beats.
This is quick and easy. Cleaning up the top staff remains tricky to do without a mouse and imprecise with one. Now if there were a filter by register, I could pretty easily tell it: “filter out all the notes below C#5” or “between such and such pitches” and that’d make it quick and accurate.
Another potential workflow is if there were a filter notes by rhythm tool, where you could tell it “only select notes on the beat.” (The other filter notes by rhythm—e.g., “only select the eighth notes”—would be useful in other cases, but not this one.)
I’m confused with Explode. Can you tell me how this can help if one has notated, for example, a single piano piece with no other instruments. Using the original post example, how does this “Do not duplicate notes” keep the Filter->Select->Lowest Note from selecting a none that is the single note at that position? I may be wrong but I think that’s what @joseph.sowa is asking for: when selecting lowest note, there needs to be a way to skip single notes.
I’ve also seen a bizarre result from using that Lowest Note selection process where after selecting the single note, the filter actually then selects different notes than the lowest note.
Not criticizing, just trying to understand the explode approach. Thanks!
