Thomas Morley <thomasmorle...@gmail.com> writes: > Hi, > > seems \parallelMusic can't deal anymore with music stored in a > variable or created by a function.
Care to explain about <URL:http://lilypond.org/doc/v2.19/input/regression/collated-files.html#make-relative.ly> then? > Also, this affects your function from > http://chemnitzer.linux-tage.de/2012/vortraege/900 > > \version "2.19.3" > > %% little change to ease displaying > ph = #(define-music-function (parser location p1 p2 p3 p4 p5) > (ly:pitch? ly:pitch? ly:pitch? ly:pitch? ly:pitch?) > (let ((music > #{ > \repeat unfold 2 {$p1 2 } | > \repeat unfold 2 {r16 $p2 8. ~ $p2 4 } | > \repeat unfold 2 {r8 $p3 16 $p4 $p5 $p3 $p4 $p5 } | > > #})) > ;(display-lily-music music parser) > music)) > > \parallelMusic #'(low middle high) { > \ph c' e' g' c'' e'' %| %% doesn't work without additional bar-check > } > > \new ChoirStaff << > \new Staff << \high \\ \middle >> > \new Staff { \clef bass \low } >> Somewhat disingenuously, the last significant change to the parallelMusic function is commit 52c5b014116cc800bf0f1e787470fb7aa77f8f1a Author: David Kastrup <d...@gnu.org> Date: Thu Jan 17 17:15:28 2013 +0100 Let \parallelMusic deal with barchecks at arbitrary depth This lets \parallelMusic react to bar checks at arbitrary depth to make it more useful in connection with music functions. This looks almost like barchecks _do_ work at arbitrary depth once LilyPond actually tries, but that some upfront check will keep LilyPond from making an attempt. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
