> A possible solution for this could be to do a similar thing to add
> certain note columns to separate NoteCollision grobs, so they can be
> spaced independently.
I've added Valentin's solution as a new snippet to the LSR.
https://lsr.di.unimi.it/LSR/Item?u=1=1172
Werner
Gould p91 "Altered Unisons" gives the requested layout, not the LilyPond one.
Paul
From: Werner LEMBERG
To:
Cc:
Sent: 12/06/2023 18:46
Subject: Re: shifting accidentals horizontally
> Not the answer to the Lilypond question, but as a reference of
>
Or rather there is the
NoteColumn.ignore-collision
property. If set to #t the Note column will not be added to any NoteCollision
grob. The problem here is that in this case there need to be no positional
correction. So we require some additional check in the engraver to apply this
correction
> A possible solution for this could be to do a similar thing to add
> certain note columns to separate NoteCollision grobs, so they can be
> spaced independently. However, it your case it should suffice to
> prevent any Collisions to be detected by doing
>
> \once\override
Hello Werner,
this Problem is not caused by my solution, but generally by your approach of
taking the Notes with collision applied (the 8th note bb on the left, the b,e
on the right) and shifting the bb until it is right of the others. This still
means that the will be offcentered.
So this
> @Werner I’ve added a small fix concerning the case when there is no
> NoteCollision grob (in which case this should not be relevant in the
> first place).
Thanks a lot! I think this would be a great snippet for the
LSR.
Note, however, that there are alignment problems with other staves,
see
> Even though I can imagine this happening, I don't recall seeing it
> as a pianist. Even if you tweak it to swap the note columns, I
> think it will still be a bit confusing.
As Damian has observed, there are plenty of examples in Bartók's piano
sonata. Other, similar situations can be found
> Even though I can imagine this happening, I don't recall seeing
> it as a pianist. Even if you tweak it to swap the note columns,
> I think it will still be a bit confusing.
>
> There are two obvious fixes: if you are the composer, you could
> consider changing the B♭ into an A♯. And the
Hello Jean,
I think a possible case would be something like the appended case, so if we
have some sort of superimposed patterns.
@Werner I’ve added a small fix concerning the case when there is no
NoteCollision grob (in which case this should not be relevant in the first
place).
Cheers,
Le lundi 12 juin 2023 à 17:02 +, Werner LEMBERG a écrit :
> Please consider the example code below. The first line shows
> LilyPond's default, the second line shows what I need. As can be
> seen, the solution in the second line is imperfect – I just did the
> most basic changes to
Hello Werner,
I’ve tried something using an engraver that sends of accidentals from the
given context to a separate AccidentalPlacement grob:
%
#(define (which lst)
(define (impl lst count)
(if (null? lst)
#f
(if (car lst)
count
(impl (cdr
> Not the answer to the Lilypond question, but as a reference of
> comparison, here is what Dorico does in this situation by default,
> and I believe this to be correct standard practice.
Well, it can't be generalized – sometimes LilyPond's default is the
right choice. However, it would be nice
Not the answer to the Lilypond question, but as a reference of
comparison, here is what Dorico does in this situation by default, and I
believe this to be correct standard practice.
Andrew
Please consider the example code below. The first line shows
LilyPond's default, the second line shows what I need. As can be
seen, the solution in the second line is imperfect – I just did the
most basic changes to demonstrate what I want, namely the down-stemmed
note to be positioned after
14 matches
Mail list logo
