Thomas Morley <thomasmorle...@gmail.com> writes:
> 2016-11-05 12:39 GMT+01:00 Malte Meyn <lilyp...@maltemeyn.de>:
>>
>>
>> Am 04.11.2016 um 23:15 schrieb Tobin Chodos:
>>>
>>> What's the best way to handle a percussion part that has a lot of
>>> pitched and un-pitched material?
>>
>>
>> You could have a “pitched” Staff accept not only “pitched” Voices but also
>> DrumVoices:
>>
>> \version "2.18.2"
>>
>> \new Staff \with {
>> \accepts DrumVoice
>> } \relative {
>> c' d e f
>> \new DrumVoice \drummode {
>> bd hh sn hh
>> }
>> g a b c
>>
>> }
>
>
> Hi Malte,
>
> this will fail if the DrumVoice is created before Voice, uncomment
> Voice to make it work.
>
> \new Staff \with { \accepts DrumVoice }
> \relative {
> %\context Voice { <> }
> \context DrumVoice \drummode { hh4 hh hh hh }
> g a b c
> }
Thinking too complex: you can just nest them:
\new Staff \with { \accepts DrumVoice }
\relative \new Voice {
\new DrumVoice \drummode { hh4 hh hh hh }
g a b c
}
Now here is another consideration: I wanted to use \drums here but it
created another DrumStaff.
It turns out that the shortcuts
\figures \chords \drums \lyrics
all create a Bottom context _except_ for \drums. Should we change \drums
revert to creating a DrumVoice? At the current point of time, only a
DrumStaff accepts a DrumVoice so this should cause very little change.
The only change to be feared is that
\drums \with ... { }
would apply the context mod to the DrumVoice, not the DrumStaff. This
will make it impossible to influence DrumStaff-level engravers with a
context mod here. However, it will allow to _override_ DrumVoice-level
settings. Overall, this might be a bit less confusing. Our code base
does not currently contain \drums \with .
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
