Re: Issue 2270 in lilypond: Feature request: cross-staff chords
Updates: Labels: Bounty Comment #2 on issue 2270 by julien.r...@gmail.com: Feature request: cross-staff chords http://code.google.com/p/lilypond/issues/detail?id=2270 Let's give the bounty hunters a hint. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2270 in lilypond: Feature request: cross-staff chords
Comment #3 on issue 2270 by m...@apollinemike.com: Feature request: cross-staff chords http://code.google.com/p/lilypond/issues/detail?id=2270 This would be a major project. Pavel has already implemented a workaround for common cases in Scheme, but a holistic and automated solution would require major rewrites in several places. If you really want the feature, I'd suggest contacting David Kastrup directly. I'm sure he could code it. It'd require more than 50 € of his time, but it's worth more than 50 € and he'd do a good job. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2270 in lilypond: Feature request: cross-staff chords
Comment #1 on issue 2270 by paconet@gmail.com: Feature request: cross-staff chords http://code.google.com/p/lilypond/issues/detail?id=2270 MS has announced a patch that implements a barebones version. This is to remind that I have promised 50 EUR to reward this feature. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: cross-staff chords
On Tue, 31 Jan 2012 21:27:37 +0100 m...@apollinemike.com m...@apollinemike.com wrote: I have a patch that implements a barebones version of this that I haven't tinkered with for some time because of the issue of NoteCollision grobs. That's great news! I'm looking forward seeing it on the issue page. Even an incomplete patch would be helpful. It takes a lot of time to find out what needs to be modified. A patch would help others contribute some changes without doing all the research. NoteCollision grobs shift notes around so that they do not collide. They would assumedly need to do this for cross-staff note heads as well. However, this poses a multi-staff problem when there are cross staff chords, especially when one needs to take collisions w/ the stem into account. Another problem that arises is where to place the beam. Cross-staff stems can cut across beams, so there'd need to be beam related code as well. I'm glad that Lilypond developers stick to strict standards with regard to collision avoidance. But please consider it in perspective. I'd rather do extra work positioning noteheads and beams manually than create workarounds that are prone to breakage. One piece that would benefit from the cross-staff chords is Schubert's Die Forelle: http://www.mutopiaproject.org/ftp/SchubertF/D550/forelle/forelle-let.pdf The distance between staves doesn't need to be that wide. It it could be make flexible, the score could use less pages or use the default staff size, which would means less page turns or less strain on eyes for the performer. All if it is doable but difficult. If you can wait till the summer, it is provisionally on my summer-of-lily 2012 list. That would be great! -- Regards, Pavel Roskin ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2270 in lilypond: Feature request: cross-staff chords
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 2270 by ma...@gregoriana.sk: Feature request: cross-staff chords
http://code.google.com/p/lilypond/issues/detail?id=2270
By Pavel Roskin:
http://lists.gnu.org/archive/html/bug-lilypond/2012-01/msg01274.html
In my opinion, Lilypond should be able to support chords with noteheads on
different staves. This is especially important within staff groups for
keyboard instruments.
Lilypond can already move a voice from one staff to another. It can connect
notes on different staves with beams. Yet it doesn't allow notes from one
voice to be on different staves at the same moment.
Lilypond supports cross-staff stems, which provides a workaround and thus
acknowledges the need to have cross-staff chords.
The problem with the cross-staff stems is that there is no reliable way to
ensure that they would reach all the noteheads unless the distance between
staves is fixed. Fixing the distance between staves requires such hacks as
negative padding. Lilypond should be free to choose the distance between
staves for the best layout and adjust the cross-staff stems to look
correctly.
It is possible to use overlapping stems to guard against stem
discontinuity. However, overlapping parts of stems may look darker than
non-overlapping parts dependent on the anti-aliasing algorithm used to
display them.
But it's not just about stems. Even whole notes could benefit from being in
a cross-staff chord. It would make it easier to connect those notes to
other notes from the same voice.
The most natural syntax would be to allow \change inside chords:
\new PianoStaff
\new Staff = right { c' \change Staff=left c4 }
\new Staff = left { \clef bass s4 }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: cross-staff chords
Hello, 2012/1/31 Pavel Roskin pro...@gnu.org In my opinion, Lilypond should be able to support chords with noteheads on different staves. This is especially important within staff groups for keyboard instruments. This has been added as http://code.google.com/p/lilypond/issues/detail?id=2270. Marek Klein bug squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Feature request: cross-staff chords
Hello!
In my opinion, Lilypond should be able to support chords with
noteheads on different staves. This is especially important within
staff groups for keyboard instruments.
Lilypond can already move a voice from one staff to another. It can
connect notes on different staves with beams. Yet it doesn't allow
notes from one voice to be on different staves at the same moment.
Lilypond supports cross-staff stems, which provides a workaround and
thus acknowledges the need to have cross-staff chords.
The problem with the cross-staff stems is that there is no reliable
way to ensure that they would reach all the noteheads unless the
distance between staves is fixed. Fixing the distance between staves
requires such hacks as negative padding. Lilypond should be free to
choose the distance between staves for the best layout and adjust the
cross-staff stems to look correctly.
It is possible to use overlapping stems to guard against stem
discontinuity. However, overlapping parts of stems may look darker
than non-overlapping parts dependent on the anti-aliasing algorithm
used to display them.
But it's not just about stems. Even whole notes could benefit from
being in a cross-staff chord. It would make it easier to connect
those notes to other notes from the same voice.
The most natural syntax would be to allow \change inside chords:
\new PianoStaff
\new Staff = right { c' \change Staff=left c4 }
\new Staff = left { \clef bass s4 }
--
Regards,
Pavel Roskin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: cross-staff chords
2012/1/31 Pavel Roskin pro...@gnu.org:
In my opinion, Lilypond should be able to support chords with noteheads on
different staves. This is especially important within staff groups for
keyboard instruments.
It is not easy. This is the closest we are to a flexible solution nowadays:
\new PianoStaff
\set PianoStaff.connectArpeggios = ##t
\override PianoStaff.Arpeggio #'stencil = #ly:arpeggio::brew-chord-bracket
\new Staff { c'4 \arpeggio }
\new Staff { \clef bass
{ c4\arpeggio }
\\
{ g, e, c,4 }
}
The most natural syntax would be to allow \change inside chords:
\new PianoStaff
\new Staff = right { c' \change Staff=left c4 }
\new Staff = left { \clef bass s4 }
A given syntax is not the feature, it is just an interface to the
feature. The feature is not there, regardless the trivial you can
think it is by looking at that neat construct.
Various users have requested the same in the past. Perhaps you can
hire a good programmer to implement it. You have been warned,
programmer work is not free.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
attachment: document.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: cross-staff chords
2012/1/31 Pavel Roskin pro...@gnu.org: Various users have requested the same in the past. I know. Perhaps it's time to have an issue in the bug tracker. Definitely. Once there is an issue in the tracker, it should be possible to attach bounties to it. I would add an amount to that, for I'm interested in the feature. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: cross-staff chords
On Jan 31, 2012, at 9:14 PM, Francisco Vila wrote: 2012/1/31 Pavel Roskin pro...@gnu.org: Various users have requested the same in the past. I know. Perhaps it's time to have an issue in the bug tracker. Definitely. Once there is an issue in the tracker, it should be possible to attach bounties to it. I would add an amount to that, for I'm interested in the feature. Hey all, I have a patch that implements a barebones version of this that I haven't tinkered with for some time because of the issue of NoteCollision grobs. NoteCollision grobs shift notes around so that they do not collide. They would assumedly need to do this for cross-staff note heads as well. However, this poses a multi-staff problem when there are cross staff chords, especially when one needs to take collisions w/ the stem into account. Another problem that arises is where to place the beam. Cross-staff stems can cut across beams, so there'd need to be beam related code as well. All if it is doable but difficult. If you can wait till the summer, it is provisionally on my summer-of-lily 2012 list. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: cross-staff chords
2012/1/31 m...@apollinemike.com m...@apollinemike.com: Hey all, I have a patch that implements a barebones version of this that I haven't tinkered with for some time because of the issue of NoteCollision grobs. NoteCollision grobs shift notes around so that they do not collide. They would assumedly need to do this for cross-staff note heads as well. However, this poses a multi-staff problem when there are cross staff chords, especially when one needs to take collisions w/ the stem into account. Another problem that arises is where to place the beam. Cross-staff stems can cut across beams, so there'd need to be beam related code as well. All if it is doable but difficult. If you can wait till the summer, it is provisionally on my summer-of-lily 2012 list. Cheers, MS I offer 50 EUR if your patch makes easy to typeset these: http://assets.sheetmusicplus.com/product/Look-Inside/large/19312987_01.jpg http://assets.sheetmusicplus.com/product/Look-Inside/large/19312994_01.jpg (fair use of low-quality previews of copyrighted material) -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
