I am trying to reproduce a manuscript which use an old style bass clef. A
screen shot from <http://lsr.di.unimi.it/LSR/Item?u=1&id=900
<http://lsr.di.unimi.it/LSR/Item?u=1&id=900>> is shown below.The code
apparently worked at one time, but fails when I run it.
%% <= htt
On 2021-09-15 6:49 pm, Stanton Sanderson wrote:
I am trying to reproduce a manuscript which use an old style bass
clef. A screen shot from <http://lsr.di.unimi.it/LSR/Item?u=1&id=900
<http://lsr.di.unimi.it/LSR/Item?u=1&id=900>> is shown below.The code
apparently worked at
(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
t we could
run an update on the code.
Paul
On 16/09/2021 03:16:59, "Aaron Hill" wrote:
>On 2021-09-15 6:49 pm, Stanton Sanderson wrote:
>>I am trying to reproduce a manuscript which use an old style bass
>>clef. A screen shot from <http://lsr.di.unimi.it/LSR/Item?u=1&
On 2021-09-16 4:30 am, Paul Hodges wrote:
That works fine. I note that it doesn't update the CueClef stencil to
match, but I guess similar code to the Clef update given would suffice
(if felt necessary at all!).
Your correction raises a question in my mind (which may or may not have
helped here
> On Sep 15, 2021, at 10:58 PM, Aaron Hill 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
>> s
> On Sep 15, 2021, at 9:16 PM, Aaron Hill wrote:
>
> On 2021-09-15 6:49 pm, Stanton Sanderson wrote:
>> I am trying to reproduce a manuscript which use an old style bass
>> clef. A screen shot from <http://lsr.di.unimi.it/LSR/Item?u=1&id=900
>> <http://lsr
