Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental
Comment #4 on issue 298 by colinpkc...@gmail.com: Ties do not appear when shortened because of an accidental http://code.google.com/p/lilypond/issues/detail?id=298 Issue 1219 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental
Updates: Cc: lemzw...@googlemail.com Comment #5 on issue 298 by colinpkc...@gmail.com: Ties do not appear when shortened because of an accidental http://code.google.com/p/lilypond/issues/detail?id=298 Issue 840 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1219 in lilypond: Broken tie may become a too small dot
Updates: Status: Duplicate Mergedinto: 298 Comment #9 on issue 1219 by colinpkc...@gmail.com: Broken tie may become a too small dot http://code.google.com/p/lilypond/issues/detail?id=1219 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 840 in lilypond: broken ties too short when time signature changes
Updates: Status: Duplicate Mergedinto: 298 Comment #1 on issue 840 by colinpkc...@gmail.com: broken ties too short when time signature changes http://code.google.com/p/lilypond/issues/detail?id=840 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space
Updates: Labels: -Patch-new Patch-review Comment #3 on issue 1563 by pkx1...@gmail.com: strange vertical line at staff begin using StaffSymbol #'staff-space http://code.google.com/p/lilypond/issues/detail?id=1563 Passes make but I get a difference in one reg test..see attached Attachments: Screenshot.png 37.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1760 in lilypond: \RemoveEmptyStaves only works inside a \layout block
Status: Accepted
Owner: n.putt...@gmail.com
Labels: Type-Defect Priority-High Patch-review
New issue 1760 by n.putt...@gmail.com: \RemoveEmptyStaves only works inside
a \layout block
http://code.google.com/p/lilypond/issues/detail?id=1760
http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg00359.html
\RemoveEmptyStaves is defined inside engraver-init.ly, which renders it
inaccessible as an identifier outside a \layout block.
The following snippet causes the parser to emit two errors, and the second
bar isn't removed:
\version "2.15.5"
\new Staff \RemoveEmptyStaves {
c'1 \break
r1
}
%{
error: unknown escaped string: `\RemoveEmptyStaves'
\new Staff
\RemoveEmptyStaves {
error: syntax error, unexpected STRING
\new Staff
\RemoveEmptyStaves {
%}
Patch: http://codereview.appspot.com/4664076/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Labels: Patch-review Comment #6 on issue 1695 by n.putt...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Patch: http://codereview.appspot.com/4683043/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes
Comment #2 on issue 1759 by lemniska...@gmail.com: hairpin aligns to lyrics instead of notes http://code.google.com/p/lilypond/issues/detail?id=1759 oops, sorry again... i searched for "hairpin" and didn't found it - i should've also searched for "hairpins". Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: startpoint of decrescendo hairpins
2011/7/12 Janek Warchoł : > I don't see this reported yet, so i add it to the tracker as issue > 1759 http://code.google.com/p/lilypond/issues/detail?id=1759 It was posted as issue 1738 which got merged as a duplicate (ulitmately of issue 620). Cheers, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1507 in lilypond: weird linebreaks in song output
Updates: Status: Started Owner: n.putt...@gmail.com Labels: Patch-review Comment #5 on issue 1507 by n.putt...@gmail.com: weird linebreaks in song output http://code.google.com/p/lilypond/issues/detail?id=1507 This is more problematic than I originally thought, since we have two regtests leaking global settings: 1) song-basic-nonenglish.ly uses \festivalsyl as detailed above; 2) song-skip-noword.ly sets *skip-word* to #f. http://codereview.appspot.com/4693046/ deals with this by changing the globals to parameters, but obviously in the case of song-skip-noword.ly, we still have to reset the default for *skip-word* at the end of the file to prevent leakage. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes
Updates: Status: Duplicate Mergedinto: 620 Comment #1 on issue 1759 by n.putt...@gmail.com: hairpin aligns to lyrics instead of notes http://code.google.com/p/lilypond/issues/detail?id=1759 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Manual beams confuse lyrics positioning when autoBeam is off
On 12 July 2011 21:08, BognárBálint wrote: > When autoBeam is off and I manually place a beam on two different 1/8 notes > (eg. a 'c' and a 'd'), only one syllable of lyrics is positioned under these > two notes (eg. if the lyrics is "ly -- rics" (or "ly rics"), "ly" is > positioned under the note 'c' and there is nothing under the note 'd'). This is correct behaviour: manual beams signal melismata, so a lyric syllable will last for the length of a beam and be left-aligned. http://lilypond.org/doc/v2.14/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable Cheers, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds.
Comment #3 on issue 620 by n.putt...@gmail.com: It should be possible to specify more specific spanner bounds. http://code.google.com/p/lilypond/issues/detail?id=620 Issue 1759 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1759 by lemniska...@gmail.com: hairpin aligns to lyrics instead
of notes
http://code.google.com/p/lilypond/issues/detail?id=1759
Both beginning and end of the hairpin are aligned to Lyrics - and they are
not even in the same voice!
\version "2.14.1"
\score {
<<
\new Staff { es''2. f'4 }
\addlyrics { a_long_hairpin blh }
\new Staff { b4 b b b }
\new Dynamics { s4 \< s4 s4 s4 \! }
>>
}
2.12.3 did the same.
Attachments:
bug.preview.png 4.4 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Manual beams confuse lyrics positioning when autoBeam is off
> I'm not top posting.
Dear Developers!
I probably found an issue in Lilypond version 2.14.1 (latest stable build at
2011-07-12).
When autoBeam is off and I manually place a beam on two different 1/8 notes
(eg. a 'c' and a 'd'), only one syllable of lyrics is positioned under these
two notes (eg. if the lyrics is "ly -- rics" (or "ly rics"), "ly" is
positioned under the note 'c' and there is nothing under the note 'd'). For
better understanding, please compare the output for the two examples below:
%% When autoBeam is off,
%% manual beams confuse lyrics position.
\version "2.14.1"
<<
\relative c' {
\autoBeamOff
a8[ b] c[ d]
}
\addlyrics {
ly -- rics ly -- rics
}
>>
%% When autoBeam is on,
%% everything goes as it should.
\version "2.14.1"
<<
\relative c' {
\autoBeamOn
a8[ b] c[ d]
}
\addlyrics {
ly -- rics ly -- rics
}
>>
Thank you in advance for your consideration and I'd like to apologise you for
my grammatical mistakes.
Best regards:
--- Bognár Bálint
--- bobq...@inf.elte.hu
Ps: To avoid confusion, I would like to tell that Bálint is my first name
(because I'm Hungarian).
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: startpoint of decrescendo hairpins
I don't see this reported yet, so i add it to the tracker as issue
1759 http://code.google.com/p/lilypond/issues/detail?id=1759
cheers,
Janek
2011/7/5 Phil Holmes :
> That seems like a bug to me. I'll report it as a bug, but you can work
> around it by putting the dynamics in the "upper" music rather than a
> dynamics context.
>
> ==
> Phil Holmes
>
>
> - Original Message - From: "Ewald Gutenkunst"
>
> To: "LilyPond"
> Sent: Tuesday, July 05, 2011 1:17 AM
> Subject: startpoint of decrescendo hairpins
>
>
> Hi,
>
> I have a question to decrescendo-hairpins and lyrics:
> How can I change the startpoint of the decresc, to begin at the note an not
> at the beginning of the lyric?
>
>
> \version "2.14.1"
>
> melody = { d''2 c''2 | es''1 }
> text = \lyricmode {a long hairpin }
> upper = {c'1 | b4 b b b }
> dynamics = {s1 | s4 \> s4 s4 s4 \! }
>
> \score {
> <<
> \new Voice = "mel" \melody
> \new Lyrics \lyricsto mel \text
> \new Staff \upper
> \new Dynamics \dynamics
> >>
> }
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 216 in lilypond: Enhancement: the ability to change staff line spacing inside a \layout{} block
Comment #7 on issue 216 by n.putt...@gmail.com: Enhancement: the ability to
change staff line spacing inside a \layout{} block
http://code.google.com/p/lilypond/issues/detail?id=216
Issue 1758 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1758 in lilypond: layout-set-staff-size doesn't work properly
Comment #2 on issue 1758 by lemniska...@gmail.com: layout-set-staff-size doesn't work properly http://code.google.com/p/lilypond/issues/detail?id=1758 oops, sorry... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura)
Updates: Status: Fixed Labels: fixed_2_15_5 backport Comment #18 on issue 75 by reinhold...@gmail.com: Slurs cannot be nested (including acciaccatura and appoggiatura) http://code.google.com/p/lilypond/issues/detail?id=75 Fixed with commit 32776795a1be5c0ec472f59694510705607673b0 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1758 in lilypond: layout-set-staff-size doesn't work properly
Updates: Status: Duplicate Mergedinto: 216 Comment #1 on issue 1758 by n.putt...@gmail.com: layout-set-staff-size doesn't work properly http://code.google.com/p/lilypond/issues/detail?id=1758 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1676 in lilypond: Tremolo with change staff produces false dotted note
Updates: Status: Fixed Labels: fixed_2_15_5 backport Comment #3 on issue 1676 by reinhold...@gmail.com: Tremolo with change staff produces false dotted note http://code.google.com/p/lilypond/issues/detail?id=1676 Fixed with commit 4e96cd885b2e6998ad1c8e3e09c39301d0699502 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning
Updates: Status: Fixed Comment #5 on issue 1581 by reinhold...@gmail.com: Pitched trill between tied notes causes `unterminated tie' warning http://code.google.com/p/lilypond/issues/detail?id=1581 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issues regarding too-short-tie
These all appear to be the same issue to me. Is it possible to merge some of the examples from the third issue into the first? I feel like the tiny.examples in that one most clearly demonstrate the problem. Derek On Tue, Jul 12, 2011 at 9:16 AM, Dmytro O. Redchuk wrote: > Hi! > > As I can see, these issues are the same very probably: >* http://code.google.com/p/lilypond/issues/detail?id=298 >* http://code.google.com/p/lilypond/issues/detail?id=840 >* http://code.google.com/p/lilypond/issues/detail?id=1219 > > If yes, I would leave the first, marking others as duplicates. > > Please, any thoughts? > > -- > Dmytro O. Redchuk > Bug Squad > "Easy to use" is easy to say. > --Jeff Garbers > > ___ > 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: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning
Updates: Labels: fixed_2_15_5 backport Comment #4 on issue 1581 by reinhold...@gmail.com: Pitched trill between tied notes causes `unterminated tie' warning http://code.google.com/p/lilypond/issues/detail?id=1581 Fixed with commit c3bbf906e97f986dda90e78cebf90a48446cef9d ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1256 in lilypond: Extra SlurEvent modifies extents of broken slurs
Updates: Status: Fixed Labels: fixed_2_15_5 backport Comment #2 on issue 1256 by reinhold...@gmail.com: Extra SlurEvent modifies extents of broken slurs http://code.google.com/p/lilypond/issues/detail?id=1256 Fixed with commit 32776795a1be5c0ec472f59694510705607673b0 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1758 in lilypond: layout-set-staff-size doesn't work properly
Status: New
Owner:
Labels: Type-Defect Priority-High
New issue 1758 by lemniska...@gmail.com: layout-set-staff-size doesn't work
properly
http://code.google.com/p/lilypond/issues/detail?id=1758
Apparently layout-set-staff-size changes everything except staff space...
\score {
{ b }
\layout {
#(layout-set-staff-size 12) %doesn't change staff spave
}
}
Attachments:
layout-set-staff-size.PNG 4.7 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 750 in lilypond: Misleading warning when a Lyrics context is empty
Updates: Status: Fixed Owner: reinhold...@gmail.com Labels: fixed_2_15_5 backport Comment #2 on issue 750 by reinhold...@gmail.com: Misleading warning when a Lyrics context is empty http://code.google.com/p/lilypond/issues/detail?id=750 Fixed with commit 10267f06f910f763196b391bd2bc664db7a78e0a ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issues regarding too-short-tie
Hi! As I can see, these issues are the same very probably: * http://code.google.com/p/lilypond/issues/detail?id=298 * http://code.google.com/p/lilypond/issues/detail?id=840 * http://code.google.com/p/lilypond/issues/detail?id=1219 If yes, I would leave the first, marking others as duplicates. Please, any thoughts? -- Dmytro O. Redchuk Bug Squad "Easy to use" is easy to say. --Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Comment #16 on issue 1752 by percival.music.ca: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 Yes, an \override would be fine for selecting the old font from a user perspective. I can't comment on whether that's the best technical solution, but presumably if it's not a good one, somebody else will complain about the eventual patch. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 409 in lilypond: collision tie and time signature
Updates: Labels: -Priority-High Priority-Medium Comment #5 on issue 409 by brownian.box: collision tie and time signature http://code.google.com/p/lilypond/issues/detail?id=409 Is this really a bug? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods
Comment #12 on issue 1234 by brownian.box: Fill-line should not use word space, but should use springs-and-rods http://code.google.com/p/lilypond/issues/detail?id=1234 Thank you! And thank you, Neil, for "supporting" me .) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 592 in lilypond: Regression: Tie direction reverse incorrectly on a middle-staff note
Comment #3 on issue 592 by brownian.box: Regression: Tie direction reverse incorrectly on a middle-staff note http://code.google.com/p/lilypond/issues/detail?id=592 Now (at least 2.12 and above) both ties are up. Please, does this mean that the issue was fixed by some incident? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1705 in lilypond: New breve rest with ledger lines
Comment #3 on issue 1705 by percival.music.ca: New breve rest with ledger lines http://code.google.com/p/lilypond/issues/detail?id=1705 sure, if somebody can send me the final patch. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Updates: Labels: font Comment #15 on issue 1752 by lemniska...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 2011/7/11 : Comment #13 on issue 1752 by percival.music.ca: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 Unless absolutely every single person prefers the new clef, I have serious concerns about changing it. This sounds like a Critical regression to me. ?!? Comment #14 by percival.music.ca: wait, let me rephrase that: it wouldn't be a Critical regression because it would be a deliberate change. However, [...] Whew. Besides, I really think that supporting the old clef would not be a great deal of work -- and that work would be beneficial to all future font work. Ok, i agree that if there will be anyone not satisfied with the change, we should make it possible to choose old clef. Do you think that approach similar to choosing between one- and double-lined breve would be sufficient? (see http://lilypond.org/doc/v2.15/Documentation/notation/writing-rhythms#durations) If so, i can investigate it. Still, i hope that my revised proposal will be accepted by people that didn't like the original suggestion; most of them didn't give their opinions on the new suggested shape yet. I mean, if you actually made a separate "Oscypek" font, which was optional, then I would be 100% comfortable pushing patches from you (to that font) completely blindly. No user discussion, no review, etc. You could make whatever changes to that font you wanted. (caveats: I'd need to get agreement from other developers, and your patches would still need to compile. And you might want to survey users anyway. But you would be working from a position of strength (i.e. you would have the final say about what went into Oscypek), instead of trying to reach consensus with everybody for every single change!) Yes, i thought about this, too. However, until we encounter a font issue that couldn't be agreed upon, i don't think it's needed. Firtsly, i'm happy with the current discussion (and i think that my revised proposal is indeed better than the original one - thanks to your feedback!). Secondly, if i see something that is - in my opinion - wrong (i'm not talking about personal style preferences), i'd prefer to fix it for everyone, not only include an optional switch. Nevertheless, designing fonts in different styles interests me, so sooner or later it will be good to do what you say. thanks, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods
Comment #11 on issue 1234 by perpeduu...@googlemail.com: Fill-line should not use word space, but should use springs-and-rods http://code.google.com/p/lilypond/issues/detail?id=1234 +1 for Neil and Dmytro: Leave it as it is. Unless I totally missed some other commit, \fill-line /does/ still use word-space. I tried to remove this in my initial patch for issue #382 and issue #1116, but it mixed up output when the spacing is very tight. I'd prefer this to use a spring-and-rods approach /additional/ to word-space, that's why it went in as an enhancement in the tracker. (However, I'm not sure anymore if there is an existing implementation of spring-and-rods which can be used here; I suppose it has to be a Scheme implementation?) But this is actually a change in semantics, which is not covered by the other issues. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
