Urs Liska | 24 Nov 09:46 2014

Time signature position broken

With a build from current master (151120c3240601fd29bbb20a315decbde681fcdb)


\version "2.19.16"


results in the attached output. This is not related to the concrete 
example but a general issue: The time signature is printed completely at 
the left edge of the staff. I suspect it has something to do with recent 
time signature code changes?

bug-lilypond mailing list
bug-lilypond <at> gnu.org
Sean Barrettt | 22 Nov 06:08 2014

multiple issues with MIDI channel assignment

> I'm not top-posting.

Because these issues relate to overflowing the 16 MIDI channels,
the minimal example would still be 18+ lines. As I've found these
issues in my first 5 minutes of using lilypond, it doesn't make
sense to spend my time trying to produce a minimal example when
the issues are trivial to trigger with a lilypond sample file

lilypond 2.18.2 on Windows.


1. lilypond with verbose output (-V) doesn't output any information
about which staves are assigned to which MIDI channels; this makes
debugging the following issues more difficult

2. lilypond assigns a separate MIDI channel to lyrics lines. This is
presumably an error. (If it is by design, then it is a documentation
error, as I couldn't find any information about this in the docs.)

You can demonstrate this by taking the orchestral template
( Documentation/learning/orchestra-choir-and-piano ) and adding
"\midi { }" at the end. When run in lilypond, it will print
"warning: MIDI channel wrapped around" 5 times. If you then
comment out the four "\new Lyrics" lines, it will only print
the wraparound warning 1 time.

3. I can't find any documentation explaining how to force multiple
staves to use the same MIDI channel. In particular, the same example
(Continue reading)

Marcus Macauley | 19 Nov 01:17 2014

Cross-staff beam problems (collisions & ugly slope)

\version "2.18.2"
\paper {indent = 0\mm ragged-right = ##t}
up = {\change Staff = "upper" \voiceTwo}
down = {\change Staff = "lower" \voiceOne}
  \new PianoStaff <<
    \new Staff = "upper" 
    \relative c' { \time 1/4 \omit Score.TimeSignature
%%%%%%% Beam collides with notehead; ugly beam slope:
      \up d16 \down f d f \break
%%%%%%%% Beam collides with accidental:
      \up d \down f! d f \break
%%%%%%%% First & last beam groups have correct minimum stem length and
horizontal slope;
%%%%%%%% Other beam groups should maintain same minimum stem length by
forcing staves apart;
%%%%%%%% Other beam groups (arguably including middle group) should have
horizontal slope:
      \up d f d f
      \up d \down f d f
      \up d f \down d f
      \up d f d \down f
      \down d f d f
    \new Staff = "lower"
    { \clef bass s4*7} >>

The example above is my attempt at a "tiny" illustration of three
simultaneous problems with a cross-staff beam: collisions (of beam with
notes or accidentals); ugly slopes; and ugly horizontal spacing (stem
spacing overcorrection).
(Continue reading)

Federico Bruni | 18 Nov 23:10 2014

issues 4199 and 4200

In case someone subscribed here does not read lilypond-auto, I've added 
two issues related to lilybin.com and the idea of an interactive guide 
to lilypond syntax:


Feel free to add comments in the tracker.
Pierre Perol-Schneider | 13 Nov 12:42 2014

Re: LSR : Dashed slurs indicating optional slurs between lyric lines

Hi David, Hi Abraham,

2014-11-12 15:23 GMT+01:00 David Nalesnik <david.nalesnik <at> gmail.com>:

> Looks a lot better to me.


2014-11-12 15:34 GMT+01:00 tisimst <tisimst.lilypond <at> gmail.com>:

> I'm very much in favor of moving the slur closer, but I'm not in love
> with the method, even if it works. Shouldn't "Whee!" technically be a
> melisma? Isn't that the point of the snippet?

Wright, looks logical.
If you don't mind I'll keep the skiped lyric in order to get the original
output; so how about :

\version "2.18.2"

\score {
    \new Voice = "melody" \relative c' {
      \set melismaBusyProperties = #'()
      c8 e d-\tweak line-thickness #2.5 ( f ) e g f a
    \new Lyrics \lyricsto "melody" {
      One two three four five six seven eight
(Continue reading)

Pierre Perol-Schneider | 12 Nov 14:57 2014

LSR : Dashed slurs indicating optional slurs between lyric lines

Hi Squad,

In this snippet : http://lsr.di.unimi.it/LSR/Item?id=308
the slur is to low.
So I'd like to slightly change it to :

\version "2.18.2"

\score {
    \new Voice = "melody" \relative c' {
      c8 e8
          d8 f8
        \new Voice {
          \omit Stem
          \override NoteColumn.ignore-collision = ##t
          d4*1/2 -\tweak line-thickness #2.5 ( f)
      e8 g8 f8 a8
    \new Lyrics \lyricsto "melody" {
      One two three four five six seven eight
    \new Lyrics \lyricsto "melody" {
(Continue reading)

Jean-Charles Malahieude | 11 Nov 16:00 2014

lyrics extender and acciaccatura

Hi all,

Trying to align a syllable to acciaccaturas, I came across an extender 

The extender should stop *before* the rest, not when encountering the 
next acciaccatura.

\version "2.19.15"

Music = {
   r4 \acciaccatura { c'8 } e'4~ e'2~
   r4 \acciaccatura { e'8 } c'2.

TextKO = \lyricmode { Ah __ KO }
TextBetter = \lyricmode { "Ah __" Hum }

\score {
   \new Staff <<
     \new Voice = "music" { \Music }
     \new Lyrics \lyricsto "music" \TextKO
     \new Lyrics \lyricsto "music" \TextBetter >>

   \layout { }

(Continue reading)

Jon Ciesla | 10 Nov 17:05 2014

Build issue in Fedora due to font changes

With the latest release of the UFW fonts, they've dropped the Cyrillic
glyphs due to poor quality. I see that both 2.18.x and 2.19.x still need
ufw's ru fonts, and so lilypond fails to build in rawhide.  Is there
another font set, preferably one in Fedora already, that you'd recommend or
are planning to migrate to?

The Fedora BZ for reference:

Jon Ciesla, Fedora lilypond maintainer.


in your fear, seek only peace
in your fear, seek only love

-d. bowie
Federico Bruni | 8 Nov 13:18 2014

bad slur

In the attached image the slur starts in a point too far away from the 
note head. Is it a bug?
I've searched the tracker but there are so many issues about slurs that 
I'm not sure if this problem is known.

\version "2.19.15"
\relative c'' {
  \time 2/4
  g'16 d bes g( fis g) bes d |

bug-lilypond mailing list
bug-lilypond <at> gnu.org
Andreas Wenger | 5 Nov 10:14 2014

MusicXML test suite: Bug in 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml

the very last lyric element should be "Voice2" instead of "Voice1"
Trevor Daniels | 1 Nov 22:34 2014

Bug in \offset with Fingering.font-size?

Should \offset work with the font-size of fingering?  It doesn't seem to.  The default value is -5, so
offsetting by -2 should give -7, with a size as shown by the \override and \tweak, but both forms of \offset
give 0.

  \set fingeringOrientations = #'(left)
  \override Fingering.font-size = #-7
  \once \offset font-size #-2 Fingering
  <a'-\tweak font-size #-7 -2>
  <a'-\offset font-size #-2 -2>

bug-lilypond mailing list
bug-lilypond <at> gnu.org