bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Staff Grouping


From: Phil Holmes
Subject: Re: Staff Grouping
Date: Thu, 15 May 2014 20:51:14 +0100

"Dave Higgins" <address@hidden> wrote in message news:address@hidden
Phil Holmes <mail <at> philholmes.net> writes:

I actually don't understand what you expect LilyPond to be doing here, but the issue of temporarily starting and stopping staves is covered quite well
in the Notation Reference in the section on Ossia Staves.  Have you tried
adapting code from there?


I expect that when I define a new staff in part1, that the new staff will
stay with part1 and not intermingle with part2 in the score of multiple
parts.  This is only an issue with building the score, not the individual
parts. If the solution is adding more notes of silence and removing them by hiding the staffs, then that's the solution. It's not an elegant solution.
I'm not sure you see what I've put in the examples and what comes out.
Maybe I just need to understand the reasoning behind why this happens
because if there's a logical reason for it to happen, then I'll stop asking the question. Just because doesn't work for me and going around in circles with there's this idea and that idea doesn't explain what I perceive as the problem. I know there are plenty of ways around this, I could take out the new staff and just have chords for the score. I could move the staffs into
the different parts for the score.  It's just odd that if you define a new
staff at the beginning and then go to a single staff and then back to a new
staff that it works fine for the first new staff, but not the second new
staff.

Fine. I've pointed you to some possible solutions. You seem not to have looked at them. I'll not add any further work to try to help.

--
Phil Holmes





reply via email to

[Prev in Thread] Current Thread [Next in Thread]