Re: 2.14.2 vertical spacing ungrouped staves...
Hi Jim,
you should address the correct context. Try:
\version "2.14.2"
\paper {
% annotate-spacing = ##t
}
Rhythms = \relative c' { r4 a4 r4 a8 a8 ~ a2 r \break r4 a4 r4 a8 a8 ~ a2 r
}
Melody = \relative c'' { g4 c a f ~ f1 \break g4 c a f ~ f1}
chrds = \chordmode { s4 a s4 b8 c8 a2 s s4 a s4 b8 c8 a2 s }
\score {
<<
\new ChordNames \chrds
%
\new RhythmicStaff \with { \override VerticalAxisGroup
#'staff-staff-spacing =
#'((basic-distance . 0)
(minimum-distance . 0)
(padding . 2))
\remove Staff_symbol_engraver
}
{
\set fontSize = #-7
\override StaffSymbol #'staff-space = #(magstep -3)
\override Staff.BarLine #'stencil = ##f
\override Staff.TimeSignature #'transparent = ##t
\stemUp
\override NoteHead #'style = #'slash
\Rhythms
}
\new Staff {
\key f \major
\clef treble
\time 4/4
\Melody
}
>>
\layout {
indent=0
\context {
\Score% !
\override VerticalAxisGroup #'staff-staff-spacing =
#'((basic-distance . 0)
(minimum-distance . 0)
(padding . 0))
} % context
} % layout
} % score
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.14.2 vertical spacing ungrouped staves...
Hi again, I forgot to add: My snippet shows two possibilities, choose one. Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.14.2 vertical spacing ungrouped staves...
On Sat, Nov 12, 2011 at 6:41 AM, Thomas Morley < thomasmorle...@googlemail.com> wrote: > Hi again, > > I forgot to add: > > My snippet shows two possibilities, choose one. > > Harm > Greetings, Harm - I just noticed, at the end of your snippet, the comments on the closing parentheses : } % context } % layout } % score Maybe I've just been thick, but I haven't noticed anyone do that before. What a wonderful idea! I think I may use that. Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
2.15.18, Mac x86
(ref Bug 1943) Get Info on v. 2.15.18 reports v. 2.14-2 after expansion. It still does not open under OS 10.5.8, x86. Stan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
2.15.18 on Mac ppc
Ref bug 1943 On Mac OS 10.5.8 ppc (PowerBook G4), v.2.15.18 appears to be fully functional and reports the correct version number under "Get Info." Files compile and render as expected. Stan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Changing beam stem length
I have collision between a stem and a note. I would like to change the
length of the beamed stem. Unfortunately
\override Stem #'length = #0.5
only works for unbeamed stems. Here is the example to tweak:
\relative c, {
\key as \major
\time 3/8
\clef bass
<< { des'8 } \\
{ as8[ ges16] } \\
{ \stemDown bes,8. \stemNeutral } >>
r16 8 |
}
I would like to shorted the stem of the as.
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.14.2 vertical spacing ungrouped staves...
On Sat, Nov 12, 2011 at 12:35:00PM +0100, Thomas Morley wrote:
> Hi Jim,
>
> you should address the correct context. Try:
Excellent result, Thomas. Thank you.
Jim
\version "2.14.2"
\paper {
% annotate-spacing = ##t
}
#(set-global-staff-size 25)
Changes = \chordmode { s4 g:m s4 f8 d8:m7 d1:m7 }
Rhythms = \relative c' { r4 a4 r4 a8 a8 ~ a2 r }
Melody = \relative c'' { g4 c a f ~ f1 }
\score {
<<
\new ChordNames {
\set chordChanges = ##t
\Changes
}
\new RhythmicStaff \with {
\override StaffSymbol #'line-count = #0
\override VerticalAxisGroup
#'staff-staff-spacing =
#'((basic-distance . 0)
(minimum-distance . 0)
(padding . 0))
} {
\set fontSize = #-7
\override StaffSymbol #'staff-space = #(magstep -3)
\override Staff.BarLine #'stencil = ##f
\override Staff.TimeSignature #'transparent = ##t
\stemUp
\override NoteHead #'style = #'slash
\Rhythms
}
\new Staff {
\key f \major
\clef treble
\time 4/4
\Melody
}
>>
\layout {
indent=0
} % layout
} % score
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Changing beam stem length
I have collision between a stem and a note. I would like to change the
length of the beamed stem. Unfortunately
\override Stem #'length = #0.5
only works for unbeamed stems. Here is the example to tweak:
\relative c, {
\key as \major
\time 3/8
\clef bass
<< { des'8 } \\
{ as8[ ges16] } \\
{ \stemDown bes,8. \stemNeutral } >>
r16 8 |
}
I would like to shorted the stem of the as.
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Changing beam stem length
Hi Helge,
2011/11/12 Helge Kruse
> I have collision between a stem and a note. I would like to change the
> length of the beamed stem. Unfortunately
>
> \override Stem #'length = #0.5
>
> only works for unbeamed stems. Here is the example to tweak:
>
> \relative c, {
>
> \key as \major
> \time 3/8
> \clef bass
>
> << { des'8 } \\
>{ as8[ ges16] } \\
>{ \stemDown bes,8. \stemNeutral } >>
> r16 8 |
> }
>
> I would like to shorted the stem of the as.
>
> Helge
>
try:
\relative c, {
\key as \major
\time 3/8
\clef bass
<< { des'8 } \\
{ \override Beam #'positions = #'(-3.5 . -5) as8[ ges16] } \\
{ \stemDown bes,8. \stemNeutral } >>
r16 8 |
}
But I'd prefer the following:
\relative c, {
\key as \major
\time 3/8
\clef bass
<< { des'8 } \\
{ as8[ ges16] } \\
{ \stemDown \override NoteColumn #'force-hshift = #0.8 bes,8.
\stemNeutral } >>
r16 8 |
}
Please, always post your version-number!
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Problem with music function in 2.15.18
There's a music function I use in virtually every guitar score I've done
with Lilypond, to move glissandi that I use to indicate that a finger
should be kept on a string when moving frets. I just downloaded and
installed 2.15.18 (Linux amd64 version running on Ubuntu 10.04), and the
parameters to the function no longer seem to be being recognised as the
correct type. The short example below shows the problem.
\version "2.15.18"
\language "english"
guide = #(define-music-function (parser location padleft padright shift
missacc) (number? number? pair? boolean?) #{
\once \override Glissando #'bound-details #'left #'padding = #$padleft
\once \override Glissando #'bound-details #'right #'padding =
#$padright
\once \override Glissando #'extra-offset = #$shift
\once \override Glissando #'bound-details #'right
#'end-on-accidental = #$missacc
\once \override Glissando #'breakable = ##t
\once \override Glissando #'after-line-breaking = ##t
#})
\relative c' { \guide #1 #1 #'(0 . 1.4) ##f \glissando }
Trying to build this gives the following in the log:
==
Processing `/home/nick/lilypond/examples/test.ly'
Parsing...
:2:91: error: GUILE signaled an error for the expression
beginning here
\once \override Glissando #(quote bound-details) #(quote left)
#(quote padding) = #
$padleft
:3:92: error: GUILE signaled an error for the expression
beginning here
\once \override Glissando #(quote bound-details) #(quote right)
#(quote padding) = #
$padright
:4:59: error: GUILE signaled an error for the expression
beginning here
\once \override Glissando #(quote extra-offset) = #
$shift
:5:102: error: GUILE signaled an error for the expression
beginning here
\once \override Glissando #(quote bound-details) #(quote right)
#(quote end-on-accidental) = #
$missacc
/home/nick/lilypond/examples/test.ly:14:45: error: error in #{ ... #}
\relative c' { c4 c \guide #1 #1 #'(0 . 1.4)
##f \glissando }
Interpreting music...
warning: type check for `extra-offset' failed; value `#'
must be of type `pair of numbers'
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
Unbound variable: $padleft
Unbound variable: $padright
Unbound variable: $shift
Unbound variable: $missacc
fatal error: failed files: "/home/nick/lilypond/examples/test.ly"
=
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
chord/rhythm/melody staves: putting it all together
Thanks again to those who helped with earlier questions.
This example snippet of some simple changes with implied rhythms
and complex changes with explicit rhythms looks great. The vertical
spacing of the chords and rhythm marks is tight but still legible:
\version "2.14.2"
SimpleChanges = \chordmode { g2:m f }
SimpleMelody = \relative c'' { g4 c a f }
ComplexChanges = \chordmode { g4:7 g:m7 f:maj7 f8:7 d8:m7 ~ d1:m7 }
ComplexRhythms = { g4 g f f8 d8 ~ d1 }
ComplexMelody = \relative c'' { g4 c a f ~ f1 }
\score {
<<
% ChordNames staff begins here.
\new ChordNames {
\key f \major
\repeat unfold 2 \SimpleChanges
<< \new RhythmicStaff \with {
\override NoteHead #'style = #'slash
\override StaffSymbol #'line-count = #0
\override StaffSymbol #'staff-space = #(magstep -3)
\override BarLine #'stencil = ##f
\override TimeSignature #'stencil = ##f
\override KeySignature #'stencil = ##f
\override Clef #'stencil = ##f
explicitKeySignatureVisibility = #end-of-line-invisible
} {
\key f \major
\set fontSize = #-5
\ComplexRhythms
} % end rhythmic staff
\ComplexChanges
>> % end of complex rhythm section
%\MoreSimpleChanges could go here
} % end of ChordNames block
% A melody staff (simultaneous to the chord staff) begins here
% \new Staff {
% \repeat unfold 2 \SimpleMelody
% \ComplexMelody
%%\MoreSimpleMelody could go here
% } % end of melody staff
>>
}
Now I'm ready to add the melody staff at the bottom.
But when I uncomment the melody section, the melody staff gets
inserted not at the bottom, but in the middle. The entire
ChordNames block is closed before the the melody staff is added
to the score. Why does the newly added melody staff 'split' the
ChordNames section? How do I tell Lily to put the Melody staff
below the ChordNames block, rather than in the middle of it?
Also, the 'ComplexRhythm' section seems redundant. I have
already specified those rhythms in the ComplexChanges section.
But if I reference \ComplexChanges as the music for the rhythm
marks, I get multiple noteheads on the rhythm stems. I presume
this is because the ComplexChanges contains chords, which of
course are polyphonic. Some notes are engraved left of the stem,
others to the right of the stem, so most all of the chords get
pitch-squashed down to one left-note and one right-note. Is
there a way I can tell the RhythmicStaff section to squash each
chord to a single note, so that just the rhythmic content of the
ComplexChanges music is used for the rhythm marks?
Thank you!
Jim
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Attaching markup to high-level objects
As I know the majority of folks here are aware, Lilypond's
typesetting language lends itself to modularization of music, so
that a recurring theme or motif can be defined once as a music
identifier, and then inserted at several places in the layout by
referencing that identifier, possibly with transposition, etc.
I appreciate this very much, because when one finds a typo in a
note or chord, or just a more elegant way of phrasing, a single
change to that music definition will make the correction appear
in all 8 or however many places the music occurs.
However, markup complicates this for me, perhaps because of my
infamiliarity with the variety of markup methods that are
available.
>From all the examples I can recall seeing, markup must be
attached to a low-level object, such as a note or rest, or
in conjunction with a rehearsal mark. However, I get errors when
I try to place two adjacent rehearsal marks, like a "\mark
default" and a Segno at the same location. They can be combined
I guess (except then the auto-sequencing feature of the 'default'
marks is lost isn't it?), but I digress
Again, from my very limited experience, binding markup only to
low-level objects means that if one has arranged their music to
take advantage of the modularization mentioned above, then the
markup must also be identical in all occurences of a particular
music expression. Please correct me if this is wrong, as it is
causing me some consternation.
Suppose my top-level arrangement looks like this:
\vamp \break
\segnoMarkup
\bar "|:"
\repeat volta 2 {
\head
\CodaJumpMarkup \break
} alternative {
{ \firstEnding \bar ":|" \break } % first ending
{ \secondEnding } % second ending
} % repeat/alternative
\bar "|:" \vamp \AdLibThenDSMarkup \bar ":|" \break
\CodaMarkup
\coda
\bar "|."
The intent is to play the vamp, play the head, play the first
ending, repeat the head, play the second ending, repeat the vamp
until cue, DS to the head, and then jump to the Coda (just before
the repeat volta -- essentially a third ending), and out. The
breaks are positioned so that major sections begin at the start
of a line.
The vamp section is repeated, and the first instance requires
no markup. The second time the vamp music is inserted, I'd like
to place markup on the ending repeat symbol to say, "repeat until
cue, then D.S. al Coda."
But I can't find a way to attach markup to a high-level object.
I have not yet even found a way to attach markup to a bar line
(the closing repeat bar would seem the logical choice).
I'd love to find out that Lilypond is able to attach markup to a
music identifier reference, or an arbitrary music expression,
such as:
\bar "|:" \vamp^\markup { \AdLibThenDSMarkup } \bar ":|" \break
or
{ a2 b4 c4 }^\markup \text "Good news!"
Failing that, if there were a way to attach markup to a bar line,
that (plus perhaps an 'extra-offset') would suffice in the majority
of situations I can think of.
Is there such a way to attach markup to a high-level music
expression or a bar line, rather than just a low-level simple
music element, like a note or rest?
Thank you very much indeed.
Jim
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with music function in 2.15.18
On 11/12/11 2:17 PM, "Nick Payne" wrote:
>There's a music function I use in virtually every guitar score I've done
>with Lilypond, to move glissandi that I use to indicate that a finger
>should be kept on a string when moving frets. I just downloaded and
>installed 2.15.18 (Linux amd64 version running on Ubuntu 10.04), and the
>parameters to the function no longer seem to be being recognised as the
>correct type. The short example below shows the problem.
>
>\version "2.15.18"
>
>\language "english"
>
>guide = #(define-music-function (parser location padleft padright shift
>missacc) (number? number? pair? boolean?) #{
> \once \override Glissando #'bound-details #'left #'padding =
>#$padleft
> \once \override Glissando #'bound-details #'right #'padding =
>#$padright
I believe you now use just $padright instead of #$padright
HTH,
Carl
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with music function in 2.15.18
On 13/11/11 13:51, Carl Sorensen wrote:
On 11/12/11 2:17 PM, "Nick Payne" wrote:
There's a music function I use in virtually every guitar score I've done
with Lilypond, to move glissandi that I use to indicate that a finger
should be kept on a string when moving frets. I just downloaded and
installed 2.15.18 (Linux amd64 version running on Ubuntu 10.04), and the
parameters to the function no longer seem to be being recognised as the
correct type. The short example below shows the problem.
\version "2.15.18"
\language "english"
guide = #(define-music-function (parser location padleft padright shift
missacc) (number? number? pair? boolean?) #{
\once \override Glissando #'bound-details #'left #'padding =
#$padleft
\once \override Glissando #'bound-details #'right #'padding =
#$padright
I believe you now use just $padright instead of #$padright
Thanks. I found that I'd forgotten to run convert-ly against the include
file containing this (and other) music functions.
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
