Peculiarities of identifier definitions
Can anybody explain to me what's going on in the following example:
\version 2.11.12
myVoiceThree = #(context-spec-music (make-voice-props-set 2) 'Voice)
\new Staff \new Voice {\voiceOne c' } \new Voice {\myVoiceThree e'}
myFailingVoiceThree = { #(context-spec-music (make-voice-props-set 2)
'Voice) }
\new Staff \new Voice {\voiceOne c' } \new Voice {\myFailingVoiceThree
e'}
If I apply \displayMusic on the second example, the \myFailingVoiceThree
translates into (make-music
'SequentialMusic
'elements
'())
i.e. an empty music expression. To me it looks like a bug or at least a
serious
limitation.
/Mats
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 243 in project lilypond
Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #2 by joeneeman: This is not actually what ragged-right does. What it does is to minimise the sum of quot;badnessquot; weights. I don't remember exactly what the weight is, but it depends on the force that is needed to stretch the line out to the full width. Since one of your lines has lots of small, stiff springs, it will require more force to stretch it to its full width, so lilypond tries to make it as long as possible. If you want a change of behaviour, the easiest way to do it is to change the definition of the weights. But to get exactly what you say would require writing a whole new line-breaking algorithm just for the ragged-right case. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 139 in project lilypond
Issue 139: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 Comment #8 by hanwenn: Actually, the fix got buried because it had other side-effects. I noticed this when trying to add NEWS entries. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Peculiarities of identifier definitions
Mats Bengtsson escreveu:
Can anybody explain to me what's going on in the following example:
\version 2.11.12
myVoiceThree = #(context-spec-music (make-voice-props-set 2) 'Voice)
\new Staff \new Voice {\voiceOne c' } \new Voice {\myVoiceThree e'}
myFailingVoiceThree = { #(context-spec-music (make-voice-props-set 2)
'Voice) }
\new Staff \new Voice {\voiceOne c' } \new Voice {\myFailingVoiceThree
e'}
If I apply \displayMusic on the second example, the \myFailingVoiceThree
translates into (make-music
'SequentialMusic
'elements
'())
i.e. an empty music expression. To me it looks like a bug or at least a
serious
limitation.
you have to ly:export the identifier, otherwise lilypond assumes it's inline
scheme
that can be ignored.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 230 in project lilypond
Issue 230: segfault 2.11.10 http://code.google.com/p/lilypond/issues/detail?id=230 Comment #2 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_13 fixed_2_11_13 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Long StanzaNumber collides with the left vertical line connecting staves
Dear all,
StanzaNumber precedes the lyrics, and extends to the left. If it becomes wide
enough, it crosses the vertical line which connects the staves of a system
(assuming a multi-staff system).
Proper behaviour would probably be to shift the start of the notes and lyrics
to the right, and space the starting matter (clef, timesig, keysig) accordingly.
Preceding a normal one-digit number with a mezzoforte dynamic is wide enough to
cause a collision. The example below has a five-digit stanza number, which is a
bit rare in practice, but otherwise equivalent and simpler.
Regards,
Sietse
Sietse Brouwer
Example code:
\version 2.10.11
\layout { ragged-right = ##t }
verseOne = \lyricmode {
\set stanza = 4.
Ma -- ry Su -- san
}
\score {
\new ChoirStaff
\new Staff = upper {
\new Voice = voiceOne
a'4 b'4 c'4 d'4
}
\new Lyrics \lyricsto voiceOne \verseOne
\new Staff = lower {
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 243 in project lilypond
Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #4 by joeneeman: Maybe I misunderstood the ragged-right stuff in Gourlay_breaker when I rewrote it. In any case, my previous comment wasn't quite correct -- the get the desired behaviour, it should be enough to change - the weighting in simple-spacer so that it only depends on the line width, not the force - the demerits calculation in constrained-breaking so that it chooses the configuration with the lowest maximum force I'll try it this weekend. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 243 in project lilypond
Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #5 by [EMAIL PROTECTED]: I don't really understand your comments Joe. Line breaking algorithms always handles the last word on the line specially, because you don't need to take the space after that word into account when doing justified output. Normally, iirc, each word is assigned two springs. The one is used if the word is last on the line, and the other is used if the word isn't last on line. To do justified output the last-on-line spring is set to zero, and to do leftified text, the not-last-on-line spring is set to zero. Btw, ofcourse my previous statement was simplified. Ofcourse you also look at the other lines, not just the shortest. trying to minimize Sum( [surplus space at the end of line]^3 ) gives something sensible, iirc. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
error in init.ly? (lilypond 2.11.12)
Hello all--
I just downloaded LilyPond 2.11.12 GUB for Linux, convert-ly'ed one of
my recent projects and ran LilyPond on the .ly file, and received this
mysterious-looking (to me) error message--
--- begin quote of error message ---
GNU LilyPond 2.11.12
Processing `blues-in-c-1.ly'
Parsing...
Interpreting music... [8][11]
Preprocessing graphical objects...
/home/xscd/lilypond/usr/bin/../share/lilypond/current/ly/init.ly:37:1:
error: GUILE signaled an error for the expression beginning here
#
(if (or (pair? toplevel-scores) output-empty-score-list)
Wrong type argument in position 1: ()
/home/xscd/lilypond/usr/bin/../share/lilypond/current/ly/init.ly:37:5:
error: syntax error, unexpected '(', expecting '='
#(if
(or (pair? toplevel-scores) output-empty-score-list)
programming error: Parsed object should be dead: static
scm_unused_struct* Prob::mark_smob(scm_unused_struct*)
continuing, cross fingers
programming error: Parsed object should be dead: static
scm_unused_struct* Context_def::mark_smob(scm_unused_struct*)
continuing, cross fingers
error: failed files: blues-in-c-1.ly
--- end quote of error message ---
I have attached the blues-in-c-1.ly file, in case it may be relevant.
-Steve D
% Blues in C 1, work for piano by Stephen C. Doonan, [EMAIL PROTECTED]
\version 2.11.11
% \paper { }
\header {
title = Blues in C 1
composer = \markup \center-align { Stephen C. Doonan \small (1952- ) }
piece = \markup { \bold Andantino ( \tiny \note #4 #0.75 \normalsize
= 85-115 \bold ) }
% Mutopiaproject.org headers
mutopiatitle = Blues in C 1
mutopiacomposer = DoonanSC
mutopiainstrument = Piano
date = 2006/Sep
source = Composer
style = Jazz
copyright = Creative Commons Attribution-ShareAlike 2.5
maintainer = Stephen C. Doonan
maintainerEmail = [EMAIL PROTECTED]
maintainerWeb = http://www.xscd.com/pub/music/;
lastupdated = 2006/September/25
}
rightHand = \relative c'' {
% 1
\key c \major \time 4/4 \clef treble e, g c2.. ees g c8~ |
ees g c~ ees aes c4 ees aes c4 f bes d8~ f bes d4 |
g e'4 e c' \new Voice { \voiceOne c'4. r8 } { \voiceTwo e,8 f g
\oneVoice ees g bes8~ } |
ees g bes4. f a8~ \afterGrace f a2 {bes16[ a]} |
e g2.. \new Voice { \voiceTwo ees8~ |
ees2 aes | }
{ \voiceOne g c8~ |
g c8 aes bes c c d ees f \oneVoice | }
% 7
c g'4 g e' \new Voice { \voiceOne c4. r8 } { \voiceTwo e,8 f g
\oneVoice ees g bes8~ } |
ees g bes4. f a8~ \afterGrace f a2 {bes16[ a]} |
e g2 \new Voice { \voiceOne c'4. r8 } { \voiceTwo e, f g \oneVoice
ees g c8~ } |
ees g c~ ees aes c4 f a d4~ f bes d4 g bes ees8~ |
g bes ees8~ g c ees4 aes c f4~ aes d f4. |
}
leftHand = \relative c, {
% 1
\time 4/4 \key c \major \clef bass c8 g' d' e c g' d e f c'~ |
f c' ees d c bes aes g f |
c g' d' e c g' d e f c'~ |
f c' ees f g d'~ g d'2 |
}
\score {
\new PianoStaff
#(set-accidental-style 'piano-cautionary)
\set PianoStaff.printPartCombineTexts = ##f
\new Staff = up \new Voice = rh \rightHand
\new Staff = down \new Voice = lh \leftHand
%\midi {
%\context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 100 4)
%}
%}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: error in init.ly? (lilypond 2.11.12)
The file compiles fine with version 2.11.10 so there's
something strange going on here.
Normally, these kind of error messages indicate that
you have a syntax error in your file, but since it works
with 2.11.10, that seems unlikely.
By commenting out sections of your file, I could narrow
the problem down to be somewhere in your definition
\rightHand, but I haven't managed to get further.
/Mats
Steve D wrote:
Hello all--
I just downloaded LilyPond 2.11.12 GUB for Linux, convert-ly'ed one of
my recent projects and ran LilyPond on the .ly file, and received this
mysterious-looking (to me) error message--
--- begin quote of error message ---
GNU LilyPond 2.11.12
Processing `blues-in-c-1.ly'
Parsing...
Interpreting music... [8][11]
Preprocessing graphical objects...
/home/xscd/lilypond/usr/bin/../share/lilypond/current/ly/init.ly:37:1:
error: GUILE signaled an error for the expression beginning here
#
(if (or (pair? toplevel-scores) output-empty-score-list)
Wrong type argument in position 1: ()
/home/xscd/lilypond/usr/bin/../share/lilypond/current/ly/init.ly:37:5:
error: syntax error, unexpected '(', expecting '='
#(if
(or (pair? toplevel-scores) output-empty-score-list)
programming error: Parsed object should be dead: static
scm_unused_struct* Prob::mark_smob(scm_unused_struct*)
continuing, cross fingers
programming error: Parsed object should be dead: static
scm_unused_struct* Context_def::mark_smob(scm_unused_struct*)
continuing, cross fingers
error: failed files: blues-in-c-1.ly
--- end quote of error message ---
I have attached the blues-in-c-1.ly file, in case it may be relevant.
-Steve D
% Blues in C 1, work for piano by Stephen C. Doonan, [EMAIL PROTECTED]
\version 2.11.11
% \paper { }
\header {
title = Blues in C 1
composer = \markup \center-align { Stephen C. Doonan \small (1952- ) }
piece = \markup { \bold Andantino ( \tiny \note #4 #0.75 \normalsize = 85-115
\bold ) }
% Mutopiaproject.org headers
mutopiatitle = Blues in C 1
mutopiacomposer = DoonanSC
mutopiainstrument = Piano
date = 2006/Sep
source = Composer
style = Jazz
copyright = Creative Commons Attribution-ShareAlike 2.5
maintainer = Stephen C. Doonan
maintainerEmail = [EMAIL PROTECTED]
maintainerWeb = http://www.xscd.com/pub/music/;
lastupdated = 2006/September/25
}
rightHand = \relative c'' {
% 1
\key c \major \time 4/4 \clef treble e, g c2.. ees g c8~ |
ees g c~ ees aes c4 ees aes c4 f bes d8~ f bes d4 |
g e'4 e c' \new Voice { \voiceOne c'4. r8 } { \voiceTwo e,8 f g \oneVoice
ees g bes8~ } |
ees g bes4. f a8~ \afterGrace f a2 {bes16[ a]} |
e g2.. \new Voice { \voiceTwo ees8~ |
ees2 aes | }
{ \voiceOne g c8~ |
g c8 aes bes c c d ees f \oneVoice | }
% 7
c g'4 g e' \new Voice { \voiceOne c4. r8 } { \voiceTwo e,8 f g \oneVoice ees
g bes8~ } |
ees g bes4. f a8~ \afterGrace f a2 {bes16[ a]} |
e g2 \new Voice { \voiceOne c'4. r8 } { \voiceTwo e, f g \oneVoice ees g
c8~ } |
ees g c~ ees aes c4 f a d4~ f bes d4 g bes ees8~ |
g bes ees8~ g c ees4 aes c f4~ aes d f4. |
}
leftHand = \relative c, {
% 1
\time 4/4 \key c \major \clef bass c8 g' d' e c g' d e f c'~ |
f c' ees d c bes aes g f |
c g' d' e c g' d e f c'~ |
f c' ees f g d'~ g d'2 |
}
\score {
\new PianoStaff
#(set-accidental-style 'piano-cautionary)
\set PianoStaff.printPartCombineTexts = ##f
\new Staff = up \new Voice = rh \rightHand
\new Staff = down \new Voice = lh \leftHand
%\midi {
%\context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 100 4)
%}
%}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 243 in project lilypond
Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #6 by joeneeman: OK, if you don't want to maximise the shortest line then you can disregard my second point. The problem is this: when we space a justified line, we assign it a penalty based on how much force is required to stretch or compress it into position. When we aren't justifying the lines, this force will always be zero. But we need to assign some penalty anyway, to reflect the fact that an almost-full line is better than an empty line. The current method bases the penalty on the amount of force that would be required to stretch the line to its full width. You want to change the penalty so that it is based on the amount of space to the right of the line. These can be quite different when two lines have springs of different lengths and stiffness. Anyway, I've made the change in my working copy and it gives the results you want. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: error in init.ly? (lilypond 2.11.12)
Han-Wen Nienhuys wrote: Mats Bengtsson escreveu: The file compiles fine with version 2.11.10 so there's something strange going on here. Normally, these kind of error messages indicate that you have a syntax error in your file, but since it works with 2.11.10, that seems unlikely. By commenting out sections of your file, I could narrow the problem down to be somewhere in your definition \rightHand, but I haven't managed to get further. the problem Wrong type argument in position 1: () which is likely coming from innards of lily. I suspect that it's the same problem that I fixed this morning in http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=commit;h=4013fd9b846c0a2167e2cdd60cda28a7a3fc16a6 I can confirm that the problem is solved in the latest source code from the repository. /Mats -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: error in init.ly? (lilypond 2.11.12)
Mats Bengtsson escreveu: The file compiles fine with version 2.11.10 so there's something strange going on here. Normally, these kind of error messages indicate that you have a syntax error in your file, but since it works with 2.11.10, that seems unlikely. By commenting out sections of your file, I could narrow the problem down to be somewhere in your definition \rightHand, but I haven't managed to get further. the problem Wrong type argument in position 1: () which is likely coming from innards of lily. I suspect that it's the same problem that I fixed this morning in http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=commit;h=4013fd9b846c0a2167e2cdd60cda28a7a3fc16a6 -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ragged-last likes to crowd last system
Rune Zedeler wrote: Rune Zedeler wrote: The following example should clearly typeset 20 bars on each system. In fact it typesets 13 on the first and 27 on the second. Is there a reason that this one didn't make it to the bug-tracker? For some reason I never got the email. I can see it in the list archives, but it's not in my gmail account. I just tested it, and 2.11.12 places every note on the same line, so I'm not certain if this report is still valid. That said, I still have 10 emails from this list that I need to process. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
MIDI file cuts off the last note
Hi!
I just found that the MIDI file always cuts off the last note. In this
example, it cuts off also a part of the note before. Is this bug has already
been declared ?
Frederic
\version 2.11.12
\score {
\new Staff {
\set Staff.midiInstrument = #acoustic grand
\time 4/4
\tempo 4 = 100
\relative c' { c d e f }
}
\midi {}
\layout{}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 87 in project lilypond
Issue 87: midi grace loses sync http://code.google.com/p/lilypond/issues/detail?id=87 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 245 in project lilypond
Issue 245: partcombine multiple tuplet brackets false warning
http://code.google.com/p/lilypond/issues/detail?id=245
New issue report by gpermus:
%%% false warning message
foo.ly:10:8: warning: No tuplet to end
\times 2/3 { b4 a g ~ } g2
[1]
\version quot;2.11.12quot;
\score {
lt;lt;
\new Staff {
\partcombine
\relative c'' {
\times 2/3 { d4 d d ~ } d2
}
\relative c'' {
\times 2/3 { b4 a g ~ } g2
}
}
gt;gt;
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Low Warning-nitpick
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 7 in project lilypond
Issue 7: \partcombine prints multiple tuplet brackets http://code.google.com/p/lilypond/issues/detail?id=7 Comment #6 by gpermus: OK, this bug is fixed; see #245 for the false warning. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 246 in project lilypond
Issue 246: collision stanza number and system start
http://code.google.com/p/lilypond/issues/detail?id=246
New issue report by gpermus:
% Proper behaviour would probably be to shift the start of the
% notes and lyrics
% to the right, and space the starting matter (clef,
% timesig, keysig) accordingly.
\version quot;2.11.12quot;
\layout { ragged-right = ##t }
verseOne = \lyricmode {
\set stanza = quot;4. quot;
Ma -- ry Su -- san
}
\score {
\new ChoirStaff lt;lt;
\new Staff = upper {
\new Voice = quot;voiceOnequot;
a'4 b'4 c'4 d'4
}
\new Lyrics \lyricsto voiceOne \verseOne
\new Staff = lower {
}
gt;gt;
}
Attachments:
foo.preview.png 3.4 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Long StanzaNumber collides with the left vertical line connecting staves
Thanks, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=246
Cheers,
- Graham
Sietse Brouwer wrote:
Dear all,
StanzaNumber precedes the lyrics, and extends to the left. If it becomes wide
enough, it crosses the vertical line which connects the staves of a system
(assuming a multi-staff system).
Proper behaviour would probably be to shift the start of the notes and lyrics
to the right, and space the starting matter (clef, timesig, keysig) accordingly.
Preceding a normal one-digit number with a mezzoforte dynamic is wide enough to
cause a collision. The example below has a five-digit stanza number, which is a
bit rare in practice, but otherwise equivalent and simpler.
Regards,
Sietse
Sietse Brouwer
Example code:
\version 2.10.11
\layout { ragged-right = ##t }
verseOne = \lyricmode {
\set stanza = 4.
Ma -- ry Su -- san
}
\score {
\new ChoirStaff
\new Staff = upper {
\new Voice = voiceOne
a'4 b'4 c'4 d'4
}
\new Lyrics \lyricsto voiceOne \verseOne
\new Staff = lower {
}
}
___
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
Issue 247 in project lilypond
Issue 247: lyrics attached to Devnull are left-aligned instead of center-aligned
http://code.google.com/p/lilypond/issues/detail?id=247
New issue report by gpermus:
Lyrics attached to a Voice are center-aligned if attached to a single
note, and left-aligned if attached to a melisma. Lyrics attached to a
Devnull context, however, are always left-aligned.
\version quot;2.11.12quot;
text = \lyricmode { foo bar baz quux }
notes = { c'4 c' c' c' }
\score {
lt;lt;
\new Staff { \new Voice = quot;staffVoicequot; \notes }
\new Devnull = quot;devnullVoicequot; \notes
\new Lyrics \lyricsto quot;staffVoicequot; \text
\new Lyrics \lyricsto quot;devnullVoicequot; \text
gt;gt;
}
Attachments:
foo.preview.png 4.0 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lyrics in Devnull context are left-aligned
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=247
I assume your earlier report about one of the Doc examples was the same
issue.
Cheers,
- Graham
Daniel Johnson wrote:
Lyrics attached to a Voice are center-aligned if attached to a single
note, and left-aligned if attached to a melisma. Lyrics attached to a
Devnull context, however, are always left-aligned. The following example
illustrates:
\version 2.10.11
text = \lyricmode { foo bar baz quux }
notes = { c'4 c' c' c' }
\score {
\new Staff { \new Voice = staffVoice \notes }
\new Devnull = devnullVoice \notes
\new Lyrics \lyricsto staffVoice \text
\new Lyrics \lyricsto devnullVoice \text
}
___
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: Tie bug
Hi On 1/18/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote: Can you run the test procedure ... and report whether it shows any unexpected problems? Ok, there a few (two or three) cases with chords that look worse. I'll have another look at the code in a few days. Erlend -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: lyrics set to Devnull ignore implicit melismata
Thanks, this bug has been entered as
http://code.google.com/p/lilypond/issues/detail?id=248
Thanks for the detailed explanation and multiple examples, but we find
it easier to investigate the bug if we have a single, simple example --
see the bug tracker as an example of how much I compressed it.
I regret cutting away all your extra work, but it's actually better for
the programmers this way. :|
Cheers,
- Graham
Sietse Brouwer wrote:
Dear Lilyists,
Lyrics are linked to a set of notes using \lyricsto. Normally, e.g. when
linking to a Voice context, implicit melismata such as slurs, ties, and
explicit beams are automagically detected. The next syllable begins after the
melisma ends.
However: If you link lyrics to a Devnull context, any melismata in the notes
are ignored and each syllable is linked to one note, melisma or no.
Users can work around this problem by explicitly declaring the melismata with
\melisma and \melismaEnd.
A little background: In practice, you link lyrics to a Devnull if you want to
let the lyrics follow a different rythm than the text. The Devnull allows the
text to be linked to the notes it contains, but it produces no output. It's
very convenient. This trick is explicitly explained in the manual, in section
7.3.7.5 Lyrics independent of notes; anybody trying it on music with
melismata will run into this bug.
The example file below contains an example of the bug for each of the three
implicit melismata: ties, slurs, and manual beams. It also contains an example
of the workaround.
Hope this helps!
Sietse
Sietse Brouwer
P.S.: when you try to compile this file, you'll notice a plethora of warnings
of the type warning: Lyric syllable does not have note. Use \lyricsto or
associatedVoice. I'm filing a seperate bug report for that.
* * *
Using Windows XP, Lilypond 2.10.11
\version 2.10.11
% Bug-demonstration: if you link lyrics to a Devnull context,
% the implicit melismata get ignored. That is, melismata
% indicated by a slur or manual beaming.
% A user-end workaround is defining the melismata explicitly.
\layout { ragged-right = ##t }
musicTie = {
c'4 g'4~ g'4 c'4
}
% musicSlur will demonstrate that slur-melismata are not detected.
musicSlur = {
c'4 d'4( e'4) f'4
}
% musicBeam will demonstrate that manual-beam-melismata are not
% detected.
musicBeam = {
c'4 d'8[ e'8] f'4
}
% musicWorkaround will demonstrate the workaround. I kid you not.
musicWorkaround = {
c'4
d'4( \melisma e'4) \melismaEnd
f'4
}
\score {
\new Staff = staffTie
% The notes. The lyrics should align to these.
\musicTie
\new Devnull = invisibleTie \musicTie
\new Lyrics \lyricsto invisibleTie
\lyricmode {
Ape nut mice
}
\new Staff = staffSlur
% The notes. The lyrics should align to these.
\musicSlur
\new Devnull = invisibleSlur \musicSlur
\new Lyrics \lyricsto invisibleSlur
\lyricmode {
Whim suss yet
}
\new Staff = staffBeam
% This example shows that 'manual beam melismata' are not
% detected, either.
\autoBeamOff
\musicBeam
\new Devnull = invisibleBeam \musicBeam
\new Lyrics \lyricsto invisibleBeam
\lyricmode {
Tin four geese
}
\new Staff
\musicWorkaround
\new Devnull = invisibleWorkaround \musicWorkaround
\new Lyrics \lyricsto invisibleWorkaround
\lyricmode {
Loam case book
}
}
___
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
Issue 135 in project lilypond
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #2 by gpermus:
I haven't seen a response to Mats' email (on Jan 3, 2007) on the subject, so I'm
adding it here and marking the bug unresolved.
Mats wrote:
Can we turn this into a question: What's the best way to specify that a
TextScript attached to a spacer note does not occupy any horizontal space
(meaning that the bar lines are placed at the same place as if you didn't have
the text)?
The best I can come up with is
\override TextScript #'X-extent = #'(0 . 0)
However, this means that it isn't taken into account in the new fancy
collision avoidance.
A common situation where this is useful is when you have a tempo change
at a bar line and the instrumental part begins with a multi measure rest.
The following example illustrates four different solutions. The last one
is the only one that gives a really nice output, but I find it a bit embarrasing
for LilyPond that you can't get this layout without using such an ugly hack.
\version quot;2.10.0quot;
\relative c''' {
c1
% Nice handling of the text but wrong rest.
r1^\markup{quot;Andante moltoquot;}
c1
% The text affects the bar lines
lt;lt; R1 s1^\markup{quot;Andante moltoquot;} gt;gt;
c1
% Better, but the collision handling doesn't work
\once \override TextScript #'X-extent = #'(0 . 0)
lt;lt; R1 s1^\markup{quot;Andante moltoquot;} gt;gt;
c1
% Desired layout, but ugly tweaks in the input:
lt;lt; R1 \once \override Rest #'transparent = ##t r1^\markup{quot;Andante
moltoquot;} gt;gt;
c1
}
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 240 in project lilypond
Issue 240: rest after \change Staff is placed below original materal on that staff http://code.google.com/p/lilypond/issues/detail?id=240 Comment #3 by gpermus: Sorry about the non-minimal example. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ragged-last likes to crowd last system
Graham Percival skrev: I just tested it, and 2.11.12 places every note on the same line, Indeed, it does. I would call that a regression, it looks way too crowded. so I'm not certain if this report is still valid. It is. Just replace 40 with 42 and you will see the reported behaviour. -Rune ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 249 in project lilypond
Issue 249: ragged-right last line too crowded
http://code.google.com/p/lilypond/issues/detail?id=249
New issue report by gpermus:
\version quot;2.11.12quot;
{
\repeat unfold 42 c''1
}
\paper {
ragged-last = ##t
indent = 0
}
Attachments:
foo.png 8.9 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI file cuts off the last note
On Thu, Jan 18, 2007 at 05:51:37PM -0500, Frédéric Chiasson wrote:
Hi!
I just found that the MIDI file always cuts off the last note. In this
example, it cuts off also a part of the note before. Is this bug has already
been declared ?
I've mentioned it, but the 2.11.11 (where it appeared) memory leak
prevented me from studying it it in detail. I can confirm it didn't
appear in 2.11.10.
Mats also mentioned it in reply to my message. In
http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00260.html
he wrote:
For the MIDI output, it seems that the last note only gets an ON event,
but no OFF event.
\version 2.11.12
\score {
\new Staff {
\set Staff.midiInstrument = #acoustic grand
\time 4/4
\tempo 4 = 100
\relative c' { c d e f }
}
\midi {}
\layout{}
}
--
=
Cameron Horsburgh
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
