Vas Crabb | 27 Mar 07:49 2015

Cowbell causes stem misalignment

% 1st beat's stem (w/cowbell) misaligns with heads for bass drum/hihat
% 2nd beat's stem (w/o cowbell) aligns correctly with heads for bass drum/hihat
% Seems to happen any time cowbell is chorded with other percussion
\version "2.18.2"

\drums {
  \tempo 4 = 120
  << bd8 hhc cb >>
  << bd8 hhc >>
  r4
}
Paul Morris | 25 Mar 14:34 2015

fixcc.py and astyle dependency problem on LilyDev

Greetings all, In the current LilyDev [0] when I try to run fixcc.py on a file [1] I get this error:

  Error: we require Artistic Style Version 2.02
  Sorry, no higher or lower versions allowed

It seems that astyle 2.01 is installed in LilyDev, and 2.01 is the only version available via apt-get or the
synaptic package manager.  The oldest version available from the astyle website is 2.03 [2].

Possible solutions: install astyle 2.02 in LilyDev by default, or revise fixcc.py so it works with astyle 2.01.

-Paul

[0] http://lilypond.org/doc/v2.19/Documentation/contributor/lilydev <http://lilypond.org/doc/v2.19/Documentation/contributor/lilydev>
[1] http://lilypond.org/doc/v2.19/Documentation/contributor/indentation <http://lilypond.org/doc/v2.19/Documentation/contributor/indentation>
[2] http://sourceforge.net/projects/astyle/files/astyle/ <http://sourceforge.net/projects/astyle/files/astyle/>
Pierre Perol-Schneider | 24 Mar 11:11 2015
Picon

[LSR] Displaying the exact extent of a system

>I'm not top posting

Hi Bug Squad,

About this snippet: http://lsr.di.unimi.it/LSR/Item?id=257
It shows a pretty old setting : \unset Staff.minimumVerticalExtent
1. AFAIK, it should have been replaced by \revert
VerticalAxisGroup.minimum-Y-extent and/but is no more used since v2.13,
shouldn't it?
2. What is the aim of this vertical unset in this particular case? Should I
delete this line? Change this line? Or maybe add a comment line for some
explanation?

Cheers,
Pierre
Ralph D. Jeffords | 24 Mar 07:18 2015
Picon
Picon

Implementation of \tuplet allow both incorrect and correct musical expressions

> I'm not top posting.

%{  MAJOR ERROR in implementation of Tuple:

  The tuple construct allows not only correct expressions but a multitude of
incorrect expressions for the same musical construction. "1st Test" shows  5
different expressions that give the same MIDI output, but only one of which
is correct.

Worse yet with the incorrect expressions, there may be multiple tuple
expressions resulting in identical music expressions, but result in
different MIDI interpretation (see "2nd test")

The solution for ruling out bogus tuples of the form  " \tuple  n/d  { _m
... }"  (where d/m is the duration for the tuple and _m indicates the
inverse duration expression for the first note of the body for the special
case when d and m are both powers of 2 is that you must have 2^floor(lg n) =
d. This correctness criterion follows from the following observation (for
the special case where duration = 1 quarter note) which is easily
generalized to durations of whole note, half note, quarter note, eight note
etc.:

(n,d,m)
-------

(1,1,4)   (single quarter note)

(2,2,8)   (two 8th notes)

(3,2,8)   ( three nominal 8th notes in notation grouped as 3 )
(Continue reading)

Urs Liska | 24 Mar 00:59 2015

Issue with symbol-list? and ly:parser-include-string

As this thread suggested
https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00193.html

there is an issue with the parser when a symbol-list? predicate is used 
as a function argument and ly:parser-include-string in that function.
As it turned out the problem is reproducible with very little effort, as 
you can see with the attached two files.

Obviously the symbol-list? predicate doesn't play well with 
ly:parser-include-string.

Some observations:

- it is not related to the \include command
   as you can see from the two alternative strings passed to 
ly:parser-include-string
- The error messages are very different depending on what comes after 
the function call
- Obviously the problem is in determining when the symbol-list? is 
completed, i.e. in the look-ahead
- In the (more complex) original context there are even other error 
messages.
- when there is any Scheme expression (the #(display "") in the example, 
but a #(define foo 'bar) works
   just the same) parsing works properly but LilyPond statements cause 
the parser to fail
Attachment (main.ly): text/x-lilypond, 624 bytes
\version "2.19.18"
(Continue reading)

