[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Slurs within chords, within tuplets -- seem to be ignored (without w
From: |
Simon Albrecht |
Subject: |
Re: Slurs within chords, within tuplets -- seem to be ignored (without warnings!) |
Date: |
Wed, 12 Apr 2017 22:26:05 +0200 |
Am 12.04.2017 um 10:59 schrieb Pete Farmer:
This tiny example compiles without warnings or errors,
Hi Pete,
just as a side note, without wanting to be obnoxious: There’s a lot to
be improved about the code formatting in your example. Much of this just
improves legibility, other points are generally accepted standards and
thus make it easier to read for others, such as the people on the list.
Here’s your original example, reformatted:
%%%%%%%%%%%%%%%%%%
\version "2.18.2"
\score {
\new Staff {
\clef "treble_8"
\key b \minor
<cis a cis'>4.\arpeggio e'8~ e'4 \tuplet 3/2 { b8\rest b\rest <gis
b(> }
\tuplet 3/2 4 { <a cis')>8~ <a cis'> <gis( b\(> <a) cis'\)>~ <a
cis'> <gis b> <a cis'>~ q e' } b4\rest
<<
{
<cis a cis'>4.\arpeggio e'8 ~ e'4 \tuplet 3/2 { b8\rest b\rest b( }
\tuplet 3/2 4 { cis'8)~ cis' b\( cis'\)~ cis' b cis'~ cis' e' }
b4\rest
}
\\
{
s2. \tuplet 3/2 { s4 gis8( }
\tuplet 3/2 4 { a8)~ a gis( a)~ a gis( a8)~ a r }
}
>>
}
}
%%%%%%%%%%%%%%%%%%
Some issues:
– judicious use of whitespace:
_always_ around { } \\ << >>
having ~ appended directly to the preceding chord or note makes the
technical function as post-event clearer
\\ should get it’s own line in most of the cases
– proper indenting (two spaces per level): most conveniently handled by
Frescobaldi’s (or ly’s) auto-formatting
– s4. s8 s4 is no different from s2. – s4 at the end of a music
expression might not make sense
– repeated durations may always be omitted (they shouldn’t be at the
start of a new line in the code)
– use the \tuplet 3/2 4 {} syntax to avoid always typing individual \tuplets
– use q to avoid respelling identical repeated chords
Best, Simon