LilyIssues / Issues / #596 collision tuplet number and slur

Google Importer - 2008-05-28

Originally posted by: hanw...@gmail.com

(No comment was entered for this change.)

Labels: -Type-Defect

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2010-01-20

Originally posted by: percival.music.ca@gmail.com

Dupe of 307

Status: Duplicate

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2010-01-20

Originally posted by: percival.music.ca@gmail.com

(No comment was entered for this change.)

Mergedinto: 307
Owner: ---

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2010-01-24

Originally posted by: v.villenave

Indeed.

Mergedinto: -307
Status: Verified

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2011-07-24

Originally posted by: mts...@gmail.com

This is actually a different issue than 307. The problem here is the polynomial solver leads to numerical inaccuracies for the roots of equations.

I've uploaded a patch at http://codereview.appspot.com/4820048.

Labels: Patch-new

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-02-09

Originally posted by: julien.r...@gmail.com

So is this verified or is this new? Please check.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-03-12

Originally posted by: dak@gnu.org

Bug is still there visually and produces the output
Drawing systems...
programming error: no solution found for Bezier intersection
continuing, cross fingers
programming error: no solution found for Bezier intersection
continuing, cross fingers
programming error: no solution found for Bezier intersection
continuing, cross fingers
programming error: no solution found for Bezier intersection
continuing, cross fingers
programming error: no solution found for Bezier intersection
continuing, cross fingers

I have no idea why this should have been marked as "verified".

Status: Accepted

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-03-13

Originally posted by: dak@gnu.org

Patchy the autobot says: Patch does not seem to apply. Discussion indicates this might need work.

Labels: Patch-needs_work

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-03-13

Originally posted by: mts...@gmail.com

I think people thought the patch was arbitrary in its choice of epsilon and I haven't thought of a better solution since. It's tricky because depending on the epsilon value used the patch may lead to over or under-inclusive avoidance behavior.

People are welcome to take a stab at it – it is an easy fix once someone finds an appropriate epsilon value and/or heuristic for specially dealing with limit values before they can be crunched into numerical-inaccuracy-land.

Last edit: Simon Albrecht 2015-09-18

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-03-13

Originally posted by: dak@gnu.org

I don't see where the numerics would originate. What kind of intersection is supposed to be calculated here? This sounds rather like a home-made problem where you start with throwing information away (like the information that some outline is closed), and then try getting away without it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-03-23

Originally posted by: gra...@percival-music.ca

(No comment was entered for this change.)

Labels: -Priority-Medium -Type-Collision Type-Ugly

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-05-13

Originally posted by: pkx1...@gmail.com

(No comment was entered for this change.)

Owner: mts...@gmail.com

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Google Importer - 2012-08-12

Originally posted by: k-ohara5...@oco.net

The reason existing Lilypond misses this collision is because Slurs may cross Spanners, and TupletNumber is a Spanner (presumably for centering it over the span of the tuplet).

If I change the code so Slurs treat TupletNumbers like any other glyph, then the examples in this issue come out nicely,
but, we still have problems for cases like issue 1642 and issue 1374, where the tuplet started before the slur. The slur engraver only watches for items that the slur must avoid, if they are created during the span of the slur. We would need to improve the sophistication of the engraver to make fixing this sub-bug worthwhile.

Labels: -Patch-needs_work
Owner: ---

Related

Issues: #1374
Issues: #1642

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -2,17 +2,21 @@

 *Originally created by:* [v.villenave](http://code.google.com/u/v.villenave/)

-% The slur may collide with the tuplet number with following conditions:
-% -tuplet is beamed
-% -the slur is on the same side as the tuplet number
-% -the slur starts or ends at the horizontal position of the tuplet number
-% \(such a tuplet is usually a triplet, quintuplet, ...\)
+The slur may collide with the tuplet number with following conditions:

+- tuplet is beamed
+- the slur is on the same side as the tuplet number
+- the slur starts or ends at the horizontal position of the tuplet number

+\(such a tuplet is usually a triplet, quintuplet, ...\)
+
+~~~~
+:::TeX
 \version "2.11.43"

-\paper \{ ragged-right = \#\#t \}
+\paper { ragged-right = ##t }

-\{
-&nbsp; \slurUp \times 2/3 \{ a'8\( a'\) a' \}
-\}
+{
+  \slurUp \times 2/3 { a'8( a') a' }
+}
+~~~~

Needs: -->
Patch: -->

Simon Albrecht - 2015-09-18

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

collision tuplet number and slur

Issue Tracker for LilyPond

Searches

Help

#596 collision tuplet number and slur

Related

Discussion

Related