lilypond-user
[Top][All Lists]
Advanced

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

Re: \articulate command doesn't handle {c4 4}


From: Thomas Morley
Subject: Re: \articulate command doesn't handle {c4 4}
Date: Sun, 15 Feb 2015 21:20:25 +0100



2015-02-15 18:25 GMT+01:00 Simon Albrecht <address@hidden>:
Hello,

the support for standalone durations was one of the first (and most important?) changes made in 2.19 (see <http://lilypond.org/doc/v2.19/Documentation/changes/index.html>. But indeed, it seems to be a bug if \articulate can’t handle them.

Yours, Simon

Am 15.02.2015 15:26, schrieb Cynthia Karl:
For example,

\version "2.19.15"
\include "articulate.ly"

\score { {
        \unfoldRepeats     \articulate
\new Staff  {cis''1~ 1~ \break cis''}
     }
     \midi {  }
}
 produces a midi file which consists of 4 beats of cis'' folowed by 4 beats of rest or silence followed by 4 beats of cis''.
Isolated durations are working copying the previous note or chord, the result is a _NoteEvent_ without 'pitch (not an EventChord, even if the previous event was an EventChord).
Look at the terminal-output of 1. example

Otoh, the articulate-script _needs_ to have all relevant events as EventChords.
Though, wrapping a NoteEvent without pitch into an EventChord will result in rubbish even without \articulate.
Look at the printed and terminal output of 2. example.

\version "2.19.15"

mus = { <dis'' fis''>1 1 }

%% 1. example
\displayMusic
  \mus

%% 2. example
\displayMusic
  $(map-some-music
    (lambda (m)
      (event-chord-wrap! m parser))
    mus)

Have a look into articulate.ly again. You'll find:
% CHANGELOG
%  * David Kastrup: basic 2.15.28 compatibility by using event-chord-wrap!
%    This should really be done by rewriting the code more thoroughly.

Seems David was prophetic again.


Pease write a bug-report.


Cheers,
  Harm


reply via email to

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