ReReRe: Bug report: measure numbering after repeat with alternative endings
Dear Mats, Bertalan and Graham, Flooded with and surprised by instant reactions, I've given the problem (or is it a bug?) some more thought. Two points of view are possible: 1. The Programmer's view. A measure of music, like any other object in programming, should have a unique number. No ambiguity is logically allowed or even thinkable. So, the first measure of the second piece section should be 18. 2. The Musician's view. Measure 16b (2a volta) is essentially/musically the same as measure 16a (1a volta). Moreover, this particular piece (bwv 1017) has not only a harsichord part but also a violin part. There, there is no distinction between 16a and 16b, and in the separate violon part there is no need to write it out that way at all. Would I indeed follow that choice when coding the violin part, I would end up with a difference in measure numbering which is rather awkward during rehearsals. So, the first measure of the second piece section should be 17 in both parts. Luckily enough, in the users reference I found the possibility to manually influence measure numbering (page 189 section 8.2.4) so to me the discussion has lost its practical relevance. Lilypond's programmers may or may not take one of the two views... Paul de Bruin. _ Ik gebruik de gratis versie van SPAMfighter http://www.spamfighter.com/lnl Wij zijn een gemeenschap van 6 miljoen gebruikers in strijd tegen spam. 214 spam-mails zijn er tot op heden geblokkeerd. De Professionele versie heeft deze voetnoot niet. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug report: measure numbering after repeat with alternativeendings
Mats Bengtsson wrote:
This is another incarnation of Issue 355, which in my opinion is a clear
bug.
However, I'm not equally certain that the bar numbering always is done
the way Paul proposes
and would have to look through my collection of scores to see what is
the most common typesetting
practice.
Does anybody have authoritative information on how the bar numbering
should be done with alternative
endings?
/Mats
Well, it's certainly not authoritative, but since I admire the engraving
practice in the Bärenreiter Urtext editions...
In several piano reductions, they use running measure numbers along the
repeats, and depict both numbers, repeats in parentheses, like this:
(18)
|:---||||
6 (22)
||||||
12 (28) {1. }
|||||---:|
33
{2. }
||||||
39
||||||
I think it's particularly useful to denote the measure number of the
first repeated measure, even if it's in the middle of a line.
Note that the volta bars are counted, too.
This way, each point in time is uniquely identified, which should please
both the programmer's and the conductor's view.
Of course, things get ugly if there is a part repeated more than once; I
haven't spotted such a thing in my Bach scores from Bärenreiter. By the
way, if the whole piece gets repeated, they don't print bar numbers for
each stanza.
Also, one could argue to use the same numbering scheme for D.C., D.S. or
Coda constructions - at least for D.C. and D.S. without jumps in the
end, they don't do that. I don't have an example with a Coda.
On the other hand, more complicated constructions with = 3 repeats
typically appear in more modern popular music, where AFAIK everybody
tends to use the stanza numbers in the rehearsals.
Just my two pence...
Alexander
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
umlaut
not top posting
I am transcribing Schubert's Du bist die Ruh, and have run into a problem with
the umlauts. In both the lyric and in the header, whenever I use an umlaut, the
text stops. In the header, instead of saying Friedrich Rückert, it says
Friedrich R, and in the lyric, instead of O füll es ganz, it says O f es ganz.
\version 2.12.2
\header {
title = Du Bist Die Ruh
composer = Franz Schubert
opus = Op. 59, 3
poet = Friedrich Rückert }
\include english.ly
***
melody = \relative c'' {
\clef treble
\key bf \major
\time 3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
f,8 f8. f16
g4 g8
bf4 a8
bf4.
}
***
text = \lyricmode {
Du bist die Ruh, O füll es ganz,
}
upper = \relative c' {
\clef treble
\key bf \major
\time 3/8
{d16 f d f d f
d g d g d g
g c, g' c, f c
bf'4.} \\
{bf,8 bf8. bf16
bf4.
a
f'16 bf, f' bf, ef bf}
f' bf f'4.
{f f'4.
f f'8 d16[ f d f]} \\
{bf8 a16 g a8
bf s s}
d16 f d f d f
d g d g d g
{bf4 a8
bf4.} \\
{d,16 f d f ef f
d f d f d f}
}
**
lower = \relative c {
\clef bass
\key bf \major
\time 3/8
s4.
s
s
g'4.
{ef'16 bf ef bf d bf
c ef c ef c ef} \\
{f,4.
f}
bf d8 r r
bf8 bf8. bf16
bf4.
d, bf'4 f c'8
bf4.
}
*
\score {
\new Voice = mel { \autoBeamOff \melody }
\new Lyrics \lyricsto mel \text
\new PianoStaff
\new Staff = upper \upper
\new Staff = lower \lower
\layout {
\context { \RemoveEmptyStaffContext }
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: umlaut
Please make sure that your text editor is saving the file using UTF-8
encoding. Then, everything should work without any problems.
/Mats
Quoting orolo kuriboo1...@gmail.com:
not top posting
I am transcribing Schubert's Du bist die Ruh, and have run into a
problem with
the umlauts. In both the lyric and in the header, whenever I use an
umlaut, the
text stops. In the header, instead of saying Friedrich Rückert, it says
Friedrich R, and in the lyric, instead of O füll es ganz, it says O
f es ganz.
\version 2.12.2
\header {
title = Du Bist Die Ruh
composer = Franz Schubert
opus = Op. 59, 3
poet = Friedrich Rückert }
\include english.ly
***
melody = \relative c'' {
\clef treble
\key bf \major
\time 3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
R1*3/8
f,8 f8. f16
g4 g8
bf4 a8
bf4.
}
***
text = \lyricmode {
Du bist die Ruh, O füll es ganz,
}
upper = \relative c' {
\clef treble
\key bf \major
\time 3/8
{d16 f d f d f
d g d g d g
g c, g' c, f c
bf'4.} \\
{bf,8 bf8. bf16
bf4.
a
f'16 bf, f' bf, ef bf}
f' bf f'4.
{f f'4.
f f'8 d16[ f d f]} \\
{bf8 a16 g a8
bf s s}
d16 f d f d f
d g d g d g
{bf4 a8
bf4.} \\
{d,16 f d f ef f
d f d f d f}
}
**
lower = \relative c {
\clef bass
\key bf \major
\time 3/8
s4.
s
s
g'4.
{ef'16 bf ef bf d bf
c ef c ef c ef} \\
{f,4.
f}
bf d8 r r
bf8 bf8. bf16
bf4.
d, bf'4 f c'8
bf4.
}
*
\score {
\new Voice = mel { \autoBeamOff \melody }
\new Lyrics \lyricsto mel \text
\new PianoStaff
\new Staff = upper \upper
\new Staff = lower \lower
\layout {
\context { \RemoveEmptyStaffContext }
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
error message
Hi-- I'm getting the following error message: F:/downloads/LilyPond/usr/share/lilypond/current/ly/init.ly:63:66: error: syntax error, unexpected $end (ly:parser-error parser (_ expected error, but none found with all of my compilations. Could you let me know what's going on, so that Ican fix whatever it is that's bugging this up? Many thanks-- I love LilyPond! Kendra Leonard ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: error message
It's very hard to give a good answer without seeing one of your files, but it's almost certainly some kind of syntax error in your file, such as a missing curly brace or missing double qoute or something similar. If you don't manage to figure it out yourself, send a followup to the lilypond-user list, including a short example file that gives this error message. /Mats Quoting Kendra Leonard caen...@gmail.com: Hi-- I'm getting the following error message: F:/downloads/LilyPond/usr/share/lilypond/current/ly/init.ly:63:66: error: syntax error, unexpected $end (ly:parser-error parser (_ expected error, but none found with all of my compilations. Could you let me know what's going on, so that Ican fix whatever it is that's bugging this up? Many thanks-- I love LilyPond! Kendra Leonard ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: hyphens not working in 2.13
The regression test and the underlying logic of the fix attempt are wrong IMHO , because they do not test the existence of additional lyrics. If the no more lyrics case is problematic, this shouldn't break the case in that there are actually additional lyrics. Anyway, now the extender is prematurely stopped with or without slurred notes or additional lyrics, as the last Karim's example shows. Sorry for the regression. It's possible that there actually are regression tests that show it, but the delta-calculating logic in the tests doesn't deal well with the thin extender lines (which I noted when I submitted the patch). It will be difficult for me to write a patch to fix this right now, as I'm limited to a crappy hotel Internet connection for the next couple of days, but I'll look into a fix if no-one beats me to it. I think the proper solution would be to add a check for the single-underscore case, and avoid completizing the extender if one is found. Chris Snyder Adoro Music Publishing http://www.adoromusicpub.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
