[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Automated custom clef settings for custom staves
From: |
Urs Liska |
Subject: |
Re: Automated custom clef settings for custom staves |
Date: |
Mon, 11 Nov 2013 07:32:15 +0100 |
User-agent: |
K-9 Mail for Android |
Paul Morris <address@hidden> schrieb:
>David Kastrup wrote
>> Paul Morris <
>
>> paul@
>
>> > writes:
>>
>>> Currently you have to make changes in the music (the content) for
>>> custom clefs to work, whether that's defining a new clef with a
>>> non-standard name,
>>
>> A definition of a new clef will usually occur outside of the music.
>
>I understand that, but if you then *use* that new clef in the music,
>then
>you can't use that music on a standard staff since the new clef only
>makes
>sense on the custom staff.
I didn't really follow this thread, but wouldn't the following be possible?
music = {
Some music }
trad = { \music }
custom = {
custom-clef-definition
\music
}
?
You could do without the "trad" wrapper, it's just there to clarify the
intention.
Urs
- Automated custom clef settings for custom staves, Paul Morris, 2013/11/10
- Re: Automated custom clef settings for custom staves, Paul Morris, 2013/11/10
- Re: Automated custom clef settings for custom staves, David Kastrup, 2013/11/10
- Re: Automated custom clef settings for custom staves, Paul Morris, 2013/11/10
- Re: Automated custom clef settings for custom staves, David Kastrup, 2013/11/10
- Re: Automated custom clef settings for custom staves, Paul Morris, 2013/11/10
- Re: Automated custom clef settings for custom staves, Paul Morris, 2013/11/11
- Re: Automated custom clef settings for custom staves,
Urs Liska <=
- Re: Automated custom clef settings for custom staves, Paul Morris, 2013/11/11
- Re: Automated custom clef settings for custom staves, Paul Morris, 2013/11/11