Re: Moving ClefModifiers vertically

[Simon Bailey]

Hi,

and after a little bit of experimentation, this is actually all that was needed:

\layout {
   \context {
     \Staff
     \override ClefModifier.clef-alignments = #'((G -0.2 . 0.1) (F -1
. -0.2) (C 0 . 0))
     \override ClefModifier.staff-padding = #'()
   }
}

\relative c, {
  \clef "F_8"
  c1
}

The scheme snippet is still useful though, i'll keep that for a rainy day! :)

Thanks, kind regards,
sb

On Tue, 31 May 2022 at 12:33, Simon Bailey <binabik@gmail.com> wrote:
>
> Hi Jean,
>
> On Tue, 31 May 2022 at 11:46, Jean Abou Samra <jean@abou-samra.fr> wrote:
> > Le 31/05/2022 à 12:14, Simon Bailey a écrit :
> > The pairs in clef-alignments are not (x . y) but (x-down . x-up),
> > where x-down and x-up respectively control the horizontal
> > alignment for clef modifiers that lower or raise the octave.
>
> Well, that's my facepalm moment of the day… How easy/hard/burocratic
> is it to submit a patch for the documentation to make that a bit
> clearer?
>
> > To get what you want, you need to use a grob callback.
> >
> > \version "2.22.2"
> >
> > #(define (clef::is-reduced grob)
> <... SNIP SNIP SNIP ...>
> > { \clef "F^8" s2 \clef "F_8" s2 }
> >
> >
> > Cf.
> > https://lilypond.org/doc/v2.23/Documentation/extending/callback-functions
> > and
> > https://extending-lilypond.readthedocs.io/en/latest/backend.html#understanding-callbacks
>
> I have absolutely no clue what's happening here, but it does the trick
> :D 20 years in and I still don't really understand Scheme. Maybe
> someday I'll be able to work these things out on my own.
>
> Thanks for your help!
>
> Kind regards,
> sb
>
> --
> Do not meddle in the affairs of trombonists, for they are subtle and
> quick to anger.



-- 
Do not meddle in the affairs of trombonists, for they are subtle and
quick to anger.