[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Standard rhythms for drums or percussion.
From: |
Stefano Antonelli |
Subject: |
Re: Standard rhythms for drums or percussion. |
Date: |
Sun, 18 Aug 2024 20:43:20 +0000 |
User-agent: |
Evolution 3.36.5-0ubuntu1 |
Hi Michael,
On Sun, 2024-08-18 at 11:02 +0200, Zlobinsky Michael wrote:
> Since I only want the drums to sound in the background (so that the
> student has an orientation for syncopated rhythms), it is not so
> dramatic.
>
> I will try to create more examples for non-drummers over time.
There was a gentleman by the name of Vaylor Trucks who put together a
blog called The Lilypond Cookbook. It contained some important
snippets to get drum notation to look like it should. Unfortunately
the landing page at <http://lilypondcookbook.com> is no longer working.
You can access the content here:
<http://web.archive.org/web/20201111224331/http://lilypondcookbook.com/
>
except the page links don't work. Thankfully all the content is on one
page and if you start from the bottom you can see all the bits of drum
notation as it's developed in order.
There is a blog post with a template that contains all those snippets
together. I've attached it to this email.
For your purposes, it's probably better to use all stems up. Rather
than both up and down stems. It's easier to see all the rhythms.
>
> https://de-m-wikiversity-org.translate.goog/wiki/Kurs:Lilypond_f%C3%BCr_Wikis:_Schlagzeug?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp
>
I had a quick look at your wiki and noticed that you had issues with
the bass drum not showing up in midi. I'm using version 2.20.0 also
and don't have a problem with the bass drum showing up in midi. I'm on
linux and use timidity to play the midi file.
I tried to copy the lilypond code for the first example on your wiki,
but I had to hand edit some stuff. I suggest you add a way to easily
copy/paste the lilypond code from your wiki. Your score plugin is
removing the leading \ from all the lilypond commands and if I edit the
page to get the raw text there is embedded html syntax. Not user
friendly at all.
Then when I compiled that file, the hihats were failing the bar line
check. I left that alone and changed the floor tom to bass drum and
the midi worked fine for me. Just to clarify that it's not a lilypond
bug.
When compiling I see:
Interpreting music...
warning: MIDI channel wrapped around
warning: remapping modulo 16
repeated several times. So something you're doing isn't right.
I think it's because
myDrum = { \new DrumStaff <<
and
\unfoldRepeats \repeat volta 32 { \myDrum }
That DrumStaff should probably be outside the repeat. So if I replace:
myDrum = { \new DrumStaff <<
with
myDrum = { <<
With other adjustments adding \new DrumStaff where it needs to be, that
fixes the two drum stave problem, but not the midi warnings.
The fix for the midi problem was to move the \new DrumVoice out of the
repeat. This then required a \\ to combine the two voices.
myDrum = { <<
\drummode { \voiceOne \repeat volta 8 {\up}}
\\
\drummode { \voiceTwo \repeat volta 8 {\down}}
>>
}
then the midi score changes from:
\unfoldRepeats \repeat volta 32 { \myDrum }
to:
\new DrumVoice \unfoldRepeats \repeat volta 32 { \myDrum }
And as far as I can tell it generates all the right outputs. You can
also move the \unfoldRepeats up into the score context and I made some
other changes that make some of the syntax more explicit. This is the
modified score block for midi output:
\score {
\unfoldRepeats
<<
\new Staff \with { midiInstrument = #"acoustic guitar (nylon)" }
\myKey
\new Voice
\repeat volta 16 { \myGuitar }
< d a-1 d'-3 fis'-2>1 % D (End)
\\
\new DrumStaff
\new DrumVoice
\repeat volta 32 { \myDrum }
>>
\midi{}
}
But I don't claim to be an expert at lilypond syntax. I just find with
drum stuff I have to be explicit, so I treated the guitar voice the
same as the drum voice. I don't know if it's the correct way to do it.
Refer to the attached test.ly.
-Stef
lilypond-drum-template.ly
Description: lilypond-drum-template.ly
test.ly
Description: test.ly