Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Status: Verified Comment #11 on issue 1695 by philehol...@googlemail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Status: Fixed Labels: -Patch-review -CD-110718 fixed_2_15_6 backport Comment #8 on issue 1695 by n.putt...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 bebd93c2dd0d7363f311d912ec1ed1f7dfcb36ba ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Labels: -backport fixed_2_14_2 Comment #9 on issue 1695 by carl.d.s...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Comment #10 on issue 1695 by carl.d.s...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Labels: CD-110718 Comment #7 on issue 1695 by colinpkc...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Labels: Patch-review Comment #6 on issue 1695 by n.putt...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Patch: http://codereview.appspot.com/4683043/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Comment #4 on issue 1695 by n.putt...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 1d4914c023a672e0e80b9b9eafc123605f4c0f00 is the first really bad commit (my initial commit is also a bit weird, but it's the tempo mark which is wrongly positioned in that case. :) It looks like a Break_align_engraver problem: despite the MetronomeMark being aligned on a note, it's still acknowledged as a break-alignable object. It gets a BreakAlignment as a temporary X-parent (until the Metronome_engraver changes it at the end of the timestep), which interferes with the loose column the clef's attached to. I think we can use 'non-musical to prevent this: if it's set in Metronome_engraver when we're sure the MetronomeMark *is* non-musical (i.e., not positioned over a note or rest), it should be easy to filter out any mark which doesn't need the services of the Break_align_engraver. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Status: Started Owner: n.putt...@gmail.com Comment #5 on issue 1695 by n.putt...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Comment #3 on issue 1695 by percival.music.ca: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 the problem occurred between BAD: 9a63326816f586dd79d326776583697f95203330 and GOOD: d3d40f3469eda2cb327bebbd392c1ce88b114394 but unfortunately the bisect in the middle has a broken commit which doesn't compile. :( there's probably some way to make git test a commit manually (so that I could avoid the broken-compile commit), but that range only has about 10 commits in it, so at least I've reduced the range? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Labels: -Priority-High Priority-Critical Regression Comment #1 on issue 1695 by philehol...@googlemail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Confirmed on my windows box. Regression occurred between 2.13.31 and 13.34. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Comment #2 on issue 1695 by reinhold...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 I can confirm it too, here on linux. If the regression occurred between 2.13.31 and .34, then my bet is that Jan's work on the Metronome-mark (and in particular the fiddling with break-align-symbol(s) ) is the culprit. This would also fit the finding that replacing the \tempo call with a \mark or a \markup yields files that are okay. Only \tempo causes the problem (btw. the triplet is not necessary, it suffices to use two eighth notes. A quarter note fixes the problem, though, as observed in the original example). Cheers, Reinhold ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
