About Us
We make edrums more accessible
Our goal has always been to make electronic drums sound exceptionally good at an affordable price.
There are numerous electronic drum kits available on the market, but many of them rely on outdated technologies.
How is it that a budget smartphone can cost just a couple of hundred dollars while boasting gigabytes of RAM, multi-core processors, ample storage, internet connectivity, and a large, vibrant color display, whereas electronic drum modules often don't even have 1 GB of RAM? Not to mention the poor user experience offered by their small, monochrome displays, all while costing thousands of dollars?
Our
Story
DrumPi began its journey in 2011 with Paolo, a guy who simply couldn't afford a proper electronic drum kit. He had been working as a software engineer for years when he had an epiphany: a smartphone could serve as a sound engine for an electronic drum module. This realization ignited his experimentation.
While the computational power was available, the latency was less than ideal. Even when using iOS devices with core audio, they couldn't keep the latency below the 6.5 ms threshold (buffer size + driver's ring buffer + USB polling). The result was decent but not groundbreaking; similar results could be achieved with any decent computer.
​
Therefore, in 2015, Paolo changed his approach, abandoning the smartphone and started coding prototypes on a Raspberry Pi 3 to work on a lower level. From a performance standpoint, this change was a success as they reduced the latency from 6.5 ms to 2.5 ms. However, there was a significant drawback: the code was written at such a low level that it made further development a daunting and painful task. It was as if he had built a Ferrari with no seats and no steering wheel.
​
He decided to set the project aside for a few years, during which he honed his skills in modern C++. In 2019, he returned to the project with a little help from his friend Max, who joined in.
Paolo completely rewrote the audio engine in modern and flexible C++, while Max took charge of the UI and UX development. They were now capable of incredible things, such as loading presets. They replaced the traditional Linux kernel with the preemptive-rt and profiled all the time executions to ensure the kernel wouldn't interfere. When they found it did, they isolated one core of the quad-core processor to run just one thread—the real-time audio thread.
​
They rapidly implemented features and got carried away with it. In approximately 10 months, the audio engine became a DAW in itself, including a 64-channel mixer, effects, MIDI support, multi-layered samples, multi-velocity samples, transients shaper, and the ability to record multitrack audio and MIDI.
​
The core part was complete, but what about the instrument's feel? They weren't sure about it. Paolo wasn't a professional drummer and couldn't assess it accurately. So, they reached out to Valerio, an expert, and spent months fine-tuning the actual response and feel of the instrument. Making Valerio happy was no easy feat; he had a keen eye for authenticity. However, given the results, all the effort was completely worthwhile
Meet
The Team
Paolo
Simonazzi
Hardware Programmer
Software engineer since I can remember, started with GW-BASIC in 1994 not because I enjoyed it but because that was what my 286 could do. Then I enjoyed it, I went from software to firmware but also electronics, I basically tried to frustrate myself as much as possible. Bachelor's degree in computer engineering to complete the struggle.
Massimo
Melina
Keyboard toucher
​I fell in love with computer programming at the age of 14, it was 1992. At about the same time I received my first musical keyboard; those days were all about programming and playing keyboard and that, after 30 years, hasn't changed.
Bachelor's degree in computer science because why not.