[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Span_dynamic_performer
From: |
Stephen |
Subject: |
Re: Span_dynamic_performer |
Date: |
Sun, 10 Apr 2005 08:50:58 -0500 |
Mats, the output went silent with this:
\tupletUp
\time 4/4
\tempo 4=50
\partial 4
g,8.\mf\< g,16 | c2.\fermata g,8. c16 | e2.\fermata g,8 c |
e4 g,8 c e4 g,8 c | e2.\fermata c8. e16 | g2\ff\> e4 c | g,2.\f
g,8. g,16 | c2.-\markup { \italic \bold "morendo" } \fermata \bar "|."
Note the 'g,8.\mf\<' beginning. An absolute dynamic did preceed the hairpin,
but on the same note.
Stephen
----- Original Message -----
From: "Mats Bengtsson" <address@hidden>
To: "Stephen" <address@hidden>
Cc: <address@hidden>; <address@hidden>
Sent: Sunday, April 10, 2005 5:02 AM
Subject: Re: Span_dynamic_performer
Just to clarify Erik's initial answer. The problem that the MIDI output
goes silent after a
(de)crescendo only happens for voices where there hasn't been any absolute
dynamics at
all before the hairpin. It doesn't matter if the absolute dynamics is 10
measures before or
on the same note.
However, it seems that you refer to another problem/feature, namely that
in the printed
output, the hairpin and the absolute dynamic will not be vertically
aligned unless
the start or end of the hairpin is on the same note as the absolute
dynamics. Of course
this is completely unrelated to the MIDI issue.
/Mats
Stephen wrote:
It has been my experience that visually it looks better to connect
absolute dynamics with a hairpin or to say it the other way around, to
connect the hairpin to an absolute dynamic. I am not trying to be
difficult. If what you say is true, what the hairpin engraver has been
written to perform optimally the hairpin performer has a bug in.
Usually a hairpin dynamic is placed between one or two absolute dynamics
so that the performer of the music knows to gradually shift from one
dynamic to the other. Usually in printed music the dynamics and hairpins
are lined up with each other vertically in this case. I learned that an
easy way to make a hairpin line up with an absolute dynamic is attach the
start or end of the hairpin to the same note as the dynamic. So if this
messes up the midi, it is very unfortunate, 'cause it is more important
to makr it look good.
I am not angry, it just takes a lot of words to make clear what I mean.
Often the purpose of a hairpin is to modulate the volume between two
given dynamics. Clearly the problem is that the hairpin modulates the
volume from its start to its endpoint, but really, it should never
modulate at its endpoints anyway. When a performer sees a hairpin, he
knows to bring it from the dynamic he is already playing at the start of
the hairpin to another absolute dynamic at the end of the hairpin. So the
modulation should never include, say, the first note of a hairpin. If
there are only two notes, it should only change the dynamic of the second
note. If the hairpin is attached to only one note, it should only change
the dynamics of the notes following the hairpin. Etc.
Again, I am curious to know which file this code is in in the sources.
Stephen
----- Original Message ----- From: "Erik Sandberg"
<address@hidden>
To: <address@hidden>
Cc: "Stephen" <address@hidden>; <address@hidden>
Sent: Saturday, April 09, 2005 4:50 PM
Subject: Re: Span_dynamic_performer
On Saturday 09 April 2005 23.10, Erik Sandberg wrote:
On Saturday 09 April 2005 15.19, Stephen wrote:
> >Known bug. You need to add an AbsoluteDynamicEvent (using e.g. \f)
> > before any
>
> cresc or dim can be used. See scm/define-music-types.scm for ideas.
>
> Erik>
>
> Actually, this is the piece that sent me looking for a solution. >
Perhaps
> because I am using Lilypond 2.4.3?
No, it's the same problem with 2.5.
The problem in your piece is another bug, midi-cresc-subp in cvs.
Absolute
dynamics don't work when they collide with start/end of cresc or dim.
Oops, I was a bit wrong. The actual problem is that cresc.s create
silence if
there is no absolute dynamic _strictly_ before them.
Erik
_______________________________________________
lilypond-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-devel
- Re: Span_dynamic_performer, (continued)
- Re: Span_dynamic_performer, Erik Sandberg, 2005/04/09
- Re: Span_dynamic_performer, Stephen, 2005/04/09
- Re: Span_dynamic_performer, Erik Sandberg, 2005/04/10
- Re: Span_dynamic_performer, Stephen, 2005/04/10
- Re: Span_dynamic_performer, Stephen, 2005/04/10
- Re: Span_dynamic_performer, David Rogers, 2005/04/10
- Re: Span_dynamic_performer, Stephen, 2005/04/11
- Re: Span_dynamic_performer, Stephen, 2005/04/14
- Re: Span_dynamic_performer, Stephen, 2005/04/14
- Re: Span_dynamic_performer, Mats Bengtsson, 2005/04/10
- Re: Span_dynamic_performer,
Stephen <=
- Re: Span_dynamic_performer, Erik Sandberg, 2005/04/11
- Re: Span_dynamic_performer, Stephen, 2005/04/14
- Re: Span_dynamic_performer, Mats Bengtsson, 2005/04/15
- Re: Span_dynamic_performer, Mats Bengtsson, 2005/04/15
- Re: Span_dynamic_performer, Juergen Reuter, 2005/04/15