Re: Wrong spacing of leading upbeat
Quoting Mats Bengtsson [EMAIL PROTECTED] from ml.lilypond.bugs:
:The example can be shortened to
:
:\version 2.11.36
:\relative c''{
: \tempo 4. = 76
: a g f e |
:}
:\layout{ragged-right = ##t }
When I tried to shorten the file for reporting the bug, I did not think
that the menronome mark could be the culprit, so all my attempts were made
without a \tempo...
:I have fixed the bug in the source code repository. Waiting for the next
:release, you can workaround the problem by adding
:\override Score.MetronomeMark #'extra-spacing-width = #'(+inf.0 . -inf.0)
Thanks, the workaround works. :-)
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Incorrect placement of repeat bar
Quoting Mats Bengtsson [EMAIL PROTECTED] from ml.lilypond.bugs: :Please read about the Known issues and warnings in the section on :Grace Notes :in the manual. Yes, I know. But putting the grace note outside of the repeat block does not work either, so I don't know what to do. Since this prevents any correct typesetting, it's not just an issue (that could be worked around), it's a show-stopper for me. Do you have any suggestion as to how I could achieve a proper typesetting? Thanks, Raphael ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Incorrect placement of repeat bar
Quoting Mats Bengtsson [EMAIL PROTECTED] from ml.lilypond.bugs: :Please read again. It's not a matter of putting grace notes inside or :outside a :repeat block. You have to add invisible grace notes of exactly the same :duration :in all staves. Ooops. Yes, of course! That works. Somehow I rememebered that there was a wrong time administration with grace notes but I mistakenly remembered that it was linked to the presence of the grace note in the repeat block. Thanks a lot for clarifying. Raphael ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Wrong spacing of leading upbeat
I could not reproduce the problem with a small example, so I'm
giving the full file, since it is for a short piece anyway.
The upbeat formatting is wrong. As you can see, the space between
the leading 2 8ths is too large: it should be the same as the
other 8ths in the piece.
Raphael
\version 2.11.37
#(set-global-staff-size 18.6)
TimeKey = { \time 6/8 \key d \major }
VoiceOne = \relative c'' {
\partial 4
a8-.\p^\( g-. |
\repeat volta 2 {
%\acciaccatura g8 fis-.
fis8-. \parenthesize e-. fis-.
\acciaccatura a8 g-. \parenthesize fis-. g-. |
\acciaccatura fis8 e-. \parenthesize d-. e-.
fis-.\ d'-. \parenthesize cis-.\! |
b4( a8) g4( fis8) | a4(\ fis8) e-.\noBeam\)
a8-.\p^\( g-. |
\acciaccatura g8 fis-. \parenthesize e-. fis-.
\acciaccatura a8 g-. \parenthesize fis-. g-. |
\acciaccatura fis8 e-. \parenthesize d-. e-.
fis-. d'-. b-. | a4( cis8) b4( gis8) |
} \alternative {
{ gis4.( a8)\) a8-. g-. | }
{ gis4.( a8)\) r8 r8 | }
}
\relative c'' {
r4. r8 a(^\(\ b | c)\! d( c\ b)\! \parenthesize cis(\ d)\! |
e( g, fis) b( g e) | d4.(\ cis8)\noBeam\)\!
e8(^\( fis | g) a( b) c( a) fis |
g( b) e, fis-. \parenthesize g-. a-. |
\parenthesize a( g-.) g-. g4( e8)\)
\setTextCresc
fis8^\( d fis\ a fis a | b
\setHairpinCresc g\
b d\! c d\ |
\parenthesize c b\! a a a-.\p g-. |
\acciaccatura g8 fis-. d'-. e-. d fis, e | e4. d8\)
}
}
VoiceTwo = \relative c' {
\partial 4 s4 |
\repeat volta 2 {
d8-. cis-. d-. d-. b-. g-. | a4. d4. | d4. cis4 d8 |
e4 d8 cis-. s4 |
d8-. cis-. d-. d-. b-. g-. | a4. d8-. \parenthesize e-. fis-. |
cis e4 e a8 d gis4 d b8 |
} \alternative {
{ d b4.( cis8) r8 r8 | }
{ d b4.( cis8) r8 r8 | }
}
\relative c' {
r4. r4. | d4. d4. | cis4 d8 d b g b | fis a4.( e a8) r8 r8 |
b'8 b dis e e c b | b4 a8 d4. | d4. a e'4 a8 |
a4. d4. | d8 e d a'4. | g8 d cis d4 e a,8 | d a fis a g b
fis a d a cis g | cis g4. d fis,8
}
}
VoiceFour = \relative c {
\partial 4 r8 r8 |
\repeat volta 2 {
d4. b4. | cis4. d8 \parenthesize e fis |
g8 fis4 e8 d4 |
cis4 d8 a'8-. r8 r8 |
d,4. b4. | cis4. d4 d8 |
e4. e, |
} \alternative {
{ a4 e'8 a8 r8 r8 | }
\relative c { a4 e'8 a8\noBeam a8\ b8\! | }
}
\relative c' {
c8 d\ c\! b a g | fis4. g |
a4 b8 g4 g,8 | a4. a8\noBeam
r8 r8 | e'8 fis g a4 dis,8 |
e4 c8 c4. | b4.
\acciaccatura d8 cis-. \parenthesize b cis-. |
d4. fis, | g fis | g4 g'8
fis4 cis8 | d4 g,8 a4 a8 |
d,4 a'8 d8
}
}
Music = \new PianoStaff
\context Staff = up
#(set-accidental-style 'modern)
\clef treble \TimeKey
\tempo 4. = 76
\context Voice = one { \voiceOne \VoiceOne \bar |. }
\context Voice = two { \voiceTwo \VoiceTwo }
\context Staff = down
#(set-accidental-style 'modern)
\clef bass \TimeKey
\context Voice = four { \VoiceFour }
\score {
\Music
\layout {
ragged-last = ##f
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Incorrect placement of repeat bar
In the presence of the leading appogiatura, there are two repeat
bars output at the beginning, whereas there should be only one.
The second one (after the appogiatura note) is the one that should
not be there.
Raphael
% Extra repeat bar
\version 2.11.37
Up = \relative c'' {
\partial 4 a8 g |
\repeat volta 2 {
\acciaccatura g8
\repeat unfold 48 { fis }
}
}
UpTwo = \relative c' {
\partial 4 s4 |
\repeat volta 2 {
\repeat unfold 48 { d8 }
}
}
Down = \relative c {
\partial 4 r8 r |
\repeat volta 2 {
\repeat unfold 48 { d }
}
}
\score {
\new PianoStaff
\context Staff = up
\clef treble \time 6/8 \key d \major
\context Voice = one { \voiceOne \Up \bar |. }
\context Voice = two { \voiceTwo \UpTwo }
\context Staff = down
\clef bass \time 6/8 \key d \major
\context Voice = four { \Down }
\layout {
ragged-last = ##f
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Cannot reset TupletNumber back to visible
[Resent because I never received the message back]
I've been using
\override TupletNumber #'transparent = ##t
in 2.8.6 to make the tuplet number disappear after measure 2 of a score
consisting mainly of triplets. However, on occasions there are tremolos
for which I would like to display the triplet above, so I've tried to
encapsulate those thusly:
\times 2/3 {
\override TupletNumber #'transparent = ##f
g:8 d:8
\override TupletNumber #'transparent = ##t
}
But this does not work. Once the transparent has been set to true, it
seems to be sticky.
Is that the expected behaviour? How can I restore tuplet numbering
temporarily?
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Cannot reset TupletNumber back to visible
I've been using
\override TupletNumber #'transparent = ##t
in 2.8.6 to make the tuplet number disappear after measure 2 of a score
consisting mainly of triplets. However, on occasions there are tremolos
for which I would like to display the triplet above, so I've tried to
encapsulate those thusly:
\times 2/3 {
\override TupletNumber #'transparent = ##f
g:8 d:8
\override TupletNumber #'transparent = ##t
}
But this does not work. Once the transparent has been set to true, it
seems to be sticky.
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Getting programming error: adding reverse spring, setting to unit
Any idea how I can fix the score to get a proper layout without the first
note of each subsequent staff right next to the clef with no space at all?
Raphael
Quoting Raphael Manfredi [EMAIL PROTECTED] from ml.lilypond.bugs:
:Hello,
:
:I have reorganized a composition of mine. It was originally
:set for a quatuor, but I turned one of the voices into the upper
:hand of a piano.
:
:Before that move, everything was right. Now I get lots of:
:
:programming error: adding reverse spring, setting to unit
:continuing, cross fingers
:
:What does this mean??
:
:The result is NOT OK: the space between the clef and the first
:note on every staff (but the first) is minimal: it almost touches
:the clef.
:
:I use the following skeleton to produce the score (places with ...
:are where I notate the clefs and use the variables for the various
:voices:
:
:Music = \new Score
: \context StaffGroup = strings
: \context Staff = violin { ... }
: \context Staff = viola { ... }
: \context Staff = cello { ... }
:
: \context PianoStaff = piano
: \context Staff = upper { ... }
: \context Staff = lower { ... }
:
:
:
:\score {
: \Music
: \layyout {}
:}
:
:Again, before I added the piano staff part, everything was fine. But
:then I was using the following skeleton:
:
:Music = \new StaffGroup
: \context Staff = violinOne { ... }
: \context Staff = violinTwo { ... }
: \context Staff = viola { ... }
: \context Staff = cello { ... }
:
:
:Is there a workaround? I'm using version 2.6.3 on Debian (no 2.8.x
:out there yet due to dependency problems apparently).
:
:Thanks,
:Raphael
:
:
:___
: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
Getting programming error: adding reverse spring, setting to unit
Hello,
I have reorganized a composition of mine. It was originally
set for a quatuor, but I turned one of the voices into the upper
hand of a piano.
Before that move, everything was right. Now I get lots of:
programming error: adding reverse spring, setting to unit
continuing, cross fingers
What does this mean??
The result is NOT OK: the space between the clef and the first
note on every staff (but the first) is minimal: it almost touches
the clef.
I use the following skeleton to produce the score (places with ...
are where I notate the clefs and use the variables for the various
voices:
Music = \new Score
\context StaffGroup = strings
\context Staff = violin { ... }
\context Staff = viola { ... }
\context Staff = cello { ... }
\context PianoStaff = piano
\context Staff = upper { ... }
\context Staff = lower { ... }
\score {
\Music
\layyout {}
}
Again, before I added the piano staff part, everything was fine. But
then I was using the following skeleton:
Music = \new StaffGroup
\context Staff = violinOne { ... }
\context Staff = violinTwo { ... }
\context Staff = viola { ... }
\context Staff = cello { ... }
Is there a workaround? I'm using version 2.6.3 on Debian (no 2.8.x
out there yet due to dependency problems apparently).
Thanks,
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Incorrect interpretation of grace notes in MIDI
Quoting liang seng [EMAIL PROTECTED] from ml.lilypond.bugs: :Hi, yes. In fact, with sponsorship, the MIDI feature will be rewritten. Look :for MIDI rewrite in here: : :http://lilypond-design.com/sponsor/open-features.html I know. I said that I would contribute 50 EUR on this, and somebody else said they would also do the same, so we have 100 EUR of funding so far. There's no price tag on the sponsorship of the MIDI rewrite, but would you like to contribute something as well? I'm sure this would be a popular feature, so the more contributors we have, the better the feature we can end-up with... Raphael ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Incorrect interpretation of grace notes in MIDI
Quoting liang seng [EMAIL PROTECTED] from ml.lilypond.bugs: :Hi, I tested this on 2.6.3 and 2.7.18. Seems that nothing has been done to :fix this although I would think MIDI generation is not the main priority for :a music engraving program like Lilypond. Says you, with all due respect! :-) I use Lilypond to typeset my composition exercices, and when I compose for a string quartet, I cannot easily play that on the piano and therefore I rely on accurate MIDI generation to be able to get a feeling of how it sounds. I'm therefore interested to contribute financially to the open-feature MIDI refactoring. There's no quote on that yet, but I'd be willing to put 50 EUR on the table to get a much better MIDI backend. Finale has what they call human playback and a Lilypond MIDI output which would include accurately things like staccato, pralls, trills, arpeggios and all the accentuations you can think of would be very helpful for me, as I prefer to use Lilypond over Finale (try to put a Finale composition under CVS). Anyone else interested into teaming up with me to match the (yet unknown) price tag for the MIDI rewrite? Raphael ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Improper parsing of \tempo in \midi block in 2.6.3
The following: \tempo 4. = 80 is not allowed in a \midi block, whereas it is properly parsed and allowed within a score. I'm using version 2.6.3. Raphael ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
lilypond-book 2.6.3 generates incorrect \includegraphics
I cannot seem to be able to use lilypond-book since I upgraded from
2.4.5 to 2.6.3.
During the run, LaTeX complains:
(./lily-1179601096-systems.tex
! Undefined control sequence.
l.1 \includegraphics
{lily-1179601096-1.eps}
Why is 2.6.3 generating output LaTeX cannot understand? I have the
latest TeX packages from Debian unstable.
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book doesn't always add \RequirePackage{graphics} version 2.7.18 /ChangeLog/1.4302/Sun Nov 27 14:37:50 2005/
Quoting Bernard Hurley [EMAIL PROTECTED] from ml.lilypond.bugs:
:actually it if you put a comment _anywhere_ before \begin{document} then
:\RequirePackage{graphics} is not generated.
This is not always the case: even without comments, the \includegraphics
is not understood.
My (lyx-generated) document to which I removed the leading comments
is not transformed successfully. The preamble is:
--
\documentclass[a4paper,twoside,frenchb]{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\makeatletter
\usepackage{babel}
\makeatother
\begin{document}
--
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book 2.6.3 generates incorrect \includegraphics
Quoting Bernard Hurley [EMAIL PROTECTED] from ml.lilypond.bugs:
:You need to put:
:
: \usepackage{graphicx}
:
:somewhere before your \begin{document} in your lytex file. This is a
:consequence of lilypond-book now generating eps files that are included
:into the file rather that inline LaTeX code. I don't think this is
:documented anywhere.
Yes, manually adding this helps go further. However I get lots
of warnings:
-
(./lily-1179601096-systems.tex lily-1179601096-1.eps)
Overfull \hbox (113.71375pt too wide) in paragraph at lines 1--47
[][]
Underfull \hbox (badness 1) in paragraph at lines 1--47
(./lily-412723092-systems.tex lily-412723092-1.eps)
Overfull \hbox (48.46999pt too wide) in paragraph at lines 1--66
[][]
Underfull \hbox (badness 1) in paragraph at lines 1--66
(./lily-545571106-systems.tex lily-545571106-1.eps) [1] (./antecedent.aux) )
(see the transcript file for additional information)
-
And then I have tons of errors in dvips (I used --psfonts when invoking
lilypond-book):
-
dvips: Font feta-alphabet16 used in file lily-412723092-1.eps is not in the
mapping file.
dvips: Font CenturySchL-Roma used in file lily-545571106-1.eps is not in the
mapping file.
dvips: Font PFAAybabtu-Regular used in file lily-545571106-1.eps is not in the
mapping file.
dvips: Font PFAEmmentaler-16 used in file lily-545571106-1.eps is not in the
mapping file.
dvips: Font feta-alphabet16 used in file lily-545571106-1.eps is not in the
mapping file.
-
In the generated PDF file, the music is incompletely rendered, making the
whole lilypond-book thing useless!
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Fingering should be above the beam automatically
Here's a file that demonstrates the problem. I'd appreciate if that
could be added to the regression tests.
% Fingering should be ABOVE the beam automatically.
% In this example, we see overlapping with fingering on the second
% and third chords.
\version 2.6.3
\new Staff {
\clef treble \time 3/8 \key a \minor
\relative c'' {
a8 r16 e-1 c'-5 f-2 c'-5 e-1 g-3 c-5 |
}
}
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Dynamics should not collide with down beams
Here's a little script demonstrating the problem. Proper dynamics
printing should probably be added to the regression tests.
---
% The mp indication should not collide with the down beam
\version 2.6.3
\new Staff {
\clef treble \time 2/4 \key f \major
\override Staff.NoteCollision
#'merge-differently-dotted = ##t
\relative c' {
f4\mp \\ \times 2/3 { f8^( c a) }
g'4 \\ \times 2/3 { g8^( e c) }
|
}
}
---
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Collision between slurs and triolet indication
When putting slurs around triolets, the slur is overriding the 3.
The slur should be curved to avoid this overlapping. Again, I think
this should be part of the regression tests because it's a basic
feature.
In the example here, I had to duplicate the measures so that enough
gets stuffed in the line for the problem to show up (using A4 paper).
% The slurs should be shifted down to not overlap triolet indications
% or should be put up automagically. Anyway, when slur is forced down,
% an automatic shift down to avoid hiding the 3 should be done.
\version 2.6.3
\new Staff {
\clef treble \time 2/4 \key f \major
\override Staff.NoteCollision
#'merge-differently-dotted = ##t
\relative c' {
f4\mp \\ \times 2/3 { f8( c a) }
g'4 \\ \times 2/3 { g8( e c) }
|
f4 \\ \times 2/3 { f8( c a) }
g'4 \\ \times 2/3 { g8( e c) }
|
f4 \\ \times 2/3 { f8( c a) }
g'4 \\ \times 2/3 { g8( e c) }
|
f4 \\ \times 2/3 { f8( c a) }
g'4 \\ \times 2/3 { g8( e c) }
|
}
}
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Misalignment in pedal indications
The following exerpt demonstrates that Ped and * are not properly
aligned on a same horizontal line, making te indications confusing
and hard to read.
Also, I've not be able to find a way to put the sustain up even AFTER
the duration of the note (here a rest), which is kind of mandatory when
you have a chord arpegiated by the other hand...
The latter is probably an enhancement request, but it prevents typesetting
of a whole set of music... Maybe there is a complex way to do what I want
to do here? It should be simple in lilypond though, because it's a rather
a basic need when dealing with Romantic-styled music.
Again, in the example below I add to stuff the line to demonstrate the
problem with the misalignment. Bars other than the 3rd are correctly
typeset, because of the leading rest, but still all the Ped indications
are not on the same line.
% Shows that Ped and * are not aligned on the same line at
% the first measure. I believe all Ped instances should be
% aligned on the same horizontal level throughout the same system.
% Also illustrates that it would be good to have a notation to
% express that sustainUp is to trigger AFTER the duration of the
% note but before the next one: I want the sustain to remain whilst
% the right hand continues to arpegiate the chord...
\version 2.6.3
\new PianoStaff {
\new Staff {
\clef treble \time 2/2 \key c \major
\relative c' {
g2 r8 c e g |
g,2 r8 c e g |
g,2 r8 c e g |
g,2 r8 c e g |
}
}
\new Staff {
\clef bass \time 2/2 \key c \major
\relative c {
\stemDown
g8\sustainDown c e g r2\sustainUp |
r8\sustainDown g, c g' r2\sustainUp |
r8\sustainDown g, c g' r2\sustainUp |
r8\sustainDown g, c g' r2\sustainUp |
}
}
}
Raphael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
