tuplets with tupletFullLength collide with barline

Hello Bug Squad, When using tuplets with tupletFullLength set to True, the last tuplet bracket in a system extends all the way to the barline. This results in potential collisions when barlines cross several staves. E.g., in the output of the code below, the right ending of the last tuplet

Re: Skip-filled tuplets crash 2.25.0

Thanks, Jean! On Fri, Jan 13, 2023 at 5:38 PM Jean Abou Samra wrote: > Le 13/01/2023 à 23:36, Trevor Bača a écrit : > > Hi, > > > > Skip-filled tuplets halt execution in 2.25.0. > > > > %%% BEGIN %%% > > > > \version "2.25.0" > &g

Re: Skip-filled tuplets crash 2.25.0

Le 13/01/2023 à 23:36, Trevor Bača a écrit : Hi, Skip-filled tuplets halt execution in 2.25.0. %%% BEGIN %%% \version "2.25.0" \new Staff { \times 2/3 { s2 s2 s2 } } %%% END %%% GNU LilyPond 2.25.0 (running Guile 2.2) Processing `test.ly' Parsing... Interpreting music... warning

Skip-filled tuplets crash 2.25.0

Hi, Skip-filled tuplets halt execution in 2.25.0. %%% BEGIN %%% \version "2.25.0" \new Staff { \times 2/3 { s2 s2 s2 } } %%% END %%% GNU LilyPond 2.25.0 (running Guile 2.2) Processing `test.ly' Parsing... Interpreting music... warning: omitting tuplet bracket with neither left

Re: Lilypond crash related to tuplets

through it, let alone set it all up for compiling. I am unable to extract an MWE from the score that proves it. However, being clued in to a possible issue around tuplets, I found the issue by trial and error rather than gdb. Here it is: calling tupletFullLengthNote = ##t causes the crash

Re: Lilypond crash related to tuplets

Here it is: Using tupletFullLengthToNote = ##t crashes it. \version "2.19.82" \paper { indent = 0 ragged-right = ##t } \layout { \set tupletFullLength = ##t \set tupletFullLengthNote = ##t } { \tuplet 1/1 { b'1 } \break 4 } That qualifies as a bug worth registering, does it not? Andrew

Re: Lilypond crash related to tuplets

. I am unable to extract an MWE from the score that proves it. However, being clued in to a possible issue around tuplets, I found the issue by trial and error rather than gdb. Here it is: calling tupletFullLengthNote = ##t causes the crash. This is definite. But it only occurs in my reasonably large

Re: Lilypond crash related to tuplets

On 2019-03-23 3:39 pm, Thomas Morley wrote: Am Sa., 23. März 2019 um 21:41 Uhr schrieb Aaron Hill : \override TupletBracket.X-positions = #(lambda (grob) (let ((xpos (ly:tuplet-bracket::calc-x-positions grob))) (if (> (car xpos) (cdr xpos)) (format #t "\nwarning:

Re: Lilypond crash related to tuplets

Am Sa., 23. März 2019 um 21:41 Uhr schrieb Aaron Hill : > > On 2019-03-23 6:46 am, Andrew Bernard wrote: > > What calls calc_x_offset for Tuplet Number? > > This likely may be coming from Scheme. If you look at the Internals > reference, you will see that the X-offset property for TupletNumber is

Re: Lilypond crash related to tuplets

On 2019-03-23 6:46 am, Andrew Bernard wrote: What calls calc_x_offset for Tuplet Number? This likely may be coming from Scheme. If you look at the Internals reference, you will see that the X-offset property for TupletNumber is by default set to ly:tuplet-number::calc-x-offset. That means

Lilypond crash related to tuplets

Ubuntu 18.10. The same occurs with 2.19.82. This seems to indeed indicate something in the tuplet machinery going wrong. I have disabled ally my music functions that have anything to do with modifying tuplets. I did this because the exact error came up a year or two go and that turned out to be

Re: Automatic beaming fails with tuplets

