Re: Wrong type with polyphony, manual beams, dotted rests and notes

2008-03-28 Thread Mats Bengtsson 

Again, I can confirm the crash with version 2.10.33 in Linux.
Version 2.11 works well also with this example.
Time to upgrade?

   /Mats

Marcus Macauley wrote:

This one is weird. Apparently some combinations of polyphony, manual
beams, and a dotted rest followed by a note, trigger a Wrong type
error (Windows XP here). Many variations I've tried still trigger the
error, while other variations don't. You can experiment for yourself.

Unlike the stemlets-over-rests-only bug which I submitted yesterday,
this one actually interferes with real-world usage.

The complete error message in context is:

Preprocessing graphical objects...ERROR: Wrong type (expecting real
number): #unknown-type (0x27 . 0x13c9e48) @ 0x35bbb80

Marcus


% The following results in an ERROR: Wrong type (expecting real number)
% even if the beamed rest is lengthened or shortened (as long as it's dotted)
% even if the beamed note is lengthened or shortened
% even if (certain) rests are inserted between, before, or after those two.
% The manual beaming and the polyphony both appear to be necessary.
\version 2.10.33
\paper{ ragged-right=##t }
{ 
{ r8.[ b16] } \\ % originally: r8[ r16. r32 r8 r16 r16 b8 r32 r16. r8]
{ r4 }  } % originally: r4 r r r



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


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



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

Re: no compile on version 2.11.43 for Windows XP

2008-03-28 Thread Trevor Daniels 



Date: Fri, 28 Mar 2008 01:20:41 -0300
From: Han-Wen Nienhuys [EMAIL PROTECTED]
Subject: Re: no compile on version 2.11.43 for Windows XP
To: Tom Richard [EMAIL PROTECTED]
Cc: bug-lilypond@gnu.org
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=UTF-8

Can you try 2.11.43-2 (uploaded today)?


Works fine on Vista Home Premium.  (At least, the fault with 2.11.43-1
has gone and a few small snippets compiled correctly.)


2008/3/26, Tom Richard [EMAIL PROTECTED]:

Version 2.10.33 for Windows XP compiles great. I have tried re-installing
 2.11.43 3 times, carefully un-installing previous version every time.

--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
Trevor D 




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

Another arpeggio collision

2008-03-28 Thread Jay Anderson 
When using cross staff arpeggios a collision can occur if accidentals
cause the arpeggio to be moved to the left too much.

(Possible related issue: 556)

Thanks!

-Jay

\version 2.11.42

\paper
{
  ragged-right = ##t
}

\book
{
  \new PianoStaff
  
\set PianoStaff.connectArpeggios = ##t
\new Staff=RH \relative c''
{
  r2. ges aes c ges'4\arpeggio |
}

\new Staff=LH \relative c'
{
  \repeat unfold 12 aes16 ees aes c4\arpeggio |
}
  
}

It is interesting to note that this does not occur with one staff and
two voices:

  \new Staff
  \with
  {
\consists Span_arpeggio_engraver
  }
  \relative c''
  {
\set Staff.connectArpeggios = ##t

  {r2. ges aes c ges'4\arpeggio |}
  \\
  {\repeat unfold 12 aes,16 ees aes c4\arpeggio |}

  }


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

vim no formatting for \f

2008-03-28 Thread Jay Anderson 
I would expect \f to look similar to other dynamic markings like \p or
\mf when using vim. Adding it to the
.../usr/share/lilypond/current/vim/syntax/lilypond-words.vim will fix
this. Thanks!

-Jay


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

Re: Another arpeggio collision

2008-03-28 Thread Neil Puttock 
Hi Jay,

I've noticed this happening recently. As a workaround I've been
setting #'infinite-spacing-height = ##t whenever it occurs.

Here's a related example with one stave and two voices where the
arpeggio collides with the time signature:

\version 2.11.42
\paper { ragged-right = ##t }
\new Staff
 \with
 {
   \consists Span_arpeggio_engraver
 }
 \relative c''
 {
   \set Staff.connectArpeggios = ##t
   
 {ces\arpeggio}
 \\
 {es,\arpeggio }
   
 }

Regards,
Neil
attachment: foo.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Another arpeggio collision

2008-03-28 Thread Jay Anderson 
Great! Thanks that worked wonderfully. Thanks!

On Fri, Mar 28, 2008 at 2:41 PM, Neil Puttock [EMAIL PROTECTED] wrote:
 Hi Jay,

  I've noticed this happening recently. As a workaround I've been
  setting #'infinite-spacing-height = ##t whenever it occurs.

  Here's a related example with one stave and two voices where the
  arpeggio collides with the time signature:


  \version 2.11.42
  \paper { ragged-right = ##t }

 \new Staff
   \with
   {
\consists Span_arpeggio_engraver
   }
   \relative c''
   {
\set Staff.connectArpeggios = ##t

  {ces\arpeggio}
  \\
  {es,\arpeggio }

   }

  Regards,
  Neil



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