[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: articulate.ly messes up drum rolls with articulations and slurs
From:       Hans_Åberg via bug-lilypond <bug-lilypond () gnu ! org>
Date:       2021-07-02 13:02:22
Message-ID: 50782C96-0718-4871-A9DC-FA67B92C9520 () telia ! com
[Download RAW message or body]


> On 2 Jul 2021, at 11:44, David Kastrup <dak@gnu.org> wrote:
> 
> Hans Åberg <haberg-1@telia.com> writes:
> 
>>> On 1 Jul 2021, at 23:36, David Kastrup <dak@gnu.org> wrote:
>>> 
>>> Separate rolls are not separated, articulations are executed on every
>>> single stroke (where they are inaudible for drums) instead of the note
>>> as such, ties (indicating an actual lack of separation) instead tie the
>>> whole roll into a single stroke, dynamics, well...
>>> 
>>> This is pretty much a disaster.
>> 
>> It is in the need for user customization.
> 
> We are not talking about "could be tweaked to give a more natural
> rendition" here.  We are talking about "blatantly and obviously
> ludicrously wrong".

Exactly, that us why I write them out by hand.

> What you call "user customization" amounts to "forget articulate.ly and
> write out a manual version yourself".  Which is certainly a workaround
> (and was so before articulate.ly even existed) but is not really related
> to fixing the problems in LilyPond and/or articulate.ly.

It a workaround in the absence of user customization.

>> I write out ornaments by hand to make sure they are correct. A spinoff
>> is that one can also typeset a version with expanded ornaments, in
>> case a performer would want to know.
> 
> That's nice but about as relevant as responding to a bug report about
> LilyPond's typesetting by proposing to pencil in the problematic
> expressions by hand.  And then calling it "user customization".

In view of the variations, it is a useful feature.

> It may be a way to get results but it certainly is not fixing a bug (and
> this is the bug reporting list of LilyPond, not the general user list).
> And it would be embarrassing to even mention something like that in the
> manual.

The file is not "bug fixable" if the intent is to provide proper articulation and ornaments.



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

[prev in list] [next in list] [prev in thread] [next in thread]