bug-lilypond
[Top][All Lists]
Advanced

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

Fwd: Re: Implementation of \tuplet allow both incorrect and correct musi


From: Simon Albrecht
Subject: Fwd: Re: Implementation of \tuplet allow both incorrect and correct musical expressions
Date: Thu, 26 Mar 2015 10:57:33 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0

wrong list to forward to…


-------- Weitergeleitete Nachricht --------
Betreff: Re: Implementation of \tuplet allow both incorrect and correct musical expressions
Datum:  Thu, 26 Mar 2015 10:53:26 +0100
Von:    Simon Albrecht <address@hidden>
An: Ralph D. Jeffords <address@hidden>, lilypond-user <address@hidden>



Hello,

in general it’s helpful if you always include the list in the
addressees, except for really private messages. You needn’t be afraid of
increasing the traffic on ly-user.
For example, someone else might comment on your question ending the
first paragraph below.

Yours, Simon

Am 26.03.2015 um 00:57 schrieb Ralph D. Jeffords:
Simon, Disregard the last message ( I messed up). Anyway, thanks for
the quick response. The essay
on writing readable tuplets was quite interesting. The documentation
mentions nothing about the intricacies of using tuplets---why isn't
there a link to this article from the section 2.1.7 of the Learning
Manual where tuplets are first discussed?

Even before I read the essay I had some second thoughts that \tuplet
7/4 { c16 ... }  might be clearer to the player  if annotated as
\tuplet 7/8 { c32 ... } since 7 is closer to 8 than to 4 (i.e., I
anticipated the "Nearness Rule"). I also found  that certain
arpeggios  which appeared in a bassoon composition of mine ( I just
downloaded LilyPond about 10 days ago, knowing nothing about it
before, and learned enough of the basics to engrave that composition)
seem easier to read if the notes are nominal 16ths rather than
following the "Mathematical Rule:"

{ c,,8( \tuplet 5/2 { g'16 c ef g c ) } }

{ df8( \tuplet 7/2 { f16 bf  df f  bf  df f~) } }

So definitely there is a need for flexibility in using tuplets.

I am definitely impressed with LilyPond's capabilities and the input
language (I was a heavy user of LaTeX in my life before retirement, so
I am a fan of WYSIWYM tools).

Sincerely,
Ralph D. Jeffords

P.S. A bit about myself:  I was a Research Computer Scientist before I
retired, but I'm also a bassoonist and even play the piano a bit (my
mother was a piano teacher).




_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user





reply via email to

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