lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 2368 di


From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 2368 discussion
Date: Sat, 26 Jan 2019 23:53:00 -0000

Diff:


I’ve been trying different values for some Tie grob-properties, and this is what I came up with. For every one of the -penalty-factor properties, there’s a threshold below which the bug doesn’t manifest (this values are linked; lowering one lessens the threshold for the others).

Of course one can also unset one of these by commenting it in the alist (for example outer-tie-length-symmetry-penalty-factor in the example below).

\version "2.21.0"
{
  \time 3/4
  \override Tie.details =
    #'(
        ;; directly copied from define-grobs.scm
        (ratio . 0.333)
        (center-staff-line-clearance . 0.6)
        (tip-staff-line-clearance . 0.45)
        (note-head-gap . 0.2)
        (stem-gap . 0.35)
        (height-limit . 1.0)
        ;; default is 10; any value higher than 2
        ;; triggers the bug:
        (horizontal-distance-penalty-factor . 10)
        (same-dir-as-stem-penalty . 8)
        (min-length-penalty-factor . 26)
        (tie-tie-collision-distance . 0.45)
        (tie-tie-collision-penalty . 25.0)
        (intra-space-threshold . 1.25)
        ;; default is 10; any value higher than 10
        ;; triggers the bug:
        (outer-tie-vertical-distance-symmetry-penalty-factor . 10)
        ;; default is 10; any value higher than 5
        ;; triggers the bug:
        (outer-tie-length-symmetry-penalty-factor . 10)
        ;; default is 7; any value lower than 7
        ;; triggers the bug:
        (vertical-distance-penalty-factor . 7)
        (outer-tie-vertical-gap . 0.25)
        (multi-tie-region-size . 3)
        (single-tie-region-size . 4)
        (between-length-limit . 1.0)
    )
  <d' g'~ c''~ >2.
  <es' g' c''>2.
}

I’ve found that some other properties also trigger ugly-Tie bugs; for example the one mentioned by Colin above is fixed by commenting the center-staff-line-clearance property (or setting to a low enough value).

Actually, most of the bugs I encountered appear to be fixed by getting rid of all these properties in bulk: simply set Tie.details to an empty list, and Bob’s your uncle.

\override Tie.details = #'() 

If so, why bother at all?


[issues:#2368] wrong position of a tie between notes in chord

Status: Accepted
Created: Thu Mar 01, 2012 01:32 AM UTC by Anonymous
Last Updated: Wed Mar 20, 2013 03:35 AM UTC
Owner: nobody
Attachments:

Originally created by: *anonymous

Originally created by: address@hidden

Reported by Karol Majewski here:

http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01194.html

% Tie that should connect 'g' and 'g'
% is located very low, so that it looks like a tie between 'd' and 'es'

\version "2.15.30"

#(set-default-paper-size "a4")
#(set-global-staff-size 18)

LiniaJeden =  \relative c'' {
  \clef "treble" \key c \major \numericTimeSignature \time 3/4
  << { g'4 f2 } \\ { < d, g ~ c ~ >2. } >>
  << { g'4 c2 } \\ { < es,, g c >2. } >>

}

\score {
    \new Staff = "LiniaJeden" \LiniaJeden
}


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.

_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

reply via email to

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