If I use \stopStaff then systems where it is active don't display
braces, even though they do display the initial clef.
For example:
\version "2.24"
\score {
\new StaffGroup <<
\new Staff {\stopStaff c'1 }
On 01/02/2023 02:56, Ahanu Banerjee wrote:
> I am trying to modify the color of the ledger lines for a single note. My
> understanding is that I need to use \stopStaff and \startStaff for this.
> However, doing so causes the staff lines to be discontinuous. This rounds the
> ends
On 01/02/2023 17:49, Valentin Petzel wrote:
> Hello Richard,
>
> This is not so much a bug in \stopStaff, but an inconsistency in the
> LedgerLineSpanner engraver. It is good you’ve found a workaround that works
> for you!
If you see a bug, please file a GitLab issue
Hello Richard,
This is not so much a bug in \stopStaff, but an inconsistency in the
LedgerLineSpanner engraver. It is good you’ve found a workaround that works
for you!
Valentin
Am Mittwoch, 1. Februar 2023, 17:08:48 CET schrieb Richard Shann:
> Thank you for the quick response Valen
r
> does not know the StaffSymbol ended.
>
> The LedgerLineSpanner will be broken on encountering a new
> StaffSymbol. To
> solve this issue one could change the engraver to listen to stop
> staff events
> and in this case also break the LedgerLineSpanner.
I guess that
I've discovered this can be made still more minimal:
>
> \version "2.24"
> music = {
> e'''1 \stopStaff e'''1 \break e'''1 }
> \score { \music }
>
> The \break is needed.
>
> Richard
>
On Wed, 2023-02-01 at 10:35 +, Richard Shann wrote:
> In this piece
I've discovered this can be made still more minimal:
\version "2.24"
music = {
e'''1 \stopStaff e'''1 \break e'''1 }
\score { \music }
The \break i
In this piece the note on the first system has ledger lines typeset
while those on the second does not.
\version "2.24"
music = {
s1*4/4 \stopStaff e'''1
s1*4/4 \break e'''1 s1*4/4 }
\score { \music }
The e
the ledger lines for a single note. My
> understanding is that I need to use \stopStaff and \startStaff for this.
> However, doing so causes the staff lines to be discontinuous. This rounds
> the ends of the staff lines surrounding the point at which the staff is
> stopped and causes ad
I am trying to modify the color of the ledger lines for a single note. My
understanding is that I need to use \stopStaff and \startStaff for this.
However, doing so causes the staff lines to be discontinuous. This rounds
the ends of the staff lines surrounding the point at which the staff is
Hi Jean,
> I think this would handle quite a number of cases without
> the user thinking about it, while still avoiding ambiguity
> at all times.
That would certainly be an improvement over the status quo!
Kieren.
Le 07/01/2023 à 19:16, Jean Abou Samra a écrit :
"\dt + warning if not used"
Come to think of it:
For sure, we don't need a warning about \dt (or grace skips) not being
used in the case where there are no zero-length events at that point.
The grace note problem is extremely general. However,
Le 07/01/2023 à 18:43, David Kastrup a écrit :
Well, this was sort of saying that there may be no silver bullet, but we
may have to pick between chrome and aluminum ones.
Sometimes there is a solution that blends better into human expectations
than strict logic.
That's possible.
In my opini
Le 07/01/2023 à 18:32, Kieren MacMillan a écrit :
David’s interpretation of my idea isn’t correct. I never suggested letting the
second Staff start after the grace note, simply that decisions for that Staff
should be made independently of the Staff that contains the grace music.
Here’s a set o
Hi all,
>> That would presumably lead to
>>
>> {
>> \once \override NoteHead.color = ...
>> \once \override Staff.NoteHead.color = ...
>> ...
>> }
>>
>> getting the events reordered so that the Staff.NoteHead override
>> starts before graces and the NoteHead one starts after, which I
>> wo
Jean Abou Samra writes:
> Le 07/01/2023 à 17:58, David Kastrup a écrit :
>>> In that case, the NoteHead one has no effect, because \once applies to
>>> the next time step only, and the next time step is for a grace note
>>> another voice.
>> The recovery action of \once should likely occur after
Hi David,
> Then I will wait until I see your actual implementation instead of
> reading any meaning into your words.
“Non-implemented” and “implemented” are not the only two possible states in the
development of computer code.
I look forward to any discussion, with any developers, of possible
Hi all,
> You cannot let the second Staff start after the grace note.
David’s interpretation of my idea isn’t correct. I never suggested letting the
second Staff start after the grace note, simply that decisions for that Staff
should be made independently of the Staff that contains the grace mu
Le 07/01/2023 à 17:58, David Kastrup a écrit :
In that case, the NoteHead one has no effect, because \once applies to
the next time step only, and the next time step is for a grace note
another voice.
The recovery action of \once should likely occur after the next _local_
timestep.
OK, that
Kieren MacMillan writes:
> Hi David,
>
>> That's just wild hand-waving. You cannot let the second Staff start
>> after the grace note. That would look like
>
> You have inferred things about my suggested implementation which I
> neither stated nor implied.
> (These kinds of discussions always g
Hi David,
> That's just wild hand-waving. You cannot let the second Staff start
> after the grace note. That would look like
You have inferred things about my suggested implementation which I neither
stated nor implied.
(These kinds of discussions always go better when people don’t make
assum
Kieren MacMillan writes:
> Hi David (et al.),
>
>>> In that case, the NoteHead one has no effect, because \once applies to
>>> the next time step only, and the next time step is for a grace note
>>> another voice.
>>
>> The recovery action of \once should likely occur after the next _local_
>> t
Hi David (et al.),
>> In that case, the NoteHead one has no effect, because \once applies to
>> the next time step only, and the next time step is for a grace note
>> another voice.
>
> The recovery action of \once should likely occur after the next _local_
> timestep.
>
>> Do they occur after?
Kieren MacMillan writes:
> Hi Jean,
>
>> Um, that is exactly the current default. And it is what makes
>>
>> \version "2.24.0"
>>
>> <<
>> \new Staff { \grace c'8 c'1 }
>> \new Staff {
>> \clef bass % zero-length => after graces
>> c'1
>> }
>> >>
>>
>> return output that most use
p.s.
> In this case (as with so many!) the problem isn't moment-bleed, it's
> context-bleed: the grace music doesn’t apply to the lower staff, and thus
> shouldn’t be included in decision-making there; likewise, the clef doesn’t
> apply to the upper staff, and so shouldn’t be included in the de
Kieren MacMillan writes:
> Hi Jean,
>
>> That sounds like you want to make all zero-length events happen
>> before the grace by default, but that is not always desirable,
>> as \once \set/\override shows.
>
> I would say the exact opposite: by default, all zero-length events
> should happen betwe
Hi Jean,
> Um, that is exactly the current default. And it is what makes
>
> \version "2.24.0"
>
> <<
> \new Staff { \grace c'8 c'1 }
> \new Staff {
> \clef bass % zero-length => after graces
> c'1
> }
> >>
>
> return output that most users are not expecting.
In this case (as wit
Jean Abou Samra writes:
> Le 07/01/2023 à 17:11, Kieren MacMillan a écrit :
>> Could you explain this a bit more, please? This is a position I’ve
>> never quite understood about Issue #34: I would love to see an input
>> where I can’t determine the output with certainty just from the
>> input.
>
Le 07/01/2023 à 17:50, Kieren MacMillan a écrit :
Hi Jean,
That sounds like you want to make all zero-length events happen
before the grace by default, but that is not always desirable,
as \once \set/\override shows.
I would say the exact opposite: by default, all zero-length events should
ha
Hi Jean,
> That sounds like you want to make all zero-length events happen
> before the grace by default, but that is not always desirable,
> as \once \set/\override shows.
I would say the exact opposite: by default, all zero-length events should
happen between the grace music and the restarting
Hi Jean,
> Just take the example I gave earlier and remove the grace skips.
>
> \version "2.24.0"
> <<
> \new Staff { \grace { c'8 d'8 } c'1 }
> \new Staff {
> \once \override Staff.TimeSignature.color = "red"
> \once \override NoteHead.color = "red"
> c'1
> }
> >>
> Do the over
Le 07/01/2023 à 17:17, David Kastrup a écrit :
I disagree. We have grace fixups in sequential music that do this
(zero-length events before grace music are executed before the grace)
and the same reasonably could be done with simultaneous music. That's
more complex, but not terribly so. Some o
Le 07/01/2023 à 17:11, Kieren MacMillan a écrit :
Could you explain this a bit more, please? This is a position I’ve never quite
understood about Issue #34: I would love to see an input where I can’t
determine the output with certainty just from the input.
Just take the example I gave earlie
Jean Abou Samra writes:
> Le 07/01/2023 à 16:48, Kieren MacMillan a écrit :
>> Hi all,
>>
>>> [ It sometimes makes me wonder if we need a concept of "infinitesimal
>>> time", to allow disambiguating ]
>>>
>>> Yes, the concept of 0-cycles, that can be allowed to execute in
>>> order for decision
Hi Jean,
>> That might even be a liminal space in which the infamous Grace Music Bug™
>> could be handled grace-fully…?
> Actually, that is what originally made me muse about this ...
“Great minds think alike…” ;)
> Issue #34 is, in my opinion, a perfectly unsolvable problem, because
> it's as
Le 07/01/2023 à 16:48, Kieren MacMillan a écrit :
Hi all,
[ It sometimes makes me wonder if we need a concept of "infinitesimal
time", to allow disambiguating ]
Yes, the concept of 0-cycles, that can be allowed to execute in order for
decisions to be made at the end of the timestep once all
Hi all,
> [ It sometimes makes me wonder if we need a concept of "infinitesimal
> time", to allow disambiguating ]
>
> Yes, the concept of 0-cycles, that can be allowed to execute in order for
> decisions to be made at the end of the timestep once all the 0-cycles have
> completed, seems like
nternals
so I don't know the ramifications of "seems like a good idea".
On 2023-01-07 13:27, Jean Abou Samra wrote:
Le 06/01/2023 à 00:37, Lukas-Fabian Moser a écrit :
The Staff_symbol_engraver is not really equipped to deal with
multiple \startStaff / \stopStaff events at the
Le 06/01/2023 à 00:37, Lukas-Fabian Moser a écrit :
The Staff_symbol_engraver is not really equipped to deal with multiple
\startStaff / \stopStaff events at the same point of time.
I would not call the current Staff_symbol_engraver behavior a bug,
but a feature.
You will see that your
Hi Tomasz,
Am 05.01.23 um 13:16 schrieb Tomasz Bauć:
I also checked version without the Scheme:
\stopStaff
\repeat unfold 9 {s8}
\startStaff
\stopStaff
\repeat unfold 3 {s8}
\startStaff
\stopStaff
\repeat unfold 11 {s8}
\startStaff
(Please always give
Hi,
I wrote a simple function to make and fill empty bars without staff
engraver.
It follows:
nbar = #(define-music-function (number) (integer?)
#{ \stopStaff
\repeat unfold #number {s8}
\startStaff #})
There is a problem when I've got to empty bars next to
a Staff with several engravers \remove’d, using \stopStaff to
> > eliminate staff lines, and then setting Stem.details.beamed-lengths
> > to reduce the length of stems. However, setting
> > Stem.details.beamed-lengths seems to have no effect after
> > \stopStaff, so the stems
o this, I’m using a Staff with
>> several engravers \remove’d, using \stopStaff to eliminate staff lines, and
>> then setting Stem.details.beamed-lengths to reduce the length of stems.
>> However, setting Stem.details.beamed-lengths seems to have no effect after
>> \stopSta
Am Sa., 16. Apr. 2022 um 13:49 Uhr schrieb Nate Whetsell
:
>
> I’m trying to put some beamed notes (no staff lines, time signature, or
> anything else) in a \markup block. To do this, I’m using a Staff with several
> engravers \remove’d, using \stopStaff to eliminate staff lin
I’m trying to put some beamed notes (no staff lines, time signature, or
anything else) in a \markup block. To do this, I’m using a Staff with several
engravers \remove’d, using \stopStaff to eliminate staff lines, and then
setting Stem.details.beamed-lengths to reduce the length of stems
On Sun, Mar 20, 2022 at 7:21 PM Shane Brandes wrote:
>
> values greater than 1 also yield odd results.
...
>> I have run into another possible-bug-certainly-ugly issue that I found
>> trying to create an ossia bar.
...
>> Is it a bug that I should post on the bugs list? Is there a work-around?
I
ed in size with magnifyStaff and there is a stopStaff
> right after it, the stems are too short and the beams are too wide.
> Here's a MWE:
>
> %%%
> \version "2.23.6"
>
> \new Staff \with { \magnifyStaff #2/3 } {
> \relative {
> c''16 c \s
Hi all,
I have run into another possible-bug-certainly-ugly issue that I found
trying to create an ossia bar. When a musical figure has beams and the
staff is reduced in size with magnifyStaff and there is a stopStaff
right after it, the stems are too short and the beams are too wide.
Here
Hi Alexandre,
You can make that note take up less horizontal space by changing
fis \stopStaff
into
fis4*1/2 \stopStaff s
Does that do what you want?
Kevin
On Fri, 2020-08-07 at 11:37 -0300, Alexandre Ficagna wrote:
> Hi there
>
> I'm having trouble trying to let the cropped st
_\circd r
c-1 a-4
g, b-4 r e-2 g-1 e-4
\time 7/4
c r e-4 a-2 d-1 r b-4
\bar "|."
}
\new Staff = "harmonicos" \with {
alignAboveContext = #"notas"
\remove "Time_signature_engraver"
\remove "Bar_engraver"
fontSize = #-3
\override StaffSymbol.staff-space = #(ma
Thanks, Robin, for your suggestion. I checked for auxiliary voices and found
none.
After some experimenting, I learned that by including
\override Staff.StaffSymbol.line-count = #0
right after \stopStaff properly displays the barlines.
--
Sent from: http://lilypond.1069038.n5.nabble.com
nagymusic wrote:
I attached a screenshot from the ending of my score in which I used
\stopStaff and \startStaff to completely hide staves at the end of the piece
for performance purposes. Would anyone be willing to have a look at the
attached screenshot and explain why there're small segmen
I attached a screenshot from the ending of my score in which I used
\stopStaff and \startStaff to completely hide staves at the end of the piece
for performance purposes. Would anyone be willing to have a look at the
attached screenshot and explain why there're small segments of staves
visib
Folks,
consider:
\version "2.19.82"
<<
\new PianoStaff <<
\new Staff { R1 \stopStaff s1*15 \startStaff R1 }
\new Staff { R1 \stopStaff s1*15 \startStaff R1 }
>>
\new Staff { R1*10 \break R1*10 }
>>
Is there a way to obtain the system start de
I know this problem, IMO it’s a bug. You can work around by putting
spacer rests after the \stopStaff until the next barline occurs. In your
case s16*10 if I counted correctly.
Am 28.10.2015 um 21:58 schrieb Ryan Michael:
Thank you. This is almost 100% what I was trying to achieve. The only
define-music-function () ()
>>> #{
>>> \context Staff
>>> \applyContext
>>> #(lambda (context)
>>>;; access context properties and pick a property setting based on
>>> them...
>>>(ly:context-pushpop-proper
\context Staff
>> \applyContext
>> #(lambda (context)
>>;; access context properties and pick a property setting based on
>> them...
>>(ly:context-pushpop-property context 'StaffSymbol 'color green))
>> \stopStaff
>> \
property setting based on
> them...
> (ly:context-pushpop-property context 'StaffSymbol 'color green))
> \stopStaff
> \startStaff
>#})
Frankly, anything wrong with
\temporary \override Staff.StaffSymbol.color = #green
here?
Assuming you want a temp
anks!
\version “2.19.22”
myfunc =
#(define-music-function () ()
#{
\context Staff
\applyContext
#(lambda (context)
;; access context properties and pick a property setting based on
them...
(ly:context-pushpop-property context 'StaffSymbol 'colo
Paul Morris writes:
> % These work as expected
> {
> c'
> \stopStaff
> \startStaff
> \override Staff.StaffSymbol.color = #red
> c'
> \override Staff.StaffSymbol.color = #green
> \stopStaff
> \startStaff
> c’
> }
>
> {
>
I found another way to do what I was trying to do. (I used \applyContext in a
music function to access and then modify a custom staff context property, and
then used a custom StaffSymbol engraver to access that context property and
change the grob properties of any new StaffSymbol grob accordin
and \stopStaff \startStaff. There’s probably some subtlety that
I’m missing… (Maybe it has to do with the difference between \temporary
\override and \override ?) Below is a tiny example (not my actual use case).
Thanks for any help with this,
-Paul
\version "2.19.22"
% These work a
racket and dynamics move to its proper place.
>>
>> \version "2.16.0"
>>
>> skipGlissOn =
>> {
>> \override NoteColumn #'glissando-skip = ##t
>> \override NoteHead #'transparent = ##t
>> \stopStaff
>> \override Staff.LedgerL
rride NoteColumn #'glissando-skip = ##t
> \override NoteHead #'transparent = ##t
> \stopStaff
> \override Staff.LedgerLineSpanner #'transparent = ##t
> \startStaff
> }
>
> skipGlissOff =
> {
> \revert NoteColumn #'glissando
ou see in the image.
Here is the lily code. When you comment out the stop- and startStaff
commands the bracket and dynamics move to its proper place.
\version "2.16.0"
skipGlissOn =
{
\override NoteColumn #'glissando-skip = ##t
\override NoteHead #'transparent = ##t
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
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
2010/1/7 Patrick Schmidt :
> Hope this helps to find the bug (if it's one).
Thank you both for your comments regarding this bug. It was caused by
an unsafe lookup, which I've just fixed in master.
Regards,
Neil
___
lilypond-user mailing list
lilypon
Original-Nachricht
> Datum: Thu, 07 Jan 2010 17:09:49 +0100
> Von: Federico Bruni
> An: Patrick Schmidt
> CC: lilypond-user@gnu.org
> Betreff: Re: \\stopStaff does not work with TabStaff in StaffGroup
> Il 07/01/2010 16:33, Patrick Schmidt ha scritto:
>
Il 07/01/2010 16:33, Patrick Schmidt ha scritto:
Federico,
I think it's a problem with moderntab. If you remove all the \clef "moderntab"
then everything works fine. (I tested it with version 2.13.10.)
Thanks Patrick,
yes it works also in 2.13.9
and you are right, it's not a matter of poly
Federico Bruni
> An: lilypond-user@gnu.org
> Betreff: \\stopStaff does not work with TabStaff in StaffGroup
> I *think* I've found a kind of bug..
> I was tryin' to suppress a couple of bars in a StaffGroup (made of one
> Staff and one TabStaff), using \stopStaff
>
> I&
I *think* I've found a kind of bug..
I was tryin' to suppress a couple of bars in a StaffGroup (made of one
Staff and one TabStaff), using \stopStaff
I've found out, after several tries (see attached file), that the
problem arises when I use \stopStaff \startStaff in a sco
On 05/02/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> I forward your question to bug-lilypond, since it shows a regression
> bug compared to earlier versions.
Yes, indeed.
I added it to the bug tracker as
http://code.google.com/p/lilypond/issues/detail?id=574
Let's hope someone will have a
version 2.11.35
Any hints?
Toine Schreurs
%=== start =
\version "2.11.38"
musicOne = \relative c' {
\time 2/4
d4 d |
a' a |
b b |
f2
}
musicTwo = \relative c' {
e4 e |
b' b |
c c |
g2
}
ossia = \relative c' {
\stopStaff
time 2/4
d4 d |
a' a |
b b |
f2
}
musicTwo = \relative c' {
e4 e |
b' b |
c c |
g2
}
ossia = \relative c' {
\stopStaff
s2*2 |
\startStaff
bes'8^"ossia" g bes g |
\stopStaff
s2 |
}
\score {
<<
\new Staff \musicOn
You can set firstClef to #f, and remove Time_signature_engraver from the
ossia-staff.
See e.g. http://lilypond.org/doc/v2.11/input/manual/lily-6910c8f3a6.ly
Met vriendelijke groet,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
"You must be the change you wish to see in the world."
Hi,
stopping a Staff at the beginning of a piece results in the clef and
time signature being printed without the staff symbol. Is there a way
to make the staff symbol appear *without* having to enter music (or to
skip musical time) before the \stopStaff?
Below is an example: I would like to
2007/9/17, Neil Thornock <[EMAIL PROTECTED]>:
> Nevermind, just figured it out (actually did it before, just didn't
> remember):
>
> \override Staff.StaffSymbol #'transparent = ##t
> \stopStaff \startStaff
>
> and then reverting, in case anybody was wondering.
Nevermind, just figured it out (actually did it before, just didn't
remember):
\override Staff.StaffSymbol #'transparent = ##t
\stopStaff \startStaff
and then reverting, in case anybody was wondering.
On 9/17/07, Neil Thornock <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
Hello folks,
Is there a way to achieve the effect of \stopStaff without eliminating the
brace at the beginning of the following (PianoStaff) system? I'd like to
eliminate only the staff lines, nothing else.
Any hints?
Thanks.
___
lilypond
= \key f \major
myTime = \time 4/4
myMarkCoda = \mark \markup { \musicglyph #"scripts.coda" }
myMarkDcAlCoda = { \once \override Score.RehearsalMark #'self-alignment-X =
#right
\mark "D.C. al Coda " }
myMarkEndCoda = {
\stopStaff
\cadenzaOn \skip1 \cadenzaOff
\clef tre
> fixed in cvs.
Thanks a lot for your help!
Markus
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Mats Bengtsson schreef:
This clearly looks like a bug, so I forward it to bug-lilypond.
/Mats
fixed in cvs.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
__
This clearly looks like a bug, so I forward it to bug-lilypond.
/Mats
Markus Schneider wrote:
Hello all,
this example has two identical repeats with an alternative ending. After
issuing /stopStaff /startStaff the volta brackets are missing.
Can anyone help me to avoid this please?
Markus
Hello all,
this example has two identical repeats with an alternative ending. After
issuing /stopStaff /startStaff the volta brackets are missing.
Can anyone help me to avoid this please?
Markus
\version "2.8.4"
\relative c'' {
% Volta brackets d
:08, Han-Wen Nienhuys wrote:
Sean Reed wrote:
hi,
since i hadn't seen a reply to this yet, maybe i formulated the
question unclearly.
\stopStaff doesn't seem to work for me at the very beginning of a
piece. everywhere else later in the piece it seems to work fine.
when used at the
Sean Reed wrote:
hi,
since i hadn't seen a reply to this yet, maybe i formulated the
question unclearly.
\stopStaff doesn't seem to work for me at the very beginning of a
piece. everywhere else later in the piece it seems to work fine.
when used at the beginning of the piece
t, maybe i formulated the
question unclearly.
\stopStaff doesn't seem to work for me at the very beginning of a
piece. everywhere else later in the piece it seems to work fine.
when used at the beginning of the piece, only the lines of very first
note are hidden, no matter how long the passag
hi,
since i hadn't seen a reply to this yet, maybe i formulated the
question unclearly.
\stopStaff doesn't seem to work for me at the very beginning of a
piece. everywhere else later in the piece it seems to work fine.
when used at the beginning of the piece, only the lines of
the piece, but no matter how long i make the first
\skip, the first \stopStaff only leaves off the staff lines for the
first 2 beats (more accurately: 1 beat plus the expected 1 beat of
lead-in lines), and creates a bunch of empty measures with full staff
lines after that.
there's
90 matches
Mail list logo
