On 07/05/2012 09:06 AM, David Kastrup wrote:
Peter O'Doherty <m...@peterodoherty.net> writes:
Hi list,
When using these two lines together
#(set-accidental-style 'dodecaphonic)
\override Accidental #'hide-tied-accidental-after-break = ##t
\override Accidental... cancels out the dodecaphonic command
everywhere in the score.
If you are using a somewhat recent version of LilyPond, the problem more
likely is that you accidentally did not set the accidental style in the
first place. Note that #(set-accidental-style 'dodecaphonic) written in
music does nothing: it calculates music expressions that set the
accidental style, then returns them as a Scheme value, and LilyPond
ignores Scheme in music by default (not so as an argument of a music
function, however).
You have to write $(set-accidental-style 'dodecaphonic) instead, or more
simply,
\accidentalStyle "dodecaphonic"
Is there another way to avoid repeated accidentals on new staves but
still keep the accidental style 'dodecaphonic?
I find that
{
\accidentalStyle "dodecaphonic"
\override Accidental #'hide-tied-accidental-after-break = ##t
cis~ cis cis~ cis~ \break cis~ cis cis~ cis
}
works just like I would expect.
Thanks for your help.
The accidental override doesn't work when the tied notes are contained
within a |<< \\ >> |construct. Is there a way to deal with these?
Regards,
Peter
--
//=============================
-> Peter O'Doherty
-> http://www.peterodoherty.net
-> m...@peterodoherty.net
-> https://joindiaspora.com/people/70716
//=============================
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
