lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 3648 in lilypond: Patch: Isolated durations in


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3648 in lilypond: Patch: Isolated durations in music sequences now stand for unpitched notes
Date: Fri, 08 Nov 2013 21:18:30 +0000


Comment #7 on issue 3648 by address@hidden: Patch: Isolated durations in music sequences now stand for unpitched notes
http://code.google.com/p/lilypond/issues/detail?id=3648

Well, the first person I remember calling for that syntax is a certain Werner Lemberg: <URL:http://lists.gnu.org/archive/html/lilypond-devel/2012-09/msg00860.html>.

It also allows to replace the Mars example:

rhythm =
#(define-music-function (parser location p) (ly:pitch?)
   "Make the rhythm in Mars (the Planets) at the given pitch"
  #{ \tuplet 3/2 { $p 8 $p $p } $p 4 $p $p 8 $p $p 4 #})

with the somewhat more readable

rhythm =
#(define-music-function (parser location p) (ly:pitch?)
   "Make the rhythm in Mars (the Planets) at the given pitch"
  #{ \tuplet 3/2 { $p 8 8 8 } 4 4 8 8 4 #})

which has the additional advantage that it does not go bonkers in \relative mode.

In general, it makes mostly rhythmical input more straightforward. But it does not apply to chords, and it does not copy articulations. Stuff like that could be done using explicit music functions, but it can't be the default. A comment somewhere explains why this would be a really bad idea: basically it would cause chords and articulations to creep into unrelated material that's supposed to be rhythm-only. The same creep will happen for pitches, but that just means that rhythm-only applications should ignore pitches.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

[Prev in Thread] Current Thread [Next in Thread]