Simon Albrecht | 22 Mar 22:37 2015
Picon

Enhancement: support modern-style ties

Hello,

in many scores of modern music, ties are not drawn to their full extent, 
but (speaking in lilypond terms :-)) only as a RepeatTie on the second 
chord (example attached), eventually also with a LaissezVibrerTie on the 
first chord. This is often necessary because full-length ties would 
produce very crowded output, be difficult or impossible to place.
Although it’s possible to produce this output with current Lily through 
q\laissezVibrer q\repeatTie, it should rather be coded as usually with 
q~ q and then modified through an override on Tie.
I suggest adding a 'style property with the following possible values:
'full-length (default)
'modern-single (or 'modern)
'modern-double

Yours,
Simon
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Dan Eble | 22 Mar 15:03 2015
Picon

"z" rest placement

Does anyone else think that the automatic placement of the second rest in this example is distractingly low
in the “z” style?  (If you have enough experience to suggest a solution, please do.  I haven’t looked
at the rest collision code yet.)  Thanks.
— 
Dan

\version "2.19.16"
\language "english"

% excerpt from the hymn tune "Diadem" by James Ellor
soprano = \relative {
  f''4 | ef4.( d8 c[ ef] | d4. c8 bf[ d] | c4. bf8 a[ c] | bf4) bf
}

alto = \relative {
  f'4 | g4 g r | f f r | f f r | f f
}

music = \relative {
  \key bf \major
  \time 3/4 \partial 4
  \partcombine \soprano \alto
}

\score {
  \new Staff { \music }
}

\score {
  \new Staff \with { \override Rest.style = #'z } { \music }
(Continue reading)

Mathieu Demange | 19 Mar 16:31 2015
Picon

LilyPond takes ages to start on non-admin user account on OSX

Hello,

I'm running several Mac computers for a music school and I noticed that
when LilyPond is executed from a non-admin user account (ie. students
accounts) it takes ages to start, be it from Frescobaldi or the standard
LilyPond.app package.

If executed from an admin user account, it starts as normal.

Thanks for your help.

Yours,

Mathieu
Patrick Karl | 18 Mar 22:52 2015

quoteDuring music is not sent to midi file

The Notation Manual is clear that quoteDuring is a convenience feature:

It is very common for one voice to use the same notes as those from another voice. For example,
first and second violins playing the same phrase during a particular passage of the music. This
is done by letting one voice quote the other, without having to re-enter the music all over again
for the second voice.

However, music so quoted is not sent to the midi file as demonstrated by the following snipper:

which produces this printed output:

and this midi file:

Although the midi fiile has two channels, channel 1 having c’ d’ e’ f’, there are no notes on channel 2.

I think this is a bug.  Channel 2 should have the equivalent of r2 e’4 f’.

Regards,
Pat Karl

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Michael Schuerig | 16 Mar 15:02 2015
Picon

Enhancement: command line option to transpose N halftones up or down

I've only been using LilyPond for a rather short time, so far mostly for 
engraving short snippets transposed into several keys for practicing. Of 
course, the transpose command works nicely for this.

However, it made me think of how transposing could be even nicer and now I'm 
wishing for a command line option to the lilypond command to transpose the 
engraved document by N halftones up or down. The particular advantage would 
be that this way the original document doesn't need to be changed in any way 
in order to transpose it.

Does this sound reasonable?

Michael
Ralph D. Jeffords | 15 Mar 23:38 2015
Picon
Picon

MIDI output for appoggiaturas not always correct

> I'm not top posting.
%----------------------------------------------------
% Midi output for \appoggiatura is not timed properly 
% in articulated mode. Same bug appears in Ver 2.19.16
%----------------------------------------------------
\include "articulate.ly"
\version "2.18.2"
\score {
  \new PianoStaff <<
\articulate 
\new Staff = "upper" 
\relative c' {
  \clef  bass
  \key c \major
  \time 2/4
%-----------------------------------------------
% incorrect timing: in third appogiatura the d32
% is longer than a 32nd note
%-----------------------------------------------
  \appoggiatura f,32 d'8   \appoggiatura e,32 e'8 
	
  	\appoggiatura d,32 f'4 |

%------------------------------------------ 
% correct timing when expanded out by hand
%------------------------------------------
    f,32 d'16.              e,32 e'16. 
	
  	  d,32 f'8.. 		
  } %relative	
(Continue reading)


Gmane