[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using \tempo or multiple events in define-event-function
From: |
Pavel Roskin |
Subject: |
Re: Using \tempo or multiple events in define-event-function |
Date: |
Fri, 27 Apr 2012 18:06:34 -0400 |
Hello David,
Sorry for replying so late :(
On Wed, 18 Apr 2012 15:31:15 +0200
David Kastrup <address@hidden> wrote:
> Pavel Roskin <address@hidden> writes:
>
> Yup. define-event-function can only be used to return _one_
> postevent.
Too bad. I'm glad I don't really need one :)
> > There is an additional problem with \tempo. It returns a value
> > that causes an error:
> >
> > \version "2.15.36"
> > rit = #(define-event-function (parser location) () #{
> > \tempo 4=40
> > #})
> > \new Voice { \tempo 4=50 c'4 e'4 \rit g'2 }
>
> \tempo is not a postevent.
My MIDI files sound much better now that you told me that! Thank
you!
After trying almost all permutations of \tempo, s1*0 and markup, I came
to this working solution:
aTempo = { \tempo 4=58 s1*0 -"a tempo" }
rit = { \tempo 4=42 s1*0 -"rit." }
moltoRit = { \tempo 4=38 s1*0 -" molto rit." }
...
% In the melody part
\override TextScript #'direction = #UP
\override TextScript #'font-shape = #'italic
\set Score.tempoHideNote = ##t
By the way, I'm surprised we have dynamicsUp and even dotsUp but not
textScriptUp.
--
Regards,
Pavel Roskin