Re: stopStaff combined with StaffGroup extents barlines
I forward your question to bug-lilypond, since it shows a regression
bug compared to earlier versions.
/Mats
Toine Schreurs wrote:
I am typesetting a score, where one of the staffs contains an ossia section.
I started from the example in section 1.6.1 of the NR. The second staff
will contain the ossia section. In the resulting score it is not obvious
to which staff this ossia belongs.
To connect the staff with the ossia section, I combined them into a StaffGroup.
Now it is clear to which staff the ossia belongs. But, all barlines are
(wrongly) extended also.
This behaviour started with version 2.11.35
Any hints?
Toine Schreurs
%=== start =
\version "2.11.38"
musicOne = \relative c' {
\time 2/4
d4 d |
a' a |
b b |
f2
}
musicTwo = \relative c' {
e4 e |
b' b |
c c |
g2
}
ossia = \relative c' {
\stopStaff
s2*2 |
\startStaff
bes'8^"ossia" g bes g |
\stopStaff
s2 |
}
\score {
<<
\new Staff \musicOne
\new StaffGroup
<<
\new Staff \with
{
\remove "Time_signature_engraver"
fontSize = #-2
\override StaffSymbol #'staff-space = #(magstep -2)
firstClef = ##f
}
\ossia
\new Staff \musicTwo
>>
>>
}
% end ==
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
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
Issue 569 in lilypond: Consistency in property names: beam-thickness
Issue 569: Consistency in property names: beam-thickness http://code.google.com/p/lilypond/issues/detail?id=569 New issue report by v.villenave: Currently, the beam-thickness property is only used for StemTremolo objects. It might be better to change the property name for the thickness of all beams to be "beam-thickness", which has the descriptive string, "Beam thickness, measured in staff-space units", and a default value of 0.48. See also http://lists.gnu.org/archive/html/lilypond-devel/2008-02/msg0.html Issue attributes: Status: Accepted Owner: v.villenave 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 570 in lilypond: Articulations can collide with ties
Issue 570: Articulations can collide with ties
http://code.google.com/p/lilypond/issues/detail?id=570
New issue report by v.villenave:
% another collision involving ties:
\version "2.11.38"
\paper {
ragged-right = ##t
}
\relative c'' {
f-- f~-- f~
}
Issue attributes:
Status: Accepted
Owner: v.villenave
Labels: Type-Collision 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
Re: articulations collide with ties
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=570
Cheers,
Valentin
On 03/02/2008, Andrew Hawryluk <[EMAIL PROTECTED]> wrote:
> I couldn't find this one on the bug list: articulations can collide with ties.
>
> \version "2.11.38"
> \paper {
> ragged-right = ##t
> }
> \relative c'' {
> f-- f~-- f~
> }
>
>
> ___
> 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: horizontal spacing problem in grace notes below the staff
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=571
You full report is quite accurate, however I just added a link to it
in order to preserve the holy minimal-reports-only-policy-thing (TM).
Cheers,
Valentin
On 03/02/2008, Andrew Hawryluk <[EMAIL PROTECTED]> wrote:
> This one's a bit long for a bug report, but only to show the way the
> horizontal problem depends on the vertical location of the grace
> notes.
> -AH
>
>
> \version "2.11.38"
> \paper {
> ragged-right = ##t
> }
>
> % In groups of grace notes below the staff, it appears
> % that the notes are only given enough horizontal room
> % when the intervals between the notes are small. In
> % larger intervals the notes are pressed very close together.
>
> {
> % spacing above the staff is fine
> \grace {e'''16[ a'' e'']} a''4
>
> % spacing in the middle of the staff is fine
> \grace {d''16[ g' d']} g'4
>
> % just one step down, an odd spacing happens because
> % c' is given very little room
> \grace {c''16[ f' c']} f'4
>
> % here the ledger lines have shifted to the right to
> % avoid a collision, but the a is not centred on the
> % ledger line
> \grace {a'16[ d' a]} d'4
>
> % here both the b and f are 'falling off' their ledgers
> \grace {f'16[ b f]} c'4
>
> % here the first two notes have enough space because
> % they are vertically close
> \grace {d'16[ c' g]} c'4
>
> % here they are all properly spaced
> \grace {d'16[ c' a]} c'4
> }
>
>
> ___
> 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 571 in lilypond: Odd spacing with grace notes below the staff
Issue 571: Odd spacing with grace notes below the staff
http://code.google.com/p/lilypond/issues/detail?id=571
New issue report by v.villenave:
% Please also read Andrew's full report on
% http://lists.gnu.org/archive/html/bug-lilypond/2008-02/msg4.html
\version "2.11.38"
\paper {
ragged-right = ##t
}
% In groups of grace notes below the staff, it appears
% that the notes are only given enough horizontal room
% when the intervals between the notes are small. In
% larger intervals the notes are pressed very close together,
% and are not horizontally centered on ledger lines.
{
\grace {a'16[ d' a]} d'4
}
Issue attributes:
Status: Accepted
Owner: v.villenave
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: Hairpin and Textscript
Trevor Daniels wrote: ... http://kainhofer.com/~lilypond/Documentation/user/lilypond-learning/index.html which shows a bug! The ottava bracket isn't moved no matter what value you specify, at least when I try with the latest 2.11.38 code from GIT. Unfortunately, this means that the example in the manual doesn't show what it's supposed to show, until this bug is fixed (if the bug fix takes long, the example can easily be modified to move the dynamics instead, which works as it should). /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: score-final mark mangles score-final tuplet bracket
On 05/02/2008, Trevor Bača <[EMAIL PROTECTED]> wrote: > Could you please consider this one for the tracker? It's quite specific > thing ever, but highly reproducible (and quite irritating). Hi Trevor, 5 insane settings and you're complaining that the output is weird? Honestly, you're pushing it here :) Anyway, this should not happen indeed. Added as http://code.google.com/p/lilypond/issues/detail?id=573 Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: instrumentName is not being vertically centered when using template 'piano centered dynamics'
On 04/02/2008, Graham Percival <[EMAIL PROTECTED]> wrote: > You hear that, Valentin? Be ambitious. :) Well, I am, but generally you're the one who prevents me from being so :) Honestly, I think this is all about LilyPond dumb-but-logical way of doing things, so the current behavior doesn't seem wrong to me. However, we can always use feature requests, and this is a good idea nevertheless: http://code.google.com/p/lilypond/issues/detail?id=572 Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 572 in lilypond: Feature request: vertical instrumentName alignment should ignore non-stafflike contexts
Issue 572: Feature request: vertical instrumentName alignment should
ignore non-stafflike contexts
http://code.google.com/p/lilypond/issues/detail?id=572
New issue report by v.villenave:
% It would be nice if the instrumentName for more than
% one staff were vertically centered before the staff-like contexts,
% and not counting not-stafflike contexts like
% lyrics/dynamics/pedals etc outside the staffs.
\version "2.11.37"
upper = \relative c'' {
a1
}
lower = \relative c {
\clef bass
a1
}
pedal = {
s1\sustainDown
}
\score {
\new PianoStaff <<
\set PianoStaff.instrumentName = "Piano "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
\new Pedals = "pedal" \pedal
>>
\layout {
\context {
\type "Engraver_group"
\name Pedals
\consists "Output_property_engraver"
\override VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1)
\consists "Piano_pedal_engraver"
\consists "Skip_event_swallow_translator"
\consists "Axis_group_engraver"
}
\context {
\PianoStaff
\accepts Pedals
}
}
}
Issue attributes:
Status: Accepted
Owner: v.villenave
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
RE: Hairpin and Textscript
Thanks Mats. Actually the bug is in the manual :( The ottava spanner is created in the Staff context, but I omitted to specify the context in the \override in the example. \once \override Staff.OttavaBracket #'outside-staff-priority = #340 works fine (at least in 2.11.34) Trevor D > -Original Message- > From: Mats Bengtsson [mailto:[EMAIL PROTECTED] > Sent: 05 February 2008 11:31 > To: [EMAIL PROTECTED]; Lilypond bug > Cc: [EMAIL PROTECTED] > Subject: Re: Hairpin and Textscript > > > > > Trevor Daniels wrote: > > ... > > > http://kainhofer.com/~lilypond/Documentation/user/ > lilypond-learning/index.html > > > > which shows a bug! The ottava bracket isn't moved > no matter what value you > specify, at least when I try with the latest > 2.11.38 code from GIT. > Unfortunately, > this means that the example in the manual doesn't > show what it's > supposed to show, > until this bug is fixed (if the bug fix takes > long, the example can > easily be modified to > move the dynamics instead, which works as it should). > > /Mats > ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 573 in lilypond: score-final mark mangles score-final tuplet bracket
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
New issue report by v.villenave:
% The score-final mark badly mangles the score-final tuplet bracket:
% Actually, mark direction can be either up or down,
% but appears more clearly with the mark set down.
\version "2.11.37"
\new Staff {
\set tupletFullLength = ##t
\time 1/8
\times 2/3 { c'16 c'16 c'16 }
\times 2/3 { c'16 c'16 c'16 }
\times 2/3 { c'16 c'16 c'16 }
\override Score.RehearsalMark #'break-visibility = ##(#t #t #t)
\override Score.RehearsalMark #'direction = #down
\override Score.RehearsalMark #'break-align-symbol = #'clef
\override Score.RehearsalMark #'self-alignment-X = #right
\mark "Composed Feb 2007 - Feb 2008"
}
Attachments:
mangled-bracket.png 9.9 KB
Issue attributes:
Status: Accepted
Owner: v.villenave
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: set associatedVoice and disappearing lyrics
On 28/01/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > This seems like exactly the same situation as in > http://lists.gnu.org/archive/html/lilypond-user/2007-11/msg00468.html OK; so, shall we report it as a bug or not? Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: set associatedVoice and disappearing lyrics
Valentin Villenave wrote: On 28/01/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote: This seems like exactly the same situation as in http://lists.gnu.org/archive/html/lilypond-user/2007-11/msg00468.html OK; so, shall we report it as a bug or not? Well, the root of the problem is the fact that you have to specify the voice change one note ahead, which is inconvenient in itself. The problem shown here is a non-obvious consequence of this basic problem. In my opinion, this makes it qualify as a bug and not only as an inconvenience (even though you can work around it by adding empty syllables). Since a bug fix isn't likely to happen very soon, a first step would be to add a note in the documentation. I offer to do that if you wish. /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 565 in lilypond: The system start brace is too large
Issue 565: The system start brace is too large http://code.google.com/p/lilypond/issues/detail?id=565 Comment #5 by v.villenave: (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: pedal position
On 29/01/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> I send a copy also to bug-lilypond, since I think there's something fishy
> going on here with outside-staff-priority.
Added as http://code.google.com/p/lilypond/issues/detail?id=575
> \version "2.11.37"
> \relative c''' {
> \override Staff.SustainPedalLineSpanner #'outside-staff-priority = #250
> \override Voice.DynamicLineSpanner #'outside-staff-priority = #0
> c2\pp\sustainDown
> c2\pp\sustainDown
> }
I don't understand why nothing happens when you set the property
on-the-fly such as
\relative c''' {
c2\pp\sustainDown
\override Staff.SustainPedalLineSpanner #'outside-staff-priority = #250
\override Voice.DynamicLineSpanner #'outside-staff-priority = #0
c2\pp\sustainDown
}
Is it because the LineSpanner is already being drawn?
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 575 in lilypond: outside-staff-priority issues with PedalLineSpanner objects
Issue 575: outside-staff-priority issues with PedalLineSpanner objects
http://code.google.com/p/lilypond/issues/detail?id=575
New issue report by v.villenave:
% as soon as you set SustainPedalLineSpanner #'outside-staff-priority,
% the dynamics and pedal marks collide, no matter the value used.
% Besides, shouldn't the different *PedalLineSpanner objects also
% have some setting of outside-staff-priority by default?
\version "2.11.37"
\relative c''' {
\override Staff.SustainPedalLineSpanner #'outside-staff-priority = #250
\override Voice.DynamicLineSpanner #'outside-staff-priority = #0
c2\pp\sustainDown
c2\pp\sustainDown
}
Issue attributes:
Status: Accepted
Owner: v.villenave
Labels: Type-Collision 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: stopStaff combined with StaffGroup extents barlines
On 05/02/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > I forward your question to bug-lilypond, since it shows a regression > bug compared to earlier versions. Yes, indeed. I added it to the bug tracker as http://code.google.com/p/lilypond/issues/detail?id=574 Let's hope someone will have a minute to fix it in the next development release. Thanks for the report! Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 574 in lilypond: Regression: stopStaff combined with StaffGroup extents barlines
Issue 574: Regression: stopStaff combined with StaffGroup extents barlines
http://code.google.com/p/lilypond/issues/detail?id=574
New issue report by v.villenave:
% This is based on the example in section 1.6.1 of the NR.
% The second staff contains an ossia section, but in the output
% it is not obvious to which staff this ossia belongs.
% To connect the staff with the ossia section, one can combine them
% into a StaffGroup; however all barlines are(wrongly) extended also.
% This behaviour started with version 2.11.35
\version "2.11.38"
musicOne = \relative c' {
\time 2/4
d2 d d d
}
musicTwo = \relative c' {
e2 e e e
}
ossia = \relative c' {
\stopStaff s2*2 |
\startStaff g'2^"ossia"
\stopStaff s2 |
}
\score {
<<
\new Staff \musicOne
\new StaffGroup
<<
\new Staff \with
{
\remove "Time_signature_engraver"
fontSize = #-2
\override StaffSymbol #'staff-space = #(magstep -2)
firstClef = ##f
}
\ossia
\new Staff \musicTwo
>>
>>
}
Issue attributes:
Status: Accepted
Owner: v.villenave
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 564 in lilypond: \setEasyHeads -> \beginEasyHeads. Add \endEasyHeads
Issue 564: \setEasyHeads -> \beginEasyHeads. Add \endEasyHeads http://code.google.com/p/lilypond/issues/detail?id=564 Comment #4 by v.villenave: (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 533 in lilypond: input/regression/cluster-cross-staff.ly
Issue 533: input/regression/cluster-cross-staff.ly http://code.google.com/p/lilypond/issues/detail?id=533 Comment #12 by v.villenave: (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 467 in lilypond: Two calls to set-octavation confound intervening clef change
Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #9 by v.villenave: (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: set associatedVoice and disappearing lyrics
Valentin Villenave wrote: On 05/02/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote: Well, the root of the problem is the fact that you have to specify the voice change one note ahead, which is inconvenient in itself. Indeed. Since a bug fix isn't likely to happen very soon, a first step would be to add a note in the documentation. I offer to do that if you wish. Yes; however I'd first add it to the tracker, and only then "solve" it by adding specific explanations in the doc. IMO we need to mention it in the tracker for a (unlikely) future fix; otherwise we'd just admit that nobody wants to ever solve it -- which is kind of sad :( Shall I open an Issue? Of course! Just make sure that it is NOT marked as fixed if we add the workaround in the documentation. /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: set associatedVoice and disappearing lyrics
On 05/02/2008, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > Well, the root of the problem is the fact that you have to specify the voice > change one note ahead, which is inconvenient in itself. Indeed. > Since a bug fix isn't likely to happen very soon, a first step would be > to add a > note in the documentation. I offer to do that if you wish. Yes; however I'd first add it to the tracker, and only then "solve" it by adding specific explanations in the doc. IMO we need to mention it in the tracker for a (unlikely) future fix; otherwise we'd just admit that nobody wants to ever solve it -- which is kind of sad :( Shall I open an Issue? Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 542 in lilypond: bus error ancient music 2.11.36
Issue 542: bus error ancient music 2.11.36 http://code.google.com/p/lilypond/issues/detail?id=542 Comment #3 by v.villenave: (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 558 in lilypond: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break
Issue 558: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break http://code.google.com/p/lilypond/issues/detail?id=558 Comment #3 by v.villenave: Has this commit already been implemented? It works fine with .38 here... 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 563 in lilypond: rename: \fatText -> \textLengthOn
Issue 563: rename: \fatText -> \textLengthOn http://code.google.com/p/lilypond/issues/detail?id=563 Comment #6 by v.villenave: (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 562 in lilypond: Vertical spacing: wrong extent-estimate with StaffGroups and hara-kiri
Issue 562: Vertical spacing: wrong extent-estimate with StaffGroups and hara-kiri http://code.google.com/p/lilypond/issues/detail?id=562 Comment #5 by v.villenave: (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 552 in lilypond: Metronome mark affects spacing
Issue 552: Metronome mark affects spacing http://code.google.com/p/lilypond/issues/detail?id=552 Comment #3 by v.villenave: (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 528 in lilypond: wish: underline markup
Issue 528: wish: underline markup http://code.google.com/p/lilypond/issues/detail?id=528 Comment #7 by v.villenave: (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 336 in lilypond: octavation, change clef produces incorrect note positions
Issue 336: octavation, change clef produces incorrect note positions http://code.google.com/p/lilypond/issues/detail?id=336 Comment #5 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Labels: fixed_2_11_38 -- 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: set associatedVoice and disappearing lyrics
On Tue, 05 Feb 2008 13:33:42 +0100 Mats Bengtsson <[EMAIL PROTECTED]> wrote: > Since a bug fix isn't likely to happen very soon, a first step would > be to add a > note in the documentation. I offer to do that if you wish. This is in vocal.itely? Yes please. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 569 in lilypond: Consistency in property names: beam-thickness
On the other hand, if we do this change, then we loose the consistency with all other objects, where the property name "thickness" is used to denote the thickness. In my opinion, we would get even more consistency if we renamed beam-thickness to thickness also for StemTremolo objects (even though, as I've already said, it's perhaps less obvious what the thickness means for a StemTremolo). Regarding the confusion about what unit of measurement is used for the thickness of different objects, it's easy to extend the current documentation of thickness to say that "... measured in line-thickness units except for Beam and StemTremolo objects, where it's measured in staff-space units." /Mats [EMAIL PROTECTED] wrote: Issue 569: Consistency in property names: beam-thickness http://code.google.com/p/lilypond/issues/detail?id=569 New issue report by v.villenave: Currently, the beam-thickness property is only used for StemTremolo objects. It might be better to change the property name for the thickness of all beams to be "beam-thickness", which has the descriptive string, "Beam thickness, measured in staff-space units", and a default value of 0.48. See also http://lists.gnu.org/archive/html/lilypond-devel/2008-02/msg0.html Issue attributes: Status: Accepted Owner: v.villenave Labels: Type-Enhancement Priority-Low -- = 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
Issue 509 in lilypond: collision nested tuplet numbers
Issue 509: collision nested tuplet numbers http://code.google.com/p/lilypond/issues/detail?id=509 Comment #1 by tdanielsmusic: There is no collision if the tuplet notes are lower on the staff so the stems and tuplet brackets are placed above the notes, but the collision still exists for high notes even when \tupletUp is specified. -- 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
Error is cross-bar arpeggios using times
> I'm not top posting.
Hi All,
For a piece of piano music, I wrote a part with 2-hand arpeggios in \times 8/7.
It was originally written with LilyPond 2.6.? where the output looked ok, but
with v. 2.10.25, the "--- 7 ---" signs (dunno how they're called in English
:-/) get printed in the wrong direction when the arpeggio goes down (upwards
works fine).
This is the code (upper staff, lower staff is just s1*4)
\change Staff = lower
\times 8/7 { es,,32 g bes es \change Staff = upper g bes es}
\times 8/7 { g es bes g \change Staff = lower es bes g}
\times 8/7 { es g bes es \change Staff = upper g bes es}
\times 8/7 { g es bes g \change Staff = lower es bes g}
\times 8/7 { f as c f \change Staff = upper as c f}
\times 8/7 { as f c as \change Staff = lower f c as}
\times 8/7 { f as c f \change Staff = upper as c f}
\times 8/7 { as f c as \change Staff = lower f c as}
\times 8/7 { as c f as \change Staff = upper c f as}
\times 8/7 { c as f c \change Staff = lower as f c}
\times 8/7 { as c f as \change Staff = upper c f as}
\times 8/7 { c as f c \change Staff = lower as f c}
\times 8/7 { g b d g \change Staff = upper b d g}
\times 8/7 { b g d b \change Staff = lower g d b}
\times 8/7 { g b d g \change Staff = upper b d g}
\times 8/7 { b g d b \change Staff = lower g d b}
I can mail more of the code and the full output (correct and erroneous) if that
might help.
Thanks for your great product!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
