Today I started to do some tests to calculate microDrum latency. I used a Behringer UCA 222 sound card as an oscilloscope , the software “Electroacoustics Toolbox” to analyze the signal and, for convenience, a MIDI Thru Box to split the output of the microDrum (this have certainly introduced a delay). I have connected an input between the piezo and the microDrum and the other input to one of the outputs of the MIDI Thru Box. I did several tests using various pads and different values ​​of Scan Time. The Scan Time is the time in milliseconds where the microDrum analyzes the signal before sending a MIDI note. The first question that I have done is, how much time elapses from when the microDrum ends to sample the signal and when the MIDI note is sent?

In all the tests this value is less than 1 ms. In the photo I used a Red Shot Trigger DDRUM and I set the value of the Scan Time 3 ms (as you can see it would be enough less). By analyzing the signals, the distance between the two fronts is 0.9 ms. It seems to me a very good result. Soon I will do the tests using an Arduino Due with 84 MHz ARM processor.

Dear microDrummers, my work goes, I’m currently working on several aspects simultaneously.

-New version of ConfigTool for OsX. This version will be released initially in a simplified form and only after I will add the extras including support for VST.

-In the version of Mac ConfigTool I’m also working on an interesting option that allows you to export on the iPhone/iPad the DKIT/DSND sounds libraries. Then I’ll do the same thing for the VST.

-New Interface for iPad / iPhone. Among you there is someone who has pictures (or rendering) of the individual parts of a drum set?

-Plexiglas box. What you see in the picture is a prototype to see if the measurements are correct, the final version should be done using only a few joints and screws.

Obviously I’m also working on other little things, on the compatibility with Arduino DUE, etc. …For example I would like to build a MIDI Router using Arduino ….

WARNING:

The current diagram of microDRUM is not compatible with the Arduino DUE. Even the code is not compatible because of the different processor.

I made the changes on a micro-microDRUM and seems to work. I will try to see if it can use the DAC to generate usable sounds, only if I can make it work I will share changes to the schema and code.

Sorry for the delay, I was busy with work. Here are the diagrams for connecting an LCD to microDRUM. The code to handle it is still incomplete, but I hope soon to have the time to finish it. I remind you that the LCD screen is optional and microDrum works fine without it, I added it because you asked me.

A friend of mine is building a prototype of the box. According to his work, I will decide how and whether to create a specific PCB for the LCD screen.

New software version for iPhone / iPad. In this new version there are two important changes: the addition of effects and a simple sequencer. Regarding the effects have I included only the reverb, but the sequences although very simple in my opinion is very effective, both to write short loop and to test the SFZ files. At this point I will cut off the buttons for the tests in the menu SFZ and I will insert the possibility to modify the sound library loaded. I’m also working on the iPad version that takes advantage of the screen, if you have any ideas / requests let me know. (Wiki)

embedded by Embedded Video

YouTube Link -

For this new video I used the Medeli dd506 linking it to microDrum and a MacBook Air with Addictive Drums.

As seen in some photos and some videos I have a MacBook Air, nice computer but incompatible with our Config Tool. Typically, to set the parameters of microDrum I had to use or VirtualBox with Windows or the iPhone with my program. In both cases worked but required more time. So I decided to write a small program in Python to help me to quickly modify the parameters directly from OsX. I used this wrapper for the Midi. In the coming days will release the code on GitHub.

We arrived, after nearly two years of development, the last barrier was broken. The microDrum firmware becomes Open Source. I think it’s an important step because the quality of microDrum no longer depend only on me but also by those who want to devote his time. So it is important that each of you publicize this project in order to bring together a larger number of developers. For version 1.1beta you will find all the code on GitHub. When deemed ready, I will compile the firmware for version 1.1 and release it in the pages of Downloads and pass on GitHub to version 1.2beta. It ‘a very simple way to manage code, but for now suffice.

I added this software to Download Page. If anyone is interested in the code write it in the comments (or on the forum) and I’ll try to upload on GitHub.

This version of DrumScope, using the algorithm of firmware 1.1 I have not yet released, but it can still be useful to analyze the DIY pads.

I’m working to migrate the code from Google Code server to GitHub server. I will leave the project for a few days on both servers, then I will delete the one on Google.