Re: bugs?
Am So., 9. Dez. 2018 um 23:27 Uhr schrieb Alex Machuca : > > Hi guy! I really love all the job you have done. I wanted just to share some > kind of input You didn't. > that do not correspond to the sheets outputed by Llilypond. Just some kind of > wrong output. > > what do I need to do? I'd suggest to read http://lilypond.org/tiny-examples.html And ask on the user-list, providing a tiny example. Cheers, Harm > > Alex > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in web.pdf
> If I understand correctly, there are two different problems. > > The former one is that XeTeX does not support `/Rotate`. > It occurs in both your environment and the GUB environment. > [...snip...] > > But, the former one seems to be difficult to solve. I've created the patch to solve the former one. https://sourceforge.net/p/testlilyissues/issues/5128/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in web.pdf
> No, it's not packaged for Fedora. > Should I install it from source? > https://github.com/trueroad/extractpdfmark No. I've found out the difference between your environment and the GUB environment. Thank you. If I understand correctly, there are two different problems. The former one is that XeTeX does not support `/Rotate`. It occurs in both your environment and the GUB environment. The latter one is that Ghostscript is "too clever" to rotate pages automatically with "majority decision". It occurs only in GUB environment which has `extractpdfmark` and Ghostscript 9.20, and it does not occur in your environment which does not have `extractpdfmark`. If you would like to reproduce the latter one, Debian stretch and Ubuntu 17.04 have `extractpdfmark` package. Anyway, I've created a patch to solve the latter one. https://sourceforge.net/p/testlilyissues/issues/5126/ But, the former one seems to be difficult to solve. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in web.pdf
Il giorno mer 26 apr 2017 alle 17:29, Masamichi Hosoda ha scritto: What's interesting is that my locally compiled web.pdf (with Xetex version 2017.03.30:1237) displays page 10 almost correctly, in that the page stays A4 vertical but the image is rotated 90° counter-clockwise. See attached the extracted page. web.pdf on lilypond.org was built with a more recent version of Xetex. I think that it is not caused by the difference in XeTeX version. Does your environment have `extractpdfmark`? No, it's not packaged for Fedora. Should I install it from source? https://github.com/trueroad/extractpdfmark GUB has `extractpdfmark` and Ghostscript 9.20. In such environments, PDFs are processed by Ghostscript after extractpdfmark. At that time, Ghostscript seems to rotate by "majority decision". http://latex.org/forum/viewtopic.php?f=45&t=9783&sid=fe022a82377196e9b0fb5ff24955ecf9 http://stackoverflow.com/questions/3089773/how-to-change-page-orientation-of-pdf-ghostscript-or-postscript-solution-neede `-dAutoRotatePages=/None` option for Ghostscript seems to need. This will prevent landscape pages like lilypond.org web.pdf page 10. However, it can not prevent image rotation like your web.pdf page 10. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in web.pdf
>> What's interesting is that my locally compiled web.pdf (with Xetex >> version 2017.03.30:1237) displays page 10 almost correctly, in that >> the page stays A4 vertical but the image is rotated 90° >> counter-clockwise. See attached the extracted page. >> web.pdf on lilypond.org was built with a more recent version of Xetex. I think that it is not caused by the difference in XeTeX version. Does your environment have `extractpdfmark`? GUB has `extractpdfmark` and Ghostscript 9.20. In such environments, PDFs are processed by Ghostscript after extractpdfmark. At that time, Ghostscript seems to rotate by "majority decision". http://latex.org/forum/viewtopic.php?f=45&t=9783&sid=fe022a82377196e9b0fb5ff24955ecf9 http://stackoverflow.com/questions/3089773/how-to-change-page-orientation-of-pdf-ghostscript-or-postscript-solution-neede `-dAutoRotatePages=/None` option for Ghostscript seems to need. This will prevent landscape pages like lilypond.org web.pdf page 10. However, it can not prevent image rotation like your web.pdf page 10. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in web.pdf
>> - PDF page 10 is in landscape (while the document is a regular A4 of >> - course) >> > > This is the actual bug. I've investigated... > If you replace v2.19 with previous versions you can see that previous > builds used PdfTex instead of Xetex and the image was compressed to > fit on the vertical A4 sheet. > > What's interesting is that my locally compiled web.pdf (with Xetex > version 2017.03.30:1237) displays page 10 almost correctly, in that > the page stays A4 vertical but the image is rotated 90° > counter-clockwise. See attached the extracted page. > web.pdf on lilypond.org was built with a more recent version of Xetex. > > Masamichi, any idea of what's going on? In my investigate, if I understand correctly, `Documentation/ly-example/granados.ly` has landscape settings. So `granados.pdf` generated from `granados.ly` has `/Rotate 90`. pdfTeX supports `/Rotate` in including PDFs. Unfortunately, XeTeX does not support it. http://tug.org/pipermail/xetex/2015-November/026197.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in web.pdf
Il giorno dom 16 apr 2017 alle 8:46, Federico Bruni ha scritto: If you give a look at this PDF: http://lilypond.org/doc/v2.19/Documentation/web.pdf you'll see some bugs: - the images not generated by LilyPond have often a poor quality and some of them run out of the page Well, this is not a new issue and depends on the quality of the images used. I guess that we can ignore it. - PDF page 10 is in landscape (while the document is a regular A4 of course) This is the actual bug. I've investigated... If you replace v2.19 with previous versions you can see that previous builds used PdfTex instead of Xetex and the image was compressed to fit on the vertical A4 sheet. What's interesting is that my locally compiled web.pdf (with Xetex version 2017.03.30:1237) displays page 10 almost correctly, in that the page stays A4 vertical but the image is rotated 90° counter-clockwise. See attached the extracted page. web.pdf on lilypond.org was built with a more recent version of Xetex. Masamichi, any idea of what's going on? web-page10.pdf Description: Adobe PDF document ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
On Sun, Nov 25, 2012 at 10:27:40PM -0800, Ben Rudiak-Gould wrote:
> Here's an example:
>
> \version "2.16.1"
> <<
> % expected output: c||ccc, actual output: c||c||c||c||
> { c' \set Staff.whichBar = "||" c' c' c' }
> % expected output: c||ccc|, actual output: c||ccc
> { c' \once \set Staff.whichBar = "||" c' c' c' c' c' c' c' }
> >>
>
Thanks, Ben.
I've created a tracker for this with your tiny example attached.
http://code.google.com/p/lilypond/issues/detail?id=2981
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
Here's an example:
\version "2.16.1"
<<
% expected output: c||ccc, actual output: c||c||c||c||
{ c' \set Staff.whichBar = "||" c' c' c' }
% expected output: c||ccc|, actual output: c||ccc
{ c' \once \set Staff.whichBar = "||" c' c' c' c' c' c' c' }
>>
On Sat, Nov 24, 2012 at 3:56 PM, Colin Hall wrote:
>
> On Sat, Nov 24, 2012 at 10:13:25PM +, Ben Rudiak-Gould wrote:
>> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
>> start-repeat bar in this staff only". What it actually seems to do in 2.16.1
>> is
>> insert a start-repeat bar after every note in that staff until the end of the
>> score. I haven't looked at the code but I guess that it's clearing
>> Timing.whichBar even if whichBar was actually set in a different context.
>>
>> The obvious workaround, \once \set Staff.whichBar = "|:", prints the repeat
>> bar
>> correctly but then never prints any automatic bar lines in that staff until
>> the
>> end of the piece. I think this may be a bug introduced by
>> codereview.appspot.com/4810042, which never unsets a \once \set variable
>> even if
>> it was unset before.
>
> Thanks for the very thorough-going bug report, Ben.
>
> Could you send a tiny example that demonstrates the unexpected
> behaviour?
>
> Cheers,
> Colin.
>
> --
>
> Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
On Sat, 24 Nov 2012 22:16:45 -0800, Keith OHara wrote:
\version "2.16.1"
<< \new Staff {
\once\set Staff.whichBar = "|:"
b2 b2 b2 b2
\once\set Staff.whichBar = ":|:"
b2 b2 b2 b2
\bar"|." }
\new Staff R1*4 >>
<< \new Staff {
b2 b2 b2 b2
\once\set Staff.whichBar = "|:"
b2 b2 b2 b2
\bar"|." }
\new Staff R1*4 >>
The above /does/ give the correct output with version 2.14.2
However, I have not found anyplace in the documentation that promised whichBar
to work when set at the Staff level.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
On Sat, 24 Nov 2012 16:44:15 -0800, Thomas Morley
wrote:
2012/11/25 Keith OHara :
Ben Rudiak-Gould gmail.com> writes:
The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
start-repeat bar in this staff only".
I suppose desired behavior is to have at least one way to change one bar-line
in one staff, preferably the way it was done in version 2.14
Using code: [...]
compiles fine with 2.12.3, 2.14.2, 2.16.0 and [...] 2.17.8
Oops. I oversimplified the example; after looking at so many erroneous
bar-lines, apparently I saw correct ones and thought they were wrong!
\version "2.16.1"
<< \new Staff {
\once\set Staff.whichBar = "|:"
b2 b2 b2 b2
\once\set Staff.whichBar = ":|:"
b2 b2 b2 b2
\bar"|." }
\new Staff R1*4 >>
<< \new Staff {
b2 b2 b2 b2
\once\set Staff.whichBar = "|:"
b2 b2 b2 b2
\bar"|." }
\new Staff R1*4 >>
but gives a segfault with 2.16.0
Use an explicit \new Staff to avoid the segfault --- which I suppose is a
separate bug.<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
2012/11/25 Keith OHara :
> Ben Rudiak-Gould gmail.com> writes:
>
>> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
>> start-repeat bar in this staff only".
>
> I suppose desired behavior is to have at least one way to change one bar-line
> in one staff, preferably the way it was done in version 2.14
> << { R1
>\once\set Staff.whichBar = "|:"
>R1*3 }
> R1*4 >>
> and to have the documentation describe the way that actually works.
>
> Of course the work-around is to explicitly change back
> << { R1
> \set Staff.whichBar = "|:"
> R1
> \unset Staff.whichBar
> R1*2 }
>R1*4 >>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
Using code:
<< {
R1
\once \set Staff.whichBar = ".|:"
R1*3
\break
R1*4
}
{
R1
R1*3
\break
R1*4
}
>>
compiles fine with 2.12.3, 2.14.2, 2.16.0 and, after converting (\bar
"|:" -> \bar ".|:") with 2.17.8
But code
<< {
\once \set Staff.whichBar = "|:"
R1*3
\break
R1*4
}
{
R1*3
\break
R1*4
}
>>
works as expected with 2.12.3 and 2.14.2 but gives a segfault with
2.16.0 and 2.17.8 (again after converting)
log:
GNU LilyPond 2.17.8
Processing `atest-01.ly'
Parsing...
Interpreting music...
warning: forced break was overridden by some other event, should you
be using bar checks?
warning: forced break was overridden by some other event, should you
be using bar checks?
Preprocessing graphical objects...
programming error: Multi_measure_rest::get_rods (): I am not spanned!
continuing, cross fingers
Segmentation fault
Regards,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
Ben Rudiak-Gould gmail.com> writes:
> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
> start-repeat bar in this staff only".
I suppose desired behavior is to have at least one way to change one bar-line
in one staff, preferably the way it was done in version 2.14
<< { R1
\once\set Staff.whichBar = "|:"
R1*3 }
R1*4 >>
and to have the documentation describe the way that actually works.
Of course the work-around is to explicitly change back
<< { R1
\set Staff.whichBar = "|:"
R1
\unset Staff.whichBar
R1*2 }
R1*4 >>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs with \set Staff.whichBar
On Sat, Nov 24, 2012 at 10:13:25PM +, Ben Rudiak-Gould wrote: > The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a > start-repeat bar in this staff only". What it actually seems to do in 2.16.1 > is > insert a start-repeat bar after every note in that staff until the end of the > score. I haven't looked at the code but I guess that it's clearing > Timing.whichBar even if whichBar was actually set in a different context. > > The obvious workaround, \once \set Staff.whichBar = "|:", prints the repeat > bar > correctly but then never prints any automatic bar lines in that staff until > the > end of the piece. I think this may be a bug introduced by > codereview.appspot.com/4810042, which never unsets a \once \set variable even > if > it was unset before. Thanks for the very thorough-going bug report, Ben. Could you send a tiny example that demonstrates the unexpected behaviour? Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs shown in regtests
On Wed, Jul 11, 2012 at 05:35:27PM +0100, Phil Holmes wrote: > Bug squadders. Please have a look at > > http://old.nabble.com/2.15.41-Regtests-td34130283.html > > I believe there are bugs there to be captured. > > Thanks. I've been through the regressions on that web page Phil and read them in conjuction with comments from David, Janek and Keith on lilypond-devel from 8th July. As a result I've created these trackers: http://code.google.com/p/lilypond/issues/detail?id=2684 http://code.google.com/p/lilypond/issues/detail?id=2685 http://code.google.com/p/lilypond/issues/detail?id=2686 Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs in slurred sextuplets
On Mon, Feb 20, 2012 at 1:37 PM, Marc M wrote:
> > I'm not top posting.
>
> % bugs in slurred sextuplets.
> % 1) fingering appear above the slur instead of below.
> % 2) the "6" is written on the beam
> %
> \language "english"
> \version "2.15.30"
> \relative c'' {
> \key d\major
> \times 4/6{ e16-0( fs gs a-1 b cs) }
> \times 4/6{ a16 ( b cs cs-1 d e ) }
> }
>
Thanks for the report, Marc M. This has been submitted as issue 2339 :
http://code.google.com/p/lilypond/issues/detail?id=2339
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
Thank you Carl! > 143709 is invalid. > 153782 is invalid. > 153784 is invalid. Why? > 437267 has been fixed in 2.14. Ok, tagged. > 607431 is accepted as lilypond issue 1683. Ok, forwarded. > 139577 has been fixed. Ok. Closed. > 335828 is a Debian bug, not a LilyPond bug. Ok. > 98659 has been fixed. Ok. Closed. Ciao! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
On 6/7/11 5:42 AM, "Carlo Stemberger" wrote: > The Debian Bug Tracking System contains some bug reports concerning LilyPond, > with short examples. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable > > Could you verify them and in case add them to your track, please? > > Thank you! Carlo, 143709 is invalid. 153782 is invalid. 153784 is invalid. 437267 has been fixed in 2.14. 607431 is accepted as lilypond issue 1683. 139577 has been fixed. 335828 is a Debian bug, not a LilyPond bug. 98659 has been fixed. Hope this helps. Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
Thank you, Colin. If you find something useful please let me know. Ciao! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in Debian
On 11-06-07 05:42 AM, Carlo Stemberger wrote: The Debian Bug Tracking System contains some bug reports concerning LilyPond, with short examples. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable Could you verify them and in case add them to your track, please? Thank you! Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Thanks, Carl. I'll have a look over the list and add anything that is new to us. Colin -- A chief event of life is the day in which we have encountered a mind that startled us. -Ralph Waldo Emerson, writer and philosopher (1803-1882) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs
2008/4/21 christophe Ferveur <[EMAIL PROTECTED]>: > bug : cannot find file for fontconfig cache > > it's to instal lilypond on a eepc assus. Is it possible ? > > I'm french... Bonjour Christophe, there's a special mailing list for French-speaking LilyPonders: http://lists.gnu.org/mailman/listinfo/lilypond-user-fr Installing LilyPond on a EePC should be ok; can you tell us (or on the French list) whether you're running Xandros, Windows or anything else? Which version have you tried to run? How did you install it? etc. Cordialement, V. Villenave ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs on the homepage
Benjamin Drung wrote: > I read the site http://lilypond.org/web/about/name and I found two bugs. > > 1. In the second paragraph there is the word about double: "I also knew about > about a package Rosegarden" > > 2. The link to Rosengarden is wrong. Instead of > http://www.rosegarden-music.com/ > it must be http://www.rosegardenmusic.com/ Thanks, this is fixed. The typo police ;-) Cheers -- John Mandereau <[EMAIL PROTECTED]> ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
I can confirm that I get the same error as you, when running the latest CVS version of LilyPond on Linux. In fact, I get the same error when trying the figured-bass.ly example from the regression test document, so it seems that the figured bass support is completely broken for the moment. /Mats Trent Johnston wrote: - Original Message - From: "Mats Bengtsson" <[EMAIL PROTECTED]> To: "Trent Johnston" <[EMAIL PROTECTED]> Cc: "Graham Percival" <[EMAIL PROTECTED]>; Sent: Monday, August 07, 2006 5:20 PM Subject: Re: Bugs in version 2.9.14 | | | Trent Johnston wrote: | | > | >Thanks Graham, | > | >But since I'm using Windows there has been some problems with python scripts | >not working. So currently I can't get convert-ly to work. I'll have to wait | >until there is some more documentation on the changes. | > | > | See http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00031.html | | /Mats | Thanks Mats, I've got convert-ly working but I'm still getting the following errors. Interpreting music... ERROR: In procedure ly_music_property: ERROR: Wrong type argument in position 1 (expecting music): #) (elements) (duration . #) (origin . #) (figure . 4))((display-methods #) (name . BassFigureEvent) (types general-music event rhythmic-event bass-figure-event)) > ) (length . #) (elements) (duration . #) (origin . #) (figure . 4))((class . bass-figure-event)) > Is the windows version working for anyone else? Trent -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology 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: Bugs in version 2.9.14
- Original Message - From: "Mats Bengtsson" <[EMAIL PROTECTED]> To: "Trent Johnston" <[EMAIL PROTECTED]> Cc: "Graham Percival" <[EMAIL PROTECTED]>; Sent: Monday, August 07, 2006 5:20 PM Subject: Re: Bugs in version 2.9.14 | | | Trent Johnston wrote: | | > | >Thanks Graham, | > | >But since I'm using Windows there has been some problems with python scripts | >not working. So currently I can't get convert-ly to work. I'll have to wait | >until there is some more documentation on the changes. | > | > | See http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00031.html | | /Mats | Thanks Mats, I've got convert-ly working but I'm still getting the following errors. Interpreting music... ERROR: In procedure ly_music_property: ERROR: Wrong type argument in position 1 (expecting music): #) (elements) (duration . #) (origin . #) (figure . 4))((display-methods #) (name . BassFigureEvent) (types general-music event rhythmic-event bass-figure-event)) > ) (length . #) (elements) (duration . #) (origin . #) (figure . 4))((class . bass-figure-event)) > Is the windows version working for anyone else? Trent ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
Frédéric Chiasson wrote: P.S. Why does this usenet top-posting warning always appear when I paste some part of my program? It is quite annoying! See http://lists.gnu.org/archive/html/bug-lilypond/2006-05/msg00038.html /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
Trent Johnston wrote: Thanks Graham, But since I'm using Windows there has been some problems with python scripts not working. So currently I can't get convert-ly to work. I'll have to wait until there is some more documentation on the changes. See http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00031.html /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
- Original Message -
From: "Graham Percival" <[EMAIL PROTECTED]>
To: "Trent Johnston" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, August 07, 2006 12:27 PM
Subject: Re: Bugs in version 2.9.14
> Trent Johnston wrote:
> > The simple example below produces the following messages:
> >
> > Processing `C:/jEdit/instr.ly'
> > Parsing...
> > Interpreting music...
> > warning: can't find property type-check for `instrument'
> > (translation-type?). perhaps a typing error?
>
> > staffViolin = \new Staff {
> > \time 4/4
> > \set Staff.instrument="Violin"
>
> If you're going to run the devel version, then please use convert-ly.
> Staff.instrument has been changed to instrumentName. The "can't find
> property `instrument'" error message is a great hint that there is some
> converting required.
>
> - Graham
Thanks Graham,
But since I'm using Windows there has been some problems with python scripts
not working. So currently I can't get convert-ly to work. I'll have to wait
until there is some more documentation on the changes.
I made the changes using instrumentName and no longer get the instrument
name errors but I still get the following errors:
Interpreting music... ERROR: In procedure ly_music_property:
ERROR: Wrong type argument in position 1 (expecting music): #) (elements) (duration . #) (origin .
#) (figure . 4))((display-methods
#) (name . BassFigureEvent) (types general-music
event rhythmic-event bass-figure-event)) >
) (length . #) (elements) (duration . #) (origin .
#) (figure . 4))((class .
bass-figure-event)) >
Trent
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
Graham Percival wrote:
Trent Johnston wrote:
The simple example below produces the following messages:
Processing `C:/jEdit/instr.ly'
Parsing...
Interpreting music...
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
staffViolin = \new Staff {
\time 4/4
\set Staff.instrument="Violin"
If you're going to run the devel version, then please use convert-ly.
Staff.instrument has been changed to instrumentName. The "can't find
property `instrument'" error message is a great hint that there is
some converting required.
I hadn't bothered to do convert-ly yet and get the same error but Lily
still produces output just fine on my Linux system.
Paul
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
Trent Johnston wrote:
The simple example below produces the following messages:
Processing `C:/jEdit/instr.ly'
Parsing...
Interpreting music...
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
staffViolin = \new Staff {
\time 4/4
\set Staff.instrument="Violin"
If you're going to run the devel version, then please use convert-ly.
Staff.instrument has been changed to instrumentName. The "can't find
property `instrument'" error message is a great hint that there is some
converting required.
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
- Original Message -
From: "Paul Scott" <[EMAIL PROTECTED]>
To: "Frédéric Chiasson" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, August 07, 2006 10:05 AM
Subject: Re: Bugs in version 2.9.14
> Frédéric Chiasson wrote:
> > Hello everyone,
> >
> > The new version of Lilypond doesn't seem to recognize the \breathe
function and
> > the TextScript #'box-padding. Is is normal?
> >
> > I'm typing it like this :
> >
> > \override TextScript #'box-padding #1
> > e1^\markup{ \hcenter \box "mi+C3" }
> >
> > for the breath sign, after a note :
> >
> > a1 \breathe
> >
> Same here. The error message might help:
>
> warning: Unknown event class breathing-sign-event[24][32][40][48][56][64]
> warning: Unknown event class breathing-sign-event[72]
> warning: Unknown event class breathing-sign-event
> warning: Unknown event class breathing-sign-event
> warning: Unknown event class breathing-sign-event[80][88][96][104][112]
>
>
> > P.S. Why does this usenet top-posting warning always appear when I paste
some
> > part of my program? It is quite annoying!
> >
> I can't help with that. I'm subscribed and never see that.
>
> Paul Scott
>
Hi All,
I can't get Windows 2.9.14 to run at all.
The simple example below produces the following messages:
Processing `C:/jEdit/instr.ly'
Parsing...
Interpreting music...
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
warning: doing assignment anyway
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
warning: doing assignment anyway
Interpreting music...
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
warning: doing assignment anyway
warning: can't find property type-check for `instrument'
(translation-type?). perhaps a typing error?
warning: doing assignment anyway
ERROR: In procedure ly_music_property:
ERROR: Wrong type argument in position 1 (expecting music): #) (elements) (duration . #) (origin .
#) (figure . 4))((display-methods
#) (name . BassFigureEvent) (types general-music
event rhythmic-event bass-figure-event)) >
) (length . #) (elements) (duration . #) (origin .
#) (figure . 4))((class .
bass-figure-event)) >
=
\version "2.9.14"
\header {
}
\include "english.ly"
staffViolin = \new Staff {
\time 4/4
\set Staff.instrument="Violin"
\set Staff.midiInstrument="violin"
\key c \major
\clef treble
\relative c' {
c4 c4 c4 c4
\bar "|."
}
}
staffCello = \new Staff = cont {
\set Staff.instrument="Cello"
\set Staff.midiInstrument="cello"
\key c \major
\clef bass
\relative c' {
c4 c4 c4 c4
\bar "|."
}
}
bc = \figuremode {
<4>4 <4> <4> <4>
}
\score {
<<
\staffViolin
\staffCello
\context Staff = "cont" \bc
>>
\midi {
}
\layout {
}
}
\paper {
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs in version 2.9.14
Frédéric Chiasson wrote:
Hello everyone,
The new version of Lilypond doesn't seem to recognize the \breathe function and
the TextScript #'box-padding. Is is normal?
I'm typing it like this :
\override TextScript #'box-padding #1
e1^\markup{ \hcenter \box "mi+C3" }
for the breath sign, after a note :
a1 \breathe
Same here. The error message might help:
warning: Unknown event class breathing-sign-event[24][32][40][48][56][64]
warning: Unknown event class breathing-sign-event[72]
warning: Unknown event class breathing-sign-event
warning: Unknown event class breathing-sign-event
warning: Unknown event class breathing-sign-event[80][88][96][104][112]
P.S. Why does this usenet top-posting warning always appear when I paste some
part of my program? It is quite annoying!
I can't help with that. I'm subscribed and never see that.
Paul Scott
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
Erlend Aasland gmail.com> writes:
> I suspect that this is because you haven't got any \repeat { } in the TB
> voices. Maybe you should do something like:
Hm, I had thought something like that before, but this one surely helped me out,
thanks.
Boobaa
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
Hi
On 5/30/06, CSÉCSYLászló <[EMAIL PROTECTED]> wrote:
Thanks, that makes some sense. Don't know why I didn't notice that
section, and
this way I got my ledger lines back, too. But the midi output is still
buggy; TB
staff still comes too early:
I suspect that this is because you haven't got any \repeat { } in the TB
voices. Maybe you should do something like:
\repeat volta 2 { R2*10 | } \alternative { { R1*4 } { R1*4 } { music... } }
Regards,
Erlend Aasland
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
Erlend Aasland gmail.com> writes:
> Why don't you just use \RemoveEmptyStaffContext? Just put multimeasure rests
> in the TB staff and change the layout block to include \context {
> \RemoveEmptyStaffContext }. This information is available in the
> documentation, section 8.3.2: "Hiding staves".
Thanks, that makes some sense. Don't know why I didn't notice that section, and
this way I got my ledger lines back, too. But the midi output is still buggy; TB
staff still comes too early:
http://frugalware.org/~boobaa/stuff/lvd-sample3.ly
http://frugalware.org/~boobaa/stuff/lvd-sample3.midi
http://frugalware.org/~boobaa/stuff/lvd-sample3.pdf
PS. As it seems, multi-measure spacers do the same job as m-m rests.
Thanks, B
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
Why don't you just use \RemoveEmptyStaffContext? Just put multimeasure rests
in the TB staff and change the layout block to include \context {
\RemoveEmptyStaffContext }. This information is available in the
documentation, section 8.3.2: "Hiding staves".
Regards,
Erlend Aasland
On 5/27/06, CSÉCSYLászló <[EMAIL PROTECTED]> wrote:
I am setting out a piece available only in an original manuscript, which
looks
like this one (only the text and the music is obfuscated, as I am not
allowed to
give out the whole score). I have encountered some bugs while working on
it; my
efforts are accessible at
http://frugalware.org/~boobaa/stuff/lvd-sample.{ly,midi,pdf}
1. In the generated MIDI the TB part comes too early: in the middle of the
second repeat, instead of at the end of the third. Did I write it wrong in
the
.ly? If yes, why is it good in the .pdf?
2. The ledger lines are missing from the first chord of TB. This looks
clearly
like a lilypond bug, as I had not done anything with or against them.
3. Not really a bug, but interesting anyway: I have 18 "warning: clef
`.notdef'
not found" messages while running the .ly through lilypond. Is there any
other
way to effectively remove the clefs? And btw, how should I remove the TB
staff
(only a clef) from the end of the second line of the .pdf? I see why is it
there, but how can it be removed? I should reproduce the original as close
as it
is possible...
Thanks,
Boobaa
(frugalware maintainer of lilypond)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
> Yes, and could you please produce a --minimal-- example of this bug? Available at: http://frugalware.org/~boobaa/stuff/lvd-sample2.ly http://frugalware.org/~boobaa/stuff/lvd-sample2.midi http://frugalware.org/~boobaa/stuff/lvd-sample2.pdf Sorry, I could not make it shorter; if I left anything out I would miss something I want to spot. Thanks, B ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
On 29-May-06, at 11:12 PM, CSÉCSYLászló wrote: Graham Percival gmail.com> writes: You either forgot to attach a .ly file, or it was removed by a mailserver. Could you produce a minimal example of this bug and send it to this list? All .ly, .midi and .pdf are available online (as I have written it before), with the following links: http://frugalware.org/~boobaa/stuff/lvd-sample.ly http://frugalware.org/~boobaa/stuff/lvd-sample.midi http://frugalware.org/~boobaa/stuff/lvd-sample.pdf Yes, and could you please produce a --minimal-- example of this bug? It will probably be less than four lines of lilypond code. If you cannot reproduce the bug in a very tiny example, then it is probably a mistake in your input code, rather than a bug in lilypond. - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
Graham Percival gmail.com> writes: > You either forgot to attach a .ly file, or it was removed by a > mailserver. Could you produce a minimal example of this bug and send > it to this list? All .ly, .midi and .pdf are available online (as I have written it before), with the following links: http://frugalware.org/~boobaa/stuff/lvd-sample.ly http://frugalware.org/~boobaa/stuff/lvd-sample.midi http://frugalware.org/~boobaa/stuff/lvd-sample.pdf Thanks, Boobaa ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs: MIDI output, missing ledger lines
On 27-May-06, at 10:25 AM, CSÉCSYLászló wrote: 2. The ledger lines are missing from the first chord of TB. This looks clearly like a lilypond bug, as I had not done anything with or against them. You either forgot to attach a .ly file, or it was removed by a mailserver. Could you produce a minimal example of this bug and send it to this list? Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs on the website, including the front page
Sietse Brouwer schreef: One thing I can do: I can get the files from Savannah, and insert the next/ previous links. However, I've never worked with Savannah, so I don't know how to upload, what tags to use etc. --- in short, I'm afraid of breaking stuff. Is there any other way I could submit those changes, or should I just try until I find a way to upload, and cross my fingers? So, should I have a go at putting in next/previous links; and how should I submit the changes? If you're on windows, it's easiest to install cygwin, and install python for cygwin. You can then run make in the newweb directory, which leaves a formatted copy of the website in out/ For submitting the changes, do cvs diff -u > patch and send the patch file to lilypond-devel@gnu.org -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs on the website, including the front page
Han-Wen Nienhuys lilypond.org> writes: > That's wonderful. Unfortunately, I'm also rather busy. Could you have go > at fixing the (simple) bugs yourself ? I'm afraid I can't do the "box not high enough" one --- lack of ability. I did some experimental rooting around, but when I downloaded the webpage files from Savannah, I couldn't even get the page to display in the same way as when I viewed the online version --- so I couldn't even know how my changes would work out. One thing I can do: I can get the files from Savannah, and insert the next/ previous links. However, I've never worked with Savannah, so I don't know how to upload, what tags to use etc. --- in short, I'm afraid of breaking stuff. Is there any other way I could submit those changes, or should I just try until I find a way to upload, and cross my fingers? > Sietse Brouwer schreef: > > Secondly, the Linux Audio Developers logo doesn't appear. > Should be fixed now. Roger that. > > [stuff about rel="up" and rel="start" in the documentation pages] > which pages are you talking about now? Is that the documentation? Then > it's really a texinfo problem/feature > Documentation, yes; and indeed a TeXinfo problem, so never mind it. > > Thirdly, in the "Introduction" section, it would be nice to have "Next" and > > "Previous" links between the pages. > > the last link on the page is actually a Next pointer. Maybe it should > have a different markup, eg. > ><< Prev: Why use lily | Next: Crash course >> > Clearer markup is a good idea -- I hadn't recognised it as a Next pointer. I suggest that for consistency, you use the same Next/Previous markup you use in your essay, such as at the bottom of [http://lilypond.org/web/about/automated- engraving/software.html], e.g. Next: A crash course in using LilyPond. As it happens, the essay only has Next links, no Previous links. At least in the Information section, I suggest putting an analogous Previous link on the next line, left-aligned. That'd look like so: Next: A crash course in using LilyPond Previous: Why use LilyPond So, should I have a go at putting in next/previous links; and how should I submit the changes? Cheers, Sietse ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs on the website, including the front page
Sietse Brouwer schreef: Some bugs I found on the web page, four in total, but the fourth is hardly noticable at all for most people. That's wonderful. Unfortunately, I'm also rather busy. Could you have go at fixing the (simple) bugs yourself ? The website is built in plain HTML, and you can check it out from https://savannah.gnu.org/cvs/?group=lilypond as the newweb module. Look for site/switch/ for the intro files. Firstly, on the front page [http://lilypond.org/web]the text "http://lilypond.org .ca mirror" appears in a box that is not high enough. The top and the bottom of the text get cut off, leaving some illegible vertical lines. This problem occurs under Windows XP, in Opera 8.54 and IE 6. It does not occur in Firefox 1.5 (no plugins). Secondly, on the "About" page [http://lilypond.org/web/about/], the image of the Linux Audio Developers doesn't appear. It should be located at [http://www.linuxdj.com/audio/lad/graphics/ladbanner_50.gif], but it isn't. should be fixed now. Thirdly, in the "Introduction" section, it would be nice to have "Next" and "Previous" links between the "Why use LilyPond?", "Testimonials", "A short tour", and "Crash course" pages. I know they don't follow each other strictly speaking, but most people would want to read them in order. I know I read them in order, all four or so times -- months apart -- that I read the section. the last link on the page is actually a Next pointer. Maybe it should have a different markup, eg. << Prev: Why use lily | Next: Crash course >> Fourthly, the navigation links in the documentation have nifty rel="up" properties where applicable. This allows Opera, for instance, to use a keyboard shortcut to go up one level. However, at the first level under the top, the link to the Top has rel="start" instead of rel="top". It might be useful to give that link both properties, if possible. This is more of a feature suggestion, though, and a *very* minor one at that. But since I'm posting anyway which pages are you talking about now? Is that the documentation? Then it's really a texinfo problem/feature -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs on the website, including the front page
> This line is to prevent Gmane from suspecting me of top-posting. Heh. Two more things I thought of. I'll continue numbering, for ease of referencing. Fifthly, I imagine more people than just me have had and will have Gmane's "top posting" problem when including .ly snippets. (I bumped into it when posting "Bug: eights-bars overlap in choirstaff" on April 30.) It happens like so: the LilyPond website allows you to post to the lilypond.bugs mailing list via a form. [http://post.gmane.org/post.php?group=gmane.comp.gnu. lilypond.bugs] This form checks for "top posting" [http://www.caliburn.nl/ topposting.html], which it "recognises" by one or more ">"-signs on a line by themselves, with text above that. Now, if somebody wants to post a LilyPond snippet which uses simultaneous music, then that *won't* work if it's of the form \new Staff = men << insert music here >> because Gmane thinks that that's top posting. There are two solutions. One is reformatting your code, like so: \new Staff = men << insert music here >> Another one is putting a line with > at the top of your post, like so: > Ssh, Gmane, I'm not top posting. \new Staff = men << insert music here >> Others may have less time than I had, and be turned away by this problem; and that would be a shame. Is it possible to tell prospective bug reporters about the problem and its workarounds? Preferably on the page with the posting form; or, otherwise, on the lilypond.org page [http://lilypond.org/web/documentation] that links to it. A simple sentence should do it, such as: "NB: When posting a LilyPond snippet, the form may tell you that you are "top posting". Solve that by putting a line that starts with > at the top of your e- mail." Sixthly and lastly, instructions on reporting bugs are located under Documentation on the website [http://lilypond.org/web/documentation]; and only on the page you reach when clicking the Documentation link on the top of the screen, not on page you reach when you follow the Quick Link to the documentation of the stable version [http://lilypond.org/doc/v2.8/Documentation /]. Not a very intuitive place; not one people come often. I recommend either * putting the bug-reporting instructions under the Development section (where I, for one, looked for it), * or putting it on the [http://lilypond.org/doc/v2.8/Documentation/] page, * or linking to it from either of these pages * or making a seperate page called "Contact" or "Contact/Support" or somesuch, and putting all contact/support information there, such as "Questions or comments?" and "Get notified of new releases?", etc. My two cents. What do you think? Sietse Brouwer ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: Bugs in lilypond 2.5.x
I have used v2.5.29 and v2.5.30 on Windows XP. The original file was compiled on v.2.4.2 which worked correctly. It was indeed saved in ANSI, when I saved it in UTF-8 it works ok. Thanx. Ben -Original Message- From: Mats Bengtsson [mailto:[EMAIL PROTECTED] Sent: zondag 12 juni 2005 21:37 To: Ben van Zanten Cc: bug-lilypond@gnu.org Subject: Re: Bugs in lilypond 2.5.x Please be more specific: - Exactly which LilyPond version did you use? - What operating system? - What text editor did you use. - Did you make sure to save the files using UTF8 encoding? /Mats Ben van Zanten wrote: > > Hello, > > In lots of lyrics with German text the special characters are not > printed, even worse: the following characters are also not there. > > > See the following example: > The composer is Bruno Stürmer, > The lyrics:: Ü -- ber allen . > > > > Greetings, > Ben van Zanten > > > > > > -- > -- > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology 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: Bugs in lilypond 2.5.x
Please be more specific: - Exactly which LilyPond version did you use? - What operating system? - What text editor did you use. - Did you make sure to save the files using UTF8 encoding? /Mats Ben van Zanten wrote: Hello, In lots of lyrics with German text the special characters are not printed, even worse: the following characters are also not there. See the following example: The composer is Bruno Stürmer, The lyrics:: Ü -- ber allen …. Greetings, Ben van Zanten ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology 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: Bugs n' wishes.
The missing signs in 1. and 2. are probably due to some setup problems on your machine. Are you running Linux or Windows? Do you see the same problem both in PDF, Postscript and DVI versions of the scores? /Mats [EMAIL PROTECTED] wrote: Hello hardworking underpayed Lilypond programmer (-s?). Reguarding version 2.2.2 I've encountered a few bugs: 1. The "\tempo 4 = 100", command produces only a note above the lines, no equals sign or beat/min. value. 2. The repeat with different endings fucks up time adding bars untimely - somebody noticed and left you a comment, here is yet another. 3. The \clef "g^8", command is not recogniced and \clef "treble^8" fails to add a digit 8 above the clef. Also I would greatly appreaciate( how is my spelling?) a possibility of forced newline, in order to end a melody and start another at the same piece of paper. And it would be a fine service if I could reduce the margin/blank space at the top of the page. Finally I would love to be able to write a large beautiful number just left of a line where I start a new melody (there is allready a fine indentation). So far this is all I've been annoyed with, thank you for giving this software freely. Best wishes Jacob D. Petersen __ Switch to the New Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp ___ bug-lilypond mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology 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 [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bugs n' wishes.
On Tuesday 22 June 2004 10.18, [EMAIL PROTECTED] wrote: > Hello hardworking underpayed Lilypond programmer (-s?). > Reguarding version 2.2.2 I've encountered a few bugs: > > 1. The "\tempo 4 = 100", command produces only a note above the lines, no > equals sign or beat/min. value. Cannot reproduce. > 2. The repeat with different endings fucks up time adding bars untimely - > somebody noticed and left you a comment, here is yet another. Yes, it's a known problem, but thanks anyways.. it's useful to know it's annoying. > 3. The \clef "g^8", command is not recogniced g should be capitalised, "G^8" > and \clef "treble^8" fails to > add a digit 8 above the clef. Cannot reproduce, works fine here. (2.2.1, 2.2.3). Could you please send small examples which demonstrate 1 and 3, and which do not work for you? > Also I would greatly appreaciate( how is my spelling?) a possibility of > forced newline, try \break > in order to end a melody and start another at the same > piece of paper. And it would be a fine service if I could reduce the > margin/blank space at the top of the page. Finally I would love to be able > to write a large beautiful number just left of a line where I start a new > melody (there is allready a fine indentation). I don't understand - have you tried setting Staff.instrument or Staff.instr? Erik ___ bug-lilypond mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs
[EMAIL PROTECTED] writes:
> On Friday 29 August 2003 07:16 pm, Han-Wen Nienhuys wrote:
> > [EMAIL PROTECTED] writes:
> > > %{ With the % stuff commented out the file runs but
> > > it does not work as expected. -2 is not in
> > > front of the notehead.
> >
> > I've added the following to the BUGS section in 1.8:
> >
> > Fingerings are only put horizontally on notes when there are also
> > fingering above and below the notes.
> >
> > I expect to fix this shortly in 1.9
>
> It's the bleeding edge for me then, because I don't want to have
> to change things later.
(fixed in 1.9.3)
> > > There also is no way that I can
> > > find to set the thickness of the staff lines. In the manual
> > > there are many many mentions of setting stem thicknesses
> > > relative to the staff line thickness but nothing about how
> > > to set the staffline thickness, and no Grob with the name
> > > staffLine, Staffline, Staff.Line etc. etc.
> >
> > Try looking up staff symbol.
>
> I kept looking. The links to the "collateds" don't work in
> debian unstable lilypond-doc1.8.1. They didn't in 1.8.0 either.
Can you check that they do in the online doco?
If yes, submit bugreport to debian maintainer, if no, submit bugreport
here.
> \paper { pagenumber = no
> % \outputproperty #(make-type-checker 'staff-symbol-interface)
> #'thickness = #'(0.4)
#'(0.4) is a list. You want #0.4
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs
On Friday 29 August 2003 07:10 pm, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > > \property Context.propertyName = value > > > > > > You only use \set or \override to set properties of objects. > > > > > > Interpreting music...lilypond: ../flower/include/array.hh:149: T& > > Array::elem_ref(int) const [with T = Finger_tuple]: Assertion `i > > > > >=0&&i > I think I've fixed this crash in 1.9 CVS. Can you check if 1.8.2 > (when it is out) fixes this crash? Absolutely. Thanks! > -- "We have learned the lessons of Viet Nam." --anon Spokesman "Failure is not an option." --anon Spokesman Can both be true? n Are both false? y Right answers get my vote. D. Raleigh Arnold dra@ http://www.openguitar.com [EMAIL PROTECTED] ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs
On Friday 29 August 2003 07:16 pm, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > %{ With the % stuff commented out the file runs but
> > it does not work as expected. -2 is not in
> > front of the notehead.
>
> I've added the following to the BUGS section in 1.8:
>
> Fingerings are only put horizontally on notes when there are also
> fingering above and below the notes.
>
> I expect to fix this shortly in 1.9
It's the bleeding edge for me then, because I don't want to have
to change things later.
>
> > There also is no way that I can
> > find to set the thickness of the staff lines. In the manual
> > there are many many mentions of setting stem thicknesses
> > relative to the staff line thickness but nothing about how
> > to set the staffline thickness, and no Grob with the name
> > staffLine, Staffline, Staff.Line etc. etc.
>
> Try looking up staff symbol.
I kept looking. The links to the "collateds" don't work in
debian unstable lilypond-doc1.8.1. They didn't in 1.8.0 either.
\outputproperty #(make-type-checker 'staff-symbol-interface) #'thickness = #'(0.4)
Gave error or did nothing depending on where it was put. I
still think an example of that in the manual would be good. DaveA
%{ With the % stuff commented out the file runs but
it does not work as expected. -2 is not in
front of the notehead. Hope this helps.
min.ly cut here%}
\header { title = "Min"
}
\include "english.ly" %
\paper { papersize = "letter" }
\include "paper20.ly" %
measureSkip = \notes{s1}
% measureSkip = s1 doesn't work.
% doesn't work:
lfinger = \property Voice.fingerHorizontalDirection = #LEFT
global = { \context Score
% \outputproperty #(make-type-checker 'staff-symbol-interface) #'thickness = #'(0.8)
\context Voice = global \notes {
% can't find any way of doing this at all:
% \outputproperty #(make-type-checker 'staff-symbol-interface) #'thickness = #'(0.2)
\property Staff.Stem \override #'thickness = #1.0
\clef "G_8" \time 4/4 \key g \major
\partial 4 s4
\measureSkip
\measureSkip
s1
s2. }
}
top = { \context Voice = top \notes {
\stemUp \lfinger
e'8 <>
g'4^4 fs'8^2 e' ds'4^4 e'8 fs'^2
g'4^4 fs'8^2 e' ds'4^4 e'8 fs'^2
b4 cs'8 ds' e'4^4 d'8^4 c'
b2. }
}
\score {
\context Staff = guitar <
\property Staff.instrument = "Guitar"
\global
\top
>
\paper { pagenumber = no
% \outputproperty #(make-type-checker 'staff-symbol-interface)
#'thickness = #'(0.4)
linewidth = 18.0 \cm
textheight = 9.0 \in
}
\midi { \tempo 4=94 }
--
"We have learned the lessons of Viet Nam." --anon Spokesman
"Failure is not an option." --anon Spokesman
Can both be true? n Are both false? y Right answers get my vote.
D. Raleigh Arnold dra@ http://www.openguitar.com [EMAIL PROTECTED]
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs
[EMAIL PROTECTED] writes: > > > > \property Context.propertyName = value > > > > You only use \set or \override to set properties of objects. > > > > /Mats > > Thanks. Tried that first. Still doesn't work. DaveA > > [EMAIL PROTECTED]:~/data/lily/bugs$ ly2dvi -p min.ly; gv min.pdf > /usr/bin/ly2dvi:629: SyntaxWarning: local name 'e' in > 'make_html_menu_file' shadows use of 'e' as global in nested scope > 'lambda' > def make_html_menu_file (html_file, files_found): > ly2dvi (GNU LilyPond) 1.8.1 > Running /usr/bin/lilypond...GNU LilyPond 1.8.1 > Now processing: `min.ly' > Parsing... > Interpreting music...lilypond: ../flower/include/array.hh:149: T& > Array::elem_ref(int) const [with T = Finger_tuple]: Assertion `i > >=0&&ihttp://www.xs4all.nl/~hanwen ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs
On Friday 29 August 2003 12:51 pm, Mats Bengtsson wrote: > > Also, in the manual, > > \notes \property \set Voice.fingerHorizontalDirection = #LEFT > > lacks the \set, but in the text it says to "set" it. > > If you the first paragraphs of the section "Tuning Output" > of the Reference Manual, you will see that translation properties > are set using the syntax > > \property Context.propertyName = value > > You only use \set or \override to set properties of objects. > > /Mats Thanks. Tried that first. Still doesn't work. DaveA [EMAIL PROTECTED]:~/data/lily/bugs$ ly2dvi -p min.ly; gv min.pdf /usr/bin/ly2dvi:629: SyntaxWarning: local name 'e' in 'make_html_menu_file' shadows use of 'e' as global in nested scope 'lambda' def make_html_menu_file (html_file, files_found): ly2dvi (GNU LilyPond) 1.8.1 Running /usr/bin/lilypond...GNU LilyPond 1.8.1 Now processing: `min.ly' Parsing... Interpreting music...lilypond: ../flower/include/array.hh:149: T& Array::elem_ref(int) const [with T = Finger_tuple]: Assertion `i >=0&&ihttp://www.openguitar.com [EMAIL PROTECTED] ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: bugs
Also, in the manual, \notes \property \set Voice.fingerHorizontalDirection = #LEFT lacks the \set, but in the text it says to "set" it. If you the first paragraphs of the section "Tuning Output" of the Reference Manual, you will see that translation properties are set using the syntax \property Context.propertyName = value You only use \set or \override to set properties of objects. /Mats ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
