lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automated custom clef settings for custom staves


From: Paul Morris
Subject: Re: Automated custom clef settings for custom staves
Date: Mon, 11 Nov 2013 07:50:45 -0800 (PST)

Urs Liska wrote
> I didn't really follow this thread, but wouldn't the following be
> possible?
> 
> music = {
>   Some music }
> 
> trad = { \music }
> 
> custom = {
>   custom-clef-definition
>   \music
> }

Hi Urs,  Thanks for the thought, but it seems this won't work.  Adding
either a new or changed clef definition in 'custom' does not affect the
music that's already been stored in the 'music' variable.  See the snippet
below.  

If you un-comment the two '#(add-new-clef' lines at the top, they will be
used in 'mymusic', but they have no effect on 'mymusic' below that as part
of 'custom'.  

However, I think you could put these definitions at the beginning of
'mymusic' and tag them, and then use the tag to include or exclude the
definitions depending on which clefs you wanted.  (Then you'd only have to
use tags in one place rather than every time there was a clef or clef change
in the music.)

-Paul


%% BEGIN SNIPPET %%

\version "2.17.95"

% add-new-clef parameters:  clef-name  clef-glyph  clef-position  octavation 
c0-position

% #(add-new-clef "myclef" "clefs.neomensural.c" -3 0 2)
% #(add-new-clef "treble" "clefs.neomensural.c" 1 0 -2)
  
mymusic = {  
  \clef treble
  c' c' c' c'
  \clef myclef
  c' c' c' c'
}

custom = {
  #(add-new-clef "myclef" "clefs.neomensural.c" -3 0 2)
  #(add-new-clef "treble" "clefs.neomensural.c" 1 0 -2)
  \mymusic
  }
  
{ \custom }

\mymusic



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Automated-custom-clef-settings-for-custom-staves-tp153665p153735.html
Sent from the User mailing list archive at Nabble.com.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]