[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: error
From: |
Erik Appeldoorn |
Subject: |
RE: error |
Date: |
Wed, 4 Nov 2009 08:47:52 +0100 |
Thanks Reinhold,
As I wanted the hairpins and the forte afterwards for me the output is not
erroneous. Indeed the error-wording does suggest a music-coding error where
in fact there might be none.
I'm not into changing source code, someone else will have to figure that one
out.
Keep well, Erik
> -----Original Message-----
> From: address@hidden [mailto:lilypond-
> address@hidden On Behalf Of Reinhold Kainhofer
> Sent: woensdag 4 november 2009 1:06
> To: address@hidden
> Subject: Re: error
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am Dienstag, 3. November 2009 21:33:51 schrieb Erik Appeldoorn:
> > Did I understand correctly that hairpins and (de)crescendo's
> automatically
> > end on a volume specifier?
> >
> > Like c\< d e f g\f, where the crescendo ends on (or just before) the g
> with
> > the forte. I shouldn't have to end them with an \!
> >
> > I get errors: (de)crescendo on items with specified volume.
>
> This has nothing to do with the implicit \!
> The problem appears when the volume before and after a (de)crescendo is
> the
> same (typically because of an implicit decrescendo, which is not notated),
> so
> lilypond does not know how to handle the crescendo.
>
> I'm able to reproduce that warning with the following code:
>
> \version "2.13.7"
> \score {
> \new Staff \relative c'{
> c\f d e f
> c\< d e f\!\f
> }
> \midi {}
> }
>
> Note that the volume is already \f, and then another crescendo starts and
> ends
> with \f, too. Typically, some parts after the first \f would be played a
> little less forte, so the crescendo makes sense.
>
> Granted, that warning message has extremly bad wording, and it does not
> tell
> you at all where in the problem is! I have not checked, whether the
> location
> can be included in the warning, which would be quite an improvement.
>
> AFAICS, that warning is triggered in the function
> Audio_span_dynamic::render(), so it happens after parsing. And the code is
> structured so that all superfluous dynamics are discarded. The message is
> then
> printed if no dynamics changes are left for the crescendo. First, I have
> no
> idea if it is even possible to get the position in the code at that time,
> even
> if the dynamic object is still available... And second, one would have to
> restructure the code a little bit to keep the discarded dynamics around,
> from
> which one might possibly get the position in the code.
>
> Cheers,
> Reinhold
> - --
> - ------------------------------------------------------------------
> Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
> * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
> * http://www.fam.tuwien.ac.at/, DVR: 0005886
> * LilyPond, Music typesetting, http://www.lilypond.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iD8DBQFK8MVmTqjEwhXvPN0RAnjTAJ4u/V1XS6WgnOoQ3ikXTEBh9Qm28QCggqv7
> VqFsIYTD7xf8YJs3wqz/+Vs=
> =1ug6
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user
- error, Erik Appeldoorn, 2009/11/03
- Re: error, Francisco Vila, 2009/11/03
- Re: error, Reinhold Kainhofer, 2009/11/03
- RE: error,
Erik Appeldoorn <=