Thank you! Glad to hear there is already a solution.
GRB
> This has already been fixed. It was
> https://gitlab.com/lilypond/lilypond/-/issues/6489
>
> It will work fine with the upcoming 2.24.1 version, and you can work
> around it by editing the file articulate.ly inside of LilyPond’s internal
When I tried to recompile a piece I had written in 2.22.1 with 2.24.0, I
got a mysterious error message:
"Exited with return code -1073741784."
Commenting out things until it would compile, I found the problem was
specifically when articulate was applied to a music group with an
accacciatura:
\ve
Success! Thank you for the fast response.
> Your \layout with
> \context { \Staff \RemoveEmptyStaves }
> works as expected, but you want to remove _DrumStaff_, add.
> \context { \DrumStaff \RemoveEmptyStaves }
>
I was thinking of a DrumStaff as a sub-type of staff.
As long as I think of Staff, D
I am having two issues with a custom unpitched-percussion staff in a score.
Item 1: \RemoveEmptyStaves does not remove the percussion staff even though
it suppresses other staves correctly. (I had the same problem with a
non-customized DrumStaff or RhythmStaff when I tried that earlier.)
This fee
Your problem is simpler in one essential way: you are neither adding nor
subtracting any notes, just repitching existing notes. I feel fairly
confident I could solve yours -- use map-some-music to find every
NoteEvent, and for each one, read the old pitch, look up the corresponding
new pitch, and w
In a nutshell, I would like to write a function that would let me replace a
given note or chord with a different chord -- I might have a table of what
gets replaced with what -- but leave all the articulations the same.
Am I missing something obvious?
The \addNote snippet does something similar -
