Re: RhythmicStaff Multimeasure Rests
Jay Anderson horndud...@gmail.com wrote in message
news:58adba261003092132h7283d8d9v980ca4a3c2ed4...@mail.gmail.com...
On Tue, Mar 9, 2010 at 3:19 PM, Neil Puttock n.putt...@gmail.com wrote:
\override RhythmicStaff.MultiMeasureRest #'staff-position = #0.01
Thanks. That works great.
Now I just have to deal with
\context{\RemoveEmptyRhythmicStaffContext} killing my settings. I
remember following the discussion recently, but I couldn't find a bug.
Was one written?
It's especially annoying here.
If I put this in a common file included by both the score and the part:
\layout
{
\context
{
\RemoveEmptyRhythmicStaffContext
}
\context
{
\RhythmicStaff
\override MultiMeasureRest #'staff-position = #0.01
}
}
Then the score looks fine, but since the bass drum (or triangle or
other percussion instrument) rest for very long sections some of the
lines in the part are taken out.
The alternative is to move the RemoveEmptyRhythmicStaffContext to the
score file and duplicate the multimeasure rest stuff below it again.
This is what I'm doing. (Though I should probably put in some cues
which would also fix this).
The cleanest solution would be for either the
RemoveEmptyRhythmicStaffContext to not kill settings or if there is
only one staff in the score the RemoveEmptyRhythmicStaffContext would
just not remove anything (or both of course).
Really these are minor inconveniences. I just want to be sure bugs.
Thanks.
-Jay
Could you clarify what you mean by
\context{\RemoveEmptyRhythmicStaffContext} killing my settings? Which
settings? Could you post a tiny example?
--
Phil Holmes
Bug Squad
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RhythmicStaff Multimeasure Rests
Jay Anderson wrote:
On Tue, Mar 9, 2010 at 3:19 PM, Neil Puttock n.putt...@gmail.com wrote:
\override RhythmicStaff.MultiMeasureRest #'staff-position = #0.01
Thanks. That works great.
Now I just have to deal with
\context{\RemoveEmptyRhythmicStaffContext} killing my settings. I
remember following the discussion recently, but I couldn't find a bug.
Was one written?
It's especially annoying here.
If I put this in a common file included by both the score and the part:
\layout
{
\context
{
\RemoveEmptyRhythmicStaffContext
}
\context
{
\RhythmicStaff
\override MultiMeasureRest #'staff-position = #0.01
}
}
Then the score looks fine, but since the bass drum (or triangle or
other percussion instrument) rest for very long sections some of the
lines in the part are taken out.
The alternative is to move the RemoveEmptyRhythmicStaffContext to the
score file and duplicate the multimeasure rest stuff below it again.
This is what I'm doing. (Though I should probably put in some cues
which would also fix this).
The cleanest solution would be for either the
RemoveEmptyRhythmicStaffContext to not kill settings or if there is
only one staff in the score the RemoveEmptyRhythmicStaffContext would
just not remove anything (or both of course).
Really these are minor inconveniences. I just want to be sure bugs. Thanks.
As long as your score.ly contains
\layout{
\context{
\RemoveEmptyRhythmicStaffContext
}
}
above the lines where you do
\include part1.ly
...
then it should work to have a
\layout{
\context{
\RhythmicStaff
\override MultiMeasureRest #'staff-position = #0.01
}
}
within your part1.ly file.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RhythmicStaff Multimeasure Rests
On 7 March 2010 22:21, Jay Anderson horndud...@gmail.com wrote:
On Fri, Mar 5, 2010 at 10:31 PM, Jay Anderson horndud...@gmail.com wrote:
\version 2.13.15
\new RhythmicStaff
{
%\override Staff.MultiMeasureRest #'extra-offset = #'(0 . -1)
R1
}
Of course this doesn't quite work because all multi measure rests are
moved and not just single whole measure rests.
I've been messing with this:
\override Staff.MultiMeasureRest #'extra-offset =
#(lambda (grob)
'(0 . -1))
I only want to return '(0 . -1) if the multi measure rest length is
the same as the length of a full bar. To get at the measure length I
need to do something like (ly:context-property context 'measureLength
#f). How can I get at the context from a callback function like the
one above? or is there a better way to move all full measure rests
down?
Try
\override RhythmicStaff.MultiMeasureRest #'staff-position = #0.01
There's a nasty hack in ly:multi-measure-rest::print which changes the
position of single full-bar rests if staff-position = #0 to ensure the
default position is effectively staff-position = #2; setting it very
slightly off tricks the code so it doesn't perform the shift.
It's interesting to me that in this example the whole rest in the last
measure works correctly:
That's because it uses a different print function (ly:rest::print).
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RhythmicStaff Multimeasure Rests
On Tue, Mar 9, 2010 at 3:19 PM, Neil Puttock n.putt...@gmail.com wrote:
\override RhythmicStaff.MultiMeasureRest #'staff-position = #0.01
Thanks. That works great.
Now I just have to deal with
\context{\RemoveEmptyRhythmicStaffContext} killing my settings. I
remember following the discussion recently, but I couldn't find a bug.
Was one written?
It's especially annoying here.
If I put this in a common file included by both the score and the part:
\layout
{
\context
{
\RemoveEmptyRhythmicStaffContext
}
\context
{
\RhythmicStaff
\override MultiMeasureRest #'staff-position = #0.01
}
}
Then the score looks fine, but since the bass drum (or triangle or
other percussion instrument) rest for very long sections some of the
lines in the part are taken out.
The alternative is to move the RemoveEmptyRhythmicStaffContext to the
score file and duplicate the multimeasure rest stuff below it again.
This is what I'm doing. (Though I should probably put in some cues
which would also fix this).
The cleanest solution would be for either the
RemoveEmptyRhythmicStaffContext to not kill settings or if there is
only one staff in the score the RemoveEmptyRhythmicStaffContext would
just not remove anything (or both of course).
Really these are minor inconveniences. I just want to be sure bugs. Thanks.
-Jay
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RhythmicStaff Multimeasure Rests
On Fri, Mar 5, 2010 at 10:31 PM, Jay Anderson horndud...@gmail.com wrote:
\version 2.13.15
\new RhythmicStaff
{
%\override Staff.MultiMeasureRest #'extra-offset = #'(0 . -1)
R1
}
Of course this doesn't quite work because all multi measure rests are
moved and not just single whole measure rests.
I've been messing with this:
\override Staff.MultiMeasureRest #'extra-offset =
#(lambda (grob)
'(0 . -1))
I only want to return '(0 . -1) if the multi measure rest length is
the same as the length of a full bar. To get at the measure length I
need to do something like (ly:context-property context 'measureLength
#f). How can I get at the context from a callback function like the
one above? or is there a better way to move all full measure rests
down?
It's interesting to me that in this example the whole rest in the last
measure works correctly:
\new RhythmicStaff
{
\time 6/4
R1.
R1.*10
r1 r2
}
Thanks.
-Jay
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