n here, and it is a flaw of LilyPond to no always require full tuple groups. So somehow, when entering a full tuplet group, that structure should be forwarded to the beaming algorithm. Then it is unclear what exactly to do when it is not a full group. >>>>> From the result

Re: Automatic beaming fails with tuplets

uplet groups, and then apply its local beatStructure. I'm not sure how that would apply if the tuplet group isn't complete, like in my example given in the previous paragraph. From the results I assume that the beaming code suffers from the same misconception as the code in beaming-patt

Re: Automatic beaming fails with tuplets

If one should have that feature, for correct beaming, one should first reduce it to full tuplet groups, and then apply its local beatStructure. >>> From the results I assume that the beaming code suffers from the same >>> misconception as the code in beaming-pattern: tuplets are re

Re: Automatic beaming fails with tuplets

esults I assume that the beaming code suffers from the same misconception as the code in beaming-pattern: tuplets are recalculated and processed according to their *absolute position* in the measure. That means that an event that happens to occur on a beat of the measure's beat structure is treate

Re: Automatic beaming fails with tuplets

p behaves like a mini-measure with its own beaming pattern, though the general structure is the same. The beaming is then as of the written notes values, not the actual timing values implied. > From the results I assume that the beaming code suffers from the same > misconception as the code

Re: Automatic beaming fails with tuplets

graver > finds the fifth 32th note to be sitting on the beat and therefore > breaks the beam. Obviously tuplets have to be treated specially. How? I'm sort-of comfortable with how we deal with beaming in graces (basically beam across the whole group unless interrupted). Not sure this will wo

Automatic beaming fails with tuplets

I think the attached beaming is wrong. In \relative c'' {   \tuplet 3/2 {     r4 c32 c c c c c c c     r4   }   r2 } The beam should *not* be broken IMO. I think the auto-beam-engraver finds the fifth 32th note to be sitting on the beat and therefore breaks the beam. Obviously tuplets have

Re: Bug - Lilypond hangs forever if too many prime tuplets are used

Prime tuplets! Give me a break. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Bug-Lilypond-hangs-forever-if-too-many-prime-tuplets-are-used-tp196554p196567.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug

Re: Bug - Lilypond hangs forever if too many prime tuplets are used

this message in context: http://lilypond.1069038.n5.nabble.com/Bug-Lilypond-hangs-forever-if-too-many-prime-tuplets-are-used-tp196554.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lily

Re: More than 5 nested tuplets of large value hangs Lilypond permanently

d this be documented (in http://lilypond.org/doc/v2.19/Documentation/notation/writing-rhythms#tuplets) b) is there a way to catch this type of issue and abort with an error instead of hanging? Urs \version "2.18.2" \new Staff { \clef "treble" % This is a Nancarrow-sty

More than 5 nested tuplets of large value hangs Lilypond permanently

ge in context: http://lilypond.1069038.n5.nabble.com/More-than-5-nested-tuplets-of-large-value-hangs-Lilypond-permanently-tp196556.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Bug - Lilypond hangs forever if too many prime tuplets are used

t; %\tuplet 11/13{r8} \tuplet 3/5{f8} } } >> -- View this message in context: http://lilypond.1069038.n5.nabble.com/Bug-Lilypond-hangs-forever-if-too-many-prime-tuplets-are-used-tp196554.html Sent from the Bugs mailing list archive at Nabble.com. ___

Re: tuplets and accidentals collision

Carl Sorensen writes: > On 7/6/16 5:07 AM, "Gilberto Agostinho" wrote: > >> >>Is this a known bug? The only similar bug I found in the tracker is this >>one here , but it >>seems to be a bit

Re: tuplets and accidentals collision

uppose in the end it's the same issue. Cheers, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/tuplets-and-accidentals-collision-tp192293p192296.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-li

Re: tuplets and accidentals collision

On 7/6/16 5:07 AM, "Gilberto Agostinho" wrote: > >Is this a known bug? The only similar bug I found in the tracker is this >one here , but it >seems to be a bit different than what I am reporting here. >

