Re: Feature request: cross-staff chords

[Pavel Roskin]

On Tue, 31 Jan 2012 18:02:35 +0100
Francisco Vila <address@hidden> wrote:

> 2012/1/31 Pavel Roskin <address@hidden>:
> > 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 } >>
>   }
> >>

Actually, I'm thinking about using an arpeggio bracket that looks
like a stem.  If that fails, I'm considering using grid lines.

> > The most natural syntax would be to allow \change inside chords:
> >
> > \new PianoStaff <<
> >  \new Staff = right { <c' \change Staff=left c>4 }
> >  \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.

I know.  That's why I wrote it in the end.  There is another syntax
that should work but doesn't because the feature is not there:

\new PianoStaff
<<
  \new Staff = right {
    c'4*0 \change Staff=left c4
  }
  \new Staff = left {
    \clef bass s4
  }
>>

> Various users have requested the same in the past.

I know.  Perhaps it's time to have an issue in the bug tracker.

> Perhaps you can
> hire a good programmer to implement it. You have been warned,
> programmer work is not free.

Once there is an issue in the tracker, it should be possible to attach
bounties to it.

By the way, I'm going to pay a bounty for issue 1110 soon, it looks
like the patch is in the way to the mainline.  I hope our great
programmers would attack another chord-related issue soon, probably
after 2.16.

-- 
Regards,
Pavel Roskin