DIY electronic drumkit notes
The idea: build a cheap electronic, velocity-sensitive, MIDI-output drumkit.
There are many simple and cheap DIY drumkit ideas out there. Check the usual video sites.
The most basic version of this is
- sense a large impact on input pin
- send according MIDI note on serial
And most of them do that quite well, actually.
I wanted to see if I could refine the idea a little, evaluating what you can improve, both electronically, and physically.
It's a neat DIY project, in that it has analog and digital and physical things to figure out, manageable and educational, and it's pretty satisfying to have it not only work but make loud sounds.
- 1 Wishes
- 2 Physical design
- 3 Piezo as a sensor
- 4 Code
- 5 PC side
You may care about a few different things
- getting enough energy to the sensor, and consistent amount of energy to it
- more makes it easier to reliably measure impact and its velocity
- detecting velocity
- and getting it reproducably
- getting minimal energy to neigbouring pads - i.e. physical isolation from others
- avoid false triggers (without having to hard-ignore pads, which would be bad for real drumming)
- allows us to be more sensitive
- allows some choice between finger drumming and stick drumming (there's a large energy difference)
- allowing fast drumming, without false triggers
- we'll discuss why this is a thing later
- having it be useful for practice
- pads that aren't loud
- half the reason is fewer complaining neighbours
- relevant for stick drumming, not finger drumming
- getting the pads to physically bounce roughly like their real-world counterpart
- do hihat pedal properly
- and potentially things like muting
- pads that aren't loud
Many designs (even most of the fancier ones - see e.g. V-drum fixing videos) use a piezo sensor because not only are they cheap, they are generally just pretty great sensors for moderately strong vibrations.
For finger drumming, the construction can be small.
For drumkit drumming, you probably want decent-sized pads (for aiming reasons), and the implied large surface is nice for a consistent amount of energy and resonance for you to measure, which also makes it a little easier to get a more predictable amount of energy.
Keep in mind that you want to attach a piezo in a way that transmits vibrations well (figure out the resonant nodes), doesn't fall apart immediately, or preferably at all.
A solid board is good enough for quick tests.
- The main resonant node is typically in the middle, so that's where you get best response
- A dollop of wood glue works well enough for testing, but likely to break sooner rather than later.
- Something solid holding it in might, if it's too solid, locally stress and damage the piezo over time.
- A holder with something soft may dampen the response, for better or worse. You at least want to know/control that.
(I plan on modifying something like  with space for rubber (to connect) and foam (to isolate))
Also keep in mind that the wires on the piezo also carry shock directly to the piezo, so you probably want to isolate at least the last part of wire (Bit of foam, hot snot, or whatnot) from the part of the wire that may get touched or moved, or might rattle.
The bit you hitSome of the mentioned issues can be solved largely in physical design, making your life easier once you get to the electronics and code.
If you only want finger drumming, then life is actually fairly easy, because the forces are much smaller, and it's easy enough to design in a way where vibrations barely carry to neighbouring pads.
I'd recommend your first version be this, if only for the satisfaction.
If you want it larger and just want it to work at all -
If you don't care about the physical loudness of hitting pads, or the physical bounce, or training for real playing (also e.g. hihat pedal and bass drum pedal feeling real), then it's basically enough to put a piezo on the back of a piece of wood with maybe a piece of rubber on it (...also, if all those things, then consider an actual drumkit).
That test kickdrum 'pedal' in the image is made of a piece of hardish wood, a piezo disc, a socket, and some glue.
If you're DIYing because you're trying out whether drumming is a hobby for you, this may not initially matter, but certainly does once you've decided that it is.
And you may like the electronic drumkit only to save your neighbours - an actual drumkit will always feel and sound a little better.
If you want practice for drumming on a real drumkit, then you want it to not only have velocity sensitivity, you also may care
- to have something you can hit with a bunch of force, have it stay in place, and not break
- to have something with real bounce
- to have something with a real layout
- to get a sensible bounce
- to get a hihat pedal
- to get sensors to detect edge hits
- to get sensors to detect bell hits on cymbals
- to get sensors to mute cymbals
...and whatever else you can think of.
Doing all of that is a lot harder.
In particular the bounce. Having played on both a fifty dollar kit and one with meshes and rim sensors, yeah, the meshes feel a lot better, because it basically is a drum, just with a quiet skin and no need for acoustic resonance. But it's a lot harder to DIY.
That block-of-wood sensitivity is actually pretty good -- but that fancier drumkit's "regular kickdrum pedal hitting a piezo" makes a lot more sense for practice (~thirty bucks for a pedal isn't too bad).
A real hihat pedal may make a lot more sense to you than two disconnected things.
Also, an large setup solid enough not to break is also hard-couple energy well, so unless you deal with mounting details, different sensors will easily get some of the energy from adjacent hits.
The more you want sensitivity, the more that matters.
It's not hard, but it's going to take iterations. Unless you really enjoy the DIY, at some point a cheap mesh kit is just worth buying.
If you do care about the bounce and loudness, and about crosstalk and the false triggers that may cause on closeby pads, then the materials above and below the pad matter.
Good physical isolation is a little more work than you'ld think, if you want an otherwise solid thing. (For example, I at one point had a MIDI guitar, which has piezos detecting the picking of each stringalike, which if you pick them hard enough will trigger the next one over even though they're mounted in rubber. Could be lessened with filtering by velocity at MIDI level, but that a commercial product has this issue is an indication of the problem)
These materials also change the strength of the signal and the resonance of the pad, so means your code shouldn't assume too much about the design, and means you may want at least basic calibration in the velocity detection part.
Piezo as a sensor
What kind of response do you get?
Piezos are essentially stress sensors, so respond well to force/weight, impact, and vibration including that caused by impact.
Due to their design, they can be seen as stress-to-voltage sensors, but also have a decent amount of capacitance, on the order of nanoFarads capacitor.
The shape of the response varies a bunch with mounting, and the damping that implies.
The images on the right are there to give some idea of how much. More on this below.
On the right some idea of the variation of signals you get depending on mounting and what you hit it with. All use the same scale: Horizontal grid=2ms, vertical=1V. This is without the discharge resistor, so these should settle better in reality.
When used to detect hits, you probably want to treat it as polarized
The help/mounted variants suggest/show that it is then likely to mainly mainly bend one way, so the response isn't quite equal on both sides. If you are about to interpret it single-sided (and basically ignore half the waveform), one way will be more responsive than the other.
The piezo in a circuit
You can model a piezo as three things in parallel:
This combination means that, without any further components, it will hold the stress-generated voltage for a relatively long time, to the point that if you hook up a piezo directly to an ADC, you get what looks like a fairly steady voltage after each hit, that is at a different level each time.
Resting a weight on the pad will give a proportional high value (falls off eventually), as the above curve with a foot resting on it illustrates.
You may even get small changes over time and with temperature as the piezo and/or the thing it's attached to expands or shifts.
You can write code to deal with such shifty input values (largely by subtracting a recent average), but it's messy, and there's more edge cases where you can still get wild triggering, or e.g. the voltage going out of range, which you can't really control.
So many designs add a resistor across the piezo.
This is essentially a discharge resistor for the piezo's capacitance, which means the voltage output is now primarily the changes in stress, and will go to 0V the rest of the time. (it also means a ground-referenced ADC will only see half the wafeform, but that's probably acceptable)
This setup resembles an RC lowpass filter, so you can quantify its impulse response.
Since a piezo disc's capacitance will probably be in the ballpark of 500pF to few dozen nF (depending on its size), and you probably want dropoff within a few dozen milliseconds, you want a resistance on the order of 100kΩ.
(More widely, something in the range of 10k to 1M can make sense, varying with specific components and further design choices. If you wanted to make a drum interface separate from the impact sensors and make it "plug in any sort of piezo", you could to add a ~1M trimpot, in series with ~10k as a minimum, so you can easily calibrate this later)
If you are multiplexing a single ADC and find the signal is bleeding between the channels.
This is probably not because of flaws in muxing, or sampling too fast.
It's probably because ADCs like the Arduino's, and its muxing, are designed to sense things with lowish output impedance (<10kOhm for AVRs, see the "Analog Input Circuitry" section in the datasheet).
If the impedance of what you're measuring is higher than that, then the interaction with the ADC's sample-and-hold capacitor starts to noticeably become part of the sampling.
One thing you could try is lower the discharge resistor. While lowering it to ~10kOhm lessens this crossbleed, it comes at the cost of having a weaker signal (making it less sensitive) as well as changing the RC circuit with the piezo to dampen faster (which makes velocity sensitity harder), and it only lessens the issue, and doesn't solve it.
A better fix is presenting a low impedance to the ADC, via a buffer (which also implies the discharge resistor now only affects the dropoff), such as a FET or op amp.
My personal preference is op amps, mostly because those will also easily let you control the gain (and it's a little easier to breadboard, with quad op amp ICs).
That said, op amps come with further considerations, like that the output voltage swing is usually lower than the rail, so try to keep under that effective clipping level.
- If you care to build a buffer that also filters, take a look at e.g. AN4708 Signal conditioning for shock sensors.
- You can only multiplex so much before you can't sample fast enough to get well defined oscillations per drum channel, start aliasing, which would mean velocity starts being less robust.
- You may want to run the ADC faster, as the time resolution is more important than the amplitude resolution or noise.
Protecting your input
Diodes you see in a bunch of circuits seem to typically be ~5V zeners from ground to the input socket's signal, to clip peaks and protecting the ADC/buffer from peak voltages from the piezo, which could be a few dozen volts if hard-coupled and hit hard enough.
How necessary this is depends on a little the choice of piezo and resistor, and specs of ADC/buffer,
In a generalized design it's a good idea that it can help lifetime, and costs cents. They should be in my circuit.
Detecting empty sockets
As the above electronic construction means self-dampening, the voltage output is amount of recent change.
That makes basic velocity-less code easy to write. Do analogRead, Is it above threshold, and have we not triggered this in the last 100ms or so? Then trigger MIDI note" goes a long way.
When you want velocity, and smartness to help isolation, then things become a little more interesting.
Physical isolation and sensitivity
If the physical part of isolation wasn't perfect, you'll still see a little of the force from neigbouring pads.
If you don't care about velocity, then the energy loss along the way may let you choose a threshold that is fine. A little threshold tweaking can help (and you can make it adaptive).
Still, your probably want you physical design to lessens this a bunch.
Particularly when you do care about velocity, because the better the physical isolation is, the lower the 'played at all?' threshold can be, and the better we support softer playing without false triggering, even while you're hitting something nearby harder.
Yes, you also have the option of 'if two pads seem to hit less than a few ms apart, and one has rather lower intensity, then then maybe just trigger the strongest' - but
- that means you have to delay all hits a few ms.
- this will sometimes ignore actual playing, and may punish good timing
...so improving physical isolation is the better solution.
Velocity isn't hard to do and in some shape, but making it work well makes things more interesting, and introduces some tradeoffs.
There are various methods. Some are simple, some are complex, some are slightly faster (latencywise), some are more consistent, some are handier for softer playing, etc.
For example, we could watch channels for the initial hit. Once we decide it has been triggered, we keep sampling it as long as the values keep increasing, trigger once it starts falling, with the peak value as the velocity.
This is probably the lowest-latency you can get, and it's simple code in that it doesn't need to store much. However, high frequency content makes this sometimes stop too early/low. Also, using just the first peak may be a little less robust between similar hits, depending e.g. on physical resonance. Also, if the signal is so strong that it clips, it will always report the same (maximum) value.
Another way is to, once we decide to trigger, keep sampling for a fixed time (probably at least 2ms, maybe up to 10ms or so), and integrate/average the values (or e.g. an over-threshold time), and use that as the velocity.
This is more robust to high frequency content, and to that potential initial clipping.
It may also be a little' easier to tell the difference between soft hits and physical crosstalk from other pads, because the latter will often arrive more damped(verify)
It can be done without storing many samples in RAM if oyu adding magnitudes to a large-int counter, and divide by sampling time.
However, it does come at the cost of somewhat higher latency (though it's also fixed latency).
It also has a fundamental tradeoff between longer sampling time (more consistent velocity) and shorter sampling time (lower latency).
Also, one thing I'm not addressing here is how different the piezo response can be depending on how you mount it.
Apparently there's some that try to find the envelope of the signal.
This is potentially more accurate, but is harder to do, and to have this be lower latency may take even more care, and specificity to particular piezos.
Since you don't have direct control over what pad voltage should correspond to the softest hardest hits (depends on the size of the piezo and the size of the pad), you may need to trial-and-error those values.
Or, in a more practical/serious setup, let you calibrate that.
- it's fairly simple to implement a 'play a few sample hits on everything
- and store that into EEPROM
- This also makes it more a lot more modular/portable around varying physical designs/piezos.
That also makes it easier to change the curve away from linear by applying a function (e.g. a power).
Fast playing (flams, drumrolls), hard playing, and false re-triggers
Playing harder means the signal is stronger (nice in that it makes velocity easier), but also a slightly longer time it takes for the physical vibrations to taper off - may be up to 40ms or so.
So if you're reading fast enough, and your logic was "collect 8ms and decide hit or not; repeat", then the next collection may see the tail of the same hit's peak, which may still be high enough to cause that logic to trigger again.
You can work around that by adding a "AND did I not trigger in the last 100ms?" condition in your note-triggering code.
A 100ms backoff on a channel is enough for basic playing, because that's 10beats/second, = 600bpm, and most playing is far slower.
...except for flams and drumrolls, which are hits that can be on the order of milliseconds apart, so if you care about these, you now do want to distinguish between a falloff and a new hit.
This is harder to get right. It's possible, but involves some informed tradeoffs.
One decent approach is to
- normally: leave a low threshold for triggers, because
- they come up from nothing
- a lower threshold can help velocity sentitivity (a little)
- a lower threshold can help lower latency (a little)
- for some time after a note trigger: temporarily set a higher threshold
- ...based on the last triggered note's actual strength if possible
- one issue is determining that new threshold reliably
- you probably want it lower than the first peak
- but higher than the average or you risk retriggers
This means a balance between
- general threshold low for lower-latency triggers,
- evade most dampened peaks from the same hit,
- still catch most similar-velocity hits.
If you do velocities, then you may like the ability to tweak the curve on the fly.
You may want some parameters to bias this towards one behaviour or the other.
Consider also that some channels have their own logic
- You're not going to do few-ms drumrolls on a kickdrum, so can reject this harder
- fast playing on a crash cymbal amounts to a sustain so the speed doesn't matter as much - while on a ride drum or tom this is more important.
And it's generally useful to have distinct inputs be specific drumkit parts anyway, though, if only because then you don't have to think about configurable MIDI mapping.
If you vary trigger designs, e.g. have kickdrum just be a block of wood, consider physical design having a some way to tweak thresholds and curves per channel.
If you care to have practice for hihats, you want to include the pedal.
It should emit
- pedal-hihat when pedal closes, note number 44 in GM (name: G#1)
- open-hihat when hit while open, note number 46 in GM (name: A#1)
- closed hihat when hit while closed, note number 42 in GM (name: F#1)
(Those notes are from the General MIDI percussion set, and some drumkits are known to deviate somewhat. Also, when setting these by name, remember the octave numbering is not well established within MIDI so may be off by one or maybe two)
Since the pedal should allow staying closed, you can't do that via a piezo, and will need one channel to read off a simple switch instead.
Any basic footswitch should work (you can find them as e.g. sustain pedals for keyboards). This is one area where buying probably gives you something sturdier than making, unless you're a bit of a mechanical engineer already, because you learn to stomp on these things. There are also sustain pedals that try to imitate piano-like resistance which might be closer to real practice (though check whether you can stomp on them). There are other options, like DIYing a swith onto a bass drum pedal.
In theory you could combine it with a piezo to also get velocity of the hihat close, but that's probably overkill, more work, and I'm not sure a lot of drumkits even use that information(verify)
Cymbals could be muted. I've seen cheaper kits with a strategically placed pushbutton, and fancier ones with a capacitive strip (on the underside).
Probably via a NoteOff (or NoteOn with 0 velocity).
I think I've also seen aftertouch for this use, but whether that works seems to depend on your specific drum software.
(see also MIDI_notes#Percussion)
Most drum related sound makers only care for the NoteOn, but DAWs that visualize notes will get confused if NoteOffs never come, so my code sends a NoteOff ~10ms later (unless the next trigger is sooner than that).
MIDI velocity works a little differently for drums than for other things, because of the dynamics of typical playing.
Regular playing may be around 100, and compared to that, velocities under 30 or so are barely heard (and some software may not emit sound at all, or it'd sound like a kit played in the next room). Even ghost notes would probably be at 40-60.
(I spent a day trying to figure out debug my electronics because hits went missing, when it was just that I'd spread them over the MIDI range, and velocities around 15 doesn't actually trigger any sound on the software I was feeding it into)
As such, you should think about tradeoffs, between more expressiveness (sounds more natural), better repeatability, and how much you care about ghost notes.
It helps to have
- good physical isolation between heads (you can't allow softer hits if you can't distinguish them from hits on neighbouring pads)
- habit in playing
- may help to put a transform that makes the mapping from physical to MIDI velocities nonlinear.
A little tweakability to that can't hurt.
|This article/section is a stub — probably a pile of half-sorted notes and is probably a first version, is not well-checked, somay have incorrect bits. (Feel free to ignore, or tell me)|
If you want to get decent sounds for free, try options like
- a decent free drum VST
- like MT-PowerDrumkit - has fairly natural drumkit sounds, and velocity sensitivity (and is free though has a click-once-at-startup annoyance, that you can disappear by contributing something once)
- ...in a VST host
- e.g. a free one like Cantabile
- if you don't have ASIO hardware, tell cantabile to use the WASAPI output, 48kHz (or higher) if you can, exclusive mode if you can, and you may be able to get away with 384-sample buffer on generic modern hardware, for ~6ms latency which is decent for drumming.
- or a DAW if you have one anyway
- Hydrogen, which is standalone and cross-platform
Linux has a steeper learning curve when it comes to MIDI routing, and low latency audio output. It's on my list of things to figure out and summarize.