Re: mid-measure key change
Hello, 2013/12/16 David Kastrup d...@gnu.org I don't see an obvious solution (but then I don't understand the bug) but I boiled down the example somewhat more, killing most of its musicality but making the problem more apparent. I was suspecting the tuplets to be involved, but no. In the following, outcommenting the line with the Staff \change cures the problem. If no other developer has a good lead, this should be picked up by the bug squad and turned into a report. This has been added as http://code.google.com/p/lilypond/issues/detail?id=3737 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \parenthesize collision with dots
Hello,
2013/12/18 Urs Liska lilyli...@googlemail.com
If I parentesize a dotted note with
{ \parenthesize f'2. }
the right paren collides with the dot.
Thank you for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=3738
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ambitus not in the beginning
2013/11/28 Colin Campbell c...@shaw.ca I've modified it a bit further, putting the \consists in a \layout context. This has was added as http://code.google.com/p/lilypond/issues/detail?id=3702 by Ralph Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \epsfile relative file locations
http://code.google.com/p/lilypond/issues/detail?id=3699 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly output indentation style
Hello, 2013/11/27 Martin Tarenskeen m.tarensk...@zonnet.nl The *.ly files that are produced using musicxml2ly use an indentation style that does not conform to LilyPond's common practice. Musicxml2ly does not un-indent closing brackets. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3680 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issue 3418 is more serious than we can imagine
Hello, 2013/11/11 Karol Majewski karol.majew...@gmail.com It seems that the difference in horizontal spacing is very small, but when the line is stretched, it becomes huge! I have added it as a comment to the issue. Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Squad Roll Call
2013/11/12 Federico Bruni fedel...@gmail.com Member DaysMeister? Monday Ralph PalmerTuesday Wednesday Thursday Friday Colin Campbell SaturdayNo Federico Bruni Sunday No ___ Marek Klein Wednesday No ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Table of content in lilypond 2.16.0 and 2.16.2
Hello, 2013/11/2 David Bariod davidr...@googlemail.com I have a set of partitions which used to build in 2.14 release. Basically the table-of-contents does not seem to work at all in the 2.16 release. If you apply convert-ly to it, markuplines would change to markuplist and it works again... HTH -- Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Fwd: No progress messages on GUI under Windows 7
-- Forwarded message -- From: Jeff Wahl jw...@bex.net Date: 2013/10/17 Subject: Re: No progress messages on GUI under Windows 7 To: Marek Klein ma...@gregoriana.sk Cc: Eluze elu...@gmail.com On 10/16/2013 3:52 PM, Marek Klein wrote: Forwarding to OP: 2013/10/14 Eluze elu...@gmail.com Jeff Wahl wrote But I prefer to work with a GUI interface. Neither LilypondTool (no longer supported) under jEdit nor Frescobaldi will show progress messages from Lilypond 2.16 binaries in the respective console windows (of LilypondTool or Frescobaldi). Both of these GUI interfaces will show the messages when using an older major version of Lilypond. What has changed (not explained in Lilypond documentation)? what exactly used to be displayed (and is not displayed in newer versions) when you run Lilypond from the command line. which versions were they? Eluze -- Marek bug squad member With previous versions of Lilypond (2.12.3, 2.14.2) the GUI programs would produce, in their console windows: Starting lilypond-windows.exe 2.12.3 [Concerto in G Major.ly]... Processing `C:/Users/Public/Music/Concerto in G Major.ly' Parsing... Interpreting music... Interpreting music... [8][16][24][32] Preprocessing graphical objects... MIDI output to `Concerto in G Major.mid'... Finding the ideal number of pages... Fitting music on 1 or 2 pages... Drawing systems... Layout output to `Concerto in G Major.ps'... Converting to `./Concerto in G Major.pdf'... Completed successfully in 3.4. This is what is produced from the command line (in terminal mode) as well, with all versions of Lilypond I've tried. Using Lilypond 2.16.2 or 2.17, through a GUI program, only the first and last lines would show. No progress messages; these are always sent to the log file on disk instead. The consoles might indicate a termination with an error code; any explanation would be in the log file. When I've looked at the Python code for Lilypond 2.16, I've seen changes to the code for logging and printing messages to stdout and stderr. Jeff ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: No progress messages on GUI under Windows 7
Could you please include original poster in your answers? Marek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: wrong notehead
Thank you both. This has been added as http://code.google.com/p/lilypond/issues/detail?id=3622 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: No progress messages on GUI under Windows 7
2013/10/17 Eluze elu...@gmail.com Marek Klein wrote Could you please include original poster in your answers? do you mean additionally to the list? I can try, but might forget sometimes. and I think he's reading the list!? He doesn't have to. Why do you think he is? Marek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: No progress messages on GUI under Windows 7
Forwarding to OP: 2013/10/14 Eluze elu...@gmail.com Jeff Wahl wrote But I prefer to work with a GUI interface. Neither LilypondTool (no longer supported) under jEdit nor Frescobaldi will show progress messages from Lilypond 2.16 binaries in the respective console windows (of LilypondTool or Frescobaldi). Both of these GUI interfaces will show the messages when using an older major version of Lilypond. What has changed (not explained in Lilypond documentation)? what exactly used to be displayed (and is not displayed in newer versions) when you run Lilypond from the command line. which versions were they? Eluze -- Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Too low stem-thickness while using high value for fontSize
Hello,
2013/10/15 Thomas Morley thomasmorle...@gmail.com
Hi,
writing some educational papers I tried the code below
\version 2.17.28
{
\set fontSize = #12
\override Stem #'length = #24
%\override Stem #'thickness = #(magstep 6)
a'8
}
%% Only for better viewing:
\layout {
\omit Staff.TimeSignature
\omit Staff.Clef
\omit Staff.StaffSymbol
}
Returning a far to low stem-thickness
Seems it is factored some way, only looking at
StaffSymbol.line-thickness, disregarding the general fontSize.
Workaround is uncommenting the Stem.thickness-override.
Thank you for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=3620
--
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: crash report for OSX
Forwarding to OP... 2013/10/8 David Kastrup d...@gnu.org Carl Witthoft c...@witthoft.com writes: For christsake lose that idiotic Top post filter will you? Latest stable LilyPond, trying to compile the example file. OSX 10.6.8 on iMac IntelCore2Duo. Which example file? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: wrong notehead
Hello,
2013/10/9 Garrett McGilvray garrett.mcgilv...@gmail.com
%The fa half note in aikenHeads renders as a quarter note
\version 2.16.2
\relative c' { \aikenHeads c2 d e f } % The d notehead is solid instead of
hollow
I can not confirm it with 2.16.2 or with 2.17.28, which version and OS have
you used?
Marek Klein
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: wrong notehead
2013/10/9 Garrett McGilvray garrett.mcgilv...@gmail.com Hi, I am using Mac OS 10.8.5, and the version of LilyPond is Version 2.16.2-1. Using the code I sent (which I have just copied directly from the email to be sure), this attachment shows what I am seeing: Thanks for looking into this. -Garrett I have different result with GNU/Linux x86: LilyPond 2.16.2-1. Could someone on Mac OS confirm this behaviour? Marek bug squad member wrong_notehead.png___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LM 4.5: dead link
Hello,
2013/9/30 Trevor Daniels t.dani...@treda.co.uk
It seems a backslash in a node name causes no problems for
references within the same manual, but cross-references across
manuals fail. The correct way of dealing with this is to drop the
backslash from the node name and encode it using the bs{}
macro in the heading. Here's an example from changing-defaults.itely:
@node The set command
@subsection The @code{@bs{}set} command
I see there are several node names in the documentation that include
native backslashes, but only the one noted above is used in a
reference across manuals. I'll fix ref_check.py to check for backslash
in note names to give a warning, and amend all the instances in the
documentation. Oh, and add a note to the CG.
@bug Squad: could you please raise an issue to track this
This has been added as
http://code.google.com/p/lilypond/issues/detail?id=3590
--
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: broken mpost binary from TeXLive (was: broken clef glyph)
Hello Werner, 2013/9/3 Werner LEMBERG w...@gnu.org I suggest that we exclude the affected mpost versions in lilypond's configure script. do we need a tracker issue for this? -- Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Eample in NR 5.5.5 Unpure-pure containers is misleading
Hello, 2013/8/19 Thomas Morley thomasmorle...@gmail.com the example in NR 5.5.5 Unpure-pure containers is misleading now. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3512 -- Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Create different pdf layers
Hello, 2013/8/1 Urs Liska u...@openlilylib.org I have brought this up before without success. But as my interest reappeared I'll try it again with a slightly more specific question. there is an existing issue based on your request: http://code.google.com/p/lilypond/issues/detail?id=2542 Do you believe, it is a good Idea to discus your Ideas on bug-list? Marek, one of the very few bug squad members ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: fatal error with toplevel-markup-identifier
Hello, 2013/8/14 Thomas Morley thomasmorle...@gmail.com Hi, the following returns a fatal error (worked fine with 2.16.2): Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3498 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bison-3.0 fix lilypond
Hello David, do we need a tracker issue for this? Marek 2013/8/5 David Kastrup d...@gnu.org Thomas Klausner t...@giga.or.at writes: Hi! The latest stable and development branches of lilypond do not compile with the recently released bison-3.0. The following patch fixes this (sorry, whitespace may be off): --- lily/parser.yy.orig 2013-01-04 13:41:57.0 + +++ lily/parser.yy @@ -100,7 +100,7 @@ or -%pure_parser +%pure-parser %locations That does not seem like a bison-3.0 fix: according to the documentation, %pure-parser is the right form even for 2.6.2. The question is what effect the wrong declaration had, if any. While I'm here, I'll just report a minor issue too: scripts/auxiliar/cg-section.sh uses the unportable == operator for test(1), only supported by bash, not even by GNU coreutils. Please use the portable = instead. Typical bashism, yes. Personally, I prefer using case/esac for almost everything. That usually is quite more flexible and has been a shell builtin for quite longer than test. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond -- Marek Klein 0918 610 720 http://gregoriana.sk Gregoriana on youtubehttp://www.youtube.com/playlist?list=PLBQHqmaUgUMZ4Bd4w4heeQF9lV9L7BS-s Graduale Project http://gregoriana.sk/graduale/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Triple-Hammer-Pull bug
Forwarding to OP: 2013/7/31 Phil Holmes m...@philholmes.net bb bblo...@arcor.de wrote in message news:51F8CFC7.2080404@arcor.** de... Please focus your Attention to the Triple-Hammer-Pull construct. It will be shown correctly in the music lines, but not in the tabs, not for guitar and not for banjo! Regards BB Please provide a sample that a) compiles without warnings and b) complies with the concept of a tiny example: http://lilypond.org/tiny-**examples.htmlhttp://lilypond.org/tiny-examples.html -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LSR-formating not transformed in /Documentation/snippets
Hello, 2013/7/21 Thomas Morley thomasmorle...@gmail.com accidentally I've found two instances in /Documentation/snippets where the LSR-formating code.../code isn't transformed: Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3474 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
bug squad
Hello, according to http://lilypond.org/doc/v2.17/Documentation/contributor/bug-squad-checklists this is daily schedule of bug squad: Monday:Eluze Tuesday: Ralph Wednesday: Marek Thursday: Joe Wakeling (soon) Friday:Colin H Saturday: Colin H Sunday:Federico Who from this list is still active? -- Marek Klein http://gregoriana.sk Gregoriana on youtubehttp://www.youtube.com/playlist?list=PLBQHqmaUgUMZ4Bd4w4heeQF9lV9L7BS-s Graduale Project http://gregoriana.sk/graduale/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book 2.17.21 and spaces in file path
Hello, 2013/7/10 Davide Liessi dal...@gmail.com lilypond-book 2.17.21 can't determine the line width from .lytex files if there is a space in the file path, while spaces only in the file name don't cause any problem. Thank you for the report. This has been added as http://code.google.com/p/lilypond/issues/detail?id=3467 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book and spaces in application name (Mac OS 10.6)
Hello, 2013/7/10 Davide Liessi dal...@gmail.com I keep multiple versions of LilyPond in /Applications folder: LilyPond.app is the latest development version, while I rename the other versions as LilyPond x.y.z.app. This makes lilypond-book from the renamed versions fail. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3468 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 1.4.1: inconsistency in the description of repeats and alternate endings?
2013/7/11 Mark Polesky markpole...@yahoo.com Yes, Federico's suggested sentence is better. It is a trivial patch to make, and can be done in a minute. I'm still unclear if developers can start tracker issues, or if that's only to be done by bug squad members. Let me know. Some of the developers do it occasionally, I can see no big deal with it. You could read http://lilypond.org/doc/v2.15/Documentation/contributor/issues before... Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 1.4.1: inconsistency in the description of repeats and alternate endings?
2013/7/11 Marek Klein ma...@gregoriana.sk 2013/7/11 Mark Polesky markpole...@yahoo.com Yes, Federico's suggested sentence is better. It is a trivial patch to make, and can be done in a minute. I'm still unclear if developers can start tracker issues, or if that's only to be done by bug squad members. Let me know. Some of the developers do it occasionally, I can see no big deal with it. You could read http://lilypond.org/doc/v2.15/Documentation/contributor/issues before... http://lilypond.org/doc/v2.17/Documentation/contributor/adding-issues-to-the-tracker This should only be done by the Bug Squad or experienced developers. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 1.4.1: inconsistency in the description of repeats and alternate endings?
Hello Federico, 2013/7/10 Federico Bruni fedel...@gmail.com 2013/7/10 Marek Klein ma...@gregoriana.sk Hello Federico, 2013/7/6 Federico Bruni fedel...@gmail.com So I would rewrite the second sentence as: Multiple repeats with one alternate ending Does it make sense what I'm writing? I believe, this isn't the right place for asking questions. Wold you like to formulate a bug report? Well, it is a bug report. As any bug report, it requires the confirmation from a person other than the reporter. If you think it makes sense, please add it to the tracker. I would interpret the silence from developers and doc writers as an implicit ok. in such a case there is no need for confirmation or discussion on bug-list. The consideration takes place on the tracker itself... Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: ly:grob-system not working as expected
Hello, 2013/7/3 David Kastrup d...@gnu.org ly:grob-system only returns the system after is has been set in the PaperColumn which is after line breaking. What you see as #Grob System above is a single system encompassing the entire score. Sorry, I do not understand this language... do we need a tracker issue here or not? Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 1.4.1: inconsistency in the description of repeats and alternate endings?
Hello Federico, 2013/7/6 Federico Bruni fedel...@gmail.com So I would rewrite the second sentence as: Multiple repeats with one alternate ending Does it make sense what I'm writing? I believe, this isn't the right place for asking questions. Wold you like to formulate a bug report? Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: anacrucis instead of anacrusis?
Hello, 2013/7/2 Federico Bruni fedel...@gmail.com I think I've found a typo: can you confirm? fede@fede-xps:~/lilypond-git/Documentation/notation$ git grep 'anacrucis' repeats.itely:@cindex anacrucis in a repeat repeats.itely:@cindex repeat with anacrucis Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3451 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Font ligatures not working on Linux 64 build
Hello, 2013/6/25 Benjamin Bloomfield bhb...@gmail.com I just installed the 64 bit version of Lilypond on a cloud9 IDE (https://c9.io/) and noticed that ligatures weren't working. (Th had a noticeable gap, when the letters should be typeset as a ligature.) I then installed the x86 version, and it produced the ligature as expected. The font I was using was Garamond Premier Pro. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3436 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: JavaScript error message using website search box
Hello, 2013/6/28 Mark Polesky markpole...@yahoo.com when I do a search for anything using the website search box, I get this dialog box: Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3437 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \omit Dots acts like \hide Dots
Hello, 2013/6/19 Pavel Roskin pro...@gnu.org Hello! \omit Dots should not reserve space for the omitted dots. That's what \hide does. The problems exists in Lilypond 2.16 as well. The \omit keyword just makes it more obvious that the current behavior is wrong. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3426 -- Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Change clef on grace silent rest has no horizontal space
Hello, 2013/6/19 Pavel Roskin pro...@gnu.org Hello! David Kastrup asked me to report this bug earlier today. This is a simplified example. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3427 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: articulate.ly generates incorrect tempo
Hello, 2013/6/21 Pavel Roskin pro...@gnu.org articulate.ly can generate wrong tempo if \tempo is not set explicitly in the beginning of every voice. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3428 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Patch:Doc-enhancement identifiers
Hello Urs, 2013/6/18 Urs Liska lilyli...@googlemail.com Nobody bothering accepting or at lest commenting a free patch contribution? ___ -- Marek Klein http://gregoriana.sk Gregoriana on youtubehttp://www.youtube.com/playlist?list=PLBQHqmaUgUMZ4Bd4w4heeQF9lV9L7BS-s ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Weird Stems with beam::align-with-broken-parts and beam::slope-like-broken-parts
Hello, 2013/6/14 Thomas Morley thomasmorle...@gmail.com Hi, the following code returns missing Stems. (A larger example would show not only missing but also all sorts of weird Stems. see: http://lists.gnu.org/archive/html/lilypond-user/2013-06/msg00334.html ) Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3415 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: If incipit has soprano clef, its staves are not aligned with main score
Hello, 2013/6/12 Pothárn Imre potharn.i...@gmail.com I'm not top posting. % When the incipit has a soprano clef, % the staff lines are not aligned % irrespective of the clef of main part Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3416 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: old-straight-flag + smaller Stem.thickness gives no output and huge overflow
Hello,
2013/5/27 Karol Majewski karol.majew...@gmail.com
The following code gives:
warning: cannot fit music on page: overflow is 1096.382978
and no output. Perhaps it's a bug?
\version 2.17.19
\layout {
\context {
\Score
\override Stem.thickness = #1.2
\override Flag.stencil = #old-straight-flag
}
}
{
c'16 r r d' c' r r d' c' r r d' c' r r d'
c' r r d' c' r r d' c' r r d' c' r r d'
c' r r d' c' r r d' c' r r d' c' r r d'
}
When I set Stem.thickness to default (1.3) everything is OK.
Version 2.16.2 gives valid output regardless of Stem.thickness value.
Thank you for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=3383
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong placed note-heads while modifiying 'staff-space
Hello, 2013/5/29 Thomas Morley thomasmorle...@gmail.com Reported in the german forum http://www.lilypondforum.de/index.php?topic=1443.0 Adjusting 'staff-space sometimes results in wrongly placed note-heads. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3384 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Fwd: Full-measure rest in wrong place after overriding
Forwarding to OP:
-- Forwarded message --
From: David Kastrup d...@gnu.org
Date: 2013/5/20
Subject: Re: Full-measure rest in wrong place after overriding
To: bug-lilypond@gnu.org
Arttu Punkkinen puukiu...@gmail.com writes:
I'm not top posting.
%The full-measure rest in a wrong place?
\version 2.17.18
{
\override Voice.MultiMeasureRest #'staff-position = #0
R1
}
What's your expectation instead?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Marek Klein
http://gregoriana.sk
Gregoriana on
youtubehttp://www.youtube.com/playlist?list=PLBQHqmaUgUMZ4Bd4w4heeQF9lV9L7BS-s
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: crash of musicxml2ly
Hello, 2013/4/24 Laura Conrad lcon...@laymusic.org I attempted to run musicxml2ly on the file http://www2.cpdl.org/wiki/images/9/91/Alessandro_Striggio-Nasce_la_pena-XML.zip using the command musicxml2ly -z --nd --nrp --npl --no-beaming *.zip and musicxml2ly 2.16.1 crashes with the terminal output: Thank you for the report. This has been added as http://code.google.com/p/lilypond/issues/detail?id=3366 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Web/Docs: LilyPond version is not clear on docs web pages
Hello, 2013/5/8 Paul Morris p...@paulwmorris.com 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. Thank you for the suggestion, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3367 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: crash of musicxml2ly
Hello Patrick, 2013/4/24 pls p.l.schm...@gmx.de Laura, you are right. For the time being you will have to unzip the file manually and run musicxml2ly on the .xml file. The conversion with musicxml2ly will be successful (no error messages) but unfortunately the compilation with LilyPond (v2.17.15) will fail due to a segmentation fault. (Something went wrong in the conversion process.) Everything is fine (apart from the -z | --compressed option) when you use our musicxml2ly-dev version on https://github.com/Philomelos/lilypond-musicxml2ly-dev. Thanks for the bug report! hth patrick Do we have a tracker issue for this? (I am not able to find any) Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: triple flats/sharps?
Hallo, 2013/5/7 Marc Hohl m...@hohlart.de Should we raise an issue for this on the tracker? This has been added as http://code.google.com/p/lilypond/issues/detail?id=3356 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: modern-straight-flag and convert-ly
Hello, 2013/4/14 robert edge projectmalam...@gmail.com Using a newly installed version of 2.16 on Linux x86-64 convert-ly is changing: \override Stem #'flag = #modern-straight-flag to: \override Flag #'print = #modern-straight-flag which does not produce the correct output and does not generate an error message. Should be(as per an earlier, related thread on this list): \override Flag #'stencil = #modern-straight-flag Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3344 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: programming error: hyphen not finished yet
Hello, 2013/4/23 Benjamin Drung bdr...@debian.org I'm not top posting. Following small example causes Lilypond to spit out programming error: hyphen not finished yet [1]. Please either fix this bug or disallow the _ -- pattern for lyrics and print a useful error message. Thank you for the report. This has been added as http://code.google.com/p/lilypond/issues/detail?id=3345 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: segfault with 2.17.12
Hello,
2013/4/3 Jan Nieuwenhuizen jann...@gnu.org
I made this typo
\layout {
music = { }
{ \music }
and Lily segfaults on me.
Thank you for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=3323
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: cross staff notes collide
Hello, 2013/4/9 Evan Laforge qdun...@gmail.com When note heads cross to the upper staff, they should cause the upper notes to flip stem directions to avoid collision. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3324 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Manual beaming over rests and vertical spacing problem
Hello, 2013/3/10 Clément themu...@gmail.com Using oneVoice position (or indirectly, partcombineApart) while making a beam go over a rest destroys vertical alignment in a staff. Thank you for the report. This has been added as http://code.google.com/p/lilypond/issues/detail?id=3242 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Increased tuplet number font size causes collision
Hello,
2013/3/13 m...@mikesolomon.org m...@mikesolomon.org
\relative c' {
\override TupletNumber.font-size = #10
\times 2/3 { d d d }
}
Ideally, the tuplet number should avoid the collision by shifting up. The
bracket should shift up as well.
This is currently difficult, as the TupletNumber is a child of the tuplet
bracket and therefore dependent on it for Y-offset.
Thank you for the report. This has been added as
http://code.google.com/p/lilypond/issues/detail?id=3243
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Suggested doc revision for customizing staff positions
Hello, 2013/2/11 Paul Morris p...@paulwmorris.com Here is a suggested revision for the docs, Notation Reference 1.6.2 http://www.lilypond.org/doc/v2.17/Documentation/notation/modifying-single-staves Thank you for the suggestion, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3175 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \remove Vertical_align_engraver creates error message
Hello, 2013/1/31 Eluze elu...@gmail.com every time I use \remove Vertical_align_engraver I get an error message: programming error: didn't find a vertical alignment in this system continuing, cross fingers question: is there a way to get rid of this message e.g. by adding the engraver in another place/context or can we get rid of this message!? This has been added as http://code.google.com/p/lilypond/issues/detail?id=3158 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bass figures are not horizontally aligned to whole notes
Hello,
2013/2/2 Xavier Scheuer x.sche...@gmail.com
My guess is that bass figures should indeed be centered on the note
heads (note column), so default behaviour should be changed accordingly.
But only the figures. Accidentals, +, etc. should not be taken into
account in the centering, contrary to Bertrand's first workaround.
If someone possessing a reference book could confirm this, thanks.
Could this be considered as the minimal example and the bad output?:
\new Staff { \clef F c1 c c \bar |.}
\new FiguredBass \figuremode {
51 6 4+ 2\+ 6
}
Marek
bug squad member
attachment: bug.preview.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: strange output with lilypond book
Hello, 2013/1/21 Julien Rioux jri...@lyx.org Indeed, there is a bug here: the automatic line width detection fails because of the included file. This detection is done by copying the latex preamble to a temporary file in a temp dir, running latex on this file, and parsing some output about the line width from latex. When we compile from the temp dir, any file \input'ed or \include'd within the preamble should also be made available, otherwise latex will fail. Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=3136 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2 Errors in german translation of lilypond.org
Hello, 2013/1/22 Graham Percival gra...@percival-music.ca Hi Michael, The proper address is the bug-lilypond mailing list, which I've CC'd here. On Tue, Jan 22, 2013 at 01:51:14PM +0100, Michael Kerkhoff wrote: On the site: http://lilypond.org/tiny-examples.de.html in the sentence: Wenn Sie einen „Bug“ in Ihrem Minimalbeispiel nicht reproduzieren können, was das Problem wohl eher zu geringes Verständnis von LilyPond, nicht jedoch ein Fehler. in the part: , was das Problem wohl eher zu geringes Verständnis i have 2 corrections: , war das Problem wohl eher ein zu geringes Verständnis Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=3137 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 1.2.4 Setting automatic beam
Hello, 2013/1/6 Federico Bruni fedel...@gmail.com I found three problems in the section Setting automatic beam: Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=3094 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Squad Rota
2013/1/8 Colin Hall colingh...@gmail.com Everyone happy with that? LGTM Marek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Squad Rota
Hello Colin, 2013/1/7 Colin Hall colingh...@gmail.com Marek, would you like me to take one of your days? If you can do other staff for lilipond instead - then do it. If you prefer doing bug squad duties, I prefer to get rid of friday... Marek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Problem with scaled durations
Hello, 2013/1/4 Colin Hall colingh...@gmail.com Oscar has run into a known issue with the limited precision of Rational in Lilypond. Although David is correct that this issue can crop up in many places it makes sense to follow Trevor's suggestion and warn future users who may end up with the same issue encountered by Oscar. Also, we need a tracker to have the C++ rational replaced with a Scheme implementation with unlimited precision. I had a look on the tracker: http://code.google.com/p/lilypond/issues/list?can=2q=rational There does not seem to be an existing issue tracker for this. So, I suggest a tracker for the documentation enhancement, and another to capture the idea of replacing the existing C++ rational implementation with an arbitrary precision implementation. That second tracker may trigger a debate about performance but I'd prefer that took place on the tracker rather than here on the bug list. Here are the issues: http://code.google.com/p/lilypond/issues/detail?id=3084 http://code.google.com/p/lilypond/issues/detail?id=3085 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement request - lookup of sub-properties
Hello, 2013/1/4 Nick Payne nick.pa...@internode.on.net See comment 13 of issue 3056: http://code.google.com/p/lilypond/issues/detail?id=3056. At the moment, when constructing an event function for a text spanner, one can't rely on using ^ or _ to set the direction of the spanner if one wants to tweak bound-details.right.text according to the direction, as that sub-property is not looked up - the direction has to be passed as an additional parameter - see comment 7 as an example of doing that. Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=3086 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: grace note articulation
Hello, just for the evidence, here is the corresponding issue: http://code.google.com/p/lilypond/issues/detail?id=3063 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tie in TabStaff displays one of the unisone notes in a chord
Hello, 2012/12/26 Federico Bruni fedel...@gmail.com In default tablature tied notes are hided. But if a chord contains two identical pitches (played on different strings), one of them is displayed (the one with the string number indication). Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=3066 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Update Contributor’s Guide 5.2 to mention use of LSR
Hello, 2012/12/21 Arle Lommel fene...@gmail.com Section 5.2 of the Contributor’s Guide currently states that all suggested changes to the documentation be submitted as bugs. However, suggestions for documentation of overrides should generally be submitted to the LSR, per this email from Trevor Daniels: The correct way to add [changes like this] to the documentation is to submit your example, with appropriate explanatory text, to the LSR, tagging it for docs, rhythms and tweaks and overrides [or the appropriate place]. This is the way users can add material to the documentation - it will then appear automatically in the Snippets list. Thank you for your suggestion, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3051 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \textLengthOn fails to allow text to align
This was added as http://code.google.com/p/lilypond/issues/detail?id=3032by Trevor. Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Avoiding collisions involving full-bar rests
Hello,
2012/12/14 Daniel Rosen drose...@gmail.com
%{ In the example below, LilyPond should automatically push the full-bar
rest in
the lower voice down vertically to avoid having it collide with the
notehead in
the upper voice. %}
Thank you for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=3043
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: articulate can't deal with
Hello, 2012/12/7 Thomas Morley thomasmorle...@googlemail.com seems articulate can't deal with in any tested version Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=3008 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-2.16.1-1.linux-ppc.sh Won't run on a debian squeeze ppc
Hello, 2012/11/29 Philippe Neyrat philippe.ney...@mailz.org Hi, evreyone. I've try to install lilypond 2.16.1 version on a IBook G4 running Debian squeeze (ppc architecture) : $ uname -a Linux neptune 2.6.32-5-powerpc #1 Sun Sep 23 09:29:40 UTC 2012 ppc GNU/Linux but get an error : the script asked for a ppc architecture : Thanks for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2988 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Funny alignment of different bar lines at the end of a system
Hello,
2012/11/29 Ben Rudiak-Gould benrud...@gmail.com
\version 2.16.1
{ c'1 } { c'1 \set Staff.whichBar = || }
Thanks for the report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=2989
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \RemoveEmptyStaves in StaffGroup context crashes
Hello,
2012/11/29 Ben Rudiak-Gould benrud...@gmail.com
% This crashes with a stack overflow (at least on the official Windows
build):
\version 2.16.1
\new StaffGroup \with \RemoveEmptyStaves { c' }
Thank you for thr report, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=2990
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: sacredHarpHeads in partcombine sections
Hello Steve,
2012/11/28 Steve Tarr stevet19...@comcast.net
If I use explicit voices for each part, the stem directions are handled
independently for each voice so I lose the information that the voices are
crossing over each other. (And I get warning messages about note
collisions
when I compile this.)
What about:
\new Staff
\new Voice { \voiceOne \PartOne }
\new Voice { \voiceTwo \PartTwo }
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midiChannelMapping (introduced in 2.14) not documented in NR
Hello, 2012/11/28 Federico Bruni fedel...@gmail.com Dear Bug Squad I don't want to push you but I think that you may have missed this report, hidden inside a reply to a question made in lilypond-user: http://lists.gnu.org/archive/**html/bug-lilypond/2012-11/**msg00112.htmlhttp://lists.gnu.org/archive/html/bug-lilypond/2012-11/msg00112.html I think that midiChannelMapping is not properly documented. Thank you for double report. This has been added as http://code.google.com/p/lilypond/issues/detail?id=2986 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: sacredHarpHeads in partcombine sections
Hello,
2012/11/28 Steve Tarr stevet19...@comcast.net
SacredHarpHeads aren't displayed in partcombine sections when the second
part is
at a higher pitch than the first part.
\version 2.17.7
\key a \minor
\partcombine
\relative a' { \sacredHarpHeadsMinor a4 c4 a4 c4 }
\relative a' { \sacredHarpHeadsMinor a4 a4 c4 c4 }
The third notes in the example are incorrectly changed from sacred-harp
heads to
conventional heads.
Thank you for the report, it has been added as
http://code.google.com/p/lilypond/issues/detail?id=2987
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: add @cindex for MIDI instruments
2012/11/19 Trevor Daniels t.dani...@treda.co.uk OK, Marek - done. See 2967. Thank you very much! Marek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Back in the saddle
Hello all, 2012/11/18 Colin Hall colingh...@gmail.com Since you were last on the squad we have a new member, Joseph Wakeling. Right now the rota is: Mon - Colin H Tue - Eluze Wed - Marek Thu - Joe Fri - Marek Sat - Mark Sun - Colin H I suggest you take one of Marek's shifts. Colin, are you sure all the members are still active? If so, I would prefer to get rid of Friday... Marek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: add @cindex for MIDI instruments
Hello Trevor, 2012/11/16 Trevor Daniels t.dani...@treda.co.uk Trevor Daniels wrote Thursday, November 15, 2012 4:10 PM I was (partly) wrong - the index entry in the left column does take you to the correct place in the document. However, the section entry (the one in the right column) and the Instrument names entry in the HTML side panel take you to Creating MIDI files, so the issue I suggested raising:- Bugsquad: could you raise an issue to check the docs for unnumberedsubsubsecs without nodes using the above as an example. Thanks. still needs to be done. would you, please, be so kind and formulate the issue, which should be tracked? I am not able to do it. Thanks, Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: finding input for notes in PDF file
Forwarding to original poster (he might not be following bug-lilypond): 2012/11/5 Phil Holmes m...@philholmes.net David Biddiscombe da...@marazion59.plus.com wrote in message news:1352122793.10889.54.**camel@augustine... I'm not top posting. Re the lilypond facility to point and click on the PDF viewer to find notes in the input (version 2.10.33 manual section 13.7), I find that the response is often *very* slow or nonexistent, despite 'jiggling' with the mouse. I can't find anything on this in your bug tracker; is there anything I can do to remedy it? Very many thanks for your help, David. It's probably related to your operating system and PDF viewer. Could you provide details. You might consider upgrading. We're currently at 2.16 stable. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bww to lilypond converter
Hello, 2012/11/4 Federico Bruni fedel...@gmail.com I've just stumbled on this converter from .bww to .ly: http://www.jezra.net/projects/**bwwtolilyhttp://www.jezra.net/projects/bwwtolily Jon Kulp already announced this converter in -user list 3 years ago: http://lists.gnu.org/archive/**html/lilypond-user/2009-07/**msg00030.htmlhttp://lists.gnu.org/archive/html/lilypond-user/2009-07/msg00030.html I don't know anything about bagpipes music, but I think that it may be added to the list in easier-editing page. It's released with GPL v3 Thank you for the suggestion, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2956 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Problem with padding and TextScript
Hello, 2012/11/6 Trevor Daniels t.dani...@treda.co.uk While browsing the Learning Manual I noticed the last example in Section 3.4.4 http://www.lilypond.org/doc/v2.16/Documentation/learning/saving-typing-with-variables-and-functions displays a fault. It is intended to show the use of 'padding to displace TextScript, but the script is not displaced. The example is still incorrect in the latest 2.17.7 manual, but I don't know when it went wrong. Possibly the new skyline code packing things closer together? I've not yet raised a bug report as I don't know whether this behaviour is now intended, so I didn't know whether to classify it as a code bug or a documentation issue. Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=2957 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Glissando avoid accidental bug?
Hello,
2012/10/31 Nick Payne nick.pa...@internode.on.net
Regardless of whether I set the end-on-accidental override to true or
false, or omit it completely, the glissandi don't stop short of the
accidental.
\version 2.17.5
\relative c'' {
\accidentalStyle modern
\override Glissando #'(bound-details right end-on-accidental) = ##t
c1\glissando cis\glissando c
}
Thank you for the report. This has been added as
http://code.google.com/p/lilypond/issues/detail?id=2942
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: A documentation suggestion, was: Problem with remove bar number/ why I'm not upgrading to the new stable version
2012/10/28 Janek Warchoł janek.lilyp...@gmail.com On Sun, Oct 28, 2012 at 11:09 AM, David Kastrup d...@gnu.org wrote: Janek Warchoł janek.lilyp...@gmail.com writes: +1 for updating documentation. Would make sense for the bug squad to register the proposal. I don't think it would be suitable in the proposed form but that does not mean we should ignore it. Forwarded to bug-lilypond. Bug Squad, please look at A documentation suggestion, was: Problem with remove bar number/ why I'm not upgrading to the new stable version thread on -user. This has been added as http://code.google.com/p/lilypond/issues/detail?id=2943 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \divisiomaior it's too much largest since version 2.15
Hello,
2012/10/25 Manuel Burgos manon...@gmail.com
The following code:
divisioMinima = {
\once \override BreathingSign #'stencil =
#ly:breathing-sign::divisio-minima
\once \override BreathingSign #'Y-offset = #0
\breathe
}
It's right working in 2.14 versions and previous, but since 2.15 it's
wrong
Thank you for the report, it was added by Benkő Pál as
http://code.google.com/p/lilypond/issues/detail?id=2926
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \divisioMaior too much largest than the older versions since 2.15.
This was added by Benkő Pál as http://code.google.com/p/lilypond/issues/detail?id=2926 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: The divisioMaior is too much larger
This was added by Benkő Pál as http://code.google.com/p/lilypond/issues/detail?id=2926 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Documentation figured-bass
Hello, 2012/10/23 Noeck noeck.marb...@gmx.de Hi, the last two snippets on this page are identical, aren't they? http://lilypond.org/doc/v2.16/Documentation/notation/figured-bass Is that a problem that only occurs in older versions? Should the documentation be adapted? Thank you for the report, it has been added as http://code.google.com/p/lilypond/issues/detail?id=2927 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Report: Duplicated Tempo and key signature
2012/10/18 Songmuh Jong song...@yahoo.com
I don't see my issue listed there. Attached is a zip file containing the
.ly file and the pdf output using both 2.14.2 and 2.16.0.
It works, if you add \grace s8 at the beginning of the upper staff:
\version 2.14.2
upper = \relative c' {
\key g \major
\time 4/4
\clef treble
\grace s8 r2_\markup{ \italic \bold \tiny marcato } \appoggiatura cis8-2
d2-3
}
lower = \relative c {
\key g \major
\clef bass
\appoggiatura cis8-2 d2-1 r2
}
\book {
\score {
\new PianoStaff
\context Staff = upper {
\upper
}
\context Staff = lower {
\lower
}
\layout { }
}
}
HTH
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Report: Duplicated Tempo and key signature
Hello, 2012/10/14 Songmuh Jong song...@yahoo.com I'm not top posting. % duplicated tempo printed % key signature appearsduped % This only happens when the bass starts with \appoggiatura This coresponds to Known issues and warnings in http://lilypond.org/doc/v2.16/Documentation/notation/special-rhythmic-concerns#grace-notes Does this help you? Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Cross-staff arpeggios and dynamics collide
Hello,
2012/10/15 Daniel Berjón asurancetu...@gmail.com
% Cross-staff arpeggios and dynamics collide.
\version 2.16.0
\new PianoStaff {
\set PianoStaff.connectArpeggios = ##t
{c' e' g'4\arpeggio}
\new Dynamics {r4\ff}
{c' e' g'4\arpeggio}
}
Thank you for the report, it has been added as
http://code.google.com/p/lilypond/issues/detail?id=2908
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Manual search returns results from wrong version
Hello, 2012/10/16 Nick Payne nick.pa...@internode.on.net Going to the manual page for 2.16 ( http://lilypond.org/manuals.html) and entering a search term (eg I tried footnote) in the search box at upper right returns hits in the 2.17 manuals. The search presented to Google is: site:lilypond.org/doc/v2.17 footnote Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2909 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: problem with 'outside-staff-padding
Hello, 2012/10/16 David Nalesnik david.nales...@gmail.com In the example in the documentation of 2.17.4 relating to 'outside-staff-padding, the last line of text ought to be close to the previous text. Compare: 2.16 - http://www.lilypond.org/doc/v2.16/Documentation/notation/vertical-collision-avoidance 2.17.4 - http://www.lilypond.org/doc/v2.17/Documentation/notation/vertical-collision-avoidance The problem is visible first with 2.17.1. Thanks for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2910 Marek, bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stems in TabStaff are not removed when manual beaming is used
Hello, 2012/10/13 Federico Bruni fedel...@gmail.com As you can see in the attached image, the pull-off sign (slur in TabStaff) is moved up when using manual beaming. It looks like Stems in default TabStaff are just made transparent when using manual beams. Maybe the stem stencil should be set to false also in this case. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2907 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: \shape warnings
Hello, 2012/10/11 Urs Liska lilyli...@googlemail.com Hi list, several months ago David Nalesnik (together with input from others) updated the older \shape function that allows shaping the control-points of curve grobs - which provided a massive increase in productivity when dealing with slurs etc. For example, one major improvement was the handling of broken curves. After it was finished the function has been incorporated in LilyPond's code (http://code.google.com/p/**lilypond/issues/detail?id=2572http://code.google.com/p/lilypond/issues/detail?id=2572 **) and was recently changed further (http://code.google.com/p/**lilypond/issues/detail?id=2873http://code.google.com/p/lilypond/issues/detail?id=2873 **) However, David removed one very interesting feature from the function in order to be able to provide a more concise and clean patch. In 'our' version of the function the function issued warnings (and optionally colored the curves) when it found a mismatch between the number of curve siblings (broken parts of the curve) and lists of offset-pairs. This is a very useful feature because you get noticed if changed line breaking results in a different number of curve parts (which is most likely to spoil your tweaking). See the attachment for the older version of the function. Please note that it just redefines the built-in \shape function and doesn't use it. It isn't meant as the model for a new implementation (as I know the function has in the meantime been changed already) but to show the mentioned functionality. What I would like to achieve with this email is that someone opens a new issue with the request for inclusion of this functionality to the \shape function now included in Lilypond. David suggested he might revisit his code to make it more stable. What i consider essential is the part that issues warnings on the console output. Personally I like the coloring very much, but I could imagine that some people would find this too intrusive (even if the default color would be black?) Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2893 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Drop C guitar tuning
Hello, 2012/10/12 Alex anticult...@googlemail.com Could you add the drop c guitar tuning to the ly\string-tunings-init.lyfile? It should be the following line: \makeDefaultStringTuning #'guitar-drop-c-tuning \stringTuning c, g, c f a d' Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2894 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement request for web page http://lilypond.org/manuals.html
Hello, 2012/10/12 Jim Long lilyp...@umpquanet.com Recently and historically, several users have commented that the web page at reference could be enhanced by having conspicuous links to downloadable PDF versions of the lilypond documentation. The following patches to http://lilypond.org/manuals.html illustrate a design mock-up of how the manuals.html page might look after Thank you for your proposal, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2895 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [musicxml2ly] unwanted staves and voices [was: missing voice-element in chorded note leads to unwanted additional staff]
Hello,
2012/10/3 pls p.l.schm...@gmx.de
now the summaries and descriptions of the issues got mixed up. I suggest
the following:
Issue 2879: [musicxml2ly] spurious staff
if an .xml file contains only staff elements with value 1 (i.e.
staff1/staff) AND no voice element in a chorded note musicxml2ly
erroneously thinks that there are several staves. (I haven't tested what
happens when there are several staff elements with different values in an
.xml fle.
Test file:
https://www.dropbox.com/s/l9mt7iqd38lqqng/unwanted_staves.xml
The result is:
\new Staff
\context Staff =1
\context Voice = PartPOneVoiceOne { \voiceOne
\PartPOneVoiceOne }
\context Voice = PartPOneVoiceNone { \voiceTwo
\PartPOneVoiceNone }
This leads to a second unwanted empty staff.
Without any staff element in the .xml file the result is:
\new Staff
\context Staff
\context Voice = PartPOneVoiceOne { \voiceOne
\PartPOneVoiceOne }
\context Voice = PartPOneVoiceNone { \voiceTwo
\PartPOneVoiceNone }
and there is NO unwanted additional staff!
In this case musicxml2ly should be taught to ignore the staff-elements
if there is only one staff.
Issue 2867: [musicxml2ly] unwanted voices
if a note element contains a chord/ element but no voice element
musicxml2ly puts the chorded note without a voice-element in an own voice
(PartPOneVoiceNone) instead of placing the notes in a chord construct ( a'
c''1) in the same voice.
In this case musicxml2ly should be taught to be tolerant and automatically
assign notes containing chord/-elements to the voice of the first note of
the chord. (In MusicXML the first note of a chord does not contain a
chord/-element.)
Test file:
https://www.dropbox.com/s/8bep4ly69xfwfmt/unwanted_voices.xml
Here the issues:
http://code.google.com/p/lilypond/issues/detail?id=2886
http://code.google.com/p/lilypond/issues/detail?id=2887
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [musicxml2ly] beams and lost lyric syllables
Hello, 2012/10/6 pls p.l.schm...@gmx.de I forgot to mention that syllables don't get lost when musicxml2ly is used with the option --no-beaming. But this is only a dirty workaround as LilyPonds' autobeaming algorithm overrides the beaming information provided by the .xml-file. Beyond that we implemented a new musicxml2ly feature to translate the stem directions ( https://github.com/Philomelos/lilypond-musicxml2ly-dev/commit/0747e5ce34f8d3a6128302ec0363a8f5f91ce3fd). This leads to ugly effects in combination with --no-beaming as LilyPond tries to connect notes with stems pointing in different directions... Am 05.10.2012 um 23:06 schrieb pls: Hey all, syllables under beamed notes are swallowed by musicxml2ly (LilyPond v2.17.3). This seems to be a close relative of Issue 2881. Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=2888 Marek bug squad member ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
