> On Sep 15, 2021, at 10:58 PM, Aaron Hill <lilyp...@hillvisions.com> wrote:
>
> (re-adding mailing list for visibility...)
>
> On 2021-09-15 8:26 pm, Stanton Sanderson wrote:
>> Unfortunately, no. With Lilypond 2.23.3, substituting \clef my-clef
>> for \cleff bass in the code results in Frescobaldi’s Lilypond Log
>> spitting out a list of supported types:
>> warning: unknown clef type `my-clef'
>> warning: supported clefs: C F G G2 GG…. (And so on). Will look further
>> tomorrow.
>
> Wait... what error were you getting with the original LSR snippet? Was it
> not something like this?
>
> ====
> GNU LilyPond 2.22.0
> Processing `custom-bass-clef.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `custom-bass-clef.cropped.eps'...
> warning: unknown line-cap-style: (quote round)
> /usr/local/lilypond/usr/share/lilypond/current/scm/output-ps.scm:272:49: In
> procedure symbol->string in expression (symbol->string join):
> /usr/local/lilypond/usr/share/lilypond/current/scm/output-ps.scm:272:49:
> Wrong type argument in position 1 (expecting symbol): (quote round)
> ====
>
> "\clef my-clef" is nonsense. You would have to register a new clef type (if
> that is even possible), and the LSR snippet certainly is not doing that. It
> is replacing the stencil for a bass clef, but you still say \clef bass.
Aaron, thanks for your help, time and the clarification.The desired clef shape
now appears in the proper location.
-Stan