Re: inconsistent \RemoveEmptyStaves action
On 22/02/2022 23:28, Lukas-Fabian Moser wrote: Do you consider this inferior (or unnecessarily verbose and therefore non-minimal)? No, the motivation for that was more naive. You’re probably right that it would actually be more minimal in a deeper sense to explicitly instantiate the staves. Best, Simon
Re: inconsistent \RemoveEmptyStaves action
On 2/22/22, 3:29 PM, "lilypond-user on behalf of Lukas-Fabian Moser"
wrote:
Hi Simon,
> This is a minimal example for the issue you were having:
>
> %%%
> \version "2.22.1"
>
> upper = { 1 \break 1 }
> lower = { R1*2 }
>
> \score {
> \new PianoStaff << \upper \lower >>
> \layout {
> \context {
> \Staff
> \RemoveEmptyStaves
> }
> }
> }
>
Now that's interesting: For my taste, this is _too_ minimal. I don't
wouldn't recommend relying on the implicit creation of contexts to turn
\upper and \lower into staves (as opposed to, for instance, voices).
So, I would always write
\new PianoStaff
<<
\new Staff \upper
\new Staff \lower
>>
Do you consider this inferior (or unnecessarily verbose and therefore
non-minimal)?
I don't think it makes any difference in this particular situation. Both work
appropriately. Personally, I always explicitly instantiate all of my contexts.
Carl
Re: inconsistent \RemoveEmptyStaves action
Hi Simon,
This is a minimal example for the issue you were having:
%%%
\version "2.22.1"
upper = { 1 \break 1 }
lower = { R1*2 }
\score {
\new PianoStaff << \upper \lower >>
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
}
Now that's interesting: For my taste, this is _too_ minimal. I don't
wouldn't recommend relying on the implicit creation of contexts to turn
\upper and \lower into staves (as opposed to, for instance, voices).
So, I would always write
\new PianoStaff
<<
\new Staff \upper
\new Staff \lower
>>
Do you consider this inferior (or unnecessarily verbose and therefore
non-minimal)?
Lukas
Re: inconsistent \RemoveEmptyStaves action
Hi,
On 12/02/2022 20:22, jh wrote:
This is the shortest example I could figure out how to make
David and Lukas-Fabian have already answered the core question, so allow
me to comment on this: tiny examples are important for communication on
the list and it takes a while to learn how to make one.
This is a minimal example for the issue you were having:
%%%
\version "2.22.1"
upper = { 1 \break 1 }
lower = { R1*2 }
\score {
\new PianoStaff << \upper \lower >>
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
}
I hope that gives you some ideas on how to boil down your excerpt even more.
Best, Simon
Re: inconsistent \RemoveEmptyStaves action
Hi Jay,
Am 12.02.22 um 20:22 schrieb jh:
From one project to the next sometimes 'Frenching' a score works and
sometimes it doesn't
This is the shortest example I could figure out how to make
the second system should be just two staves (and using the same
context etc 5 days ago worked as expected on a different score so this
was copy pasted)
You are using PianoStaff. The only point of a PianoStaff is that it
keeps all its contained staves alive together; to wit, the definition of
PianoStaff is:
\context{
\GrandStaff
\name "PianoStaff"
\alias "GrandStaff"
\description "Just like @code{GrandStaff}, but the staves are only
removed
together, never separately."
\consists "Keep_alive_together_engraver"
%% explicitly set instrument, so it is not inherited from the parent
instrumentName = #'()
shortInstrumentName = #'()
}
So the only difference between a PianoStaff and a GrandStaff is that,
with a GrandStaff, you get what you want.
To be honest, it looks a bit strange to use a braced staff group for
your score. Is this intentional?
(By the way, with current development versions of LilyPond, it suffices
to issue \numericTimeSignature once - for example, in the \layout block.
For \accidentalStyle ..., this has been true for a while now.)
Lukas
Re: inconsistent \RemoveEmptyStaves action
jh writes:
> From one project to the next sometimes 'Frenching' a score works and
> sometimes it doesn't
> This is the shortest example I could figure out how to make
> the second system should be just two staves (and using the same
> context etc 5 days ago worked as expected on a different score so this
> was copy pasted)
> \version "2.22.1"
> \header {
> title = "Caucasus"
>composer = "Jay Hamilton"
> copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
> \center-column
> { "CC lic 2.5 some rights reserved Jay Hamilton 2022"
> "see http://creativecommons.org/licenses/by-nd/2.5/;
>} }
>}
> #(ly:set-option 'delete-intermediate-files #t)
> #(set-default-paper-size "letter" )
> #(set-global-staff-size 20)
>
>
> upper = \relative c' {
> \clef treble
> \key c \major
> \time 4/4
> \tempo "andante" 4 = 72
> \numericTimeSignature
> \accidentalStyle forget
> \times 2/3 {g'8 d bes'}\times 2/3 {g d bes'}
>\times 2/3 {g d bes'}\times 2/3 {g d bes'}
>\times 2/3 {a d, c'} \times 2/3 {a d, c'}
>\times 2/3 {a d, c'} \times 2/3 {a d, c'}\break
>\times 2/3 {bes g d'} \times 2/3 {bes g d'}
>\times 2/3 {bes g d'} \times 2/3 {bes g d'}
>es16 bes ges bes es bes ges bes es bes ges bes es bes ges bes\break
>
> }
>
> lower = \relative c {
> \clef bass
> \key c \major
> \numericTimeSignature
> \accidentalStyle forget
> bes'4 c d g,
> \times 2/3 {a8 g fis} d4 \times 2/3 {c8 a c}\times 2/3 {fis g a}
> \times 2/3 {bes8 a g}\times 2/3 {d bes d}\times 2/3 {fis g a} d4
> es4 ges8 [d] c [bes] ges a ~
> }
> three = \relative c {
> \clef bass
> \key c \major
> \numericTimeSignature
> \accidentalStyle forget
>R1*4
>
> }
> four = \relative c {
> \clef "bass_8"
> \key c \major
> \numericTimeSignature
> \accidentalStyle forget
>R1*4
> }
>
>
> \score {
> \context PianoStaff
> <<
> \context Staff = upper \upper
> \context Staff = lower \lower
> \context Staff = three \three
> \context Staff = four \four
> >>
> \layout {
> \context {
> \Staff
>\RemoveEmptyStaves
> }
> }
> \midi { }
> }
> Please point to my stupid errors.
> thanks
> J
File: lilypond-internals.info, Node: PianoStaff, Next: RhythmicStaff, Prev:
PetrucciVoice, Up: Contexts
2.1.24 ‘PianoStaff’
---
Just like ‘GrandStaff’, but the staves are only removed together, never
separately.
--
David Kastrup
inconsistent \RemoveEmptyStaves action
From one project to the next sometimes 'Frenching' a score works and
sometimes it doesn't
This is the shortest example I could figure out how to make
the second system should be just two staves (and using the same context
etc 5 days ago worked as expected on a different score so this was copy
pasted)
\version "2.22.1"
\header {
title = "Caucasus"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2022"
"see http://creativecommons.org/licenses/by-nd/2.5/;
} }
}
#(ly:set-option 'delete-intermediate-files #t)
#(set-default-paper-size "letter" )
#(set-global-staff-size 20)
upper = \relative c' {
\clef treble
\key c \major
\time 4/4
\tempo "andante" 4 = 72
\numericTimeSignature
\accidentalStyle forget
\times 2/3 {g'8 d bes'}\times 2/3 {g d bes'}
\times 2/3 {g d bes'}\times 2/3 {g d bes'}
\times 2/3 {a d, c'} \times 2/3 {a d, c'}
\times 2/3 {a d, c'} \times 2/3 {a d, c'}\break
\times 2/3 {bes g d'} \times 2/3 {bes g d'}
\times 2/3 {bes g d'} \times 2/3 {bes g d'}
es16 bes ges bes es bes ges bes es bes ges bes es bes ges bes\break
}
lower = \relative c {
\clef bass
\key c \major
\numericTimeSignature
\accidentalStyle forget
bes'4 c d g,
\times 2/3 {a8 g fis} d4 \times 2/3 {c8 a c}\times 2/3 {fis g a}
\times 2/3 {bes8 a g}\times 2/3 {d bes d}\times 2/3 {fis g a} d4
es4 ges8 [d] c [bes] ges a ~
}
three = \relative c {
\clef bass
\key c \major
\numericTimeSignature
\accidentalStyle forget
R1*4
}
four = \relative c {
\clef "bass_8"
\key c \major
\numericTimeSignature
\accidentalStyle forget
R1*4
}
\score {
\context PianoStaff
<<
\context Staff = upper \upper
\context Staff = lower \lower
\context Staff = three \three
\context Staff = four \four
>>
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
\midi { }
}
Please point to my stupid errors.
thanks
J
--
Thank you Sound & Silence
Beginning May 1, 2021 a new address; 1814 Lake Washington Blvd. So.,
Seattle, Wa. 98144
_206-328-7694 or messages at 206-308-8189_
www.soundand.com
and an online short (45 minute) concert of new material on Wayward in
Limbo
https://www.waywardmusic.org/?p=6082
frenched score problem.pdf
Description: Adobe PDF document
Re: RemoveEmptyStaves doesnt remove percussion staff
> \layout {
> \context {
> \Staff
> \RemoveEmptyStaves
> }
> %% You need to add this:
>\context {
> \DrumStaff
> \RemoveEmptyStaves
> }
> }
Yes~ That works~
Thank you very much~
Valentin Villenave 於 2020年4月19日 週日 下午11:17寫道：
>
> On 4/16/20, neuro黃學仁 wrote:
> > How can one remove the empty percussion staff in Grandscore?
> > The \RemoveEmptyStaves seems not working on percussion staff.
>
> Greetings,
> here is a solution:
>
>
>
> \layout {
> indent = 2.6\cm
> short-indent = 1.6\cm
> \context {
> \Staff
> \RemoveEmptyStaves
> }
> %% You need to add this:
> \context {
> \DrumStaff
> \RemoveEmptyStaves
> }
> }
>
>
>
> Cheers,
> V.
Re: RemoveEmptyStaves doesnt remove percussion staff
On 4/16/20, neuro黃學仁 wrote:
> How can one remove the empty percussion staff in Grandscore?
> The \RemoveEmptyStaves seems not working on percussion staff.
Greetings,
here is a solution:
\layout {
indent = 2.6\cm
short-indent = 1.6\cm
\context {
\Staff
\RemoveEmptyStaves
}
%% You need to add this:
\context {
\DrumStaff
\RemoveEmptyStaves
}
}
Cheers,
V.
RemoveEmptyStaves doesnt remove percussion staff
How can one remove the empty percussion staff in Grandscore? The \RemoveEmptyStaves seems not working on percussion staff. Sample files can be reached at http://orchestra.tw/lilypond_Q including: 00.ly bdrum.ly timp.ly v1.ly v2.ly To run lilypond 00.ly (http://orchestra.tw/lilypond_Q/00.ly), and it results in 00.pdf (http://orchestra.tw/lilypond_Q/00.pdf) Thanks very much for any advise~ neuro neu...@gmail.com
RE: \RemoveEmptyStaves
Thank you!
This should definitely be in the Lilypond Docs for keyboard-specific notation.
-Original Message-
From: lilypond-user
On Behalf Of Malte Meyn
Sent: Monday, March 4, 2019 2:39 AM
To: lilypond-user@gnu.org
Subject: Re: \RemoveEmptyStaves
Am 04.03.19 um 03:17 schrieb Richard Gress:
> Hi all,
>
> Why is \RemoveEmptyStaves not working the way I'm using it? The output
> still shows blank staves in a ten-page document. Uncommenting the
> global command doesn't work, either.
PianoStaff contains the Keep_alive_together_engraver. This means that
individual staves aren't hidden, only the PianoStaff as a whole when all staves
are empty. This makes sense in orchestra music but not for piano solo. You can
use a GradStaff instead or remove the
Keep_alive_together_engraver:
\new GrandStaff <<
\new Staff ...
\new Staff ...
\new Staff ...
\new Staff ...
>>
\new PianoStaff \with {
\remove Keep_alive_together_engraver
} <<
\new Staff ...
\new Staff ...
\new Staff ...
\new Staff ...
>>
In fact, the Keep_align_together_engraver is the only difference between the
two contexts, so both solutions are equivalent.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
G'day.
On Mon, Mar 4, 2019 at 1:40 PM Richard Gress wrote:
> Why is \RemoveEmptyStaves not working the way I’m using it? The output still
> shows blank staves in a ten-page document. Uncommenting the global command
> doesn’t work, either.
Because it's not a Staff, it's a PianoStaff. It took me a while to
work this out, too.
It's a similar story for ChoirStaff. I use this:
\layout {
\context {
\Staff \RemoveEmptyStaves
}
\context {
\ChoirStaff \RemoveEmptyStaves
}
\context {
\PianoStaff \RemoveEmptyStaves
}
}
Andrew Bromage
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
Hi All, This is an FAQ (and indeed I have asked it). I wonder where we should put this sort of thing, some sort of FAQ repository? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
Am 04.03.19 um 03:17 schrieb Richard Gress:
Hi all,
Why is \RemoveEmptyStaves not working the way I’m using it? The output
still shows blank staves in a ten-page document. Uncommenting the global
command doesn’t work, either.
PianoStaff contains the Keep_alive_together_engraver. This means that
individual staves aren’t hidden, only the PianoStaff as a whole when all
staves are empty. This makes sense in orchestra music but not for piano
solo. You can use a GradStaff instead or remove the
Keep_alive_together_engraver:
\new GrandStaff <<
\new Staff …
\new Staff …
\new Staff …
\new Staff …
>>
\new PianoStaff \with {
\remove Keep_alive_together_engraver
} <<
\new Staff …
\new Staff …
\new Staff …
\new Staff …
>>
In fact, the Keep_align_together_engraver is the only difference between
the two contexts, so both solutions are equivalent.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves
Hi all,
Why is \RemoveEmptyStaves not working the way I'm using it? The output still
shows blank staves in a ten-page document. Uncommenting the global command
doesn't work, either.
The input... (complete file: https://1drv.ms/u/s!AucNdHoia6D-2TnE0_Op2BKlUKGh )
\version "2.18.2"
#(set-default-paper-size "letter" 'landscape)
uppera = \relative c'' {
%MUSIC
}
upperb = \relative c' {
% MUSIC
}
lowera = \relative c {
% MUSIC
}
lowerb = \relative c, {
% MUSIC
}
\score {
\new PianoStaff \with {
instrumentName = "Piano"
} <<
\new Staff = "uppera" \uppera
\new Staff = "upperb" \upperb
\new Staff = "lowera" \lowera
\new Staff = "lowerb" \lowerb
>>
\layout {
\context {
\Staff \RemoveEmptyStaves
% To use the setting globally, uncomment the following line:
%\override VerticalAxisGroup #'remove-first = ##t
}
}
}
Midterm.ly
Description: Midterm.ly
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
+1. I've *never* seen an ambitus except at the very beginning of a piece. I often use an ambitus in front- or end-matter, to give vocal ranges separate from the score itself. Of course, "front-matter" can be interpreted as "the very beginning of a piece", but I think of it as entirely separate from the piece — and end-matter is definitely not "the very beginning of a piece". Not trying to battle semantics — just giving a use case, and putting forward my concern that any changes to the Ambitus engraver shouldn’t eliminate the possibility of using it somewhere other than the "traditional place" (i.e., immediately to the left of the first measure of a vocal staff). ... the least common denominator probably being that an Ambitus indication should be put at some *distinguished* place - front matter, end matter, first system, and so on, where it may be found easily. But to bury it at some more-or-less arbitrary place within the music doesn't seem a good idea to me. Anyway: _How_ do you place the Ambitus in, e.g., the front matter? Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Am Do., 1. Nov. 2018 um 16:24 Uhr schrieb Kieren MacMillan
:
>
> Hi Werner,
>
> > +1. I've *never* seen an ambitus except at the very beginning of a piece.
>
> I often use an ambitus in front- or end-matter, to give vocal ranges separate
> from the score itself. Of course, "front-matter" can be interpreted as "the
> very beginning of a piece", but I think of it as entirely separate from the
> piece — and end-matter is definitely not "the very beginning of a piece".
>
> Not trying to battle semantics — just giving a use case, and putting forward
> my concern that any changes to the Ambitus engraver shouldn’t eliminate the
> possibility of using it somewhere other than the "traditional place" (i.e.,
> immediately to the left of the first measure of a vocal staff).
I'd second Werner.
Though, it's already possible to do:
{
\new Voice = "intro"
{ R1*4 \break }
\new Voice
\with { \consists "Ambitus_engraver" }
\relative c' {
\override AmbitusNoteHead.break-visibility = ##(#f #f #t)
\override AmbitusLine.break-visibility = ##(#f #f #t)
c4 d e f g a b c |
\break
b2 c |
d1
}
}
alas not very convenient.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Hi Werner, > +1. I've *never* seen an ambitus except at the very beginning of a piece. I often use an ambitus in front- or end-matter, to give vocal ranges separate from the score itself. Of course, "front-matter" can be interpreted as "the very beginning of a piece", but I think of it as entirely separate from the piece — and end-matter is definitely not "the very beginning of a piece". Not trying to battle semantics — just giving a use case, and putting forward my concern that any changes to the Ambitus engraver shouldn’t eliminate the possibility of using it somewhere other than the "traditional place" (i.e., immediately to the left of the first measure of a vocal staff). Best, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
> So, to be honest, I'm not sure whether trying to make the > Ambitus_engraver compatible with hiding empty staves would be worth > the effort, especially if (as you say) that effort would be large. +1. I've *never* seen an ambitus except at the very beginning of a piece. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line [OT-ish]
Hi Lukas, > It seems to me that the whole point (or, at least, the most important > application) of the Ambitus indication is to enable users of the score to > judge the tessitura "at first glance" (even though, of course, for a reliable > judgement one would have to look at the actual music in more detail). I’ve often wondered [only to myself] whether the Ambitus engraver could be tweaked to output a graphical cluster, the thickness of which would depend on the number of times that note appears in the piece (or total duration of each note, etc.) — that way, a pretty reliable judgement could be made just by looking at the ambitus, and seeing where the "bulges" were (if any). Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Where would you expect the Ambitus marker to show up if you do not want the staff to appear in the first system? First entry? I am not sure that the interfaces the Ambitus_engraver exercises would allow to make that difference, but if they did, this would be a reasonable expectation. Though probably rather hard to implement, given how late in the typesetting stage "empty" staves get pruned. Yes, that's probably the only sufficiently reasonable place to expect it. But: It seems to me that the whole point (or, at least, the most important application) of the Ambitus indication is to enable users of the score to judge the tessitura "at first glance" (even though, of course, for a reliable judgement one would have to look at the actual music in more detail). This application is somewhat hindered if one has to look for the right system containing the first entry of a voice first. So, to be honest, I'm not sure whether trying to make the Ambitus_engraver compatible with hiding empty staves would be worth the effort, especially if (as you say) that effort would be large. Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Lukas-Fabian Moser writes: > Am 01.11.18 um 01:34 schrieb Rohan Srinivasan: >> Thank you - I meant to reply to the list. I have the following: > > The problem is the Ambitus_engraver. The ambitus is given at the > beginning of the piece, and if you do this, the first staff of the > singing voice is not empty (but contains the Ambitus designation). > > Where would you expect the Ambitus marker to show up if you do not > want the staff to appear in the first system? First entry? I am not sure that the interfaces the Ambitus_engraver exercises would allow to make that difference, but if they did, this would be a reasonable expectation. Though probably rather hard to implement, given how late in the typesetting stage "empty" staves get pruned. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Am 01.11.18 um 01:34 schrieb Rohan Srinivasan: Thank you - I meant to reply to the list. I have the following: The problem is the Ambitus_engraver. The ambitus is given at the beginning of the piece, and if you do this, the first staff of the singing voice is not empty (but contains the Ambitus designation). Where would you expect the Ambitus marker to show up if you do not want the staff to appear in the first system? Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Thank you - I meant to reply to the list. I have the following:
\version "2.19.82"
\header {
title = "CLOUDS AND SUNSHINE"
subtitle = "or, I'VE JUST ARRIVED FROM DIXIE"
composer = "George H. Coes (1828?-1897)"
}
\paper {
#(set-paper-size "a4")
}
\layout {
\context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
}
}
\layout {
\context {
\Staff
\RemoveAllEmptyStaves
}
}
paren =
#(define-event-function (parser location dyn) (ly:event?)
(make-dynamic-script
#{ \markup \concat {
\normal-text \italic \fontsize #2 (
\pad-x #0.2 #(ly:music-property dyn 'text)
\normal-text \italic \fontsize #2 )
}
#}))
global = {
\key f \major
\numericTimeSignature
\time 2/4
\partial 8
}
sopranoVoice = \relative c'' {
\global
\dynamicUp
r8 |
R2*20
}
right = \relative c'' {
\global
\partial 8 c,8 |
c c d8. e16 |
f8 a r a |
c[ b bes8. g16] |
g4. c8 |
\override DynamicLineSpanner.staff-padding = #3
d16\f d c d a' g f d |
c\paren\f c b c g' f c a |
c\p c b c e d b g
}
left = \relative c' {
\global
\partial 8 r8 |
\override Beam.damping = #1 f,,[ ] r |
f,[ ] r |
c,[ ] r |
f,[ ] r |
\undo \override Beam.damping = #1
bes[ ] r | \break
c,[ ] r |
c,[ ] r |
}
sopranoVoicePart = \new Staff \with {
instrumentName = ""
\consists "Ambitus_engraver"
} { \sopranoVoice }
pianoPart = \new PianoStaff \with {
instrumentName = ""
} <<
\new Staff = "right" \right
\new Staff = "left" { \clef bass \left }
>>
\score {
<<
\sopranoVoicePart
\pianoPart
>>
\layout { }
}
On Wed, Oct 31, 2018 at 12:54 AM Lukas-Fabian Moser wrote:
> (Replying to list, assuming you wrote to me personally only by accident,
> as implied by your wording):
> Am 31.10.18 um 00:42 schrieb Rohan Srinivasan:
>
> Could any of you give me an example of how \RemoveAllEmptyStaves is used?
> I have:
>
> \layout {
> \context {
> \Staff
> \RemoveAllEmptyStaves
> }
> }
>
> This still doesn't seem to clear the empty staves in the first system.
>
> Please always try to provide a compilable minimal example showing your
> problem.
>
> \version "2.19.80"
>
> \layout {
> \context {
> \Staff
> \RemoveAllEmptyStaves
> }
> }
>
> <<
> \new Staff \with { instrumentName = "Voice" shortInstrumentName = "Voc"
> } { R1*30 \repeat unfold 80 c'4 }
> \new PianoStaff \with { instrumentName = "Piano" shortInstrumentName =
> "Pn" } <<
> \new Staff { \repeat unfold 200 c'4 }
> \new Staff { \clef bass \repeat unfold 400 c8 }
> >>
> >>
>
> works here:
>
> Best
> Lukas
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Have also used the \override VerticalAxisGroup.remove-first = ##t and can
confirm this works with 2.18.2 when added to score block.
\score {
<<
\flutePart
\pianoPart
>>
\layout { #(layout-set-staff-size 22)
\context { \Staff \RemoveEmptyStaves
\override VerticalAxisGroup.remove-first
= ##t }
}
\midi { }
}
On Mon, 29 Oct 2018 at 03:41, Malte Meyn wrote:
>
>
> Am 29.10.18 um 05:52 schrieb Lukas-Fabian Moser:
> >
> >> I am currently engraving a song for soprano and piano which begins
> >> with 15 measures of piano solo. I would like the soprano's staff not
> >> to show since it is not playing. \RemoveEmptyStaves does not seem to
> >> hide the first line of the piece.
> >>
> > In current versions (there's no reason not to use the 2.19.xx
> > development versions which are stable enough for professional everyday
> > use), there's |\RemoveAllEmptyStaves| which does just that (like
> > \RemoveEmptyStaves but also remove the respective staves in the first
> > system).
>
> In 2.18.2 there is \override VerticalAxisGroup.remove-first = ##t for that.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
(Replying to list, assuming you wrote to me personally only by accident,
as implied by your wording):
Am 31.10.18 um 00:42 schrieb Rohan Srinivasan:
Could any of you give me an example of how \RemoveAllEmptyStaves is
used? I have:
\layout {
\context {
\Staff
\RemoveAllEmptyStaves
}
}
This still doesn't seem to clear the empty staves in the first system.
Please always try to provide a compilable minimal example showing your
problem.
\version "2.19.80"
\layout {
\context {
\Staff
\RemoveAllEmptyStaves
}
}
<<
\new Staff \with { instrumentName = "Voice" shortInstrumentName =
"Voc" } { R1*30 \repeat unfold 80 c'4 }
\new PianoStaff \with { instrumentName = "Piano" shortInstrumentName
= "Pn" } <<
\new Staff { \repeat unfold 200 c'4 }
\new Staff { \clef bass \repeat unfold 400 c8 }
>>
>>
works here:
Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
Am 29.10.18 um 05:52 schrieb Lukas-Fabian Moser: I am currently engraving a song for soprano and piano which begins with 15 measures of piano solo. I would like the soprano's staff not to show since it is not playing. \RemoveEmptyStaves does not seem to hide the first line of the piece. In current versions (there's no reason not to use the 2.19.xx development versions which are stable enough for professional everyday use), there's |\RemoveAllEmptyStaves| which does just that (like \RemoveEmptyStaves but also remove the respective staves in the first system). In 2.18.2 there is \override VerticalAxisGroup.remove-first = ##t for that. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves not removing first line
I am currently engraving a song for soprano and piano which begins with 15 measures of piano solo. I would like the soprano's staff not to show since it is not playing. \RemoveEmptyStaves does not seem to hide the first line of the piece. In current versions (there's no reason not to use the 2.19.xx development versions which are stable enough for professional everyday use), there's |\RemoveAllEmptyStaves| which does just that (like \RemoveEmptyStaves but also remove the respective staves in the first system). Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves not removing first line
Dear list, I am currently engraving a song for soprano and piano which begins with 15 measures of piano solo. I would like the soprano's staff not to show since it is not playing. \RemoveEmptyStaves does not seem to hide the first line of the piece. Rohan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Am 18.07.2018 um 03:36 schrieb Marcos Press: > Link for the example image... > https://drive.google.com/open?id=1vuTzR23XOfx1gTEra-aMv-oz35s_XY0h That's the image that you already attached to a former mail (Date: Tue, 17 Jul 2018 14:11:38 -0300). It shows a snippet from a sheet of music with incomplete lines. Best regards, Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Link for the example image...
https://drive.google.com/open?id=1vuTzR23XOfx1gTEra-aMv-oz35s_XY0h
El mar., 17 de jul. de 2018 a la(s) 16:30, Helge Kruse (helge.kr...@gmx.net)
escribió:
> Am 17.07.2018 um 19:09 schrieb Marcos Press:
> > Actually I'm not certain of which method to use. Perhaps it should be
> other
> > way.
> > The attached image is what I'm transcribing.
> >
> > It's for a double hand/staff instrument that lots of times use only one.
> Or
> > both doing the same so we just write one hand.
> >
> > The result is reduction of pages and unnecessary eye data.
> >
> > How would you resolve these?
>
> This looks like an example for \RemoveEmptyStaves. You could do
> something like this:
>
> \version "2.18.2"
>
> cello = \relative c'' {
> \time 3/8
> \repeat unfold 10 { R4. }
> \repeat unfold 37 { c8 d e }
> }
>
> celloII = \relative c {
> \time 3/8
> \repeat unfold 40 { R4. }
> c c c c c c c
> }
>
> \score {
> <<
> \new StaffGroup <<
> \new Staff { \clef treble \cello }
> \new Staff { \clef bass \celloII }
> >>
> >>
> \layout {
> \context {
> \Staff \RemoveEmptyStaves
> }
> }
> }
>
> Of course, this shows only the automatic disappearance of empty staff
> lines but not your score.
>
> Regards, Helge
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Am 17.07.2018 um 19:09 schrieb Marcos Press:
> Actually I'm not certain of which method to use. Perhaps it should be other
> way.
> The attached image is what I'm transcribing.
>
> It's for a double hand/staff instrument that lots of times use only one. Or
> both doing the same so we just write one hand.
>
> The result is reduction of pages and unnecessary eye data.
>
> How would you resolve these?
This looks like an example for \RemoveEmptyStaves. You could do
something like this:
\version "2.18.2"
cello = \relative c'' {
\time 3/8
\repeat unfold 10 { R4. }
\repeat unfold 37 { c8 d e }
}
celloII = \relative c {
\time 3/8
\repeat unfold 40 { R4. }
c c c c c c c
}
\score {
<<
\new StaffGroup <<
\new Staff { \clef treble \cello }
\new Staff { \clef bass \celloII }
>>
>>
\layout {
\context {
\Staff \RemoveEmptyStaves
}
}
}
Of course, this shows only the automatic disappearance of empty staff
lines but not your score.
Regards, Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Hi Marcos, > Is there any way to set RemoveEmptyStaves just for SKIP's or when the > rest/skip is larger than 1 (one) bar? Have you looked to see if keep-alive-interfaces can be set such that skips are the only items considered? Just an untested brainstorm. Hope it helps! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
The \tag metoth does not respect the time of removed bars. Still nice tip ;)
El El mar, 17 de jul de 2018 a las 14:11, Marcos Press
escribió:
> My bad! Send without attach!
> Sorry!
> Here...
>
> El El mar, 17 de jul de 2018 a las 14:09, Marcos Press
> escribió:
>
>> Actually I'm not certain of which metoth to use. Perhaps it should be
>> other way.
>> The attached image is what I'm transcribing.
>>
>> I'ts for a double hand/staff instrument that lots of times use only one.
>> Or both doing the same so we just write one hand.
>>
>> The resault is reduction of pages and unnecesary eye data.
>>
>> How would you resolve these?
>>
>> El El mar, 17 de jul de 2018 a las 02:06, Helge Kruse <
>> helge.kr...@gmx.net> escribió:
>>
>>> Marcos Press schrieb am Di., 17. Juli 2018, 02:58:
>>>
>>>> Is there any way to set RemoveEmptyStaves just for SKIP's or when the
>>>> rest/skip is larger than 1 (one) bar?
>>>>
>>>> {
>>>> a1 | b4 a8 g b2 |
>>>> R1 | % no Remove
>>>> a1 | b4 a8 g b2 |
>>>> R1*2 | % yes Remove
>>>> a1 | b4 a8 g b2 |
>>>> R1 | % no Remove
>>>> f1 |
>>>> }
>>>>
>>>
>>> RemoveEmptyStaves is used to remove entire staff lines in a multi staff
>>> context. Your example looks as you want to remove individual measures. Why
>>> should Lilypond do this?
>>>
>>> Regards, Helge
>>>
>>>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Actually I'm not certain of which metoth to use. Perhaps it should be other
way.
The attached image is what I'm transcribing.
I'ts for a double hand/staff instrument that lots of times use only one. Or
both doing the same so we just write one hand.
The resault is reduction of pages and unnecesary eye data.
How would you resolve these?
El El mar, 17 de jul de 2018 a las 02:06, Helge Kruse
escribió:
> Marcos Press schrieb am Di., 17. Juli 2018, 02:58:
>
>> Is there any way to set RemoveEmptyStaves just for SKIP's or when the
>> rest/skip is larger than 1 (one) bar?
>>
>> {
>> a1 | b4 a8 g b2 |
>> R1 | % no Remove
>> a1 | b4 a8 g b2 |
>> R1*2 | % yes Remove
>> a1 | b4 a8 g b2 |
>> R1 | % no Remove
>> f1 |
>> }
>>
>
> RemoveEmptyStaves is used to remove entire staff lines in a multi staff
> context. Your example looks as you want to remove individual measures. Why
> should Lilypond do this?
>
> Regards, Helge
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
I didnt knew about these \tag !!!
Lilypond is so big and I'm so ...
Seams a nice work around. I'll try.
Thanks for these one.
El El mar, 17 de jul de 2018 a las 02:44, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> escribió:
> Hi Marcos,
>
> How about using tags ?
>
> %%
> \version "2.18.2"
>
> music = {
>
> a1 | b4 a8 g b2 |
> R1 | % no Remove
> a1 | b4 a8 g b2 |
> \tag #'yes R1*2 | % yes Remove
>
> a1 | b4 a8 g b2 |
> R1 | % no Remove
> f1 |
> }
>
> \new Staff \music
> \new Staff \removeWithTag #'yes \music
>
> %%
>
> 2018-07-17 7:06 GMT+02:00 Helge Kruse :
>
>> Marcos Press schrieb am Di., 17. Juli 2018, 02:58:
>>
>>> Is there any way to set RemoveEmptyStaves just for SKIP's or when the
>>> rest/skip is larger than 1 (one) bar?
>>>
>>> {
>>> a1 | b4 a8 g b2 |
>>> R1 | % no Remove
>>> a1 | b4 a8 g b2 |
>>> R1*2 | % yes Remove
>>> a1 | b4 a8 g b2 |
>>> R1 | % no Remove
>>> f1 |
>>> }
>>>
>>
>> RemoveEmptyStaves is used to remove entire staff lines in a multi staff
>> context. Your example looks as you want to remove individual measures. Why
>> should Lilypond do this?
>>
>> Regards, Helge
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Hi Marcos,
How about using tags ?
%%
\version "2.18.2"
music = {
a1 | b4 a8 g b2 |
R1 | % no Remove
a1 | b4 a8 g b2 |
\tag #'yes R1*2 | % yes Remove
a1 | b4 a8 g b2 |
R1 | % no Remove
f1 |
}
\new Staff \music
\new Staff \removeWithTag #'yes \music
%%
2018-07-17 7:06 GMT+02:00 Helge Kruse :
> Marcos Press schrieb am Di., 17. Juli 2018, 02:58:
>
>> Is there any way to set RemoveEmptyStaves just for SKIP's or when the
>> rest/skip is larger than 1 (one) bar?
>>
>> {
>> a1 | b4 a8 g b2 |
>> R1 | % no Remove
>> a1 | b4 a8 g b2 |
>> R1*2 | % yes Remove
>> a1 | b4 a8 g b2 |
>> R1 | % no Remove
>> f1 |
>> }
>>
>
> RemoveEmptyStaves is used to remove entire staff lines in a multi staff
> context. Your example looks as you want to remove individual measures. Why
> should Lilypond do this?
>
> Regards, Helge
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Customize \RemoveEmptyStaves
Marcos Press schrieb am Di., 17. Juli 2018, 02:58:
> Is there any way to set RemoveEmptyStaves just for SKIP's or when the
> rest/skip is larger than 1 (one) bar?
>
> {
> a1 | b4 a8 g b2 |
> R1 | % no Remove
> a1 | b4 a8 g b2 |
> R1*2 | % yes Remove
> a1 | b4 a8 g b2 |
> R1 | % no Remove
> f1 |
> }
>
RemoveEmptyStaves is used to remove entire staff lines in a multi staff
context. Your example looks as you want to remove individual measures. Why
should Lilypond do this?
Regards, Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Customize \RemoveEmptyStaves
Is there any way to set RemoveEmptyStaves just for SKIP's or when the
rest/skip is larger than 1 (one) bar?
{
a1 | b4 a8 g b2 |
R1 | % no Remove
a1 | b4 a8 g b2 |
R1*2 | % yes Remove
a1 | b4 a8 g b2 |
R1 | % no Remove
f1 |
}
Thanks!
Marcos.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves removes Dynamics context
Malte and Simon - I didn't have the opportunity to try your suggestions yet,
but just wanted to say thanks for helping!
Am 07.05.2018 um 01:21 schrieb Simon Albrecht:
> On 06.05.2018 23:03, Malte Meyn wrote:
>> Am 06.05.2018 um 22:35 schrieb Thomas Weber:
>>> Can anybody help me with keeping the dynamics alive? Many thanks!
>>>
>>> […]
>>>
>>> \layout {
>>> \context {
>>> \Score
>> Replace \Score by \Staff here.
>>> \RemoveEmptyStaves
>>> \override VerticalAxisGroup.remove-first = ##t
> In case you’re using any version starting from 2.19.36, you can replace the
> above two lines by
> \RemoveAllEmptyStaves
>
> Best, Simon
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves removes Dynamics context
On 06.05.2018 23:03, Malte Meyn wrote:
Am 06.05.2018 um 22:35 schrieb Thomas Weber:
Can anybody help me with keeping the dynamics alive? Many thanks!
[…]
\layout {
\context {
\Score
Replace \Score by \Staff here.
\RemoveEmptyStaves
\override VerticalAxisGroup.remove-first = ##t
In case you’re using any version starting from 2.19.36, you can replace
the above two lines by
\RemoveAllEmptyStaves
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves removes Dynamics context
Am 06.05.2018 um 22:35 schrieb Thomas Weber:
Can anybody help me with keeping the dynamics alive? Many thanks!
[…]
\layout {
\context {
\Score
Replace \Score by \Staff here.
\RemoveEmptyStaves
\override VerticalAxisGroup.remove-first = ##t
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves removes Dynamics context
Can anybody help me with keeping the dynamics alive? Many thanks!
dynamics = {s1\p}
music = {c'1}
\layout {
\context {
\Score
\RemoveEmptyStaves
\override VerticalAxisGroup.remove-first = ##t
}
}
\score {
<<
\new Staff \music
\new Dynamics \dynamics
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves for drums?
Hi, Molly!
On Sat, Aug 5, 2017 at 7:34 PM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
>
> > However I can't seem to get it to \RemoveEmptyStaves for the \DrumStaff.
> This is what I tried.
> >
> > \layout {
> > \context {
> > \Staff
> > \RemoveEmptyStaves
> > \DrumStaff
> > \RemoveEmptyStaves
> > }
>
> To be honest, I'm not even sure *what* that would do… =\
>
> Here's what I just tried, and it seems to work:
>
> SNIPPET BEGINS
> \version "2.19"
>
> \layout {
> \context {
> \DrumStaff
> \RemoveAllEmptyStaves
> }
> }
>
The problem you ran into is that you were combining things that shouldn't
have been. In other words, \Staff and \DrumStaff need to be in their own
\context block, as Kieren hinted at. More fully, this should work for you:
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
\context {
\DrumStaff
\RemoveEmptyStaves
}
}
HTH,
Abraham
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves for drums?
Hi Molly,
> However I can't seem to get it to \RemoveEmptyStaves for the \DrumStaff. This
> is what I tried.
>
> \layout {
> \context {
> \Staff
> \RemoveEmptyStaves
> \DrumStaff
> \RemoveEmptyStaves
> }
To be honest, I'm not even sure *what* that would do… =\
Here's what I just tried, and it seems to work:
SNIPPET BEGINS
\version "2.19"
\layout {
\context {
\DrumStaff
\RemoveAllEmptyStaves
}
}
<<
\new DrumStaff << R1 >>
\new Staff << c''1 >>
>>
SNIPPET ENDS
Hope that helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves for drums?
Hello,
I am making parts and have glockenspiel and the non-pitched percussion on
one part.
However I can't seem to get it to \RemoveEmptyStaves for the \DrumStaff.
This is what I tried.
\layout {
\context {
\Staff
\RemoveEmptyStaves
\DrumStaff
\RemoveEmptyStaves
}
}
Thanks!
Molly
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
Instead that has worked. Thanks (my fault). -- View this message in context: http://lilypond.1069038.n5.nabble.com/RemoveEmptyStaves-don-t-work-as-I-would-to-tp201683p201691.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
Hi,
> Thanks for the lesson (maybe I'll be able to understand it), but still it
> doesn't work…
Below is your original snippet, with the suggested fix.
It doesn’t work for you as you expect? (It certainly does for me.)
Kieren.
\version "2.19.26"
\layout {
\context {
\Score
skipBars = ##t
}
\context {
\Staff
\RemoveAllEmptyStaves
}
}
PartPOneVoiceOne = \relative g' {
\clef "treble" \key c \major \numericTimeSignature\time 4/4 g1 | % 2
g1 \break | % 3
R1*2 \bar "|."
}
PartPTwoVoiceOne = \relative b' {
\clef "treble" \key c \major \numericTimeSignature\time 4/4 R1*2
\break | % 3
b1 | % 4
b1 \bar "|.”
}
% The score definition
\score {
<<
\new Staff <<
\set Staff.instrumentName = "Voce"
\set Staff.shortInstrumentName = "Vo."
\context Staff <<
\context Voice = "PartPOneVoiceOne" { \PartPOneVoiceOne }
>>
>>
\new Staff <<
\set Staff.instrumentName = "Soprano"
\set Staff.shortInstrumentName = "S."
\context Staff <<
\context Voice = "PartPTwoVoiceOne" { \PartPTwoVoiceOne }
>> >> >>
}
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
Thanks for the lesson (maybe I'll be able to understand it), but still it doesn't work... -- View this message in context: http://lilypond.1069038.n5.nabble.com/RemoveEmptyStaves-don-t-work-as-I-would-to-tp201683p201689.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
I've installed the latest version, but no changes :-( -- View this message in context: http://lilypond.1069038.n5.nabble.com/RemoveEmptyStaves-don-t-work-as-I-would-to-tp201683p201687.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
Hi Son,
about minimal examples, see my comments below. ;)
2017-03-28 21:48 GMT+02:00 Son_V <vincenzo.a...@gmail.com>:
> neither \\RemoveAllEmptyStaves ..
>
> This is my try for a Minimum example, sorry if I failed to make it smaller:
>
> \version "2.19.26"
> \layout {
> \context {
> \Score
no need for skipBars
> skipBars = ##t
> %\RemoveEmptyStaves
> }
> }
> PartPOneVoiceOne = \relative g' {
no need for
clef "treble" \key c \major \numericTimeSignature\time 4/4
it's mostly the default, or suoerfluous for a minimal
Also too many notes/rests.
> \clef "treble" \key c \major \numericTimeSignature\time 4/4 g1 | % 2
> g1 \break | % 3
> R1*2 \bar "|."
> }
>
> PartPTwoVoiceOne = \relative b' {
same here
> \clef "treble" \key c \major \numericTimeSignature\time 4/4 R1*2
> \break | % 3
> b1 | % 4
> b1 \bar "|."
> }
>
>
For a minimal no complete score-definition, (unless the problem would
be in there)
> % The score definition
> \score {
> <<
> \new Staff <<
> \set Staff.instrumentName = "Voce"
> \set Staff.shortInstrumentName = "Vo."
> \context Staff <<
> \context Voice = "PartPOneVoiceOne" { \PartPOneVoiceOne }
> >>
> >>
> \new Staff <<
> \set Staff.instrumentName = "Soprano"
> \set Staff.shortInstrumentName = "S."
> \context Staff <<
> \context Voice = "PartPTwoVoiceOne" { \PartPTwoVoiceOne }
> >>
> >>
> >>
> }
Remaining minimal with solution,
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
<<
\new Staff { g'1 \break R1 }
\new Staff { R1 \break b'1 }
>>
RemoveEmptyStaves needs to be applied in a Staff-context, examples in the NR
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
Son_V <vincenzo.a...@gmail.com> writes:
> neither \\RemoveAllEmptyStaves ..
>
> This is my try for a Minimum example, sorry if I failed to make it smaller:
>
> \version "2.19.26"
> \layout {
> \context {
> \Score
> skipBars = ##t
> %\RemoveEmptyStaves
> }
> }
\RemoveEmptyStaves and \RemoveAllEmptyStaves apply to the context
containing them.
Removing the Score context could be ... interesting.
You probably want to use this invocation on Staff instead of Score.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves don't work as I would to
Hi, > neither \\RemoveAllEmptyStaves .. In 2.19.56, that (with a single \ of course) works as expected for me. Maybe upgrade? Hope this helps, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves don't work as I would to
neither \\RemoveAllEmptyStaves ..
This is my try for a Minimum example, sorry if I failed to make it smaller:
\version "2.19.26"
\layout {
\context {
\Score
skipBars = ##t
%\RemoveEmptyStaves
}
}
PartPOneVoiceOne = \relative g' {
\clef "treble" \key c \major \numericTimeSignature\time 4/4 g1 | % 2
g1 \break | % 3
R1*2 \bar "|."
}
PartPTwoVoiceOne = \relative b' {
\clef "treble" \key c \major \numericTimeSignature\time 4/4 R1*2
\break | % 3
b1 | % 4
b1 \bar "|."
}
% The score definition
\score {
<<
\new Staff <<
\set Staff.instrumentName = "Voce"
\set Staff.shortInstrumentName = "Vo."
\context Staff <<
\context Voice = "PartPOneVoiceOne" { \PartPOneVoiceOne }
>>
>>
\new Staff <<
\set Staff.instrumentName = "Soprano"
\set Staff.shortInstrumentName = "S."
\context Staff <<
\context Voice = "PartPTwoVoiceOne" { \PartPTwoVoiceOne }
>>
>>
>>
}
If you uncomment \RemoveEmptyStaves, the "solo" disappears but remains the
void Soprano voice.
I would have seen the void Soprano voice to disappear.
Even using \RemoveAllEmptyStaves won't work, on the contrary it gives a
cahotic result.
What should I do? Thanks.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/RemoveEmptyStaves-don-t-work-as-I-would-to-tp201683.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves + 8 part polyphony
On 11/05/16 01:07, Dirk Koopman wrote:
On 11/05/16 00:38, Kieren MacMillan wrote:
Hi Dirk,
Is there any way of controlling which part of a score has
\RemoveEmptyStaves active and which not?
showMMRs = {
\set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface) }
hideMMRs = \unset Staff.keepAliveInterfaces
Hope this helps!
Hmm...
Close but no cigar. Each of my stave in 2nd choir look like this:
\new Staff <<
\new Voice="v8" {
\set Staff.instrumentName = "Bass 2"
\set Staff.shortInstrumentName = "B2"
\clef "bass"
\key f \major
\numericTimeSignature\time 4/2
\BtwoKone \break % 1st kyrie notes
\BtwoC \break % christe notes
\showMMRs \BtwoKtwo % 2nd Kyrie notes
}
\new Lyrics \lyricsto "v8" {
\TextBtwo
}
>>
The Christe is just a lot of R1*n followed by a \bar "||" |. What
happens is that the 2nd Kyrie is now set correctly, but the empty 2nd
choir part of the Christe now also appears. I am guessing that I have
to put the \showMMRs somewhere else?
Dirk
And as if by magic removing all four \showMMRs makes it format as I want
it. So it appears that just defining those functions makes it work.
Which is a worry.
Dirk
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves + 8 part polyphony
On 11/05/16 00:38, Kieren MacMillan wrote:
Hi Dirk,
Is there any way of controlling which part of a score has \RemoveEmptyStaves
active and which not?
showMMRs = {
\set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface) }
hideMMRs = \unset Staff.keepAliveInterfaces
Hope this helps!
Hmm...
Close but no cigar. Each of my stave in 2nd choir look like this:
\new Staff <<
\new Voice="v8" {
\set Staff.instrumentName = "Bass 2"
\set Staff.shortInstrumentName = "B2"
\clef "bass"
\key f \major
\numericTimeSignature\time 4/2
\BtwoKone \break % 1st kyrie notes
\BtwoC \break % christe notes
\showMMRs \BtwoKtwo % 2nd Kyrie notes
}
\new Lyrics \lyricsto "v8" {
\TextBtwo
}
>>
The Christe is just a lot of R1*n followed by a \bar "||" |. What
happens is that the 2nd Kyrie is now set correctly, but the empty 2nd
choir part of the Christe now also appears. I am guessing that I have to
put the \showMMRs somewhere else?
Dirk
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves + 8 part polyphony
Hi Dirk,
> Is there any way of controlling which part of a score has \RemoveEmptyStaves
> active and which not?
showMMRs = {
\set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface) }
hideMMRs = \unset Staff.keepAliveInterfaces
Hope this helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves + 8 part polyphony
I am setting an 8 part 2 choir Lassus mass arranged into 2 ChoirStaffs,
one for each choir. In the Kyrie, the first and the last Kyrie is full
parts and the intervening Christe is just 4 parts (1st choir).
I have this in the layout section:
\layout { \context {
\Staff
\RemoveEmptyStaves
} .. .. }
And for the Christe this does exactly what I want viz: remove the empty
2nd choir staves / system. However, it happens that in the last Kyrie,
the 2nd choir has some 4 bars rest at the beginning. The layout engine
clearly has an "Aha!" moment and has optimised out the "empty" 2nd choir
staves containing those 4 bars. Now while a choir can cope with this, it
doesn't look very good, especially as the layout engine has stuck the
"entry" of the 2nd choir on the following page.
Is there any way of controlling which part of a score has
\RemoveEmptyStaves active and which not?
Dirk
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Segfault when using RemoveEmptyStaves
I get a segfault with 2.18.2 (Ubuntu repos) but not with 2.19.21. Ubuntu 15.10 64bit If it helps, I can post a stack trace or other information apport gathers. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Segfault when using RemoveEmptyStaves
On 15.02.2016 23:15, Frank Steinmetzger wrote: Hello list I was ponding along with 2.18.2 and all of a sudden, the piece I was typing didn't build a PDF anymore. As it turns out, lilypund is suffering a segmentation fault. I took the file apart and in an hour's search narrowed it down to those features: - RemoveEmptyStaves is enabled - there is a \break at the end followed by a \bar command Under those conditions lilypond crashes if I use either lyrics or a dynamics context. If I comment out either the Dynamics and Lyrics, the PDF compiles. If all are there, I get the segfault. Hello Frank, that seems to be a model bug report. Thank you very much. Interestingly, the bug doesn’t occur on my machine – and I’m on 64-bit Linux as well. No idea why… Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Segfault when using RemoveEmptyStaves
Hello list
I was ponding along with 2.18.2 and all of a sudden, the piece I was typing
didn't build a PDF anymore. As it turns out, lilypund is suffering a
segmentation fault.
I took the file apart and in an hour's search narrowed it down to those
features:
- RemoveEmptyStaves is enabled
- there is a \break at the end followed by a \bar command
Under those conditions lilypond crashes if I use either lyrics or a dynamics
context. If I comment out either the Dynamics and Lyrics, the PDF compiles.
If all are there, I get the segfault.
I attached the file in question. Please try it yourself by commenting out
line 46 and/or 55. Here is my backtrace from compiling it:
$ LC_ALL=C gdb lilypond
GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lilypond...Reading symbols from
/usr/lib64/debug/usr/bin/lilypond.debug...done.
done.
(gdb) run reger.ly
Starting program: /usr/bin/lilypond reger.ly
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
GNU LilyPond 2.18.2
Processing `reger.ly'
Parsing...
Interpreting music...[8][16][24][32][40][48][56]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Program received signal SIGSEGV, Segmentation fault.
Page_layout_problem::find_system_offsets (this=this@entry=0x7fff97a0) at
page-layout-problem.cc:839
839 page-layout-problem.cc: No such file or directory.
(gdb) bt
#0 Page_layout_problem::find_system_offsets (this=this@entry=0x7fff97a0)
at page-layout-problem.cc:839
#1 0x0065b5f7 in Page_layout_problem::fixed_force_solution
(this=this@entry=0x7fff97a0, force=force@entry=0) at
page-layout-problem.cc:956
#2 0x005f65fd in Page_breaking::make_pages
(this=this@entry=0x7fff9de0, lines_per_page=std::vector of length 1,
capacity 1 = {...}, systems=systems@entry=0x7fffeff3bc10) at
page-breaking.cc:630
#3 0x005a58dc in Optimal_page_breaking::solve
(this=this@entry=0x7fff9de0) at optimal-page-breaking.cc:219
#4 0x00458490 in ly_optimal_breaking (pb=) at
page-breaking-scheme.cc:43
#5 0x0030cc44c27b in scm_dapply (proc=0x745f2a30, arg1=0x7134f4e0,
args=0x404) at eval.c:4895
#6 0x0057813c in Paper_book::pages (this=this@entry=0xd97e00) at
paper-book.cc:654
#7 0x005784e2 in Paper_book::output_aux (this=this@entry=0xd97e00,
output_channel=output_channel@entry=0x73a03340, is_last=is_last@entry=true,
first_page_number=first_page_number@entry=0x7fffa148,
first_performance_number=first_performance_number@entry=0x7fffa150) at
paper-book.cc:162
#8 0x005786bc in Paper_book::output (this=this@entry=0xd97e00,
output_channel=output_channel@entry=0x73a03340) at paper-book.cc:188
#9 0x0046d2c9 in ly_book_process (book_smob=,
default_paper=0x7168eab0, default_layout=0x718a6c50,
output=0x73a03340) at book-scheme.cc:79
#10 0x0030cc44c7bf in scm_dapply (proc=0x73d494f0, arg1=0x746091b0,
args=0x7134f500, args@entry=0x404) at eval.c:4930
#11 0x0030cc44d309 in deval (x=, env=) at
eval.c:4378
#12 0x00420eab in ly_eval_scm (form=form@entry=0x71352d40, i=...,
safe=safe@entry=false, parser=parser@entry=0xd59e20) at parse-scm.cc:182
#13 0x006ad35e in Lily_lexer::eval_scm (this=this@entry=0xd802e0,
readerdata=readerdata@entry=0x71352d40, hi=...,
extra_token=extra_token@entry=35 '#') at lexer.ll:1120
#14 0x006c1cf7 in Lily_lexer::eval_scm_token (this=0xd802e0,
sval=0x71352d40, w=...) at ./include/lily-lexer.hh:59
#15 0x006b5f64 in yyparse (parser=parser@entry=0xd59e20,
retval=retval@entry=0x7fffc1f8) at parser.yy:434
#16 0x006c1ca7 in Lily_parser::do_yyparse (this=this@entry=0xd59e20) at
parser.yy:3625
#17 0x005bc8d8 in Lily_parser::parse_file (this=this@entry=0xd59e20,
init="init.ly", name="reger.ly", out_name="reger") at lily-parser.cc:124
#18 0x005c2f18 in ly_parse_file (name=) at
lily-parser-scheme.cc:121
#19 0x0030cc44dc40 in deval (x=, x@entry=0x723e0920,
env=, env@entry=0x7231a1d0) at eval.c:4232
#20 0x0
Re: Programming error with removeEmptyStaves
On 15.11.2015 17:04, Jean-Charles Malahieude wrote: How could I find the culprit in a 5 staves score which looks all right? Perhaps you can reproduce it with fewer bars of music? You might try showFirstLength/showLastLength, or just delete some music. Generally: save a copy of the main input file as debug.ly and start minimizing with that. But yes, it is very difficult to do this with larger projects and the more \includes there are. HTH, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Programming error with removeEmptyStaves
Hi all,
How could I find the culprit in a 5 staves score which looks all right?
The logs say
--8<--
Processing `/home/jcharles/Partothek/Campra/Fetes_Venitiennes/Conducteur.ly'
Parsing...
Interpreting music...
Interpreting
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 7 or 8 pages...
Drawing systems...
programming error: could not find this grob's vertical axis group in the
vertical alignment
continuing, cross fingers
programming error: could not find this grob's vertical axis group in the
vertical alignment
continuing, cross fingers
Layout output to `/tmp/lilypond-rYwu8w'...
Converting to `Conducteur.pdf'...
Success: compilation successfully completed
-->8--
Those errors disappear as soon as I either remove
\context { \Staff \RemoveEmptyStaves }
from the layout block, or randomly omit one or some of the staves.
TIA
Jean-Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Fwd: Re: Problem RemoveEmptyStaves
Message transféré
Sujet : Re: Problem RemoveEmptyStaves
Date : Thu, 23 Apr 2015 17:05:00 +0200
De :Les Éditions Valmajour - pg p...@editions-valmajour.fr
Pour : tisimst tisimst.lilyp...@gmail.com
Hello, thanks for your answer, I actually just found out a few minutes ago :
I added a \StaffGroup context with a
\denies \PianoStaff
Works perfectly.
Thanks a lot!
Pierre
Le 23/04/2015 17:01, tisimst a écrit :
This is curious, but it can be taken care of. If the solo part is
*always* visible, then you can do:
\new Dynamics \with { \override VerticalAxisGroup.remove-empty = ##f }
{ ... }
in _just_ the solo staff. This, of course, will not be effective if
there are times when it is appropriate for it to vanish.
- Abraham
On Thu, Apr 23, 2015 at 7:52 AM, Les Editions Valmajour [via Lilypond]
[hidden email] /user/SendEmail.jtp?type=nodenode=175167i=0 wrote:
Hello,
Hello everyone,
I have a contextproblem; in the attached file, I need to have the
dynamics(placed in a context Dynamics) in all parts.
But when I use \ RemoveEmptyStaves in the context \PianoStaff,
dynamics disappear from the solo part.
I do not see what it comes from. Does anyone have an idea?
___
lilypond-user mailing list
[hidden email] http:///user/SendEmail.jtp?type=nodenode=175155i=0
https://lists.gnu.org/mailman/listinfo/lilypond-user
*testEmptyStaves.ly* (765 bytes) Download Attachment
http://lilypond.1069038.n5.nabble.com/attachment/175155/0/testEmptyStaves.ly
If you reply to this email, your message will be added to the
discussion below:
http://lilypond.1069038.n5.nabble.com/Problem-RemoveEmptyStaves-tp175155.html
To start a new topic under User, email [hidden email]
/user/SendEmail.jtp?type=nodenode=175167i=1
To unsubscribe from Lilypond, click here.
NAML
http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
View this message in context: Re: Problem RemoveEmptyStaves
http://lilypond.1069038.n5.nabble.com/Problem-RemoveEmptyStaves-tp175155p175167.html
Sent from the User mailing list archive
http://lilypond.1069038.n5.nabble.com/User-f3.html at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\version 2.18.2
\score {
\new StaffGroup
\new Staff = 1
{\repeat unfold 20 {c4 d e f}}
\new Dynamics
{\repeat unfold 20 { s4\p s s s }}
\new DrumStaff = 2
{\repeat unfold 20 { R1} }
\new PianoStaff
\new Staff = P1
{\repeat unfold 8 {c4 d e f} R1*12}
\new Dynamics
{\repeat unfold 8 {s4\p r r r } R1*12}
\new Staff = P2
{\repeat unfold 20 {R1}}
\layout {
\context {
\Score
%\RemoveEmptyStaves
}
\context {
\StaffGroup
\denies PianoStaff
}
\context {
\PianoStaff
\RemoveEmptyStaves
}
\context {
\DrumStaff
\RemoveEmptyStaves
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem RemoveEmptyStaves
This is curious, but it can be taken care of. If the solo part is *always*
visible, then you can do:
\new Dynamics \with { \override VerticalAxisGroup.remove-empty = ##f }
{ ... }
in _just_ the solo staff. This, of course, will not be effective if there
are times when it is appropriate for it to vanish.
- Abraham
On Thu, Apr 23, 2015 at 7:52 AM, Les Editions Valmajour [via Lilypond]
ml-node+s1069038n175155...@n5.nabble.com wrote:
Hello,
Hello everyone,
I have a contextproblem; in the attached file, I need to have the
dynamics(placed in a context Dynamics) in all parts.
But when I use \ RemoveEmptyStaves in the context \PianoStaff,
dynamics disappear from the solo part.
I do not see what it comes from. Does anyone have an idea?
___
lilypond-user mailing list
[hidden email] http:///user/SendEmail.jtp?type=nodenode=175155i=0
https://lists.gnu.org/mailman/listinfo/lilypond-user
*testEmptyStaves.ly* (765 bytes) Download Attachment
http://lilypond.1069038.n5.nabble.com/attachment/175155/0/testEmptyStaves.ly
--
If you reply to this email, your message will be added to the discussion
below:
http://lilypond.1069038.n5.nabble.com/Problem-RemoveEmptyStaves-tp175155.html
To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com
To unsubscribe from Lilypond, click here
http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=2code=dGlzaW1zdC5saWx5cG9uZEBnbWFpbC5jb218Mnw4MzU3Njg3MDU=
.
NAML
http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Problem-RemoveEmptyStaves-tp175155p175167.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Problem RemoveEmptyStaves
Hello,
Hello everyone,
I have a contextproblem; in the attached file, I need to have the
dynamics(placed in a context Dynamics) in all parts.
But when I use \ RemoveEmptyStaves in the context \PianoStaff,
dynamics disappear from the solo part.
I do not see what it comes from. Does anyone have an idea?
\version 2.18.2
\score {
\new StaffGroup
\new Staff = 1
{\repeat unfold 20 {c4 d e f}}
\new Dynamics
{\repeat unfold 20 { c4\p r r r }}
\new DrumStaff = 2
{\repeat unfold 20 { R1} }
\new PianoStaff
\new Staff = P1
{\repeat unfold 8 {c4 d e f} R1*12}
\new Dynamics
{\repeat unfold 8 {c4\p r r r } R1*12}
\new Staff = P2
{\repeat unfold 20 {R1}}
\layout {
\context {
\Score
%\RemoveEmptyStaves
}
\context {
\PianoStaff
%\RemoveEmptyStaves
}
\context {
\Dynamics
}
\context {
\DrumStaff
\RemoveEmptyStaves
}
}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
On 06/04/2015 00:23, Urs Liska wrote: I don't know enough about your setup, but if you'd write \hide MultiMeasureRest it should make the rests invisible but still act as rests. Maybe this helps? Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Yes! exactly what I needed. Thanks! Is there a shorter command than \override MultiMeasureRest.transparent = ##f to display the rests again? Anton Curl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
On 06/04/2015 11:48, Simon Albrecht wrote: Yes: \undo\hide MultiMeasureRest. Yours, Simon Very well. Thanks to all of you! Anton Curl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
Am 06.04.2015 um 09:59 schrieb Anton Curl: On 06/04/2015 00:23, Urs Liska wrote: I don't know enough about your setup, but if you'd write \hide MultiMeasureRest it should make the rests invisible but still act as rests. Maybe this helps? Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Yes! exactly what I needed. Thanks! Is there a shorter command than \override MultiMeasureRest.transparent = ##f to display the rests again? Yes: \undo\hide MultiMeasureRest. Yours, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
Am 06.04.2015 um 00:00 schrieb Anton Curl: On 05/04/2015 23:50, Urs Liska wrote: Do you really need to write spacer rests in such staves? Usually you would enter MultiMeasureRests when instruments are pausing and let LilyPond remove the staves automatically if appropriate. In that case Kieren's solution should work also for you. HTH Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user In fact, it's at a point where the musician is improvising. I can't write rests, because he's playing. Therefor I use spacer rest with \startTextSpan and \stopTextSpan. I don't know enough about your setup, but if you'd write \hide MultiMeasureRest it should make the rests invisible but still act as rests. Maybe this helps? Urs Anton Curl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
Am 05.04.2015 um 23:38 schrieb Anton Curl:
On 05/04/2015 21:58, Kieren MacMillan wrote:
You need to add multi-measure-rest-interface to the
keepAliveInterfaces for that staff.
Here are the two bits of syntactic sugar I use:
showMMRs = {
\set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface) }
hideMMRs = \unset Staff.keepAliveInterfaces
So put a \showMMRs in your music expression at the point where you
want to force that Staff context to appear (despite having
\RemoveEmptyStaves active), and put a \hideMMRs when you want it to
return to “default” (i.e., the Staff will disappear, if possible).
Hope this helps!
Kieren.
___
Kieren MacMillan, composer
www: http://www.kierenmacmillan.info
email: i...@kierenmacmillan.info
Thanks for the reply!
Your solution works with R1*4 for example, but not with s1*4.
I assume I have to add an *-interface, but I can't find which.
Do you really need to write spacer rests in such staves? Usually you
would enter MultiMeasureRests when instruments are pausing and let
LilyPond remove the staves automatically if appropriate. In that case
Kieren's solution should work also for you.
HTH
Urs
Anton Curl
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
On 05/04/2015 21:58, Kieren MacMillan wrote:
You need to add multi-measure-rest-interface to the keepAliveInterfaces for
that staff.
Here are the two bits of syntactic sugar I use:
showMMRs = {
\set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface) }
hideMMRs = \unset Staff.keepAliveInterfaces
So put a \showMMRs in your music expression at the point where you want to
force that Staff context to appear (despite having \RemoveEmptyStaves active),
and put a \hideMMRs when you want it to return to “default” (i.e., the Staff
will disappear, if possible).
Hope this helps!
Kieren.
___
Kieren MacMillan, composer
www: http://www.kierenmacmillan.info
email: i...@kierenmacmillan.info
Thanks for the reply!
Your solution works with R1*4 for example, but not with s1*4.
I assume I have to add an *-interface, but I can't find which.
Anton Curl
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
On 05/04/2015 21:59, Colin Campbell wrote: As a quick, off the top of my admittedly empty head, kludge: assuming you know where the staff will break, why not just put in a spacer rest? Cheers, Colin I don't know if I understand well what you mean by put in a spacer rest. My staff is already full of s1, so it's not displayed because of \removeEmptyStaves, and this isn't what I want. Anton Curl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
On 05/04/2015 23:50, Urs Liska wrote: Do you really need to write spacer rests in such staves? Usually you would enter MultiMeasureRests when instruments are pausing and let LilyPond remove the staves automatically if appropriate. In that case Kieren's solution should work also for you. HTH Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user In fact, it's at a point where the musician is improvising. I can't write rests, because he's playing. Therefor I use spacer rest with \startTextSpan and \stopTextSpan. Anton Curl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Displaying a staff despite \removeEmptyStaves
Hi everyone! Is it possible to force an empty staff to be displayed occasionally when \removeEmptyStaves is used? Thanks! Anton Curl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
On 2015-04-05 01:38 PM, Anton Curl wrote: Hi everyone! Is it possible to force an empty staff to be displayed occasionally when \removeEmptyStaves is used? Thanks! Anton Curl As a quick, off the top of my admittedly empty head, kludge: assuming you know where the staff will break, why not just put in a spacer rest? Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying a staff despite \removeEmptyStaves
Hi Anton,
Is it possible to force an empty staff to be displayed occasionally when
\removeEmptyStaves is used?
You need to add multi-measure-rest-interface to the keepAliveInterfaces for
that staff.
Here are the two bits of syntactic sugar I use:
showMMRs = {
\set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface) }
hideMMRs = \unset Staff.keepAliveInterfaces
So put a \showMMRs in your music expression at the point where you want to
force that Staff context to appear (despite having \RemoveEmptyStaves active),
and put a \hideMMRs when you want it to return to “default” (i.e., the Staff
will disappear, if possible).
Hope this helps!
Kieren.
___
Kieren MacMillan, composer
www: http://www.kierenmacmillan.info
email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves doesn’t work after percent repeats
When using \RemoveEmptyStaves, after a section of percent repeats the next
line containing only rests doesn’t get removed:
\version 2.17.29
{
\repeat percent 4 {
c'1
} \break
R1*4
}
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
Is there a way to manually remove the second line? I need this in a
songbook I’m working on right now (close to the deadline) and only want to
unfold my percent repeats if nothing else is possible.
It does work correctly with both \repeat volta \repeat unfold, by the way.
--
Peter Crighton | Musician Music Engraver based in Mainz/Wiesbaden, Germany
http://www.petercrighton.de
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. I would phrase that there *would* be two systems after removing the empty staves. No, I don't mean that. I mean the situation where Lilypond is only able to put a single system on a page (due to lack of vertical space), and if this is the case, I want lilypond to insert empty staves back to get a vertically well filled page. Maybe my option should be rather a list to handle the concern Keith has mentioned (overfull pages due to a very large number of staves). For example, it could be remove-empty-single-system = #'(celesta harp) so that the staves called `celesta' and `harp' get removed even if all other systems would be added to fill a single system. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
I want an option that staves are only removed if there are at least two systems on a page. A second pass over the full score should be quite cheap, if really necessary, since line breaks are already done. I think this could be done automatically, without a second pass, [...] This would be great! I've added this as issue #3389. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
Thanks. *Very* kludgy. No, not at all. The RemoveEmptyStaves feature was intended to be adjusted in that way, so the solution in that snippet is a safe and direct way to avoid removing staves when you don't want them removed. It will not break at the next LilyPond version or interfere with anything else. But it is a *manual* solution, severely limiting the choices of lilypond to find a good layout. Your point of view is: `Don't remove this staff at that very place.' Mine is: `Don't create pages with bad layout if it can be avoided.' Doing what you want requires compiling twice: once to see where only one system fits on a page, then place \once\showMultiRests and compile again. Yes, it seems to be the only solution right now. However, just imagine that I have to insert a bar: I would then have to disable all `\once\showMultiRests' commands, check what lilypond produces, then re-insert these commands at the proper places, which might be completely different locations. This *is* kludgy. :-) What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. A second pass over the full score should be quite cheap, if really necessary, since line breaks are already done. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
Am 01.06.2013 06:17, schrieb Werner LEMBERG: What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. I would phrase that there *would* be two systems after removing the empty staves. Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
On Fri, 31 May 2013 21:17:02 -0700, Werner LEMBERG w...@gnu.org wrote: Thanks. *Very* kludgy. No, not at all. But it is a *manual* solution, Yep, but (after looking up 'kludgy' I see that) manual and kludgy are different things. What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. A second pass over the full score should be quite cheap, if really necessary, since line breaks are already done. I think this could be done automatically, without a second pass, if the removal of empty staves were to just mark them as removable and as taking no space, inserting a step to put them back and figure their space requirements just after page-breaking. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
Werner LEMBERG wl at gnu.org writes: In a big score, it removes staves even if only a single system fits on a page, see the attached image. In some big scores (say, Mahler) you need to remove the empty staves just to let the rest fit legibly on a page. You might like it if you restore some stretchability at the bottom of the page. (I don't remember the command, but the default has some stretch.) How can I avoid this? The last time this question came up, the suggestion was http://lsr.dsi.unimi.it/LSR/Item?id=312 Probably you will want to adapt that to apply to the whole Score. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
In a big score, it removes staves even if only a single system fits on a page, see the attached image. In some big scores (say, Mahler) you need to remove the empty staves just to let the rest fit legibly on a page. OK. In other words, we would need a new value for property `remove-empty', say, `multiple-systems-per-page-only', to make lilypond do what I want. Would this be possible to implement? I can imagine cyclic dependencies... How can I avoid this? The last time this question came up, the suggestion was http://lsr.dsi.unimi.it/LSR/Item?id=312 Probably you will want to adapt that to apply to the whole Score. Thanks. *Very* kludgy. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
On Wed, 29 May 2013 02:58:44 -0700, Werner LEMBERG w...@gnu.org wrote: In a big score, it removes staves even if only a single system fits on a page, see the attached image. How can I avoid this? The last time this question came up, the suggestion was http://lsr.dsi.unimi.it/LSR/Item?id=312 Probably you will want to adapt that to apply to the whole Score. Thanks. *Very* kludgy. No, not at all. The RemoveEmptyStaves feature was intended to be adjusted in that way, so the solution in that snippet is a safe and direct way to avoid removing staves when you don't want them removed. It will not break at the next LilyPond version or interfere with anything else. I just tried it. I changed Staff to Score in showMultiRests and at the places where I want all the staves to print I put \once\showMultiRests in the voice I use for tempo and time signatures. Doing what you want requires compiling twice: once to see where only one system fits on a page, then place \once\showMultiRests and compile again. Putting the empty staves back where you want them should not change the page breaks, so you won't need go in circles. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
problem with \RemoveEmptyStaves
Folks, the \RemoveEmptyStaves command apparently has a big drawback: In a big score, it removes staves even if only a single system fits on a page, see the attached image. How can I avoid this? Werner inline: remove-empty.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RemoveEmptyStaves and the ambitus_engraver
Janek Warchoł janek.lilypond at gmail.com writes:
On Mon, Apr 1, 2013 at 3:41 PM, Roman Stawski roman at stawski.fr wrote:
Interesting. If i were you, i'd place the skips inside MainSequence
and have the ambitus appear at the very beginning, and keep that first
system alive (which makes
some sense in my opinion):
\new Staff \relative c' {
\clef treble
\new MainSequence {
\skip 1*8
\repeat unfold 2 { e1 e'1 }
}
}
Unfortunately, in the real piece that doesn't work so well. Ah well, I'll
try and find a work around...
Cześć
Roman
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RemoveEmptyStaves and the ambitus_engraver
On Mon, Apr 1, 2013 at 3:41 PM, Roman Stawski ro...@stawski.fr wrote:
I'm not top posting.
It seems that \RemoveEmptyStaves doesn't play very well with the
ambitus_engraver.
In this example, I'm trying to get the treble staff removed in the
first two systems, and appear with an ambitus on the third.
It is removed correctly in the first system. But reappears in the
second. If I comment out the line (*), then the staves are removed as
needed, but the ambitus is too of course.
Interesting. If i were you, i'd place the skips inside MainSequence
and have the ambitus appear at the very beginning, and keep that first
system alive (which makes
some sense in my opinion):
\new Staff \relative c' {
\clef treble
\new MainSequence {
\skip 1*8
\repeat unfold 2 { e1 e'1 }
}
}
hth,
Janek Warchoł
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RemoveEmptyStaves and the ambitus_engraver
I'm not top posting.
It seems that \RemoveEmptyStaves doesn't play very well with the
ambitus_engraver.
In this example, I'm trying to get the treble staff removed in the
first two systems, and appear with an ambitus on the third.
It is removed correctly in the first system. But reappears in the
second. If I comment out the line (*), then the staves are removed as
needed, but the ambitus is too of course.
---
\version 2.17.11
\paper { ragged-right = ##t }
\layout {
\context {
\type Engraver_group
\name MainSequence
\accepts Voice
\consists Ambitus_engraver %% (*)
\override AmbitusNoteHead.break-visibility = ##(#f #t #t)
\override AmbitusLine.break-visibility = ##(#f #t #t)
\override AmbitusAccidental.break-visibility = ##(#f #t #t)
}
\context {
\Staff
\accepts MainSequence
\override VerticalAxisGroup.remove-empty = ##t
\override VerticalAxisGroup.remove-first = ##t
}
}
\new ChoirStaff
\new Staff \relative c' {
\clef treble
\skip 1*8
\new MainSequence {
\repeat unfold 2 { e1 e'1 }
}
\bar |.
}
\new Staff \relative c {
\clef bass
\repeat unfold 4 {e1} \break
\repeat unfold 4 {e1} \break
\repeat unfold 4 {e1}
}
---
It looks as if the ambitus is keeping the system alive. I can't get it
to work by setting keepAliveInterfaces in the staff context either.
Has anyone any ideas?
Thanks for any help
Roman
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
On 11/14/2012 07:51 PM, Thomas Morley wrote:
2012/11/14 Peter O'Doherty m...@peterodoherty.net:
Yes, great. It works perfectly.
Thanks,
Peter
Hi Peter,
would be nice, if you could tell us which kind of solution worked for
you and how.
Adapting the LSR-snippet? Then I would be highly interested. I didn't manage.
Cheers,
Harm
Harm, I'm very sorry for not replying sooner - I must have missed your
email, am just seeing it now.
This is what I used:
showMultiRests = {
\set Staff.keepAliveInterfaces = #'(
rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface)
}
hideMultiRests = \unset Staff.keepAliveInterfaces
And then simply:
\hideMultiRests
s8 s8 s8
Hope this helps.
Best,
Peter
--
//=
- Peter O'Doherty
- http://www.peterodoherty.net
- m...@peterodoherty.net
- https://joindiaspora.com/people/70716
//=
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
2012/12/20 Peter O'Doherty m...@peterodoherty.net:
On 11/14/2012 07:51 PM, Thomas Morley wrote:
2012/11/14 Peter O'Doherty m...@peterodoherty.net:
Yes, great. It works perfectly.
Thanks,
Peter
Hi Peter,
would be nice, if you could tell us which kind of solution worked for
you and how.
Adapting the LSR-snippet? Then I would be highly interested. I didn't
manage.
Cheers,
Harm
Harm, I'm very sorry for not replying sooner - I must have missed your
email, am just seeing it now.
This is what I used:
showMultiRests = {
\set Staff.keepAliveInterfaces = #'(
rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface)
}
hideMultiRests = \unset Staff.keepAliveInterfaces
And then simply:
\hideMultiRests
s8 s8 s8
Hope this helps.
Best,
Peter
Many thanks!
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
Yes, great. It works perfectly. Thanks, Peter On 11/06/2012 11:38 PM, Kieren MacMillan wrote: Hi Peter, Have you looked at this hint? http://lsr.dsi.unimi.it/LSR/Item?id=312 Hope this helps! Kieren. On 2012-Nov-6, at 10:36, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Peter O'Doherty m...@peterodoherty.net To: lilypond-user lilypond-user@gnu.org Sent: Tuesday, November 06, 2012 1:46 PM Subject: \RemoveEmptyStaves Hi, I have a score with a system where some staves have measures which are filled with rests and others with spacer rests (I need these to enable \change Staff elements). I would like to remove the staves with have rests only but as far as I can see \RemoveEmptyStaves will remove those with spacers rests as well. Is there a way round this? Many thanks, Peter A solution (there may be others) would be to use some hidden notes as well as spacer rests. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- //= - Peter O'Doherty - http://www.peterodoherty.net - m...@peterodoherty.net - https://joindiaspora.com/people/70716 //= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
2012/11/14 Peter O'Doherty m...@peterodoherty.net: Yes, great. It works perfectly. Thanks, Peter Hi Peter, would be nice, if you could tell us which kind of solution worked for you and how. Adapting the LSR-snippet? Then I would be highly interested. I didn't manage. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaves
Hi, I have a score with a system where some staves have measures which are filled with rests and others with spacer rests (I need these to enable \change Staff elements). I would like to remove the staves with have rests only but as far as I can see \RemoveEmptyStaves will remove those with spacers rests as well. Is there a way round this? Many thanks, Peter -- //= - Peter O'Doherty - http://www.peterodoherty.net - m...@peterodoherty.net - https://joindiaspora.com/people/70716 //= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
- Original Message - From: Peter O'Doherty m...@peterodoherty.net To: lilypond-user lilypond-user@gnu.org Sent: Tuesday, November 06, 2012 1:46 PM Subject: \RemoveEmptyStaves Hi, I have a score with a system where some staves have measures which are filled with rests and others with spacer rests (I need these to enable \change Staff elements). I would like to remove the staves with have rests only but as far as I can see \RemoveEmptyStaves will remove those with spacers rests as well. Is there a way round this? Many thanks, Peter A solution (there may be others) would be to use some hidden notes as well as spacer rests. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
Hi Peter, Have you looked at this hint? http://lsr.dsi.unimi.it/LSR/Item?id=312 Hope this helps! Kieren. On 2012-Nov-6, at 10:36, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Peter O'Doherty m...@peterodoherty.net To: lilypond-user lilypond-user@gnu.org Sent: Tuesday, November 06, 2012 1:46 PM Subject: \RemoveEmptyStaves Hi, I have a score with a system where some staves have measures which are filled with rests and others with spacer rests (I need these to enable \change Staff elements). I would like to remove the staves with have rests only but as far as I can see \RemoveEmptyStaves will remove those with spacers rests as well. Is there a way round this? Many thanks, Peter A solution (there may be others) would be to use some hidden notes as well as spacer rests. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \RemoveEmptyStaves
2012/11/6 Phil Holmes m...@philholmes.net:
- Original Message - From: Peter O'Doherty
m...@peterodoherty.net
To: lilypond-user lilypond-user@gnu.org
Sent: Tuesday, November 06, 2012 1:46 PM
Subject: \RemoveEmptyStaves
Hi,
I have a score with a system where some staves have measures which are
filled with rests and others with spacer rests (I need these to enable
\change Staff elements). I would like to remove the staves with have rests
only but as far as I can see \RemoveEmptyStaves will remove those with
spacers rests as well. Is there a way round this?
Many thanks,
Peter
A solution (there may be others) would be to use some hidden notes as well
as spacer rests.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Peter,
the `normal´ way to do what you want is to trim keepAliveInterfaces as
shown in LSR
http://lsr.dsi.unimi.it/LSR/Item?id=312
But { s1 } seems not to result in a Grob. And I found no interface for
it to distinguish from { r1 }.
Is there any?
So Phil's suggestion (or some similiar) seems to be the way.
Sorry,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Bar lines appearing even with \stopStaff and \RemoveEmptyStaves
Hy,
does someone know why, even with \stopStaff and \RemoveEmptyStaves,
the barlines on the upper staff stand still?
Below the code:
up= { \stopStaff s2*8 \startStaff
% \set Staff.instrumentName = m.e.
s8 d8- s d-
}
center=\relative c {
\time 2/4
\clef bass
ees8.\mf f,16 a'4^\open^+ aes,8 f8 ~ f4
a'16 ees8. ~ ees8 aes, ~ aes8 f8 ~ f16 ees'16 aes,8
a'4 ~ a16 f,8. ees'4 ~ ees8 a16 f, ~ \break
f8. aes16 ~ aes ees'8. a4 ~ a8 aes,8 ~
aes ees'8 ~ ees8. f,16 ~ f a'16 ees8 ~ ees16 f,8. ~
f16 a'8. ~ a8 ees16 aes,16 ~ aes4 ~ aes16 f8. \break
}
\score {
\new RhythmicStaff = up \with {
\remove Time_signature_engraver
\remove Bar_number_engraver
} \up
\new Staff = center \center
\layout {
\context {
\Staff
\RemoveEmptyStaves
\override VerticalAxisGroup #'remove-first = ##t
}
}
}
--
www.myspace.com/alexandreficagna
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar lines appearing even with \stopStaff and \RemoveEmptyStaves
Alexandre Ficagna wrote: Hy, does someone know why, even with \stopStaff and \RemoveEmptyStaves, the barlines on the upper staff stand still? Below the code: you didn't apply \RemoveEmptyStaves \override VerticalAxisGroup #'remove-first = ##t to the RhythmicStaff Eluze -- View this message in context: http://old.nabble.com/Bar-lines-appearing-even-with-%5CstopStaff-and-%5CRemoveEmptyStaves-tp34134929p34135099.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
