Re: Tremolo + Chord Repetition Error

2010-09-10 Thread Urs Liska 

Am 10.09.2010 04:27, schrieb Jay Anderson:

\version "2.13.32"

\new Staff \relative c'
{
   %Causes error:
   8 q q q \repeat tremolo 4 q |

   %This works:
   %8 q q q \repeat tremolo 4  |
}
   

Hi Jay,

I don't see why your first statement should be invalid. The docs say: 
"The chord repetition symbol always remembers the last instance of a 
chord so it is possible to repeat the most recent chord even if other 
non-chorded notes or rests have been added since."


So I assume this is an issue. Reported as 
http://code.google.com/p/lilypond/issues/detail?id=1258


Best
Urs

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

Issue 1258 in lilypond: Chord repetition with "q" gives error when used in tremolo

2010-09-10 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Defect Priority-Low

New issue 1258 by lilyli...@googlemail.com: Chord repetition with "q" gives  
error when used in tremolo

http://code.google.com/p/lilypond/issues/detail?id=1258

\version "2.13.32"

\new Staff \relative c'
{
  %Causes error:
  8 q q q \repeat tremolo 4 q |

  %This works:
  %8 q q q \repeat tremolo 4  |
}

Error:
Interpreting music...
/home/jay/lilypond/usr/share/lilypond/current/scm/lily-library.scm:210:5:
In procedure ly:book-process in expression (process-procedure book
paper ...):
/home/jay/lilypond/usr/share/lilypond/current/scm/lily-library.scm:210:5:
Wrong type (expecting exact integer): ()

---
From the docs one should be able to use "q" as equivalent to repeating the  
chord manually.

So this seems to be a problem with parsing the input (?)


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

Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break

2010-09-10 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Defect Priority-Low

New issue 1259 by lilyli...@googlemail.com: DynamicTextSpanner #'style =  
#'none doesn't work over \break

http://code.google.com/p/lilypond/issues/detail?id=1259

\version "2.13.32"

\score
{
  \new Staff \relative c'
  {
%Works fine over break:
c1\cresc
\break
c1\f

\override DynamicTextSpanner #'style = #'none
c1\cresc
\break
c1\f
  }
}

dts.ly:13:6: programming error: Spanner `DynamicTextSpanner' is not
fully contained in parent spanner. Ignoring orphaned part
c1
  \cresc

As a result the 'cresc' is not printed. The closest issue I could find is
issue #1089

Attachments:
dynamic-text-spanner.png  13.0 KB


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

Re: DynamicTextSpanner is not fully contained in parent spanner

2010-09-10 Thread Urs Liska 

Am 10.09.2010 06:33, schrieb Jay Anderson:

\version "2.13.32"

\score
{
   \new Staff \relative c'
   {
 %Works fine over break:
 c1\cresc
 \break
 c1\f

 \override DynamicTextSpanner #'style = #'none
 c1\cresc
 \break
 c1\f
   }
}

dts.ly:13:6: programming error: Spanner `DynamicTextSpanner' is not
fully contained in parent spanner. Ignoring orphaned part
 c1
   \cresc

As a result the 'cresc' is not printed. The closest issue I could find
is 1089 (http://code.google.com/p/lilypond/issues/detail?id=1089).

-Jay

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

I can't tell if there is some valid reason that this shouldn't be allowed.
So I added is as http://code.google.com/p/lilypond/issues/detail?id=1259

Best
Urs

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

Re: Tempo Segmentation Fault

2010-09-10 Thread Phil Holmes 


"Jay Anderson"  wrote in message 
news:aanlkti==7jnywojnvnssd5xniocj5tbfa0cbkwrox...@mail.gmail.com...

\version "2.13.32"

\score
{
 <<
   \new Staff
   {
 \tempo "Andante" 4=63
 R1
   }
   \new Staff
   {
 R1
   }
 >>
 \layout
 {
 }
}

$ lilypond seg.ly
GNU LilyPond 2.13.32
Processing `seg.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...Segmentation fault

How to make the segmentation fault go away:
- Remove the tempo indication
- Change the multi-measure rest to a note
- Remove the second staff

Thanks for the help!

-Jay


Related to this?

http://code.google.com/p/lilypond/issues/detail?id=1251


--
Phil Holmes
Bug Squad



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

Issue 1260 in lilypond: Crash with \tempo

2010-09-10 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Defect Priority-Critical Regression

New issue 1260 by lilyli...@googlemail.com: Crash with \tempo
http://code.google.com/p/lilypond/issues/detail?id=1260

Reported by Jay Anderson:
\version "2.13.32"

\score
{
  <<
\new Staff
{
  %R1 % inserting this music removes the segfault
  \tempo "Andante" 4=63 % commenting out removes the segfault
  R1
}
\new Staff
{
  R1
}
  >>
  \layout
  {
  }
}

$ lilypond seg.ly
GNU LilyPond 2.13.32
Processing `seg.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...Segmentation fault

---

The crash doesn't happen with one of the following solutions:
- \tempo command is commented out
- the second staff is commented out
- there is some music before the \tempo command

2.12.3 compiles just fine!


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

Re: Tempo Segmentation Fault

2010-09-10 Thread Urs Liska 

Am 10.09.2010 07:29, schrieb Jay Anderson:

\version "2.13.32"

\score
{
   <<
 \new Staff
 {
   \tempo "Andante" 4=63
   R1
 }
 \new Staff
 {
   R1
 }
   >>
   \layout
   {
   }
}

$ lilypond seg.ly
GNU LilyPond 2.13.32
Processing `seg.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...Segmentation fault
   
Thanks for reporting, added as 
http://code.google.com/p/lilypond/issues/detail?id=1260


Just a few remarks:
Changing the whole bar rest to a note doesn't fix it.
When the \tempo command isn't at the beginning of the voice it works 
just fine.


Best
Urs

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

Re: Issue 1260 in lilypond: Crash with \tempo

2010-09-10 Thread lilypond 

Updates:
Status: Invalid

Comment #1 on issue 1260 by lilyli...@googlemail.com: Crash with \tempo
http://code.google.com/p/lilypond/issues/detail?id=1260

Sorry, this is the same as issue #1251.
I didn't find this one because I only searched for open issues (and 1251 is  
already fixed as for 2.13.33)



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

Re: Tempo Segmentation Fault

2010-09-10 Thread Jay Anderson 
On Fri, Sep 10, 2010 at 1:07 AM, Phil Holmes  wrote:
> Related to this?
>
> http://code.google.com/p/lilypond/issues/detail?id=1251

Yep, that's it. I guess I missed it in my searching. Thanks.

-Jay

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

Re: Tempo Segmentation Fault

2010-09-10 Thread Paul Scott 
On Fri, Sep 10, 2010 at 07:32:59AM -0700, Jay Anderson wrote:
> On Fri, Sep 10, 2010 at 1:07 AM, Phil Holmes  wrote:
> > Related to this?
> >
> > http://code.google.com/p/lilypond/issues/detail?id=1251
> 
> Yep, that's it. I guess I missed it in my searching. Thanks.

Most important is workaround:
 
  \once \override Score.MetronomeMark #'non-break-align-symbols = #'()  
  \override Score.MetronomeMark #'break-align-symbols = #'(time-signature)

Paul Scott



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

FW: Automatic beaming global settings

2010-09-10 Thread Carl Sorensen 
The message below shows a bug in the autobeaming code.

Please mark is as a Defect with High priority (perhaps it should be
Critical, rather than high, as it causes an intended new feature not to
work).

Thanks,

Carl

-- Forwarded Message
From: James Worlton 
Date: Fri, 10 Sep 2010 07:35:26 -0600
To: lilypond-user 
Conversation: Automatic beaming global settings
Subject: Automatic beaming global settings

Hello,

I'm trying to define the set of default automatic beamings for a score. The
new beaming function is nice, but it won't let me set multiple rules in a
global variable. Here is what I'm trying to do--I have a rule for 4/4 and a
rule for 3/4 that limits beaming to a quarter note:

\version "2.13.32"
global = {
    \overrideTimeSignatureSettings
    #'Score
    #'(4 . 4)  % time signature fraction
    #'(1 . 4)  % base moment fraction
    #'(1 1 1 1)    % beatStructure
    #'()   % beamExceptions
  
    \overrideTimeSignatureSettings
    #'Score
    #'(3 . 4)  % time signature fraction
    #'(1 . 4)  % base moment fraction
    #'(1 1 1)    % beatStructure
    #'()   % beamExceptions %}
}

music = \relative c' {
    \time 4/4
    \repeat unfold 4 { c8 c c c c c c c }
    \time 3/4
    \repeat unfold 4 { c8 c c c c c }
}

\score {
    \new Staff { 
    \global
    \music 
    }
    \layout { }
}

The problem is that with just one of those rules define in \global,
everything is fine. With the 2 definitions, only the last one takes effect.
I tried putting them in separate variables (\globalFour and \globalThree)
and then calling both in the \new Staff before \music, but that didn't work
either.

Is there a way to do this?

Thanks,
James Worlton

-- End of Forwarded Message


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

Re: FW: Automatic beaming global settings

2010-09-10 Thread Graham Percival 
On Fri, Sep 10, 2010 at 11:10:05AM -0600, Carl Sorensen wrote:
> The message below shows a bug in the autobeaming code.
> 
> Please mark is as a Defect with High priority (perhaps it should be
> Critical, rather than high, as it causes an intended new feature not to
> work).

I believe that this functionality was working in 2.12.3, so it
counts as a Critical regression.

Cheers,
- Graham

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

Re: Automatic beaming global settings

2010-09-10 Thread Carl Sorensen 



On 9/10/10 11:14 AM, "Graham Percival"  wrote:

> On Fri, Sep 10, 2010 at 11:10:05AM -0600, Carl Sorensen wrote:
>> The message below shows a bug in the autobeaming code.
>> 
>> Please mark is as a Defect with High priority (perhaps it should be
>> Critical, rather than high, as it causes an intended new feature not to
>> work).
> 
> I believe that this functionality was working in 2.12.3, so it
> counts as a Critical regression.

Perhaps.  The functionality is not exactly the same, but I'd be fine with a
Critical designation.

Carl


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

Re: Issue 894 in lilypond: lilypond-book fails from the command-line in OSX 10.4

2010-09-10 Thread lilypond 

Updates:
Status: Verified

Comment #19 on issue 894 by percival.music.ca: lilypond-book fails from the  
command-line in OSX 10.4

http://code.google.com/p/lilypond/issues/detail?id=894

meh, I can't be bothered to wait for a proper verification.


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

close voices influence noteheads/ledger lines

2010-09-10 Thread Patrick Schmidt 

Hi all,

when voices get very close to one another ledger lines and/or note  
heads seem to change their behavior. In the following example the  
note head of the c is too far to the right. The ledger lines of the  
notes on the left side of the chord are shorter than normal. The  
ledger line of the f sharp is hardly visible.


\version "2.13.31" % on Mac OS X
\paper{ raggedright = ##t }

musicVoiceOne =  {
  %cis'1
  c'1
  %d'1
  %e'1
}

musicVoiceTwo =   {
r84
}

\score {
\new Staff <<
  \key g\major
  \new Voice {
  \musicVoiceOne
  }
  \new Voice {
  \musicVoiceTwo
  }
  >>
}

HTH,
patrick

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

Re: Automatic beaming global settings

2010-09-10 Thread Carl Sorensen 
This bug is now fixed, so there's no need to open an issue.

Thanks,

Carl


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

Re: DynamicTextSpanner is not fully contained in parent spanner

2010-09-10 Thread Jay Anderson 
On Fri, Sep 10, 2010 at 12:52 AM, Urs Liska  wrote:
> Am 10.09.2010 06:33, schrieb Jay Anderson:
>>
>> \version "2.13.32"
>>
>> \score
>> {
>>   \new Staff \relative c'
>>   {
>>     %Works fine over break:
>>     c1\cresc
>>     \break
>>     c1\f
>>
>>     \override DynamicTextSpanner #'style = #'none
>>     c1\cresc
>>     \break
>>     c1\f
>>   }
>> }
>>
>> dts.ly:13:6: programming error: Spanner `DynamicTextSpanner' is not
>> fully contained in parent spanner. Ignoring orphaned part
>>     c1
>>       \cresc
>>
>
> I can't tell if there is some valid reason that this shouldn't be allowed.
> So I added is as http://code.google.com/p/lilypond/issues/detail?id=1259

This is definitely a hack, but it works for me:

diff --git a/lily/spanner.cc b/lily/spanner.cc
index 32e0d21..827f5d6 100644
--- a/lily/spanner.cc
+++ b/lily/spanner.cc
@@ -112,6 +112,8 @@ Spanner::do_break_processing ()

  bool ok = parent_rank_slice.contains
(bounds[LEFT]->get_column ()->get_rank ());
  ok = ok && parent_rank_slice.contains
(bounds[RIGHT]->get_column ()->get_rank ());
+
+  ok = ok || ly_symbol2scm("none") == get_property ("style");

  if (!ok)
{

I haven't spent the time to understand how things work yet, but this
at least gets me past this problem for now.

-Jay

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