Re: Override NoteHead glyph
Hi Ahanu,
Am 22.06.22 um 21:19 schrieb Ahanu Banerjee:
I am trying to create noteheads (without stems) that have a duration
longer than a quarter note (crotchet) but are filled-in. They are
meant to represent the notes that will be heard when a harmonic is
played. I am not sure how to do this; one workaround is to use a
quarter note value and a spacer rest, but this results in too much
empty space. I tried \override NoteHead.glyph-name = #'"noteheads.s2",
but that did not work.
Example below (the notes are arbitrary):
\version "2.23.7"
\relative c''
{ << { \override Parentheses.font-size = #-1.5 \omit Flag \omit Stem
\teeny \tweak X-offset #0.2
%% the higher voice should have filled-in noteheads
<\parenthesize d \parenthesize f>2 } \\
{ 2 } >> }
I think
filled = \tweak duration-log 2 \etc
is easier than the solutions proposed so far:
\version "2.23.7"
filled = \tweak duration-log 2 \etc
\relative c''
{
<<
{
\override Parentheses.font-size = #-1.5 \omit Flag \omit Stem
\teeny \tweak X-offset #0.2
%% the higher voice should have filled-in noteheads
\filled <\parenthesize d \parenthesize f>2
} \\
{ 2 }
>>
}
Lukas
Re: CrossStaff and Dynamics
Oh - I just realised you were talking about the engraver! Andrew Andrew Bernard wrote on 26/06/2022 12:35 PM: No need for shame. I think it depends on the direction of the stem in the upper staff doesn't it? So it's not always the case that you have to put the cross staff indication in the upper staff. I think. Andrew Alberto Simões wrote on 26/06/2022 6:53 AM: Dear Paul, I feel ashamed now. Indeed, I lost it when changing to the new Dynamics. Thanks for your quick answer. Its working back ;)
Re: CrossStaff and Dynamics
No need for shame. I think it depends on the direction of the stem in the upper staff doesn't it? So it's not always the case that you have to put the cross staff indication in the upper staff. I think. Andrew Alberto Simões wrote on 26/06/2022 6:53 AM: Dear Paul, I feel ashamed now. Indeed, I lost it when changing to the new Dynamics. Thanks for your quick answer. Its working back ;)
Re: CrossStaff and Dynamics
Dear Paul,
I feel ashamed now.
Indeed, I lost it when changing to the new Dynamics.
Thanks for your quick answer.
Its working back ;)
Alberto
On Sat, Jun 25, 2022 at 9:49 PM Paul Hodges wrote:
> Your snippet doesn't include the Span_stem_engraver, so I guess you lost
> that when adding the Dynamics. Here is an extracted part of the score of
> that I am just now working on, with /lots/ of cross-staff joins as well as
> central dynamics:
>
> \score {
> <<
> \new PianoStaff \with {
> \consists "Span_stem_engraver"
> }
> <<
> \set PianoStaff.instrumentName = \markup\bold"Piano I"
> \new Staff = "priRH" { \clef treble \IpriRH }
> \new Dynamics = "priDy" \IpriDy
> \new Staff = "priLH" { \clef bass \IpriLH }
> >>
> >>
> }
>
> Regards,
> Paul
>
>
> * From: * Alberto Simões
> * To: *
> * Sent: * 25/06/2022 21:17
> * Subject: * CrossStaff and Dynamics
>
> Hello
>
> I am using CrossStaff and everything worked fine.
> But after following a snippet that suggest adding the dynamics as an
> independent voice of spaces:
>
> \score {
> \new PianoStaff = "PianoStaff_pf" <<
> \new Staff = "upper" << \upper >>
> \new Dynamics = "dynamics" \dynamics
> \new Staff = "lower" << \lower >>
> >>
> }
>
> the beams are no longer connected.
> Is there any way to overcome this problem?
>
> The idea of using a dynamic "voice" was to get all dynamics middle-aligned
> between them...
>
> Thank you for any hint,
> Alberto
>
>
Re: CrossStaff and Dynamics
Your snippet doesn't include the Span_stem_engraver, so I guess you lost that
when adding the Dynamics. Here is an extracted part of the score of that I am
just now working on, with /lots/ of cross-staff joins as well as central
dynamics:
\score {
<<
\new PianoStaff \with {
\consists "Span_stem_engraver"
}
<<
\set PianoStaff.instrumentName = \markup\bold"Piano I"
\new Staff = "priRH" { \clef treble \IpriRH }
\new Dynamics = "priDy" \IpriDy
\new Staff = "priLH" { \clef bass \IpriLH }
>>
>>
}
Regards,
Paul
From: Alberto Simões
To:
Sent: 25/06/2022 21:17
Subject: CrossStaff and Dynamics
Hello
I am using CrossStaff and everything worked fine.
But after following a snippet that suggest adding the dynamics as an
independent voice of spaces:
\score {
\new PianoStaff = "PianoStaff_pf" <<
\new Staff = "upper" << \upper >>
\new Dynamics = "dynamics" \dynamics
\new Staff = "lower" << \lower >>
>>
}
the beams are no longer connected.
Is there any way to overcome this problem?
The idea of using a dynamic "voice" was to get all dynamics middle-aligned
between them...
Thank you for any hint,
Alberto
CrossStaff and Dynamics
Hello
I am using CrossStaff and everything worked fine.
But after following a snippet that suggest adding the dynamics as an
independent voice of spaces:
\score {
\new PianoStaff = "PianoStaff_pf" <<
\new Staff = "upper" << \upper >>
\new Dynamics = "dynamics" \dynamics
\new Staff = "lower" << \lower >>
>>
}
the beams are no longer connected.
Is there any way to overcome this problem?
The idea of using a dynamic "voice" was to get all dynamics middle-aligned
between them...
Thank you for any hint,
Alberto
Re: How do I keep space between staves reasonable?
It's an issue with flexible vertical spacing relating to ChordNames and FretBoards, easily solved with setting this up with VerticalAxisGroup alist property settings. Kevin sent me the score. When I refine the solution I'll post something about it here soon. I have to say, even after years of using LilyPond, I always find the flexible vertical spacing settings manual page quite hard reading, I suppose because there are so many fine details and interactions that can be adjusted in all sorts of ways. But I could not think of a way to write that section simpler of more clearly. It's just a subtle feature of great power in LilyPond. Andrew
Re: How do I keep space between staves reasonable?
It sounds like Kieren's suggestion would work best. If you have more music or markup before or after, just put that page into its own bookpart. Get BlueMail for Android On Jun 24, 2022, 10:50 PM, at 10:50 PM, Kevin Cole wrote: >I'm sorry I don't know how to create a minimal working example. > >I have a rather simple melody with a single staff (vocal). Under the >staff I have two stanzas of lyrics (the first verse and the chorus). >After the score, I have a \markup section with additional verses. > >When I have just the first verse, everything looks fine. When I add >the chorus, the spaces where I have \break become ridiculously large, >as LilyPond tries to anticipate my needs, and forces the \markup >section to a new page and vertically justifies / fills the page. > >On the surface, what I want to do seems deceptively simple. > >I've experimented with annotate-spacing and system-system-spacing to >no avail. The truth is I don't really understand what I'm looking at >with all the various distances. (In the annotated PDF, it looks like I >want to shrink "extra dist (system-system-spacing)".) > >If I tightened the space between the \break's I think everything would >remain on one page. > >Or, if I can't do that, and it has to force the \markup additional >verses to a new page, it still seems weird to have so much whitespace >between \break's. I think it would look better with all the whitespace >at the end of the score...
Re: Cross-Staff stems not working
On Sat, Jun 25, 2022 at 5:59 AM Simon Bailey wrote:
>
> Hi,
>
> consider this code:
>
> \version "2.23.9"
> \layout {
> \context {
> \PianoStaff
> \consists "Span_stem_engraver"
> }
> }
>
> {
> \new PianoStaff <<
> \new Staff {
> 4 r r2 |
> }
> \new Staff {
> \clef bass
> \crossStaff { 4 } r r2 |
> }
> >>
> }
>
> What am I missing to get the stem to span the staves? I get the
> attached output with two separate chords...
It worked for me when I used \crossStaff on the upper chord, not the lower:
\version "2.23.9"
\layout {
\context {
\PianoStaff
\consists "Span_stem_engraver"
}
}
\new PianoStaff <<
\new Staff {
\crossStaff { 4 } r r2 |
}
\new Staff {
\clef bass
4 r r2 |
}
>>
--
Knute Snortum
Re: How do I keep space between staves reasonable?
On Fri, Jun 24, 2022 at 7:49 PM Kevin Cole wrote:
>
> I'm sorry I don't know how to create a minimal working example.
>
> I have a rather simple melody with a single staff (vocal). Under the
> staff I have two stanzas of lyrics (the first verse and the chorus).
> After the score, I have a \markup section with additional verses.
>
> When I have just the first verse, everything looks fine. When I add
> the chorus, the spaces where I have \break become ridiculously large,
> as LilyPond tries to anticipate my needs, and forces the \markup
> section to a new page and vertically justifies / fills the page.
>
> On the surface, what I want to do seems deceptively simple.
>
> I've experimented with annotate-spacing and system-system-spacing to
> no avail. The truth is I don't really understand what I'm looking at
> with all the various distances. (In the annotated PDF, it looks like I
> want to shrink "extra dist (system-system-spacing)".)
>
> If I tightened the space between the \break's I think everything would
> remain on one page.
>
> Or, if I can't do that, and it has to force the \markup additional
> verses to a new page, it still seems weird to have so much whitespace
> between \break's. I think it would look better with all the whitespace
> at the end of the score...
>
I'd try a couple of things. system-system-spacing can be confusing.
Sometimes just setting the padding and clearing the other values
helps.
\paper {
system-system-spacing =
#'((basic-distance . 0)
(minimum-distance . 0)
(padding . 4)
(stretchability . 60))
}
Also, have you tried playing with the page breaking algorithm?
\paper {
page-breaking = #ly:minimal-breaking
% or
% page-breaking = #ly:one-page-breaking
}
--
Knute Snortum
Re: simplify the program code
On Fri, Jun 24, 2022 at 1:16 AM Лысов Дмитрий wrote: > > Hello. How to simplify the program code? > Source text (.xlsx): https://disk.yandex.ru/i/QNJiHUoFMqGdWA > Program code (.ly): https://disk.yandex.ru/d/SfNy-mchF9V34g I have a feeling you'll get more responses if you add your ly file as a text attachment, or just paste it in your post. Also, the more specific your question, the more likely you can get help. What exactly is it you want to simplify?
Cross-Staff stems not working
Hi,
consider this code:
\version "2.23.9"
\layout {
\context {
\PianoStaff
\consists "Span_stem_engraver"
}
}
{
\new PianoStaff <<
\new Staff {
4 r r2 |
}
\new Staff {
\clef bass
\crossStaff { 4 } r r2 |
}
>>
}
What am I missing to get the stem to span the staves? I get the
attached output with two separate chords...
Thanks, kind regards,
sb
--
Do not meddle in the affairs of trombonists, for they are subtle and
quick to anger.
Re: How do I keep space between staves reasonable?
Hi Kevin,
Does
\paper {
page-count = 1
}
work for you?
Thanks,
Kieren.
