[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2835 in lilypond: set Instrument Change inform
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2835 in lilypond: set Instrument Change information once per Staff, not once per Voice |
Date: |
Sat, 30 Aug 2014 08:03:32 +0000 |
Comment #6 on issue 2835 by address@hidden: set Instrument Change information
once per Staff, not once per Voice
https://code.google.com/p/lilypond/issues/detail?id=2835
Well, it's conceivable to have both a cue as well as a full voice (like
when the full voice just repeats itself and is not useful for cueing a
waiting full voice).
In that case, any instrument name switches might need to follow the general
voice direction. Or something.
With regard to just using music variables: one thing is a name-space
problem: \kaspar is more likely to indicate the content rather than the
switcheroo. \setKaspar or even \set-kaspar would help with that.
All in all I agree that it's not clear that this feature is really overly
helpful. The one thing it provides is an implied \context \Staff { ... }
and converting all overrides to overrides at staff level.
But basically one can achieve that even with music these days by filtering
it through
(context-spec-music (make-apply-context
(lambda (c) (ly:context-mod-apply! c #{ \with { #music } #}))) 'Staff)
which would then reroute all overrides to Staff level. So if such a
rerouting
is desired, providing a command that does it is comparatively simple.
Obviously _somebody_ is using that feature and I seem to remember that
somewhere is a notice that it had been sponsored.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Lilypond-auto] Issue 2835 in lilypond: set Instrument Change information once per Staff, not once per Voice,
lilypond <=