Brett Duncan wrote:
The problem was that George had used the \cresc command in his file,
but had \crescHairpin command _before_ the \cresc command. Moving
\crescHairpin appears to have solved his problem.
I couldn't find \cresc in the Notation Reference, but it does appear
in the Internals Reference, where it is listed simply as an
alternative notation for \<. From George's file, it appears to not
only generate a text crescendo but also switch the display of
crescendos to text mode until explicitly changed back to hairpin - is
this the intended behaviour?
The \cresc macro is defined in ly/spanners-init.ly and is preceded by a
comment:
% STOP: junkme!
so it's clearly not well-supported It's certainly intended to generate a
text style crescendo "cresc.".
However, at the time the macro was implemented, any setting of
crescendoText was automatically
reverted after the next crescendo event (i.e. it worked like a \once
\set ...) so now that the crescendoText
property works just as all other properties, it would make more sense to
let the macro be implemented as
cresc = {
#(ly:export (make-event-chord (list cr)))
\once \set crescendoText = \markup { \italic "cresc." }
\once \set crescendoSpanner = #'text
}
if we want it to remain. In contrast to using the supported and
documented macro \crescTextCresc,
you don't get any dashed line when using \cresc. Note also that there is
a macro \endcresc that reverts
the settings done by \cresc (which wouldn't be needed if we used the
above definition).
/Mats
by \cresc. Finally
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
