Re: More than 5 nested tuplets of large value hangs Lilypond permanently
Am 13.11.2016 um 07:28 schrieb mclaren: > \version "2.18.2" > > << > > \new Staff { > \clef "treble" > > % This is a Nancarrow-style 1% acceleration. It hangs Lily permanently with > message "Preprocessing graphical objects..." > % One fewer nested tuplet runs without error. To prove this, comment out > next line, and uncomment the line after that. > \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 > \tuplet 100/99{a8 \tuplet 100/99{a8}} > > > %\tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 > \tuplet 100/99{a8} > } > I have reformatted the example to make it more accessible and readable. I have the impression this actually hits an internal calculating limitation. Could please someone check this? And if that's so: a) should 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-style 1% acceleration. It hangs Lily permanently with % message "Preprocessing graphical objects..." % One fewer nested tuplet runs without error. To prove this, comment out %next line, and uncomment the line after that. \tuplet 100/99 { a8 \tuplet 100/99 { a8 \tuplet 100/99 { a8 \tuplet 100/99 { a8 \tuplet 100/99 { % Prepend the next line with an additional percent to uncomment the fifth tuplet %{ a8 \tuplet 100/99{ a8 } %} } } } } } } > > > > > -- > View this message 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 mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
More than 5 nested tuplets of large value hangs Lilypond permanently
\version "2.18.2" << \new Staff { \clef "treble" % This is a Nancarrow-style 1% acceleration. It hangs Lily permanently with message "Preprocessing graphical objects..." % One fewer nested tuplet runs without error. To prove this, comment out next line, and uncomment the line after that. \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8}} %\tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8 \tuplet 100/99{a8} } >> -- View this message 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
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. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how nested tuplets are rendered after importing into lilypond. Urs I can't tell from the LilyPond documentation whether MusicXML - either import, export, or both - is explicitly supported by LilyPond. Before I submit this as an issue, can someone please confirm for me that LilyPond does support MusicXML? I appreciate your time and help, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how nested tuplets are rendered after importing into lilypond. Urs Thanks for the report, Urs. (And thanks for the clarification, as well!) This has been submitted as Issue 4434 : https://code.google.com/p/lilypond/issues/detail?id=4434 All the best, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 be properly read by Finale but not be reimported through musicxml2ly. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how nested tuplets are rendered after importing into lilypond. Urs I can't tell from the LilyPond documentation whether MusicXML - either import, export, or both - is explicitly supported by LilyPond. Before I submit this as an issue, can someone please confirm for me that LilyPond does support MusicXML? Well, the musicxml2ly script ships with LilyPond just like lilypond-book, isn't it? I appreciate your time and help, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 nested tuplets are rendered after importing into lilypond. Urs ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/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 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/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 mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/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.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 129 KB Screenshot-1.png 59.4 KB Screenshot-2.png 55.7 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/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-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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. Only the notes and the slopes of the brackets should be different, as in the previous version. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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 it here for comparison. Otherwise looks ok. James Attachments: Screenshot.png 74.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Bus error on skip within doubly-nested tuplets
Hi, A skip within a doubly-nested tuplet causes a bus error. For example ... %%% BEGIN BUG %%% \version 2.9.26 \new Staff { \times 2/3 { \times 2/3 { c'8 s4 % THIS IS THE OFFENDING EXPRESSION } c'4 c'4 c'4 } } %%% END BUG %%% ... generates the following: GNU LilyPond 2.9.26 Processing `0016.ly' Parsing... Interpreting music... Preprocessing graphical objects... Bus error The skip is required for the error; changing the note to a skip like this interprets fine: %%% BEGIN OK %%% \version 2.9.26 \new Staff { \times 2/3 { \times 2/3 { c'8 c'4 % THIS IS OK } c'4 c'4 c'4 } } %%% END OK %%% The error seems somewhat important, given that interpretation stops completely. -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Nested tuplets are automatically positioned--no more !
karim haddad schreef: hello Unfortunately Trevor's wonderful feature doesn't work good with the latest version 2.9.5-1 (i am using macosxppc version) THe tuplets are nested in inverse fashion that is no good. this is definitively a bug... Erik, can you have a look at this? I believe that this is related to your changes of tuplet-engraver.cc -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
nested tuplets
Hello First of all , i wish to say thanx to everybody working on the dev of lily. the last version is great. Ok, now for some remarks. the nested tuplets feature which is really great has however one inconvenient. As we can see in the news doc, when these occur the brackets are too tight i.e they are too close one on the other and sometimes very hard to read. Is there a way to add some extra space between them. This would be great. Another question , when using \ChoirStaff is there a way at the end of the system to put a final barline all acrooss the staffs as in Staff group. thanx Karim ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: nested tuplets
On 4/5/06, karim haddad [EMAIL PROTECTED] wrote: Hello First of all , i wish to say thanx to everybody working on the dev of lily. the last version is great. Ok, now for some remarks. the nested tuplets feature which is really great has however one inconvenient. As we can see in the news doc, when these occur the brackets are too tight i.e they are too close one on the other and sometimes very hard to read. Is there a way to add some extra space between them. This would be great. Hi Karim, Two good things help with tuplet bracket positioning: 1. You can use \override TupletBracket #'staff-padding = #5.0 % or whatever value you like ... to move the whole nest of brackets up to so some uniform level above the staff; this will set all the *innermost* brackets level with each other, meaning that toplevel brackets will just stack higher and higher. 2. You can use \override TupletBracket #'padding = #2.3 % or whatever value you want ... to adjust the exact spacing that you're talking about *between* the brackets in the nest. I find values between #1.5 and #3.0 work nicely. Remember, too, if you're doing a lot of things with nested prolation that you can control the graphic object properties of the tuplet number with the TupletNumber grob (which is now independent of the TupletBracket grob). And you can force the tuplet number as a fraction with \set tupletNumberFormatFunction = #fraction-tuplet-formatter. Hope this helps; the total set of time-notation features in lily now is amazing. I can't think of a better vehicle for sketching rhythmic material for a piece. If you find something you *can't* set, please say something. -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: nested tuplets
Dear Trevor Great Thanx it works ! it was the bracket padding that i have missed. I will let you know if i encounter some impossible notation. But for the time being, Lily is the best. Thanx to all again . Karim On 4/5/06, karim haddad [EMAIL PROTECTED] wrote: Hello First of all , i wish to say thanx to everybody working on the dev of lily. the last version is great. Ok, now for some remarks. the nested tuplets feature which is really great has however one inconvenient. As we can see in the news doc, when these occur the brackets are too tight i.e they are too close one on the other and sometimes very hard to read. Is there a way to add some extra space between them. This would be great. Hi Karim, Two good things help with tuplet bracket positioning: 1. You can use \override TupletBracket #'staff-padding = #5.0 % or whatever value you like ... to move the whole nest of brackets up to so some uniform level above the staff; this will set all the *innermost* brackets level with each other, meaning that toplevel brackets will just stack higher and higher. 2. You can use \override TupletBracket #'padding = #2.3 % or whatever value you want ... to adjust the exact spacing that you're talking about *between* the brackets in the nest. I find values between #1.5 and #3.0 work nicely. Remember, too, if you're doing a lot of things with nested prolation that you can control the graphic object properties of the tuplet number with the TupletNumber grob (which is now independent of the TupletBracket grob). And you can force the tuplet number as a fraction with \set tupletNumberFormatFunction = #fraction-tuplet-formatter. Hope this helps; the total set of time-notation features in lily now is amazing. I can't think of a better vehicle for sketching rhythmic material for a piece. If you find something you *can't* set, please say something. -- Trevor BaÄ?a [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond