Re: Huge memory usage!

[Joshua Koo]

Hi,

I think many of the failed barchecks was because of something like
\acciaccatura \stemDown cis32 a4

I will have to change them to 
\acciaccatura { \stemDown cis32 } a4

also, having more than 1  \acciaccatura causes an error,
example, \acciaccatura cis32 \acciaccatura dis32 a4

therefore,
  \time 6/8
  cis( b4) \acciaccatura \times 2/3 { \stemUp cis32([ \acciaccatura b 
\acciaccatura a] }
  b8.)[ cis16-. d8-.] |

has to be changed into

\time 6/8
        cis8( b4) \acciaccatura { \times 2/3 {  cis32([ b a] } }
        b8.)[ cis16-. d8-.]

As for,

\time 6/8
r1

its because in noteworthy composer, thats the value for a full bar rest.

Is there any way to place a fullbar rest just by detecting the time signature? 
so there wont need to figure out to use R1 or R2 so on...

:)_Joshua

======= At 2005-04-28, 00:01:26 you wrote: =======

>Han-Wen Nienhuys <address@hidden> writes:
>> 451 bars is a pretty large for an orchestral score, 
>
>that's true, but lily should handle it. and indeed it does. the problem
>was actually this code:
>
>  \time 6/8
>  cis( b4) \acciaccatura \times 2/3 { \stemUp cis32([ \acciaccatura b 
> \acciaccatura a] }
>  b8.)[ cis16-. d8-.] |
>
>it makes lily hang (I filed a bug report)
>
>> and 400 meg isn't extraordinary.
>
>the rest of the piece is compiled using less than 200 megs here (my
>system is similar of Joshua's)
>
>> Op ma, 25-04-2005 te 00:32 +0800, schreef Joshua Koo:
>
>>> oh ya. i was trying to lilypond a file using the nwc2ly converter im
>>> developing and. tried to convert that beethoven 7th symphony movement
>>> 1.
>
>from the file you sent, it seems this tool generates wrong code. for
>instance, it generates
>
>\time 6/8
>r1
>
>when it should generate r2. for a full bar, or better yet, R2.
>
>Pedro
>

= = = = = = = = = = = = = = = = = = = =