bug-lilypond
[Top][All Lists]
Advanced

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

Re: pitchedtrill accidental problem


From: Neil Puttock
Subject: Re: pitchedtrill accidental problem
Date: Sun, 18 May 2008 20:17:17 +0100

2008/5/18 Valentin Villenave <address@hidden>:
> 2008/5/18 Neil Puttock <address@hidden>:
>
>> If you're wondering how I worked out it was broken in .42, I looked at
>> the bug report for issue 524 and picked a version at random later than
>> .35, narrowing it down until I got to version 2.11.42.
>
> Are you telling me you had to download and install every version? How
> do you handle this?

I just install and uninstall (the tedious bit.)

>> As for Karim's problem with forcing the accidental, I think I was
>> mistaken; having looked at the code in pitched-trill-engraver.cc, it
>> appears to be a slightly different issue from bug 524.
>
> I suspect the code in init-music-functions.ly is actually at stake
> here, like in Issue 561.

Quite possibly; in addition, the Pitched_trill_engraver doesn't read
the 'cautionary and 'forced-accidental properties, so even if the
information is there, it's ignored.

>
> I do think it's the same bug, that could be described this way: if a
> pitchedTrill occur on a note that has already been printed earlier
> (either explicitly or as a pitchedTrill itself), then the accidental
> will not be printed.

The way it's implemented is flawed, since there's no alteration check;
only a cross reference between the pitch/octave of the pitched trill
note and the localKeySignature. That's why the ges in Issue 524 has no
accidental (ditto your example in the bug tracker.)

Regards,
Neil




reply via email to

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