Re: slur to next note, bend up to next note

Am Mo., 20. Juli 2026 um 23:46 Uhr schrieb <[email protected]>:
>
>
> Quoting [email protected]:
>
> > Quoting Thomas Morley <[email protected]>:
> >
> >> Am So., 19. Juli 2026 um 22:33 Uhr schrieb <[email protected]>:
> >>>
> >>>
> >>> I would like to reproduce the last note of bar 145 in the attached
> >>> picture with a slur to the first note in bar 146, but also a bend-up
> >>> to the second note.
> >>> With a double voice, the upper one with hidden notes from last note
> >>> bar 145 with a bend to 2nd note bar 146 gives gives a bar check error
> >>> and no bend-up sign.
> >>>
> >>> << {  < c'-3\3 >8.. ~ < d'-3\2 >16  } ||
> >>>       { < c'-3\3\RH 1 >8\DN < c'-3\3 >8.
> >>>         < d'-3\2\RH 1 >16\RH 1 } >>
> >>>
> >>> Help would be appreciated.
> >>
> >> Please always post a compilable example.
> >>
> >> Anyway, see below (comments inline)
> >> \version "2.26.0"
> >>
> >> \new TabStaff \with { \tabFullNotation }
> >> {
> >>  s2..
> >>  \once \override BendSpanner.font-shape = #'upright
> >>  \once \override BendSpanner.details.bend-amount-strings.full = "full"
> >>  % Influence the strict horizontal part of BendSpanner, change to
> >> your liking.
> >>  \once \override BendSpanner.details.curvature-factor = 0.01
> >>  % Make the bending target visible.
> >>  \once \override BendSpanner.details.target-visibility = ##t
> >>  % Do not parenthesize the bending target. The default would do so.
> >>  \once \override BendSpanner.before-line-breaking = #'()
> >>  c'8\3_~\^
> >>  % Parenthesize the tie target. The default would not do so.
> >>  \once \override TabNoteHead.parenthesized = ##t
> >>  % Do not regard next NoteColumn as bending target.
> >>  \once \override NoteColumn.bend-me = ##f
> >>  c'8.\3
> >>  d'16\2
> >> }
> >>
> >> HTH,
> >>  Harm
> >
> > Amazing! Thanks.
> > I take it lilypond provides no option to put the dot at the lower
> > part of the stem, just above the beam?
>
> I tried to position the dot as in the picture, but it seems the
> Dots_engraver only accepts integers.
> \once \override Dots.staff-position = #'-4 is too high, -5 too close
> to the beam.
>
> cheers
>

Currently LilyPond warrants a Dot is never printed on a staff-line.
This holds even if the Dot is above/below top/bottom staff-line (in a
standard Staff there would be ledger lines to avoid).
You could circumvent this limitation by some esoteric code (not posted
here) or simply use extra-offset.

That said, its not the first time such a request pops up. For standard
staves style-sheets are possible to warrant a certain user-defined
output, different from default.
Why not do the same for tablature? I already did some steps in this
direction before.
Alas, I never got sufficient info about how to style what.

Consider:
\new TabStaff \with { \tabFullNotation }
{
  \time 6/16
  b8. 8.
  \time 3/2
  1.
  \time 2/4
  4. 8
  8. 16
  16 8.


  \time 6/16
  r8. 8.
  \time 3/2
  r1.
  \time 2/4
  r4. r8
  r8. r16
  r16 r8.
}

Where to place the dots (for all those cases)?
Stems: Always down? Which length, same length beamed/unbeamed? How to
deal with polyphonic situations?
How to distinguish whole and half notes?
etc.

Cheers,
  Harm