Re: Tempo / tuplet bracket bug

2010-01-25 Thread Valentin Villenave
2010/1/25 Carl Sorensen :
> Nope.  It certainly looks like a bug to me.  Please create a new issue, and
> I'll see if I can get it to work right.

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=996

Cheers,
Valentin


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Tempo / tuplet bracket bug

2010-01-25 Thread Carl Sorensen



On 1/24/10 1:22 PM, "Valentin Villenave"  wrote:

> On Mon, Dec 21, 2009 at 5:36 AM, Trevor Bača  wrote:
>> The following snippet exhibits a bug in the form of contention between
>> metronome mark and tuplet instantiation:
> 
> Thanks, and sorry about the delay. Added as
> http://code.google.com/p/lilypond/issues/detail?id=995
> I think it's probably just a limitation that needs to be documented:
> tuplets must begin with a note or a rest. (I've had strange results
> with \bar as well).
> 
> Your example also showed something odd with the beaming of 2/8
> measures. (see attached) Carl, I believe it was you who worked on
> beaming recently, does this look like the desired/intended default
> behavior to you?

Nope.  It certainly looks like a bug to me.  Please create a new issue, and
I'll see if I can get it to work right.

Thanks,

Carl



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Tempo / tuplet bracket bug

2010-01-24 Thread Valentin Villenave
On Mon, Dec 21, 2009 at 5:36 AM, Trevor Bača  wrote:
> The following snippet exhibits a bug in the form of contention between
> metronome mark and tuplet instantiation:

Thanks, and sorry about the delay. Added as
http://code.google.com/p/lilypond/issues/detail?id=995
I think it's probably just a limitation that needs to be documented:
tuplets must begin with a note or a rest. (I've had strange results
with \bar as well).

Your example also showed something odd with the beaming of 2/8
measures. (see attached) Carl, I believe it was you who worked on
beaming recently, does this look like the desired/intended default
behavior to you?

{
  \time 2/8
 c'8
 c'8
  \times 2/3 {
 c'8
 c'8
 c'8
   }
 c'8
 c'8
}

Cheers,
Valentin
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Tempo / tuplet bracket bug

2009-12-20 Thread Trevor Bača
Hi,

The following snippet exhibits a bug in the form of contention between
metronome mark and tuplet instantiation:


%%% BEGIN TEMPO INSTANTIATION BUG %%%

\version "2.13.9"

\new Staff {
   \time 2/8
   \times 2/3 {
  \tempo 8=52
  c'8 (
  c'8
  c'8
}
   \time 2/8
  c'8
  c'8 )
}

%%% END TEMPO INSTANTIATION BUG %%


The interpreter gives the following warnings:

GNU LilyPond 2.13.9
Processing `0329.ly'
Parsing...
Interpreting music...
programming error: stopped tuplet bracket has left nor right bound.
continuing, cross fingers
0329.ly:10:10: warning: unterminated slur
  c'8
  (
0329.ly:16:10: warning: cannot end slur
  c'8
  )
Preprocessing graphical objects...
Solving 1 page-breaking chunks...[1: 1 pages]
Drawing systems...

And the output is attached here as tuplet-bracket-bound-bug.png.


The problem apparently has to do with the lexical spot at which the tempo
mark instantiates. Moving the tempo mark prior to the tuplet \times command
provides a workaround:

%%% BEGIN WORKAROUND %%%

\version "2.13.9"

\new Staff {
   \time 2/8
   \tempo 8=52
   \times 2/3 {
  c'8 (
  c'8
  c'8
}
   \time 2/8
  c'8
  c'8 )
}

%%% END WORKAROUND %%%


Note that what makes this one particularly slippery is that the output from
the buggy example (shown in the png attached here) is actually syntactically
wrong: the measure of 2/8 prints with three eighth notes (because the tuplet
bracket goes missing). The rhythmic inaccuracy is easy enough to spot in
this pared-down example; but in a situation of considerably more rhythmic
complexity this can be lethal. (In the realworld score that I am working on
that surfaced the bug it was, in fact, only the very visible absence of an
extended slur that made this one possible to find.)


Trevor.


-- 
Trevor Bača
trevorb...@gmail.com
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond