[Lilypond-auto] Issue 3928 in lilypond: Add parameters to articulate/ly to set the appropriate style for trills and pralls depending on the type

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Enhancement

New issue 3928 by address@hidden: Add parameters to articulate/ly to set  
the appropriate style for trills and pralls depending on the type
http://code.google.com/p/lilypond/issues/detail?id=3928

The file articulate.ly writes ornaments as used before c. 1800, it seems:  
initially, the PrallTriller was four notes beginning with upper auxiliary,  
which is what this file writes for \prall but used only in special  
positions, cf. example below from "Harvard concise", "inverted mordent",  
but it was replaced by the variation in the example below, called the  
Schneller. Also, the \trill it writes starts on the upper auxiliary, an  
older convention, and slows down with longer value of the note (instead of  
being on the 32nds).


----

\version "2.19.6"

\include "articulate.ly"

\language "english"

music = \new Staff = main {
  \tempo 4 = 120
  \time 2/4
%  \set beatStructure = #'(3 2 2 3 2)

  \key a \minor

  \relative c'' {
     a16\prall g c8\prall  a4\trill | a32(^\markup { \italic "After c.  
1800" }
       b) g16 c32( d c16)  a32( b a b a b a b) |
     e8( d\prall) c4 | e8^\markup { \italic "Hist. Pralltriller" } ~ e64 d  
e d ~ d16 c4 |
  }
}

\score {
  \music
        \layout {}
}

\score {
  \unfoldRepeats \articulate \music
        \midi {}
}


---

There might be needed a series of parameters, setting the style for each  
ornament:

The interpretation of these ornamental signs have changed historically. For  
example, the Baroque trill starts on the upper auxiliary, whereas in modern  
use, after ca 1800, it starts on the main note. And I write them so they  
expand into 32nds, but it could also means just a fast alteration. A  
composer might write a series of horizontal bars between the two notes to  
indicate how fast, or add a few more to indicate as fast as possible.

Hans

--
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