Am 13.11.2016 um 15:57 schrieb Urs Liska:
> % One fewer nested tuplet runs without error. To prove this, comment out
> %next line, and uncomment the line after that.
Sorry, I forgot to remove this comment.
The proper way to check is to comment out the innermost tuplet by
editing the multilin
0/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
}
%}
}
}
}
}
}
}
>
>
>
>
> --
> Vi
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
On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska 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.
>
>
Am 05.06.2015 um 15:09 schrieb Urs Liska:
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
Am 5. Juni 2015 13:55:04 MESZ, schrieb Ralph Palmer :
>On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska 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 pro
On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska 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.
>
>
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
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
Updates:
Status: Verified
Comment #15 on issue 1855 by philehol...@googlemail.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
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
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
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
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
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
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
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
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
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 :
Comment #5 on issue 1855 by reinhold...@gmail.com: Prevents nested tuplets
from colliding
http://code.google.com/p/lilypond/issues/detail?id=1855
Sorry, what am I missing? There are two measures added to the beginning,
but the last two measures exactly match the previous version, sans the
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
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
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
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
Trevor Bača escreveu:
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
}
}
http://code
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 f
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 t
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...
Trevor's example:
\paper {
#(define dump-extents #t)
ragged-right =
;>
>> 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 i
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
&
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
31 matches
Mail list logo
