Feature Integration Request for Simplified Note Selection

Dear developers,

Hello,
Currently, when selecting regular notes without grace notes, or grace notes without regular notes, the following properties are visible:

  • hide/show note head
  • hide/show stem
  • hide/show ledger line

While these features are invaluable, the process of hiding or showing them individually can be somewhat cumbersome and time-consuming. This often disrupts the flow of work, making the experience less efficient than it could be.

Therefore, I humbly request that these properties be integrated into a more streamlined process. By doing so, users would be able to manage these features more effortlessly, allowing for a smoother and more intuitive workflow.

Your consideration of this request would be immensely appreciated, as it would not only improve the usability of the application but also enhance the satisfaction of its dedicated users.

Thank you very much for your time and attention to this matter. I look forward to the possibility of seeing this feature integrated in the near future.

Warm regards,

For my own usage I made a little script for this:

local app=DoApp.DoApp()
app:doCommand([[UI.InvokePropertyChangeValue?Type=kNoteHideStem&Value=string: "true"]])
app:doCommand([[UI.InvokePropertyChangeValue?Type=kNoteHideNotehead&Value=null: ]])
app:doCommand([[UI.InvokePropertyChangeValue?Type=kNoteLedgerLineHide&Value=string: "true"]])

I put it in the Script Plugins folder and invoke it with the jump bar. Of course this only works in Engrave Mode.

hide notes script

2 Likes

Under what circumstances do you need to completely hide notes?

(I’ve been using this for ā€žhelperā€œ notes, for example for extending beams and similar tricks. Of course I don’t know OPā€˜s motivation.)

EDIT example

I have been making practice sheets for my teenage student who is learning to compose. I am currently working on the following material from Beethoven’s Cello Sonata:


Last term, I used Bach’s Inventions from No. 5 to No. 15. These were suitable because Bach does not use many articulations. However, Beethoven’s music contains a lot of dynamic markings, articulations, ties, and slurs. I spend too much time on that.

My student does not have enough experience composing music of the common practice period, so I think that filling in the blank bars by guessing based on the provided information is a good exercise to bring her up to standard in a short time and help her pass the exam.

(I think these materials could be published later…)

1 Like

Thanks!

I made some scripts as follows:
Archive.zip (9.2 KB)

Yes, that’s right - I also use all sorts of hiding things for worksheets for students.
@prko that looks like very dedicated teaching ! :+1:

1 Like

I suppose I’m not really sure why, in the case of leaving blank bars for a student to fill in, the original music needs to be there in the first place. Of course you need to ensure the bar is wide enough to write in, but chances are you would actually want the bar to be somewhat wider than it would have been in the published original in any case, because people (especially students) can generally not handwrite music with perfect rhythmic spacing.

1 Like

Yes, you are absolutely right!
But there is one more thing to consider:
After filling in the empty part, the filled parts should be compared with the original score. To compare two scores quickly, the layout of both scores should be the same. Otherwise it might be difficult to find certain positions or elements in certain bars.
So I want to make some parts invisible.

Deleting an element changes the width of the bar. This leads me to change the width of each bar, which is less efficient…

2 Likes

That is a sound pedagogical consideration. That kind of 1:1 visual simplicity is especially helpful with younger and/or less experienced students.

Per Daniel’s valuable observation, then, you could set your note spacing wider than you would for a ā€œregularā€ score to ensure there’s enough room for the handwritten version.