Thanks for reiterating. I was being dense when replying and have since
figured out the same, was just meaning to reply again and then saw your
message :)
Thanks for the help and all the best!
Simon
On 10/02/2023 00:02, Saul Tobin wrote:
I think the reason is that the mark engravers belong to
I think the reason is that the mark engravers belong to the staff grouping
context, which isn't removed along with the child staves. Structuring the
code like this avoids the duplicate marks:
\version "2.24.0"
\layout {
\context {
\Score
\remove Bar_number_engraver
\remove
Hi Saul,
On 08/02/2023 22:03, Saul Tobin wrote:
Is there a reason to have the marks in a child context rather than
just a simultaneous music variable?
You mean the Devnull? Just convenience. It works well with the way I
assemble different ChoirStaffs for different output formats and adding
Hi Simon,
Is there a reason to have the marks in a child context rather than just a
simultaneous music variable?
Saul
On Wed, Feb 8, 2023 at 10:24 AM Simon Albrecht
wrote:
> Hello everyone,
>
> I am working on a large score with several ChoirStaves and want to have
> BarNumbers and Marks in
Hello everyone,
I am working on a large score with several ChoirStaves and want to have
BarNumbers and Marks in the middle as well. However, when I use
\RemoveEmptyStaves, removed Staves still have their BarNumbers etc.
How can I solve this without hard-coding where the Staves are removed?
