Re: KeyCancellation spacing issue when staves have different key signatures
Neil Puttock wrote: If you really want to get rid of it anyway (which means that you have to invent some other method to tell your musicians that there is a key change), you can use brute force: \override Staff.KeyCancellation #'stencil = ##f I don't! I'd just like the extra space to be removed. One solution is to set \override Staff.KeyCancellation #'X-extent = #'(0 . 0) /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hara_kiri_engraver shouldn't handle both staves of a PianoStaff as separate single staves
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=442
Cheers,
- Graham
Valentin Villenave wrote:
Greetings,
this issue has been discussed on -user for a few days with Kieren, Neil and Tao:
When typesetting an orchestral score with Piano or Harp parts, and using
RemoveEmptyStaffContext, the PianoStaff can sometimes be reduced to one
single staff (for instance when only one hand is playing).
This doesn't seem to be the right engraving rule in orchestral scores,
where both staves are usually preserved wherever there's enough space
on the page.
Here's Kieren suggestion to deal with this issue:
-- Forwarded message --
From: Kieren MacMillan [EMAIL PROTECTED]
Date: 26 août 2007 17:47
IMO, this should be a setting similar to connectArpeggios -- say,
keepAliveTogether -- where the default is ##t, but it can be set to
##f as desired. I suppose this could also be extended (as an
interface) to ChoirStaff, StaffGroup, etc., for ultimate flexibility.
In the following example, the piano staves should only be hidden in
the third system.
one = {
\repeat unfold 4 { a4 b c' d'} \break
\repeat unfold 4 { a4 b c' d'} \break
\repeat unfold 4 { a4 b c' d'} \break
a1
}
two = { \clef bass
\repeat unfold 4 { a4 b c' d'} \break
\repeat unfold 4 { a4 b c' d'} \break
R1*4 \break
a1
}
three = { \clef bass
\repeat unfold 4 { a4 b c' d'} \break
R1*4 \break
R1*4 \break
a1
}
\score {
\context Staff = one \one
\new PianoStaff
\context Staff = two \two
\context Staff = three \three
\layout {
\context { \RemoveEmptyStaffContext }
}
}
This is more enhancement than a real bugfix, but maybe it could be
added to the tracker...
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 442 in lilypond: request: RemoveEmptyStaffContext reducing PianoStaff to one staff
Issue 442: request: RemoveEmptyStaffContext reducing PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442
New issue report by gpermus:
When typesetting an orchestral score with Piano or Harp parts, and using
RemoveEmptyStaffContext, the PianoStaff can sometimes be reduced to one
single staff (for instance when only one hand is playing).
This doesn't seem to be the right engraving rule in orchestral scores,
where both staves are usually preserved wherever there's enough space
on the page.
Here's Kieren suggestion to deal with this issue:
-- Forwarded message --
From: Kieren MacMillan [EMAIL PROTECTED]
Date: 26 août 2007 17:47
IMO, this should be a setting similar to connectArpeggios -- say,
keepAliveTogether -- where the default is ##t, but it can be set to
##f as desired. I suppose this could also be extended (as an
interface) to ChoirStaff, StaffGroup, etc., for ultimate flexibility.
In the following example, the piano staves should only be hidden in
the third system.
one = {
\repeat unfold 4 { a4 b c' d'} \break
\repeat unfold 4 { a4 b c' d'} \break
\repeat unfold 4 { a4 b c' d'} \break
a1
}
two = { \clef bass
\repeat unfold 4 { a4 b c' d'} \break
\repeat unfold 4 { a4 b c' d'} \break
R1*4 \break
a1
}
three = { \clef bass
\repeat unfold 4 { a4 b c' d'} \break
R1*4 \break
R1*4 \break
a1
}
\score {
\context Staff = one \one
\new PianoStaff
\context Staff = two \two
\context Staff = three \three
\layout {
\context { \RemoveEmptyStaffContext }
}
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 367 in lilypond: layout-set-staff-size doesn't change the distance between the staff lines
Issue 367: layout-set-staff-size doesn't change the distance between the staff lines http://code.google.com/p/lilypond/issues/detail?id=367 Comment #2 by gpermus: Ok, done. Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 407 in lilypond: tabStaff cannot handle \partcombine
Issue 407: tabStaff cannot handle \partcombine http://code.google.com/p/lilypond/issues/detail?id=407 Comment #2 by gpermus: I've added this as a bug in the docs. Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 440 in lilypond: Tie direction reverse incorrectly between whole notes tied across line breaks
Issue 440: Tie direction reverse incorrectly between whole notes tied across line breaks http://code.google.com/p/lilypond/issues/detail?id=440 Comment #2 by gpermus: Yes, dupe of 434. However, it's weird that Trevor reports specific requirements for this bug to appear, whereas 434 has a fairly bland example. Issue attribute updates: Status: Duplicate -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \markup \note doesn't work inside #'bound-details
Added as
http://code.google.com/p/lilypond/issues/detail?id=443
Please look at the example I added; I greatly simplified your example.
In the future, please send minimal examples like that.
- Graham
David F. Place wrote:
I'm not top posting.
I want the \markup in the right of the TextSpanner to have a quarter note just
like the first markup.
\version 2.11.32
\paper { ragged-right = ##t }
\score
{
\relative c''
{
\textSpannerUp
\override TextSpanner #'bound-details #'left #'text = \markup \upright rit.
\override TextSpanner #'bound-details #'right
#'text =
\markup \line {\upright {\bold {sehr langsam} \tiny \note #4 #1 = ca 42}}
\time 4/4
c4^\markup \line {\bold {sehr langsam} \tiny \note #4 #1 = ca 42} d e f
c d e f c d e f c\startTextSpan d e f c d e f c1\stopTextSpan
c1 c c c c \bar |.
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly not working
In general, programs shouldn't quit with that kind message, so in that regards it's a bug. :) Unfortunately, we don't have the resources to maintain midi2ly any more, so we can't help. Sorry, - Graham Jonathan Mitchem wrote: I've been unable to get any midis to convert. They have been stored as Midi format 1, as per what I read about midi2ly. The error is... C:\midi2ly 2007-07-05-002-ex.mid1.mid Traceback (most recent call last): File C:\Program Files\LilyPond\usr\bin\midi2ly.py, line 996, in ? main() File C:\Program Files\LilyPond\usr\bin\midi2ly.py, line 994, in main convert_midi (f, o) File C:\Program Files\LilyPond\usr\bin\midi2ly.py, line 834, in convert_midi for (dur, num, den) in global_options.allowed_tuplets: SystemError: /home/lilydev/vc/gub/target/mingw/gubfiles/src/python-2.4.2/Objects /listobject.c:243: bad argument to internal function Do I need to specify more parameters? or is there actually a bug? I can get you the midi file(s) in question if need be. Jonathan [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 443 in lilypond: \markup note disappears when instide a TextSpanner #'bound-details
Issue 443: \markup note disappears when instide a TextSpanner #'bound-details
http://code.google.com/p/lilypond/issues/detail?id=443
New issue report by gpermus:
\version 2.11.32
\paper { ragged-right = ##t }
\relative c'' {
\textSpannerUp
\override TextSpanner #'bound-details #'left #'text = \markup {rit}
\override TextSpanner #'bound-details #'right
#'text = \markup { \note #4 #1 = 90 }
c1^\markup { \note #4 #1 = 60}
c\startTextSpan
c\stopTextSpan
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: problem with lilypond from the command line
Give the filename, I presume that you're using OSX? Where did the script in /usr/local/bin come from? I don't think that we install such a script (although I could be wrong) We recently changed the variable name; see the NEWS file for 2.11. Perhaps this update was accidentally merged back into 2.10... or perhaps your script was designed for a different version of LilyPond? Do you get any errors when you run from the GUI? We'll be making a new stable release soon, so if it only affects command-line users, I'd rather concentrate on bugs in the upcoming release. :) Cheers, - Graham Jake Rundall wrote: The script (lilypond) listed at the end of this message is in /usr/local/bin. When I execute it, I get the following error: GNU LilyPond 2.10.29 error: LILYPONDPREFIX is obsolete, use LILYPOND_DATADIR If I edit Lilypond.app/Contents/Resources/lilycall.py by changing 'LILYPONDPREFIX' to 'LILYPOND_DATADIR' everything seems to work fine. #!/bin/sh # # Example file for invoking LilyPond.app from the commandline. # # customize the following variables ## where was the app installed? INSTALLDIR=/Applications ## uncomment to get some debugging info, and leave .ps files # export LILYPOND_WRAPPER_DEBUG=1 if [ $1 == --print-appdir ]; then echo $INSTALLDIR/LilyPond.app/ exit 0 fi # where to put the output export LILYPOND_DESTDIR=`pwd` # run the program python $INSTALLDIR/LilyPond.app/Contents/Resources/lilycall.py \ $INSTALLDIR/LilyPond.app/ $* ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 443 in lilypond: \markup note disappears when instide a TextSpanner #'bound-details
Issue 443: \markup note disappears when instide a TextSpanner #'bound-details http://code.google.com/p/lilypond/issues/detail?id=443 Comment #1 by gpermus: Sorry, I'm out of practice. Here's the image. Attachments: foo.preview.png 2.1 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: programming error: minimise_least_squares (): Nothing to minimise
Added as
http://code.google.com/p/lilypond/issues/detail?id=444
Cheers,
- Graham
Neil Puttock wrote:
Hi there,
The following snippet spits out this error, but the output is
unobjectionable:
\version 2.11.30
\paper{ ragged-right=##t }
\score {
\new Staff \relative c'' {
{ \time 12/16 c16[ b a r b g] } \\ { r8. r } %error
disappears if manual beaming or second rest in lower voice is removed
}
}
Regards,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 444 in lilypond: false progerror with beaming and rest
Issue 444: false progerror with beaming and rest
http://code.google.com/p/lilypond/issues/detail?id=444
New issue report by gpermus:
%{ output is perfect, but produces a warning:
Preprocessing graphical objects...
programming error: minimise_least_squares (): Nothing to minimise
This means that vertical spacing is triggered
before line breaking
continuing, cross fingers
Finding the ideal number of pages...
%}
\version 2.11.30
\paper{ ragged-right=##t }
\score {
\new Staff \relative c'' {
{ \time 12/16 c16[ b a r b g] } \\ { r8. r }
%error disappears if manual beaming or second rest in lower voice is removed
}
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Low Warning-nitpick
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hara_kiri_engraver shouldn't handle both staves of a PianoStaff as separate single staves
2007/9/5, Graham Percival [EMAIL PROTECTED]: Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=442 Great! Thanks a lot Graham, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 445 in lilypond: minimum-Y-extent missing for staffs
Issue 445: minimum-Y-extent missing for staffs
http://code.google.com/p/lilypond/issues/detail?id=445
New issue report by gpermus:
%{ Mats comment:
Clearly a bug! What has happened to the setting of
VerticalAxisGroup #'minimum-Y-extent = ##f in the Staff context?
I see in the GIT repository that it was removed already in January:
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=5a25c944e475df407dd7f57347b6da48b974a1d3
but as the following example shows, the resulting layout can be really
ridiculous.
%}
\version 2.11.32
\relative
\new Staff {\clef bass R1*3}
\new Staff {\clef bass R1*3}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Regression
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation)
Issue 430: Cross-staff beam craziness (when down-markup combines with down-articulation) http://code.google.com/p/lilypond/issues/detail?id=430 Comment #4 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange cross-stave beam and slur behaviour with portato
Similar issue, but not exact -- 430 is fixed in 2.11.32, but this bug remains. http://code.google.com/p/lilypond/issues/detail?id=446 Cheers, - Graham Neil Puttock wrote: Hi Trevor On 9/2/07, Trevor Bača [EMAIL PROTECTED] wrote: I can't be certain, but I'd bet that this is related to Google #430: http://code.google.com/p/lilypond/issues/detail?id=430 If it's the same bug, then we're in luck because Han-Wen and Joe have marked #430 fixed in the upcoming 2.11.32 build. That certainly looks like a similar issue. I should have mentioned however that it's only the portato script which produces this weirdness; I tested it with several other articulations, and none resulted in broken beams. Regards, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 446 in lilypond: portato and slur cross-staff weirdness
Issue 446: portato and slur cross-staff weirdness
http://code.google.com/p/lilypond/issues/detail?id=446
New issue report by gpermus:
%{
The portato sign is causing some strange behaviour with both beams and
slurs when a voice crosses staves.
%}
\version 2.11.30
\paper { ragged-right = ##t }
lh = \change Staff = lh
rh = \change Staff = rh
\score {
\new PianoStaff
% remove the -_ and the output is good
\new Staff = rh \relative { c8-_( \lh \stemDown e[ c g]) }
\new Staff = lh { \clef bass s4. }
}
Attachments:
foo.preview.png 3.0 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unbeamed notes after a cadenza and an appogiatura
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=447
Cheers,
- Graham
Nicolas Klutchnikoff wrote:
I'm not top posting.
% Tested with 2.10.29 and 2.11.30 on MacOS 10.4.10 and Ubuntu 7.04
\version 2.10.29
\paper{ ragged-right=##t }
\relative c'' {
\time 2/4
c4 e |
\cadenzaOn
g g,
\cadenzaOff \bar |
\acciaccatura d'8 c16 c c c c c c c
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 446 in lilypond: portato and slur cross-staff weirdness
Issue 446: portato and slur cross-staff weirdness http://code.google.com/p/lilypond/issues/detail?id=446 Comment #1 by gpermus: Only the -_ articulation produces this behavior; other kinds of articulation produce good output. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: KeyCancellation spacing issue when staves have different key signatures
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=448
I kind-of lost track in the rest of this discussion (what was a
workaround, what was bug investigation). If there's any other bug info,
please add it to the tracker.
Cheers,
- Graham
Neil Puttock wrote:
Hello,
In the following snipper the key cancellation in the lower voice influences
the spacing in the upper voice resulting in excess space before the new key
signature:
\version 2.11.31
\paper { ragged-right = ##t }
\score {
\new GrandStaff
\new Staff { c'1 \key es \major }
\new Staff { \key des \major s1 \key c \major }
}
Regards,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 447 in lilypond: Unbeamed notes after a cadenza and an appogiatura
Issue 447: Unbeamed notes after a cadenza and an appogiatura
http://code.google.com/p/lilypond/issues/detail?id=447
New issue report by gpermus:
\version 2.11.32
\paper{ ragged-right=##t }
\relative c'' {
\time 2/4
c4 e |
\cadenzaOn
g g,
\cadenzaOff \bar |
\acciaccatura d'8 c16 c c c c c c c
}
Attachments:
foo.preview.png 3.1 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 367 in lilypond: layout-set-staff-size doesn't change the distance between the staff lines
Issue 367: layout-set-staff-size doesn't change the distance between the staff lines http://code.google.com/p/lilypond/issues/detail?id=367 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Regression: trill-spanner-pitched.ly
Thanks, http://code.google.com/p/lilypond/issues/detail?id=449 Cheers, - Graham Christian Hitz wrote: Hi, I found the following regression in 2.11.31 in trill-spanner-pitched.ly: The parentheses of the indicated pitch collide with the following note. Christian ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Regression: tuplet-properties.ly
Thanks, http://code.google.com/p/lilypond/issues/detail?id=450 Cheers, - Graham Christian Hitz wrote: Hi, I found a regression in 2.11.31 over 2.10.29 in tuplet-properties.ly: The tuplet number of the second group collides with the stem of the middle note. Christian ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 407 in lilypond: tabStaff cannot handle \partcombine
Issue 407: tabStaff cannot handle \partcombine http://code.google.com/p/lilypond/issues/detail?id=407 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 448 in lilypond: KeyCancellation spacing issue when staves have different key signatures
Issue 448: KeyCancellation spacing issue when staves have different key
signatures
http://code.google.com/p/lilypond/issues/detail?id=448
New issue report by gpermus:
%{ Big unwanted space in second bar %}
\version 2.11.31
\paper { ragged-right = ##t }
\score {
\new GrandStaff
\new Staff { c'1 \key es \major }
\new Staff { \key des \major s1 \key c \major }
}
Attachments:
foo.preview.png 3.2 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 449 in lilypond: input/regression/trill-spanner-pitched.ly
Issue 449: input/regression/trill-spanner-pitched.ly http://code.google.com/p/lilypond/issues/detail?id=449 New issue report by gpermus: Parenthesis collide with the following notehead. Issue attributes: Status: Accepted Owner: gpermus Labels: Type-Collision Priority-Regression -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 450 in lilypond: input/regression/tuplet-properties.ly
Issue 450: input/regression/tuplet-properties.ly http://code.google.com/p/lilypond/issues/detail?id=450 New issue report by gpermus: The tuplet number of the second group collides with the stem of the middle note. This one looks really ugly. -gp Issue attributes: Status: Accepted Owner: gpermus Labels: Type-Collision Priority-Regression -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unbeamed notes after a cadenza and an appogiatura
I guess that this problem is closely related to
http://code.google.com/p/lilypond/issues/detail?id=372
The workaround described in
http://lists.gnu.org/archive/html/bug-lilypond/2007-06/msg00024.html
applies here as well:
\version 2.10.29
\paper{ ragged-right=##t }
\relative c'' {
\time 2/4
c4 e |
\cadenzaOn
g g,
\cadenzaOff \bar |
\acciaccatura d'8 \partial 2 c16 c c c c c c c
}
/Mats
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=447
Cheers,
- Graham
Nicolas Klutchnikoff wrote:
I'm not top posting.
% Tested with 2.10.29 and 2.11.30 on MacOS 10.4.10 and Ubuntu 7.04
\version 2.10.29
\paper{ ragged-right=##t }
\relative c'' {
\time 2/4
c4 e |
\cadenzaOn
g g,
\cadenzaOff \bar |
\acciaccatura d'8 c16 c c c c c c c
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unbeamed notes after a cadenza and an appogiatura
Mao! I knew that I recognized the bug report, but I only searched for
cadenza, grace, and accaciatura.
Cheers,
- Graham
Mats Bengtsson wrote:
I guess that this problem is closely related to
http://code.google.com/p/lilypond/issues/detail?id=372
The workaround described in
http://lists.gnu.org/archive/html/bug-lilypond/2007-06/msg00024.html
applies here as well:
\version 2.10.29
\paper{ ragged-right=##t }
\relative c'' {
\time 2/4
c4 e |
\cadenzaOn
g g,
\cadenzaOff \bar |
\acciaccatura d'8 \partial 2 c16 c c c c c c c
}
/Mats
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=447
Cheers,
- Graham
Nicolas Klutchnikoff wrote:
I'm not top posting.
% Tested with 2.10.29 and 2.11.30 on MacOS 10.4.10 and Ubuntu 7.04
\version 2.10.29
\paper{ ragged-right=##t }
\relative c'' {
\time 2/4
c4 e |
\cadenzaOn
g g,
\cadenzaOff \bar |
\acciaccatura d'8 c16 c c c c c c c
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 447 in lilypond: Unbeamed notes after a cadenza and an appogiatura
Issue 447: Unbeamed notes after a cadenza and an appogiatura http://code.google.com/p/lilypond/issues/detail?id=447 Comment #1 by gpermus: Dupe of 372 Issue attribute updates: Status: Duplicate -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 448 in lilypond: KeyCancellation spacing issue when staves have different key signatures
Issue 448: KeyCancellation spacing issue when staves have different key
signatures
http://code.google.com/p/lilypond/issues/detail?id=448
Comment #1 by [EMAIL PROTECTED]:
A workaround in this particular case is to add
\override Staff.KeyCancellation #'X-extent = #'(0 . 0)
in the lower stave.
One question is what the desired layout is in the following situation:
\version 2.11.31
\paper { ragged-right = ##t }
\score {
\new GrandStaff
\new Staff { c'1 \key es \major }
\new Staff { \key des \major s1 \key d \major }
}
Should the key signature in the upper stave be aligned with the key
cancellation of
the new key signature in the lower stave or should it be centered over both?
Finding a solution that handles both these examples well seems difficult.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
\relative doesn't work when using \parallelMusic
Hello everybody (well, Hello Graham, mostly :)
this discussion was never added to the tracker; however it is, if not
a major bug, a major annoyance when writing piano music (for example).
I'm refering to
http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00289.html
Nicolas proposed a workaround, which was never implemented (IIRC it's
been broken for many releases now).
I don't know if there's a way to implement it now, and very few people
seem to use \parallelmusic (maybe because of this bug precisely -- I
would use everyday it if this was addressed).
As for the minimal example: this doesn't work:
\parallelMusic {
\relative { a' b c d } |
\relative {a, b c d} |
}
This doesn't either :
\relative {
\parallelMusic {
a' b c d |
a, b c d |
}
}
...but most of the subject has been discussed on the thread I mentioned.
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \relative doesn't work when using \parallelMusic
Hi Valentin,
Can't help you with \parallelMusic directly, but...
I would use everyday it if this was addressed
Don't forget that you can fake \parallelMusic by explicitly pushing
notes into an existing Voice context -- see snippet, below, for an
example.
It's not quite as pretty, but it accomplishes essentially the same
thing.
Hope this helps!
Kieren.
___
\version 2.11.30
theMusic = \relative c''
{
%% m. 1
\context Voice = A
{
\voiceOne
\override Voice.NoteHead #'color = #red
a b c d
}
\new Voice = B
{
\voiceTwo
\override Voice.NoteHead #'color = #blue
a g f e
}
%% m. 2
\context Voice = A { a c c b }
\context Voice = B { a f f g }
%% m. 3
\context Voice = A { a f' e d }
\context Voice = B { a d, e f }
}
\score
{
\theMusic
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 440 in lilypond: Tie direction reverse incorrectly between whole notes tied across line breaks
Issue 440: Tie direction reverse incorrectly between whole notes tied across line breaks http://code.google.com/p/lilypond/issues/detail?id=440 Comment #3 by lemzwerg: I'm not sure whether it's a real duplicate. Note that in Trevor's example, the tie direction already changes *before* the break. Issue attribute updates: Status: Started -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 448 in lilypond: KeyCancellation spacing issue when staves have different key signatures
Issue 448: KeyCancellation spacing issue when staves have different key
signatures
http://code.google.com/p/lilypond/issues/detail?id=448
Comment #2 by [EMAIL PROTECTED]:
A workaround in this particular case is to add
\override Staff.KeyCancellation #'X-extent = #'(0 . 0)
in the lower stave.
One question is what the desired layout is in the following situation:
\version 2.11.31
\paper { ragged-right = ##t }
\score {
\new GrandStaff
\new Staff { c'1 \key es \major }
\new Staff { \key des \major s1 \key d \major }
}
Should the key signature in the upper stave be aligned with the key
cancellation or
the new key signature in the lower stave or should it be centered over both?
Finding a solution that handles both these examples well seems difficult.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \relative doesn't work when using \parallelMusic
Ok, added.
http://code.google.com/p/lilypond/issues/detail?id=451
Cheers,
- Graham
Valentin Villenave wrote:
Hello everybody (well, Hello Graham, mostly :)
this discussion was never added to the tracker; however it is, if not
a major bug, a major annoyance when writing piano music (for example).
I'm refering to
http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00289.html
Nicolas proposed a workaround, which was never implemented (IIRC it's
been broken for many releases now).
I don't know if there's a way to implement it now, and very few people
seem to use \parallelmusic (maybe because of this bug precisely -- I
would use everyday it if this was addressed).
As for the minimal example: this doesn't work:
\parallelMusic {
\relative { a' b c d } |
\relative {a, b c d} |
}
This doesn't either :
\relative {
\parallelMusic {
a' b c d |
a, b c d |
}
}
...but most of the subject has been discussed on the thread I mentioned.
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 451 in lilypond: \parallelMusic and \relative don't mix
Issue 451: \parallelMusic and \relative don't mix
http://code.google.com/p/lilypond/issues/detail?id=451
New issue report by gpermus:
More discussion here:
http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00289.html
As for the minimal example: this doesn't work:
\parallelMusic {
\relative { a' b c d } |
\relative {a, b c d} |
}
This doesn't either :
\relative {
\parallelMusic {
a' b c d |
a, b c d |
}
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \relative doesn't work when using \parallelMusic
2007/9/5, Graham Percival [EMAIL PROTECTED]: Ok, added. http://code.google.com/p/lilypond/issues/detail?id=451 Great! Thanks a lot Graham. Kieren: thanks for your workaround (Actually, I was already using a function like this one), but it isn't very light-weight... :) Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 451 in lilypond: \parallelMusic and \relative don't mix
Issue 451: \parallelMusic and \relative don't mix http://code.google.com/p/lilypond/issues/detail?id=451 Comment #1 by v.villenave: I don't think another function (such as \parallelRelativeMusic) has to be created; it seems that modifying the already existing one, to make it accept \relative, could hardly break anything (since nobody has ever used \relative yet). Thanks -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: KeyCancellation spacing issue when staves have different key signatures
Hi Mats, On 9/5/07, Mats Bengtsson [EMAIL PROTECTED] wrote: One solution is to set \override Staff.KeyCancellation #'X-extent = #'(0 . 0) I always seem to go looking for the most complicated solution (though I'm still interested why keyAlterationOrder doesn't work). Thanks, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \relative doesn't work when using \parallelMusic
Valentin Villenave [EMAIL PROTECTED] writes: Hello everybody (well, Hello Graham, mostly :) this discussion was never added to the tracker; however it is, if not a major bug, a major annoyance when writing piano music (for example). I'm refering to http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00289.html Nicolas proposed a workaround, which was never implemented (IIRC it's been broken for many releases now). I did implement something: http://lists.gnu.org/archive/html/lilypond-devel/2006-05/msg00181.html but I confess not being interested in such a feature... Resurrecting it won't be granted the highest priority (I'm preparing the full orchestral material of /Armide/ by Lully for a company that will eventually play it...) nicolas ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
