[LSR] Pipe-band snare drums
Hi All, Here's a new snippet posted by a French user : http://lsr.di.unimi.it/LSR/Item?u=1id=970 who asked for translation help. So I've made it but engish is not my mother language and I'm no percussionist; please be so kind to tell if anything's wrong. I've also tagged it as docs See disussion here : http://lilypond-french-users.1298960.n2.nabble.com/Partitions-de-caisse-claire-ecossaise-tt7582079.html Cheers, Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
many-lyrics separator (slightly OT)
Hello, Considering a choir-setting with many stanzas, the text makes this is a little bit ugly to read, specially for amateur-choirs in stressing situation (concert...). How does engravers eventually make these lyrics more readable? I think of four possibilities: - repeating the stanza # at each system, but I dont want this solution... - make some stanzas in italic - change some stanzas for sans-serif - draw a line-separator every 3-4 stanzas (but how to do that with ly?) Did somebody found any hymn-setting with this kind of typesetting? Thanks in advance, Francois ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Solved: Re: Accidental in parentheses
So easy! Many thanks F 2015-01-05 8:58 GMT-05:00, Brian Barker b.m.bar...@btinternet.com: At 08:14 05/01/2015 -0500, you wrote: is there a way to parenthesize an accidental-only like in the attachment? Yes: you just follow the pitch by a question mark: cis? or cs?. Brian Barker - privately ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Accidental in parenthesize
Hello and Happy New Year to all, is there a way to parentesize an accidental-only like in the attachement? This is \key a-minor (or whatever key that doesnt contain a c-sharp) and should give a notice that the last repeat of refrain CAN be c-sharp (picard third). Thanks in advance, Francois ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
moving the ottoava bracket, but not at the very beginning
Dear community,
I would like to move the ottava-bracket a bit upwards.
Not at the beginning but at the 2nd bar.
Is there a way to do this?
\version 2.18.2
Music = \relative d''' {
\ottava #1
d8 e f e d4 c \break
d'8( e b' e, d2)
}
\new Staff \Music
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: many-lyrics separator (slightly OT)
On 2015-01-05 16:42, Alicuota618 wrote:
Dear Alexander,
About poem, yes, I agree, but spanish songs translators generally dont
care about original rythm (in other words, they dont do the job right
- but the songs are known this way) and there are songs with different
rythm from stanza to stanza too. So this is better to have the text
under music, at least in this case, I suppose.
I see. That's a fair exception...
How do you:
- set stanza # repeating at each new system?
- draw a line-separator between lyrics
Sorry, I think I can help with neither of those. I've got almost no
idea at all about the second - except that you could add a special staff
with no symbols and only one staff line, but that will look awful, I guess.
Maybe something like an artificial stanza containing
{ \markup \null __ %{ many %} _ \markup \null }?
But this looks quite cumbersome to use, and needs tweaking for the
vertical distances, and probably also some horizontal shifting of the
first and last empty markups...
For the first, StanzaNumber supports the item-interface, but unfortunately
\override StanzaNumber.break-visibility = #begin-of-line-visible
does not work as expected; probably because the syllable is below the
first note, which is not quite the first element in a line. My idea was
to have a function which adds the stanza number to /each/ syllable of a
stanza and use it with begin-of-line-visible to kill all but the first
occurence per line. Perhaps an after-line-breaking callback inspecting
the Y-parent of a LyricText element might work instead, but that's more
than what I can test right now, sorry.
Best,
Alexander
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: many-lyrics separator (slightly OT)
Francois, Francois Planiol wrote How do you: - set stanza # repeating at each new system? I'm not aware of any automagic way of doing it (but that doesn't mean it can't be done, of course :), so in the mean time, simply add the \set stanza = # wherever you want it to appear! It's that easy! You might want to add it once you know where the line breaks are, though, or you could get stanza numbers in the middle of a system :) May be a hassle, but it works without that much effort. Francois Planiol wrote - draw a line-separator between lyrics There is a markup function called \draw-hline, but I couldn't figure out how to put it in-between the lyrics. By default, it extends the entire line-length, but that can be customized. Here's the documentation for it: http://www.lilypond.org/doc/v2.19/Documentation/notation/graphic#index-_005cdraw_002dhline http://www.lilypond.org/doc/v2.19/Documentation/notation/graphic#index-_005cdraw_002dhline HTH, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/many-lyrics-separator-slightly-OT-tp170129p170140.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: many-lyrics separator (slightly OT)
Hi Francois, I prefer to simply repeat the music: http://yen-hansen.ca/hymns/mlh03.pdf Improved readability that often doesn't even cost extra paper. Regards, Mogens On 2015-01-05, at 6:03, Alicuota618 alicuota...@gmail.com wrote: Hello, Considering a choir-setting with many stanzas, the text makes this is a little bit ugly to read, specially for amateur-choirs in stressing situation (concert...). How does engravers eventually make these lyrics more readable? I think of four possibilities: - repeating the stanza # at each system, but I dont want this solution... - make some stanzas in italic - change some stanzas for sans-serif - draw a line-separator every 3-4 stanzas (but how to do that with ly?) Did somebody found any hymn-setting with this kind of typesetting? Thanks in advance, Francois manyStanzas.jpg ___ 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: moving the ottoava bracket, but not at the very beginning
Hi Stefan,
On Mon, Jan 5, 2015 at 10:48 AM, Stefan Thomas kontrapunktste...@gmail.com
wrote:
Dear community,
I would like to move the ottava-bracket a bit upwards.
Not at the beginning but at the 2nd bar.
Is there a way to do this?
\version 2.18.2
Try \alterBroken:
Music = \relative d''' {
\alterBroken padding #'(1 3) Staff.OttavaBracket
\ottava #1
d8 e f e d4 c \break
d'8( e b' e, d2)
}
\new Staff \Music
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
REQUEST: #'omit and #'include options for \repeat unfold?
Hello all!
I’m just wondering whether it might be easy — and ultimately desireable — to
have a built-in method of choosing which grobs get repeated and/or omitted
during an unfold \repeat expression.
For example, in a string piece I’m currently writing, I have
\repeat unfold 2 { b8( d') b8( d') b8\downbow d'--(\upbow a--) }
I’d like the bowing to show up only on the first repeat, so it would be great
to have something like
\set repeatOmitInterfaces = #’(text-script-interface)
Another oft-encountered use case would be
\repeat unfold N { a4\pp a a a }
for which one currently must write
a4\pp a a a \repeat unfold N-1 { a4 a a a }
Note that I know of the “create a variable with tagged content” option, and
while it certainly has its place, it’s not nearly as user-friendly as the one
I’m suggesting here.
Cheers,
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
Re: REQUEST: #'omit and #'include options for \repeat unfold?
On Mon, 5 Jan 2015 17:19:47 -0500
Kieren MacMillan kieren_macmil...@sympatico.ca wrote:
Another oft-encountered use case would be
\repeat unfold N { a4\pp a a a }
for which one currently must write
a4\pp a a a \repeat unfold N-1 { a4 a a a }
\repeat unfold N { \atfirstrepeat{a\pp} \atsecondrepeat{a\ff} a a a }
\repeat unfold N { \atrepeat{{a\pp}{a\ff}} a a a }
I think these should be relatively easy to implement in scheme,
provided you can examine the value of the current repeat counter.
-- Johan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: many-lyrics separator (slightly OT)
Anyway, 2.18.0 didnt like it. And adapt this chinese thing (scheme) is still for me not an option. So I suppose its time to upgrade... Thanks to all, Francois 2015-01-05 17:19 GMT-05:00, David Nalesnik david.nales...@gmail.com: On Mon, Jan 5, 2015 at 4:08 PM, David Nalesnik david.nales...@gmail.com wrote: I've adapted this to create the divider. A bit cleaner--overrides moved to grob definition. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: many-lyrics separator (slightly OT)
Hi Francois, On Mon, Jan 5, 2015 at 4:46 PM, Alicuota618 alicuota...@gmail.com wrote: Anyway, 2.18.0 didnt like it. And adapt this chinese thing (scheme) is still for me not an option. So I suppose its time to upgrade... The change I mentioned above should be sufficient to make this work with 2.18: Notice in the comments to 'add-grob-definition' near the top of the file that there is a change you need to make for versions 2.19.13 or before. Best, david ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: many-lyrics separator (slightly OT)
Hi,
On Mon, Jan 5, 2015 at 10:50 AM, tisimst tisimst.lilyp...@gmail.com wrote:
Francois,
Francois Planiol wrote
How do you:
- set stanza # repeating at each new system?
I'm not aware of any automagic way of doing it (but that doesn't mean it
can't be done, of course :), so in the mean time, simply add the \set
stanza = # wherever you want it to appear! It's that easy! You might want
to add it once you know where the line breaks are, though, or you could get
stanza numbers in the middle of a system :) May be a hassle, but it works
without that much effort.
Unfortunately, the attached won't work properly when repeating the stanza
number like this. I'll fiddle around with it, but first things first :)
Francois Planiol wrote
- draw a line-separator between lyrics
There is an old thread which describes how to adapt input/regression/
scheme-text-spanner.ly to create intelligent underlining of lyrics:
http://www.mail-archive.com/lilypond-user%40gnu.org/msg60732.html
I've adapted this to create the divider.
Notice in the comments to add-grob-definition near the top of the file
that there is a change you need to make for versions 2.19.13 or before.
(Depending on how old the version you're using, there may be other changes
needed.)
Hope this is helpful!
--David
\version 2.19.15
\header {
tagline = ##f
}
#(define (add-grob-definition grob-name grob-entry)
(let* ((meta-entry (assoc-get 'meta grob-entry))
(class(assoc-get 'class meta-entry))
(ifaces-entry (assoc-get 'interfaces meta-entry)))
; if version is 2.19.13 or before, replace ly:grob-properties?
; in the following line with list?
(set-object-property! grob-name 'translation-type? ly:grob-properties?)
(set-object-property! grob-name 'is-grob? #t)
(set! ifaces-entry (append (case class
((Item) '(item-interface))
((Spanner) '(spanner-interface))
((Paper_column) '((item-interface
paper-column-interface)))
((System) '((system-interface
spanner-interface)))
(else '(unknown-interface)))
ifaces-entry))
(set! ifaces-entry (uniq-list (sort ifaces-entry symbol?)))
(set! ifaces-entry (cons 'grob-interface ifaces-entry))
(set! meta-entry (assoc-set! meta-entry 'name grob-name))
(set! meta-entry (assoc-set! meta-entry 'interfaces
ifaces-entry))
(set! grob-entry (assoc-set! grob-entry 'meta meta-entry))
(set! all-grob-descriptions
(cons (cons grob-name grob-entry)
all-grob-descriptions
#(add-grob-definition
'LyricSeparator
`(
(bound-details . ((left . ((Y . 0)
(padding . 0.25)
(attach-dir . ,LEFT)
))
(left-broken . ((end-on-note . #t)))
(right . ((Y . 0)
(padding . 0.25)
))
))
(dash-fraction . 0.2)
(dash-period . 3.0)
(direction . ,UP)
(font-shape . italic)
(left-bound-info . ,ly:line-spanner::calc-left-bound-info)
(outside-staff-priority . 350)
(right-bound-info . ,ly:line-spanner::calc-right-bound-info)
(staff-padding . 0.8)
(stencil . ,ly:line-spanner::print)
(style . dashed-line)
(meta . ((class . Spanner)
(interfaces . (font-interface
line-interface
line-spanner-interface
outside-staff-interface
side-position-interface))
#(define (add-bound-item spanner item)
(if (null? (ly:spanner-bound spanner LEFT))
(ly:spanner-set-bound! spanner LEFT item)
(ly:spanner-set-bound! spanner RIGHT item)))
#(define (axis-offset-symbol axis)
(if (eq? axis X) 'X-offset 'Y-offset))
#(define (set-axis! grob axis)
(if (not (number? (ly:grob-property grob 'side-axis)))
(begin
(set! (ly:grob-property grob 'side-axis) axis)
(ly:grob-chain-callback
grob
(if (eq? axis X)
ly:side-position-interface::x-aligned-side
side-position-interface::y-aligned-side)
(axis-offset-symbol axis)
LyricSeparatorEngraver =
#(lambda (context)
(let ((span '()))
(make-engraver
(acknowledgers
((stanza-number-interface engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'lyric-bits grob)
(ly:spanner-set-bound! span LEFT grob
((lyric-syllable-interface engraver grob source-engraver)
(if
Re: many-lyrics separator (slightly OT)
On Mon, Jan 5, 2015 at 4:08 PM, David Nalesnik david.nales...@gmail.com
wrote:
I've adapted this to create the divider.
A bit cleaner--overrides moved to grob definition.
\version 2.19.15
\header {
tagline = ##f
}
#(define (add-grob-definition grob-name grob-entry)
(let* ((meta-entry (assoc-get 'meta grob-entry))
(class(assoc-get 'class meta-entry))
(ifaces-entry (assoc-get 'interfaces meta-entry)))
; if version is 2.19.13 or before, replace ly:grob-properties?
; in the following line with list?
(set-object-property! grob-name 'translation-type? ly:grob-properties?)
(set-object-property! grob-name 'is-grob? #t)
(set! ifaces-entry (append (case class
((Item) '(item-interface))
((Spanner) '(spanner-interface))
((Paper_column) '((item-interface
paper-column-interface)))
((System) '((system-interface
spanner-interface)))
(else '(unknown-interface)))
ifaces-entry))
(set! ifaces-entry (uniq-list (sort ifaces-entry symbol?)))
(set! ifaces-entry (cons 'grob-interface ifaces-entry))
(set! meta-entry (assoc-set! meta-entry 'name grob-name))
(set! meta-entry (assoc-set! meta-entry 'interfaces
ifaces-entry))
(set! grob-entry (assoc-set! grob-entry 'meta meta-entry))
(set! all-grob-descriptions
(cons (cons grob-name grob-entry)
all-grob-descriptions
#(add-grob-definition
'LyricSeparator
`(
(bound-details . ((left . ((Y . 0)
(padding . 0)
(attach-dir . ,LEFT)
))
(right . ((Y . 0)
(padding . 0)
(attach-dir . ,RIGHT)
))
))
(dash-fraction . 0.2)
(dash-period . 3.0)
(direction . ,DOWN)
(font-shape . italic)
(left-bound-info . ,ly:line-spanner::calc-left-bound-info)
;(outside-staff-priority . 350)
(right-bound-info . ,ly:line-spanner::calc-right-bound-info)
(staff-padding . 0.8)
(stencil . ,ly:line-spanner::print)
(style . line)
(meta . ((class . Spanner)
(interfaces . (font-interface
line-interface
line-spanner-interface
outside-staff-interface
side-position-interface))
#(define (add-bound-item spanner item)
(if (null? (ly:spanner-bound spanner LEFT))
(ly:spanner-set-bound! spanner LEFT item)
(ly:spanner-set-bound! spanner RIGHT item)))
#(define (axis-offset-symbol axis)
(if (eq? axis X) 'X-offset 'Y-offset))
#(define (set-axis! grob axis)
(if (not (number? (ly:grob-property grob 'side-axis)))
(begin
(set! (ly:grob-property grob 'side-axis) axis)
(ly:grob-chain-callback
grob
(if (eq? axis X)
ly:side-position-interface::x-aligned-side
side-position-interface::y-aligned-side)
(axis-offset-symbol axis)
LyricSeparatorEngraver =
#(lambda (context)
(let ((span '()))
(make-engraver
(acknowledgers
((stanza-number-interface engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'lyric-bits grob)
(ly:spanner-set-bound! span LEFT grob
((lyric-syllable-interface engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'lyric-bits grob)
(add-bound-item span grob)
((process-music trans)
(if (not (ly:spanner? span))
(let ((ccc (ly:context-property context 'currentCommandColumn)))
(set! span (ly:engraver-make-grob trans 'LyricSeparator ccc))
(set-axis! span Y
((finalize trans)
(set! span '())
\score {
\new Staff
\new Voice = melody {
\time 3/4
g'2 g'4
\break
e'2 a'4
g'2. e'
}
\new Lyrics \lyricsto melody{
\set stanza = #1.
Na na na na na na
}
\new Lyrics \lyricsto melody{
\set stanza = #2.
Na na na na na na
}
\new Lyrics \with {
\consists \LyricSeparatorEngraver
% the following line controls space above and below
\override LyricSeparator #'Y-extent = #'(-1 . 1)
}
\lyricsto melody {
\set stanza = #3.
Na na na na na naaah
}
\new Lyrics \lyricsto melody{
\set stanza = #4.
Na na na na na na
}
\new Lyrics
Re: many-lyrics separator (slightly OT)
On 6 January 2015 at 02:57, Mogens Lemvig Hansen mog...@kayju.com wrote: Hi Francois, I prefer to simply repeat the music: http://yen-hansen.ca/hymns/mlh03.pdf Improved readability that often doesn't even cost extra paper. Regards, Mogens I agree. I think extra paper is “cheaper” than performer-stress. Vaughan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Typesetting chord symbols
Date: Mon, 5 Jan 2015 02:09:27 + From: Carl Sorensen c_soren...@byu.edu To: Thomas Morley thomasmorle...@gmail.com Subject: Re: Typesetting chord symbols On 12/29/14 12:42 PM, Thomas Morley thomasmorle...@gmail.com wrote: I'm thinking about a major revision of our chord-naming-procedures for quite a while. Something at the lines of: -Don't do any formating in basic functions/definitions -Store all data in lists -As _last_ step write a formatter Carl, what do you think? I'm glad that effort is going into chord symbols! I'm no Carl. But here are some observations I hope might be useful. As a starter, we could have things like the following (taken from Brandt and Roemer): I admit to not being familiar with this seminal work. I wonder how much it reflects common practice? In any case, I am simply going to speak from my own experience writing and reading chord charts. root A root like Ab will be constructed out of more than one font: the A from a text font, and the flat from a music font. As such, I can imagine wanting to be able to specify the relative size and alignment (both horizontal and vertical for both parts of the rootl, as well as right padding before what comes next. ( I've also found that, when transposing chord charts I often need to tweak them so that, for example, ii-V-I cadences all have the same sharp/flat enharmonicity. I don't have a well-formed request at the moment, but just throwing out the idea that it might be fruitful to consider transposition not just of single notes (chord roots), but of sequences of chords. ) mode (major or minor)? I would argue that the basic types of chords represented by chord symbols might include: major minor dominant diminished augmented half-diminished Of course this list could get arbitrarily long. But my motivation for listing these, and not others, is threefold. 1) These are all diatonic 7th chords--at least, if you count the harmonic minor scale as diatonic. ( On this basis, you could also say that minor with a major 7 is also diatonic. Except no one uses non-compound symbols for that chord, so it does not add uniquely to the chord symbol lexicon. ) 2) For each of these chords types, there are at least 2 common styles for notating them. Some of these styles follow patterns, and could be grouped as such. It might make sense to offer configuration that let you choose a preferred style, which applies for all chord types for which your style defines a treatement. Since not every style has distinct symbols for each of these chord types, ideally there could be a cascade to resolve treatments that are not in your preferred style. 3) I find that in practical use, it is far more important that the the chord type be easier to parse visually than extensions and alterations. in practical terms, this means that I like to format the 7 for a dominant chord larger than any extensions (like b9, #9). Similarly, the desired formatting of the symbols or letters that represent that chord type may generally be different than either the size/alignment of either the root, or the extensions. Therefore, I would suggest we think in terms of chord type rather than just mode to describe what goes in between the root and the extensions. Here are the categories of chord symbol treatment I am thinking of: symbols: triangle, dash, seven, circle, plus, empty set three-letters: maj, min, dim, aug single letters: M, m minimal: nothing for major, treat everything that isn't major or minor as a dominant with extensions: 7 #5 for augmented, m7b5 for half-diminished added-bass Does this refer to slash chords? modifiers (maybe a list -- I.e. sharp9, flat5) There should be a difference between considering modifiers in chord definitions versus symbolic representation. In some cases, you can't spell a chord without using modifiers (like a 7 b9 #9) . Whereas in other cases, use of modifiers is a stylistic choice of notating a chord using modifiers rather than more compact symbols. For example, writing m7b5 and 7+5 rather than half-diminished or aug7, where the modified 5ths might be called out as an extension, or not, depending on the choice of chord symbol style. polychord Not sure how this differs in notation from a slash chord, except that you have two full chords notated, rather than a chord and a bass note. Probably has implications for how lilypond internally represents chords as a group of notes, which I have not thought about. omissions I have literally never seen a chord symbol (in actual musical context) that refer to omissions. I'm sure some people would actually write chord symbols with omissions (rather than using things like add 9). If so, more power to them. But from my standpoint, this does not fall under core chord symbol practice. I realize lilypond lets you define chords using omissions. And you can certainly conceive of chords in that way. But I think that is more of a
Re: REQUEST: #'omit and #'include options for \repeat unfold?
Kieren MacMillan kieren_macmillan at sympatico.ca writes:
I’m just wondering whether it might be easy — and ultimately desireable —
to have a built-in method of
choosing which grobs get repeated and/or omitted during an unfold \repeat
expression.
Another oft-encountered use case would be
\repeat unfold N { a4\pp a a a }
Until somebody implements the requested options, we have to use parallel
music threads, one with repeated stuff, the other with the non-repeated
\new Staff \transpose c c'
\repeat unfold 16 { a4 b f g }
{ s4\pp\ s2 s4 s2\mp }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
controlling number of bars in a line
I'm feeling really stupid because I can't find this information (and I know it's there) in the manuals either online or in the pdfs. basically just want to hold the bars to 6 per line and yes I know I can do this manually but would like to see the appearance if done automatically. Thanks in advance I'm sure this is easily found but I couldn't version 2.18.2 Jay -- Thanks for reading blogs at https://learnivore.com/users/music# www.soundand.com www.themaptheopera.com Jay ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidental in parenthesize
This may help: http://lsr.di.unimi.it/LSR/Item?id=155 Knute Snortum (via Gmail) On Mon, Jan 5, 2015 at 5:14 AM, Alicuota618 alicuota...@gmail.com wrote: Hello and Happy New Year to all, is there a way to parentesize an accidental-only like in the attachement? This is \key a-minor (or whatever key that doesnt contain a c-sharp) and should give a notice that the last repeat of refrain CAN be c-sharp (picard third). Thanks in advance, Francois ___ 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: many-lyrics separator (slightly OT)
Dear Alexander, About poem, yes, I agree, but spanish songs translators generally dont care about original rythm (in other words, they dont do the job right - but the songs are known this way) and there are songs with different rythm from stanza to stanza too. So this is better to have the text under music, at least in this case, I suppose. How do you: - set stanza # repeating at each new system? - draw a line-separator between lyrics Thanks again F 2015-01-05 10:18 GMT-05:00, Alexander Kobel n...@a-kobel.de: On 2015-01-05 15:03, Alicuota618 wrote: Hello, Considering a choir-setting with many stanzas, the text makes this is a little bit ugly to read, specially for amateur-choirs in stressing situation (concert...). How does engravers eventually make these lyrics more readable? I think of four possibilities: - repeating the stanza # at each system, but I dont want this solution... - make some stanzas in italic - change some stanzas for sans-serif - draw a line-separator every 3-4 stanzas (but how to do that with ly?) Did somebody found any hymn-setting with this kind of typesetting? Hi, I've never seen option 3 (sans-serif), but all the others. The one I like most is 4, using a little bit of whitespace (instead of a rule-/line-separator) after three stanzas. This can easily be achieved by overriding nonstaff-nonstaff-spacing.minimum-distance for the last stanza of each such group. Option 1 can help in addition, in particular if for some reason only some of the stanzas are sung. (Happens more often than not for those pieces in churches here.) Italics I prefer if text is given in several languages. If you go for readability, however... As a singer, I prefer if additional stanzas are written after the score, like a poem, and only = 3 are printed between the staves. More than 4 stanzas (at most, and only if there is no fifth one) are too difficult for me to catch easily. In particular, if you have a usual SATB setting with = 2 staves, the lower voices notoriously have trouble with large distance between notes and first stanza. OTOH, if the singers get the melody after three stanzas, it suffices to have them as a poem (in particular if you can avoid page turns in between). If they don't get the melody, they have to rehearse the piece anyway to coordinate lyrics even if you print eleven stanzas below the notes, and once they rehearsed, the poem will be enough again. Just my two pence... HTH, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: many-lyrics separator (slightly OT)
On 2015-01-05 15:03, Alicuota618 wrote: Hello, Considering a choir-setting with many stanzas, the text makes this is a little bit ugly to read, specially for amateur-choirs in stressing situation (concert...). How does engravers eventually make these lyrics more readable? I think of four possibilities: - repeating the stanza # at each system, but I dont want this solution... - make some stanzas in italic - change some stanzas for sans-serif - draw a line-separator every 3-4 stanzas (but how to do that with ly?) Did somebody found any hymn-setting with this kind of typesetting? Hi, I've never seen option 3 (sans-serif), but all the others. The one I like most is 4, using a little bit of whitespace (instead of a rule-/line-separator) after three stanzas. This can easily be achieved by overriding nonstaff-nonstaff-spacing.minimum-distance for the last stanza of each such group. Option 1 can help in addition, in particular if for some reason only some of the stanzas are sung. (Happens more often than not for those pieces in churches here.) Italics I prefer if text is given in several languages. If you go for readability, however... As a singer, I prefer if additional stanzas are written after the score, like a poem, and only = 3 are printed between the staves. More than 4 stanzas (at most, and only if there is no fifth one) are too difficult for me to catch easily. In particular, if you have a usual SATB setting with = 2 staves, the lower voices notoriously have trouble with large distance between notes and first stanza. OTOH, if the singers get the melody after three stanzas, it suffices to have them as a poem (in particular if you can avoid page turns in between). If they don't get the melody, they have to rehearse the piece anyway to coordinate lyrics even if you print eleven stanzas below the notes, and once they rehearsed, the poem will be enough again. Just my two pence... HTH, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: controlling number of bars in a line
Have a look at: http://lsr.di.unimi.it/LSR/Item?id=838 Jim On Mon, Jan 05, 2015 at 01:39:46PM -0700, Jay Hamilton wrote: I'm feeling really stupid because I can't find this information (and I know it's there) in the manuals either online or in the pdfs. basically just want to hold the bars to 6 per line and yes I know I can do this manually but would like to see the appearance if done automatically. Thanks in advance I'm sure this is easily found but I couldn't version 2.18.2 Jay -- Thanks for reading blogs at https://learnivore.com/users/music# www.soundand.com www.themaptheopera.com Jay ___ 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
