Re: Feature request: change clef in the beginning of piece without affecting other staves

[David Kastrup]

Pavel Roskin <address@hidden> writes:

> I also saw this request in forum and mailing posts.  They mention two
> workarounds - use \partial and hide bars or use \grace with a hidden
> note in all staves.

Grace with spacer rest possibly.

> I consider both unacceptable hacks that would affect the MIDI output and
> require changes to all staves.  Lilypond input should be readable and
> durable, and adding extra notes to all staves looks like an obfuscation
> to me.  Hacks tend to break and scare away potential contributors.
>
> I believe Lilypond should be made smart enough to understand this:
>
> \version "2.15.23"
> \score {
>   <<
>     \new Staff <<
>       \context Voice = "melody" { \clef treble \clef bass c1 }
>     >>
>   >>
>   \layout {}
> }
>
> As it stands now, the treble key is eliminated.  If the user cares to
> write "\clef treble \clef bass", why should the user input be ignored
> and the first clef eliminated?

Because you can't set more than one clef at a given time step.  Clefs
are set by changing properties.  If those indicate a change of clef, an
appropriately changed clef is typeset.

Property changes are done by property change events, those are put to
effect by a suitable engraver early in the order, before the clef
engraver runs.

> At least there should be an option to suppress such annoying
> optimization.

It is not an optimization.

-- 
David Kastrup