Bruce McIntyre | 1 Jun 09:02 2004
Picon

piece field lilypond 2.3.3

Hi,

As you can probably see, the piece field in the headers of les nereides
http://lilypond.org/doc/v2.3/input/out-www/les-nereides-page1.png

and the Solo Cello Suite 
http://lilypond.org/doc/v2.3/input/mutopia/J.S.Bach/out-www/baerenreiter-sarabande-page1.png
are printed twice with lilypond 2.3.3

Cheers,
Bruce
Erik Sandberg | 1 Jun 11:52 2004
Picon
Picon

Re: LilyPond 2.2.2 is out

On Tuesday 01 June 2004 00.36, Han-Wen Nienhuys wrote:
> erik.sandberg.9195 <at> student.uu.se writes:
> > On Monday 31 May 2004 20.48, you wrote:
> > > erik.sandberg.9195 <at> student.uu.se writes:
> > > > rest-collision:
> > > >  The code gives a warning in 2.3 cvs, but it still gives incorrect
> > > > output. Is
> > >
> > > What output do you expect?
> >
> > I would expect <<r \\ s \\ r>> to give two rests above each other; one
> > for voice 1 and one for voice 3. However, I strongly suspect that I have
> > misunderstood something. Have I?
>
> Dunno. Things get rather crowded in that case, since the v3 rest can
> not be at the bottom of the staff. To tell the truth, I haven't seen
> this in practice (then again, I haven't specially looked for it
> either).

I don't understand.. Apparently you can typeset
<<r\\r\\r>>
but you mean there are problems with
<<r\\s\\r>>
? To me this looks easier to do, in any case you could just take r\\r\\r and 
make the voiceTwo rest invisible. Would IMO be better than a warning + 
possibly incorrect output.

BTW, I just discovered that 2.2.1 crashes on the score
\score \note {{<<r\\r>> <<r\\s\\r>> <<r\\r\\r>>}}
with a msg
(Continue reading)

John Williams | 1 Jun 17:17 2004

Re: lilypond-book filename fragment option

On Mon, 31 May 2004, Han-Wen Nienhuys wrote:

> williams <at> tni.com writes:
> > I was able to fix this in lilypond-book-2.0.1 with the patch below.  It
> > then used "xyzzy" as the basename for the whole process (.ly .tex .dvi
> > .eps .png etc).  This patch saved my project, since python was choking on
> > the size of my source file.  I had to break it into smaller pieces for
>
> lilypond-book in 2.2 will not choke on long files, if you break them
> in parts using \include.  Why do you need extra features, then?

Translation: lilypond-book still chokes on long files.  The workaround is
to break them in parts using \include.

Unfortunately that workaround doesn't work for large html files.

I would have thought the benefit of non-random filenames would be
self-evident, and I provided an example of when it was specifically
needed.
Han-Wen Nienhuys | 1 Jun 20:12 2004
Picon
Picon

Re: lilypond-book filename fragment option

williams <at> tni.com writes:
> > > then used "xyzzy" as the basename for the whole process (.ly .tex .dvi
> > > .eps .png etc).  This patch saved my project, since python was choking on
> > > the size of my source file.  I had to break it into smaller pieces for
> >
> > lilypond-book in 2.2 will not choke on long files, if you break them
> > in parts using \include.  Why do you need extra features, then?
> 
> Translation: lilypond-book still chokes on long files.  The workaround is
> to break them in parts using \include.

Can you provide an example of a file that chokes 2.2 lilypond-book ?

> Unfortunately that workaround doesn't work for large html files.
> 
> I would have thought the benefit of non-random filenames would be
> self-evident, and I provided an example of when it was specifically
> needed.

I know, but I prefer to solve the underlying problem if possible.

--

-- 

 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen 
Han-Wen Nienhuys | 1 Jun 20:17 2004
Picon
Picon

Re: LilyPond 2.2.2 is out

