Chord fingering

Many issues related to fingering positioning and collisions are caused by incorrect input.
A fingering number should always (!) be attached to a specific note, never to a chord in general.

Therefore, the coding used in this issue is not supposed to work anyway.
Instead of

{
  <e'' f'' cis'''>1 ^1^2^5
}

this should be input as

{
  <e''^1 f''^2 cis'''^5>1
}

in the first place.

Cause of collision

Currently, the New_fingering_engraver does not take care of accidentals for up/down fingerings at all. As all the chord's accidentals may get into the way (at least for chords containing intervals of a second, i.e. if there are noteheads on both sides of the stem).

Proposed Solution

Make all the accidentals known to the fingering side-positioning interface.
The attached image illustrates the result before and after the correction.
Noteheads, accidentals and fingerings are coloured to show the elements belonging together.
As you can see, the 1 fingering collides with the accidental of another note, so all the accidentals should be known in order to be avoided.

I'm either waiting for issue 5393 or extend this issue by adding left-alinged fingering collisions with dots.

All the best,
Torsten

Attachments:

issue3692a.png (34.9 kB; image/png)

[issues:#3692] Fingering collision with accidentals

Status: Started
Created: Sat Nov 30, 2013 09:17 AM UTC by Anonymous
Last Updated: Fri Aug 03, 2018 01:01 PM UTC
Owner: Torsten Hämmerle
Attachments:

fingering.preview.png (4.6 kB; image/png)

Originally created by: *anonymous

Originally created by: address@hidden

Fingerings do not take accidentals into account, and fingerings align over the first note inout of a chord, rather than centering over the whole chord.
\version "2.17.96"

{
<e'' f'' cis'''>1 ^1^2^5
}

From Keith Ohara:
"Unfortunately this is a different bug -- or two -- so it will
not be fixed at the same time as collisions between Fingerings.

(1) LilyPond has never looked at Accidentals when placing Fingering;
until recently that caused only small overlaps with sharps because
the Fingering did not previously fit so close to the chord.

(2) Fingering on a chord as a whole should center over the main column
of note-heads; instead it centers over the first-input note.

So, you can do the same as we did when using version 2.12: rearrange
the order of pitches in the chord so a main-column note comes first.

{ <f'' e'' cis'''>1 ^1^2^5 }

***********
From Janek :

and i believe to solve it in a general way we would have to teach
lilypond about different kinds of extents - see:

http://lists.gnu.org/archive/html/lilypond-devel/2012-06/msg00230.html
https://code.google.com/p/lilypond/issues/detail?id=3239 (sorry, that
issue got pretty messy).

Currently the work i started on this is waiting until 2.18.0 is out...
What about leaving it for now and attacking this together after 2.18?
************
Possibly a Known Issue in NR 1.7.1 would be in order.

Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

From:	Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject:	[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #3692 Fingering collision with accidentals
Date:	Fri, 03 Aug 2018 13:52:47 -0000

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #3692 Fingerin

Chord fingering

Cause of collision

Proposed Solution