tuplets and accidentals collision

re <https://sourceforge.net/p/testlilyissues/issues/3766/> , but it seems to be a bit different than what I am reporting here. Cheers, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/tuplets-and-accidenta

crossStaff, beams and tuplets [was: Re: three small bugs]

? If one wants to use \crossStaff for a certain passage, then very likely he doesn't want beams and tuplets displaying there. The reference mentions that one should use \autoBeamOff but there are no mentions about tuplets. \version "2.19.28" \score{ \new PianoStaff << \new Staff

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

Thanks for the confirmation of version, Simon. For what it's worth, the bad output is no problem in actual scores because other layout settings will be used to space everything correct, move time signatures around and so on. It's only the crashing of the system that is a problem. Also, the

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

On 20.09.2015 19:07, Trevor Bača wrote: Thanks for the confirmation of version, Simon. For what it's worth, the bad output is no problem in actual scores because other layout settings will be used to space everything correct, move time signatures around and so on. It's only the crashing of

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

Simon Albrecht writes: > On 16.09.2015 23:04, Trevor Bača wrote: >> \version "2.19.27" >> >> \layout { >> \context { >> \Score >> \override SpacingSpanner #'strict-note-spacing = ##t >> tupletFullLength = ##t >> } >> } >> >> \new Staff

Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

Hi, I've been using length-1 tuplets in my music recently. (Length-1 tuplets being tuplets with only a single note or rest.) It's quite wonderful that Lily handles these things correctly (just like how the system handles unusual time signatures like 1/12 and 5/14, too). But I've now uncovered

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

On 16.09.2015 23:04, Trevor Bača wrote: \version "2.19.27" \layout { \context { \Score \override SpacingSpanner #'strict-note-spacing = ##t tupletFullLength = ##t } } \new Staff { \time 1/8 \times 2/3 { c'8. } \time 5/8

Re: musicxml2ly doesn't handle nested tuplets

On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska u...@openlilylib.org wrote: When dealing with export of nested tuplets to MusicXML ( https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly

Re: musicxml2ly doesn't handle nested tuplets

On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska u...@openlilylib.org wrote: When dealing with export of nested tuplets to MusicXML ( https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly

Re: musicxml2ly doesn't handle nested tuplets

Am 5. Juni 2015 13:55:04 MESZ, schrieb Ralph Palmer ralphbugl...@gmail.com: On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska u...@openlilylib.org wrote: When dealing with export of nested tuplets to MusicXML ( https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can

musicxml2ly doesn't handle nested tuplets

When dealing with export of nested tuplets to MusicXML (https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how

crash with tuplets containing only skips and dynamics

Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} output: Starte lilypond.exe 2.17.26 [Ohne Titel] ... Processing `c:/users/brandenr/appdata/local/temp/frescobaldi-gyhmmg/tmph84id7/document.ly' Parsing... Interpreting music...

Re: crash with tuplets containing only skips and dynamics

2013/10/12 René Brandenburger r...@brandenburger.lu: Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} output: Starte lilypond.exe 2.17.26 [Ohne Titel] ... Processing

Re: crash with tuplets containing only skips and dynamics

René Brandenburger r...@brandenburger.lu writes: Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} URL:http://code.google.com/p/lilypond/issues/detail?id=3551 Fixed in 2.17.27. Keith was faster than you. -- David Kastrup

Re: crash with tuplets containing only skips and dynamics

Am 12.10.2013 20:55, schrieb David Kastrup: René Brandenburger r...@brandenburger.lu writes: Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} URL:http://code.google.com/p/lilypond/issues/detail?id=3551 Fixed in 2.17.27.

Tuplets Calculated Wrong

I'm not top posting. % graphically, \times 4/5 and \times 2/5 will look the same, but the note % duration is calculated differently, and on the second example there are % more notes in the bar than should be. \version 2.16.2 \relative c'' { \time 2/4 r4 \times 4/5 { a8 g16 a g } | a32 a a a a

Re: Tuplets Calculated Wrong

Érico Schmitt ericoschm...@yahoo.com.br writes: I'm not top posting. % graphically, \times 4/5 and \times 2/5 will look the same, but the note % duration is calculated differently, and on the second example there are % more notes in the bar than should be. \version 2.16.2 \relative c'' {

Re: Tuplets Calculated Wrong

Érico Schmitt ericoschm...@yahoo.com.br wrote in message news:loom.20130109t200321-...@post.gmane.org... I'm not top posting. % graphically, \times 4/5 and \times 2/5 will look the same, but the note % duration is calculated differently, and on the second example there are % more notes in the

Re: Tuplets Calculated Wrong

Érico Schmitt writes: I'm not top posting. % graphically, \times 4/5 and \times 2/5 will look the same, but the note % duration is calculated differently, and on the second example there are % more notes in the bar than should be. \version 2.16.2 \relative c'' { \time 2/4 r4 \times 4/5

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Status: Fixed Labels: -Patch-review fixed_2_15_35 Comment #9 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 Pushed to staging

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Labels: -Patch-needs_work Patch-new Comment #7 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 OK, I've uploaded a patch that fixes the memory leak

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Labels: Patch-review Comment #8 on issue 2408 by d...@gnu.org: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408#c8 Patchy the autobot says: LGTM

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Labels: -Patch-countdown Patch-push Comment #5 on issue 2408 by colinpkc...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 Mike and David have comments on Rietveld, but can

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Labels: -Patch-push Patch-needs_work Comment #6 on issue 2408 by gra...@percival-music.ca: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 I think that David's suggestion is important

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Labels: Patch-new Comment #2 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 New patch uploaded. Restores 2.12.3 behavior. Does not automatically

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Labels: Patch-review Comment #3 on issue 2408 by julien.r...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408#c3 Patchy the autobot says: LGTM. No visual changes to regtests

Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Updates: Status: Started Owner: carl.d.s...@gmail.com Comment #1 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 Have a patch just about ready to go

Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other

Status: Accepted Owner: Labels: Type-Critical New issue 2408 by pkx1...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 \version 2.15.32 \relative c' { \time 2/4 c16 c \times 2/3 { c8 c16

Re: tuplets

G.S. Williams gorsw...@xtra.co.nz wrote in message news:loom.20120130t041720-...@post.gmane.org... Hi, I've been tied up with classical music for several decades, and we have always referred to pairs of notes as DUPLETS, not,TUPLETS:.why do you people in the U.S.A. always change terminology? I

Re: tuplets

Phil Holmes m...@philholmes.net writes: G.S. Williams gorsw...@xtra.co.nz wrote in message news:loom.20120130t041720-...@post.gmane.org... Hi, I've been tied up with classical music for several decades, and we have always referred to pairs of notes as DUPLETS, not,TUPLETS:.why do you

tuplets

Hi, I've been tied up with classical music for several decades, and we have always referred to pairs of notes as DUPLETS, not,TUPLETS:.why do you people in the U.S.A. always change terminology? I''m curious! Ciao. G.S.Williams ___ bug

Re: tuplets

G.S. Williams gorsw...@xtra.co.nz writes: Hi, I've been tied up with classical music for several decades, and we have always referred to pairs of notes as DUPLETS, not,TUPLETS:.why do you people in the U.S.A. always change terminology? That's not a change. A duplet is a pair

Re: Regression: 16th tuplets not subdivided with subdivideBeams

Xavier Scheuer x.sche...@gmail.com wrote in message news:CADGqHRfMs2GpBr3qw=axfs2cxuug8sa-yfrnfempjvs0+zp...@mail.gmail.com... Hello, Just reported on the French Users mailing list: Snippet %% subdivideBeams does not work anymore with 16th tuplets. %% With 2.15.26 only the second beat

Regression: 16th tuplets not subdivided with subdivideBeams

Hello, Just reported on the French Users mailing list: Snippet %% subdivideBeams does not work anymore with 16th tuplets. %% With 2.15.26 only the second beat is subdivided as expected. %% Worked well with stable 2.14.2, so this is a Regression. \version 2.15.26 \relative c'' { \set

error: auto beaming in tuplets after dotted semiquaver

I'm not top posting. Autobeaming dotted semiquaver with 64th in tuplet is incorrect for 2.15.23. Beams of first 64th points to the left instead of beeing connected to the beams of the 2nd and 3rd 64th. Maybe this is a side effect of the latest patch for issue 11

RE: error: auto beaming in tuplets after dotted semiquaver

From: Martin Straeten [martin.strae...@gmail.com] Sent: Friday, December 30, 2011 12:47 PM To: bug-lilypond@gnu.org Subject: error: auto beaming in tuplets after dotted semiquaver I'm not top posting. Autobeaming dotted semiquaver with 64th in tuplet is incorrect for 2.15.23. Beams

Re: Issue 992 in lilypond: Tuplets collide with notes outside the staff

Updates: Labels: -Priority-High Comment #9 on issue 992 by pkx1...@gmail.com: Tuplets collide with notes outside the staff http://code.google.com/p/lilypond/issues/detail?id=992 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 992 in lilypond: Tuplets collide with notes outside the staff

Comment #7 on issue 992 by mts...@gmail.com: Tuplets collide with notes outside the staff http://code.google.com/p/lilypond/issues/detail?id=992 Issue 2007 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: Issue 992 in lilypond: Tuplets collide with notes outside the staff

Comment #8 on issue 992 by gra...@percival-music.ca: Tuplets collide with notes outside the staff http://code.google.com/p/lilypond/issues/detail?id=992 oops. ok. Could somebody add a little note to both regtests, indicating that we know that they are broken Put the text inside

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-new -Fixed_2_15_14 fixed_2_15_14 Comment #16 on issue 1855 by tdaniels...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 (No comment was entered for this change

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: Fixed_2_15_14 Comment #14 on issue 1855 by colinpkc...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: Patch-new Comment #12 on issue 1855 by mts...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855#c12 Prevents nested tuplets from colliding. http://codereview.appspot.com/4808082

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Status: Fixed Comment #13 on issue 1855 by mts...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Fixed with 2bf0066ec032cdea3897dd66145c752b82ccb865. ___ bug-lilypond

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-countdown Patch-push Comment #11 on issue 1855 by colinpkc...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Counted down to 20110928 ___ bug-lilypond

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-review Patch-countdown Comment #10 on issue 1855 by colinpkc...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 (No comment was entered for this change

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-new Patch-review Comment #9 on issue 1855 by pkx1...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Passes make and some reg tests show as before - attached. James Attachments: Screenshot.png

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-needs_work Patch-new Comment #8 on issue 1855 by percival.music.ca: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Mike thinks this is now ready. ___ bug-lilypond

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-review Patch-needs_work Comment #7 on issue 1855 by percival.music.ca: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Mike has more work to do on this one. ___ bug

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-review Patch-needs_work Comment #4 on issue 1855 by tdaniels...@googlemail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 The new version is wrong. The tuplet nesting should be the same in both bars

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-needs_work Patch-review Comment #6 on issue 1855 by tdaniels...@googlemail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 You're right, Reinhold. Perhaps I hadn't quite woken up earlier :) LGTM now

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-needs_work Patch-new Comment #2 on issue 1855 by pkx1...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 (No comment was entered for this change.) ___ bug

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-new Patch-review Comment #3 on issue 1855 by pkx1...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 passes make, some trivial reg test differences but one is very different and I have attached

Issue 1855 in lilypond: Prevents nested tuplets from colliding

Status: Accepted Owner: mts...@gmail.com Labels: Type-Enhancement Patch-new New issue 1855 by pkx1...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 http://codereview.appspot.com/4808082

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Updates: Status: Verified Comment #6 on issue 1720 by philehol...@googlemail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 (No comment was entered for this change

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Updates: Status: Fixed Labels: -Patch-needs_work fixed_2_15_7 Comment #5 on issue 1720 by n.putt...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Updates: Labels: -Patch-review -CD-110718 Patch-needs_work Comment #4 on issue 1720 by colinpkc...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 Taken off countdown: Neil has suggested

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Updates: Labels: CD-110718 Comment #3 on issue 1720 by colinpkc...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 (No comment was entered for this change

Issue 1745 in lilypond: Strange vertical space above TupletBracket when moving it for the sake of cross-staff beamed tuplets

Status: Accepted Owner: Labels: Type-Defect Priority-Medium New issue 1745 by brownian.box: Strange vertical space above TupletBracket when moving it for the sake of cross-staff beamed tuplets http://code.google.com/p/lilypond/issues/detail?id=1745 Reported by David Nalesnik, see here

Re: Issue 1745 in lilypond: Strange vertical space above TupletBracket when moving it for the sake of cross-staff beamed tuplets

Comment #1 on issue 1745 by brownian.box: Strange vertical space above TupletBracket when moving it for the sake of cross-staff beamed tuplets http://code.google.com/p/lilypond/issues/detail?id=1745 For the record -- tuplet number placement is a subject of issue 696

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Updates: Status: Started Labels: Priority-Medium Patch-review Comment #2 on issue 1720 by n.putt...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 (No comment was entered

Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Comment #1 on issue 1720 by n.putt...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 Issue 1651 has been merged into this issue. ___ bug-lilypond

Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

Status: New Owner: mts...@gmail.com Labels: Type-Collision New issue 1720 by pkx1...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 \context Voice \relative c'' { \time 2/4 \times 2/3 { r c

tuplets and quotation - impossible to remove bracket without removing numbers

I'm not top posting. Dear webmaster, A remark concerning the use of tuplets in quotation : The variable Score.quotedCueEventTypes permit to chose wich event will be shown in quotations. But it is impossible to remove separatly tuplet brakets and tuplet numbers, at least with quarter notes

Re: tuplets and quotation - impossible to remove bracket without removing numbers

On 25 July 2010 18:47, Jean-François Lucarelli j-f.lucare...@espace-midi.com wrote: The variable Score.quotedCueEventTypes permit to chose wich event will be shown in quotations. But it is impossible to remove separatly tuplet brakets and tuplet numbers, at least with quarter notes and

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Updates: Status: Verified Comment #18 on issue 995 by brownian.box: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 (No comment was entered for this change

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Comment #14 on issue 995 by pkx1...@hotmail.com: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Can you be more specific and say why? james ___ bug-lilypond mailing

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Comment #15 on issue 995 by brownian.box: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Why what?-) Why unreadable? Well, yes, this can be an arguable thing. Anyway, take a look, please: -8

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Updates: Status: Fixed Labels: fixed_2_13_24 Comment #16 on issue 995 by percival.music.ca: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 *sigh* I was wondering what would happen here. After

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Comment #17 on issue 995 by pkx1...@hotmail.com: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Thank you. I just wanted to be clear that the issue was ony one of 'text formatting' and not something

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Updates: Status: Accepted Labels: -fixed_2_13_23 Comment #13 on issue 995 by brownian.box: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Well, since here is no any other opinion (for last 42 hours

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Comment #12 on issue 995 by brownian.box: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 1.2.1 Writing rhythms: http://lilypond.org/doc/v2.13/Documentation/notation/writing-rhythms#tuplets --- would be *much

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Comment #10 on issue 995 by pkx1...@hotmail.com: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Thanks, patch added. Please check it as it compiles ok but I had an error from lilygit after it had made the patch

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Updates: Status: Fixed Labels: fixed_2_13_23 Comment #11 on issue 995 by percival.music.ca: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Thanks, committed and will be pushed in a few minutes

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Updates: Owner: --- Comment #9 on issue 995 by percival.music.ca: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Hmm. Actually, I was thinking about Learning 2.2.1, but I must admit

  1   2   >