erik.sandberg.9195 <at> student.uu.se writes:
> > > misunderstood something. Have I?
> >
> > Dunno. Things get rather crowded in that case, since the v3 rest can
> > not be at the bottom of the staff. To tell the truth, I haven't seen
> > this in practice (then again, I haven't specially looked for it
> > either).
> 
> I don't understand.. Apparently you can typeset
> <<r\\r\\r>>
> but you mean there are problems with
> <<r\\s\\r>>
> ? To me this looks easier to do, in any case you could just take r\\r\\r and 

The rest-collision is rather old and dates from the time that we
didn't look closely at scores. In  fact, I am pleasantly surprised
that

 <<r4 \\ r8 \\ r16 \\ r32>>

seems to give a meaningful result at all. I'll put this bug back into
my mental pipeline.

> with a msg
> lilypond-bin: ../flower/include/array.hh:149: void *& Array<void 
> *>::elem_ref(int) const: Assertion `i >=0&&i<size_' failed.

works for me (2.2.2)

--

-- 
(Continue reading)

Han-Wen Nienhuys | 1 Jun 22:22 2004
Picon
Picon

piece field lilypond 2.3.3

bmcintyre <at> primus.com.au writes:
> Hi,
> 
> As you can probably see, the piece field in the headers of les nereides
> http://lilypond.org/doc/v2.3/input/out-www/les-nereides-page1.png

thanks, fixed.

> http://lists.gnu.org/mailman/listinfo/bug-lilypond

--

-- 

 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen 
Han-Wen Nienhuys | 1 Jun 22:22 2004
Picon
Picon

set-staff-size 2.3.2

bmcintyre <at> primus.com.au writes:
> #(set-global-staff-size x) doesn't change the staff size in 2.3.2; only
> notes are affected.

seems to work in 2.3.3, over here.

--
 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen 
Bertalan Fodor | 2 Jun 13:14 2004
Picon

Point-and-click problems

Hello,

There are two serious problems with the point-and-click feature (2.2.0) 

- At chords the source link gets to src:0:0.
- Tab characters are considered as 8 characters and not 1

See \input\mutopia\F.Schubert\standchen.ly

Bert
John Williams | 2 Jun 18:05 2004

Re: lilypond-book filename fragment option

On Tue, 1 Jun 2004, Han-Wen Nienhuys wrote:
> > > lilypond-book in 2.2 will not choke on long files, if you break them
> > > in parts using \include.  Why do you need extra features, then?
>
> Can you provide an example of a file that chokes 2.2 lilypond-book ?

I tested files of up to 1 MB is size with lilypond-book-2.3.1, and they
all worked, so it looks like that problem is fixed on recent versions.

> > I would have thought the benefit of non-random filenames would be
> > self-evident, and I provided an example of when it was specifically
> > needed.
>
> I know, but I prefer to solve the underlying problem if possible.

I still would like to be able to name my .png files.  Would you accept a
patch to implement that feature?

~ John Williams
Mats Bengtsson | 3 Jun 18:58 2004
Picon
Picon

Re: LilyPond 2.2.2 is out

There's at least one serious bug left in 2.2.2, namely that
lilypond-book doesn't work correctly on LaTeX documents when
run in Cygwin.

What happens is that lilypond-book copies the header of the LaTeX file
and adds a small dummy body that is run through latex to figure out what
the line width is. The problem is that there is no such thing as
/dev/stdin in Cygwin, so the command
latex "\\nonstopmode \input /dev/stdin"
breaks which results in the setting linewidth=0pt in the .ly file
so all the music ends up on a single long line without any line breaks.

Example file:

\documentclass[a4paper]{article}
\begin{document}
\begin{lilypond}
\score{\notes\relative c'{
   \repeat unfold 10 { c d e g }
}}
\end{lilypond}
\end{document}

    /Mats

Erik Sandberg wrote:
> On Monday 31 May 2004 18.57, Erik Sandberg wrote:
> 
>>On Monday 31 May 2004 16.47, Han-Wen Nienhuys wrote:
>>
(Continue reading)


Gmane