http://blog.gmane.org/gmane.comp.gnu.lilypond.bugs hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37634 <pre> %The full-measure rest in a wrong place? \version "2.17.18" { \override Voice.MultiMeasureRest #'staff-position = #0 R1 } </pre> Arttu Punkkinen 2013-05-20T11:39:12 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37628 <pre>V. 2.14.2 Running: lilypond-book ---output=out MYFILE.lytex I obtain: UnicodeDecodeError: 'utf8' codec can't decode byte 0xab in position 13: invalid start byte The main.tex file is not produced in out dir. It doesn't contain any accented letter... </pre> nicola g. 2013-05-19T15:42:32 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37625 <pre>Hi all, Here is something very odd when the text of a footnote is spread over more than one line: there are as many "marks" as the number of lines. Using auto-footnote, each line get numbered. Hit the wrong button... Cheers, Jean-Charles _______________________________________________ bug-lilypond mailing list bug-lilypond&lt; at &gt;gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond </pre> Jean-Charles Malahieude 2013-05-18T16:20:02 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37624 <pre>Hi all, Here is something very odd when the text of a footnote is spread over more than one line: there are as many "marks" as the number of lines. Using auto-footnote, each line get numbered. _______________________________________________ bug-lilypond mailing list bug-lilypond&lt; at &gt;gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond </pre> Jean-Charles Malahieude 2013-05-18T16:18:16 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37623 <pre>reported in the French community http://lilypond-french-users.1298960.n2.nabble.com/Probleme-avec-repeat-tremolo-en-partcombine-tp7579661.html I couldn't find this in the many issues about \partcombine you can circumvent this problem by adding explicit beaming in both voices for the critical notes (but dozens of warnings and errors still appear) here is the code: \version "2.16.0" FluteI = \relative c'' { \time 3/4 \repeat tremolo 6 {c16 e} \repeat tremolo 6 {c16 e} } FluteII = \relative c'' { \time 3/4 \repeat tremolo 6 {g16 b} \repeat tremolo 6 {g16 g'} } \score { &lt;&lt; \new Staff \FluteI \new Staff \FluteII \new Staff \partcombine \FluteI \FluteII &gt;&gt; } Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/crash-with-partcombine-repeat-tremolo-when-voices-cross-tp146036.html Sent from the Bugs mailing list archive at Nabble.com. </pre> Eluze 2013-05-17T08:41:32 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37618 <pre>LSR 507 &lt;http://lsr.dsi.unimi.it/LSR/Item?id=507&gt; produces erroneous code since version 2.15.28: mus = { c4 d e f |} \displayLilyMusic \ghostMusic \mus \version "2.15.28" the result is: { s | } and the log warns: test2.ly:17:17: warning: barcheck failed at: 1/4 mus = { c4 d e f |} Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/LSR-507-ghost-voice-broken-since-2-15-28-tp146000.html Sent from the Bugs mailing list archive at Nabble.com. </pre> Eluze 2013-05-16T09:40:53 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37616 <pre>Hi all, This isn't an problem as regards en-users, but only occurs when running LilyPond under gdb. The problem is that running under gdb fails early on in initialization in the main.cc/guile-init.cc code with the call to ly_init_ly_module called from ly_c_init_guile, called from main_with_guile, which is a call-back from scm_boot_with_guile in main(). Basically gdb causes the guile code to barf saying it can't find lily.scm in the current setting of %load-path. I've added some code to show the value of %load-path in the start-up which shows what the value of %load-path is before the call and it looks fine if I run it up without gdb and with --loglevel=DEBUG. Here's a vanilla gdb session using Han-Wen's .gdbinit, the pwd is the build directory under the lilypond git directory: ----------------------------------------------------------------------- ian&lt; at &gt;nanny-ogg ~/src/lilypond/build (T3154)$ gdb --command ../.gdbinit GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu Copyright (C) 2013 Free Software Foundation, In</pre> Ian Hulin 2013-05-16T09:10:15 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37613 <pre>I want to put text like rall----en---tan---do into some music. I've noticed that the mailing list also had someone who wanted to put cres---cendo similarly. The current text spanner cannot do this, and various people have suggested workarounds. The main problem is that with a simple text spanner, each item of text is separate from the next, and the heights can vary. I'm a newbie to Lilypond, so I'm afraid that I can't really help by suggesting a syntax for a replacement that would be compatible with LP's design methods, but I'm sure that someone here can do this! Regards, Peter mailto:lilypond&lt; at &gt;ptoye.com www.ptoye.com </pre> Peter Toye 2013-05-15T11:51:12 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37607 <pre> Lilypond crashes out when I use the "%e" format in a header (I'm allergic to leading zeroes). This is under Windows 7 Home Premium. Postings on the Lilypond mailing list indicate that this is specific to Windows - and it works OK on Linux. I'm not in a position to test this. Example: \version "2.16.2" \header { tagline = \markup { Engraved \simple #(strftime "%d %e %Y" (localtime (current-time))) } } { c d e f } Lilypond log: Starting lilypond-windows.exe 2.16.2 [Bridge6(strftime).ly]... Processing `c:/users/peter_2/appdata/local/temp/ frescobaldi-y9etc5/tmpurt867/Bridge6(strftime).ly' Parsing...FATAL: memory error in realloc Exited with return code 3. </pre> Peter Toye 2013-05-13T08:37:52 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37603 <pre> Why is the staccato dot far below the note? Strangely, the slur is important: if you remove the slur, the dot moves to the correct place. Bug first appears in 2.17.10 \version "2.17.10" { &lt;&lt; \new Staff = "R" { s2 } \new Staff = "L" { \new Voice { \voiceTwo f'8 \change Staff="R" f'( \change Staff="L" f'_. f') } } &gt;&gt; } </pre> Timothy Lanfear 2013-05-12T17:11:47 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37601 <pre>Hi, \balloonLengthOn doesn't work any more. Example taken from http://lilypond.org/doc/v2.17/Documentation/notation/outside-the-staff#balloon-help \version "2.17.17" \relative c'' \new Voice \with { \consists "Balloon_engraver" } { \balloonLengthOff \balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" } a8 \balloonGrobText #'Rest #'(-4 . -4) \markup { "I'm a rest" } r \balloonLengthOn &lt;c, g'-\balloonText #'(-2 . -2) \markup { "I'm a note head" } c&gt;2. } 2.16.2 worked correct. -Harm </pre> Thomas Morley 2013-05-10T15:53:04 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37597 <pre>although it doesn't make much sense to use a tie here LP shouldn't exit fatally: &lt;&lt; \new Staff=A { c'1~ \change Staff=B c'} \new Staff=B { \clef bass R1 R } up to 2.17.13 the pdf was created. Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/ties-for-notes-in-changed-Staff-brings-LP-to-crash-tp145669.html Sent from the Bugs mailing list archive at Nabble.com. </pre> Eluze 2013-05-10T11:40:37 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37588 <pre>PROBLEM In the docs on the web it is not obvious, especially to new users, which version of LilyPond any given page is for. This is particularly a problem when landing on a doc page directly from a web search or link. For example, a new user does a web search that takes them directly to an old docs page like this: http://lilypond.org/doc/v2.14/Documentation/notation/writing-rhythms The only clue they have that they are not looking at the current docs is the "2.14" in the URL (which they will probably not notice), and the tiny text "This page is for LilyPond-2.14.2 (stable-branch)." that is not visible until you scroll all the way down a long page. SUGGESTION A simple thing would be to put the version number of LilyPond somewhere at the top of every web page. For example, it could go at the top of the left hand column. Where it says "LilyPond - Notation Reference" it could say "LilyPond 2.14 - Notation Reference" instead. To make it more obvious, you could have "LilyPond 2.14" in a larger font s</pre> Paul Morris 2013-05-08T16:57:55 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37586 <pre>noah&lt; at &gt;noah-Aspire-M5-481TG:~$ sudo apt-get install lilypond Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: lilypond : Depends: lilypond-data (= 2.16.2-1) but 2.16.0-1~exp+2 is to be installed E: Unable to correct problems, you have held broken packages. </pre> Noah 2013-05-08T11:24:28 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37581 <pre>% Bug report: The "vocalName" of the Lyrics context isn't visible in the output: The text "myvocalname" should appear in the output, but it doesn't. % The problem seems to occur as long as the corresponding voice (here "myvoice") starts with a rest: If you remove "r2" than "myvocalname" appears correctly in the output. \version "2.16" \score { &lt;&lt; \context Staff &lt;&lt; \context Voice = myvoice { r2 a2 } &gt;&gt; \context Lyrics \lyricsto myvoice \lyricmode { \set vocalName = #"myvocalname" mylyrics } </pre> Lukas Sommer 2013-05-07T15:40:39 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37559 <pre> I think that our current code balks at setting paper sizes like "A4" rather than "a4". Can someone check with older versions? </pre> David Kastrup 2013-05-04T20:00:37 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37549 <pre>Hi, I experienced an unfriendly installation on Windows 7 pro, similar to what was mentioned in http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00226.html * You need to run lilypond-setup.exe as admininstator (even if you already have administrator rights * LilyPad with Welcome_to_LilyPond.ly does not pop up when you click on the lilypond icon, until after you explicitly run lilypond as admininstrator once After that, it works fine. It would be nice if these setup hurdles were fixed, or at least they should be documented for now. Greetings, Jan </pre> Jan Nieuwenhuizen 2013-05-01T06:28:37 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37547 <pre>Hi! I've just installed Lilypond, but it hasn't appeared in my menu, and when I try to open it from terminal, this shows up: GNU LilyPond 2.14.2 Usage: lilypond [OPTION]... FILE... Typeset music and/or produce MIDI from FILE. LilyPond produces beautiful music notation. For more information, see http://lilypond.org Options: -d, --define-default=SYM[=VAL] set Scheme option SYM to VAL (default: #t). Use -dhelp for help. -e, --evaluate=EXPR evaluate scheme code -f, --formats=FORMATs dump FORMAT,... Also as separate options: --pdf generate PDF (default) --png generate PNG --ps generate PostScript -h, --help show this help and exit -H, --header=FIELD dump header field FIELD to file named BASENAME.FIELD -I, --include=DIR add DIR to</pre> Candela 2013-05-01T03:26:01 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37544 <pre>Hm, I recall having read about this or a similar issue recently, but I don't seem to be able to find it anymore ... Searching the issues I only found references to problems with vertical croppings of -dpreview. When compiling this: \version "2.17.17" \score { \new PianoStaff &lt;&lt; \new Staff { R1 } \new Staff { R1 } &gt;&gt; } with -dpreview the output crops the PianoStaff bracket completely (see attached image). I can 'fix' this by setting the instrumentName to " " (not ""), but it definitely seems that -dpreview output doesn't take the bracket into account at all. Urs _______________________________________________ bug-lilypond mailing list bug-lilypond&lt; at &gt;gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond </pre> Urs Liska 2013-04-30T20:00:37 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37542 <pre>Hello. In "File structure" we are saying that bookparts can help on having different paper settings for each part, but in fact this conflicts with the statement we state (in the same page) that paper settings act on the whole book. This is confusing, do you agree? I've also seen many unanswered questions in the list archives about using bookparts to join scores. IMO it is confusing that we don't offer a template or something warning that you can not simply include a working score in a bookpart, and instead you have to handle a bookpart as if it were a score block. </pre> Francisco Vila 2013-04-30T08:43:39 http://comments.gmane.org/gmane.comp.gnu.lilypond.bugs/37530 <pre>I have two problems with the doc-snippet http://www.lilypond.org/doc/v2.17/Documentation/snippets/rhythms#rhythms-making-an-object-invisible-with-the-_0027transparent-property a) I'm not sure if this snippet is adequate at all: I think writing cross-voice curves by setting the 'transparent property isn't a good way because (as is mentioned in the snippet!) the blanked objects _do_ take part in collisions etc. With ties this will especially lead to problems with the flags that often collide with ties -&gt; the tie will try to avoid a flag that isn't there at all. IMO this should be done by setting 'stencil = ##f So one should have either a different example for 'transparent or rewrite this example with 'stencil and label it accordingly. b) Independent of the opinion on a) the example has the flags still showing. So the least to be done is to update the example to blank the flags too. Which is done by attached patch. b') The example for creating cross-voice curves should be somewhat expanded because new</pre> Urs Liska 2013-04-29T13:26:25 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnu.lilypond.bugs