Cybo-Drummer

Humanize those drum computers!

Note

Cybo-Drummer’s hardware design is currently in it’s first prototype stage and the firmware in it’s first public beta (version 0.1.0) stage. It is my very first Python/MicroPython project, my first PCB design (learning still!) and generally the first microcontroller-based project I developed from scratch and I actually brought to the finish line. It has been a learning experience, but by no way I’d say it's perfect, so I'm happy to receive your feedback on the hardware, the software, the feature set, a bug you found or anything you’d like to share.

Are you an experienced drummer (I’ve only been drumming for about 1.5 year – too much of which I’ve spent on this project instead of practising…) with a fascination for synthesized drum sounds? I’d love to hear how you experience using Cybo-Drummer. What would you change? What features are you missing?

Of course I’m open for collaboration. Just let me know how you think you can contribute!

Please use the [issues tab](hlammers/cybo-drummer/issues/ to report bug and other issues, or the discussion tab to discuss anything else.

Introduction

I own an electronic drum kit and a bunch of drum computers and my dream was to use the former to play the latter, so I went searching for a way to do just that – allowing me to easily switch between different configurations combining the sounds of one or more drum computers. I looked for hardware solutions, but couldn’t find any. I looked for software solutions, but I could only find MIDI mappers or other complex solutions that would never give me the easy to use experience I had it mind. It turns out that (as usual) I go against the current fashion of trying to make an electronic drum kit sound (and look) as acoustic as possible. So I decided to develop my own solution – and publish it as open source DIY project, hoping it finds like-minded drummers!

Overview

Cybo-Drummer is a MIDI router/mapper with 6 input ports and 6 output ports, specially designed for mapping drum triggers (electronic drum kits’ brains) to drum computers. Since there is no standard for the MIDI messages sent by drum kits, nor the messages received by drum computers, Cybo-Drummer offers a flexible way of mapping the one to the other.

The idea for the hardware was inspired by the work of diyelectromusic (Kevin), in particular his Raspberry Pi Pico Multi MIDI Router. The first prototype is an additional PCB on top of the Multi Midi Router.

Features

Hardware

6 times 5-pin DIN MIDI input port: connect up to 6 drum kits, drum pads, keyboards, etc.
6 times 5-pin DIN MIDI output port: connect up to 6 drum computers, samplers, synthesizer, etc.
micro USB port for power and firmware update (MIDI over USB is not yet implemented; next prototype will include 5.5mm socket for 5V DC power supply)
2.2 inch colour display (220×176 pixels)
2 rotary encoders and 2 push buttons for input and navigation (plus reset button)

Mapping

graph LR
    subgraph IP["`input port assignment (6)`"]
        IPORT["`**input port**
        _includes:_
        - channel`"]
    end
    subgraph IDEF[input device-level presets/triggers]
        direction TB
        IDEV-->|1 to many|ITRIG["`**input trigger**
        _includes:_
        - note
        - pedal cc`"]
        IDEV["`**input device**`"]-->|1 to many|IPRES
        ITRIG-->|up to 6 to 1|IPRES["`**input preset**
        _includes:_
        - pedal cc minimum value
        - pedal cc maximum value`"]
    end
    subgraph PR["`mapping program (many)`"]
        PROG["`**program**
        _includes:_
        - program change
        - bank select`"]
    end
    subgraph ODEF[output device-level presets/triggers]
        direction TB
        OPRES-->|many to 1|ODEV["`**output device**
        _includes:_
        - channel
        - 0 velocity as note off toggle
        - running status toggle`"]
        OPRES["`**output preset**
        _includes:_
        - note`"]-->|1 to up to 5|OTRIG["`**output trigger**
        _includes:_
        - channel
        - note
        - note off send toggle
        - velocity threshold
        - velocity curve
        - minimum velocity
        - maximum velocity`"]-->|many to 1|ODEV
    end
    subgraph OP["`output port assignment (6)`"]
        OPORT["`**output port**`"]
    end
    SEL(["`**select**`"])-->|1 of up to 255|PR
    IMIDI(["`**MIDI in**`"])-->IPORT-->|1 to 1|IDEV
    IDEF-->|many to 1|PROG
    PROG-->|1 to up to 6|ODEF
    ODEV-->|1 to 1|OPORT-->OMIDI(["`**MIDI out**`"])

Flexible layered approach to mapping:
- Define input and output devices and trigger definitions – a trigger is always associated to a specific device
- Assign input and output triggers to presets – one preset can be linked to multiple triggers and the same trigger can be linked to multiple presets (mixing different devices)
- Assign multiple input and output presets to each other in programs to quickly switch between different configurations
- Limits:¹ 255 programs, 4,096 devices, 4,096 presets – there’s no hard limit to the number of triggers
Send program change and/or bank select commands on program change
Set trigger dependency to cc value (for example to distinguish between open and closed hi-hat from many drum modules)
Supports both one note per sound on the same channel and one sound per channel, or a combinations of both – including tonal mapping
Adjust velocity dynamics (threshold, curve, minimum velocity, maximum velocity)

Note

Cybo-Drummer Mapping Terminology
Input device: A drum kit, drum pad, keyboard or other device that outputs MIDI data
Input trigger: The MIDI note that is been sent by an input device when playing a drum pad, key, etc.
Input preset: A combination of input triggers and optional foot pedal settings that can be assigned to trigger an output preset
Output device: A drum computer, sampler, synthesizer or other device that responds to MIDI data
Output trigger: The MIDI channel and/or note that triggers a sound in the output device
Output preset: A combination of output triggers and optional note that can be assigned to be triggered by an input preset
Program: A mapping of one or more input presets to one or more output presets plus optionally program change and/or bank select commands to be sent to output devices

Other Features

MIDI learn: Set one of the input ports to receive midi learn data (note values, channel values, cc numbers, etc.)
MIDI thru: Set all data² received on one of the input ports to be sent unaltered to one of the output ports
MIDI monitor with three views: Show mapping flow (input preset > output preset), MIDI data coming in and MIDI data sent out

Building Instructions

Cybo-Drummer is a DIY project which is currently in a prototype stage. The hardware design is a pragmatic solution, building upon an existing design by diyelectromusic (Kevin), who designed the bottom PCB with the MIDI ports. As a next step I want to design new hardware (including 3d printable enclosure) and now I have a working prototype I’m considering what to improve in the next iteration. These are a few of my considerations:

Where to place the MIDI ports? The current prototype has input ports at the front and output ports at the back. The disadvantage is that the MIDI cables take a lot of space at two sides of the device. Perhaps MIDI ports at the top of the device is a better solution? In two rows above the display, buttons and knobs? Alternatively I could leave the ports at the top and the bottom (angled PCB-mounted 5-pin DIN ports are much easier available than straight ones) and design a drum rack mounted casing (or a casing with 70mm × 10mm spaced holes to connect a standard size mounting plate for drum modules and multi-pads).
Should I add more buttons? All GPIO pins of the Raspberry Pi Pico are in use, so that would require adding IO ports, for example using one ore more PCF8574 I2C IO expander ICs. Having more IO ports would allow improvements like:
- Splitting the TRIGGER button into a TRIGGER and a TRIGGER SELECT button
- Adding a SAVE button
- Adding quick buttons for pages
- Adding status LEDS

I have no intention to sell Cybo-Drummer as a fully assembled product, nor as DIY package – I might change my mind in the future, but for now that doesn’t seem like a realistic idea, next to a full-time job and a family (especially because I expect it to be a very niche product – unless the a change in trend occurs and many more drummers become interested again in electronic drums as an instrument of its own – like in the 1980s – instead of a means to simulate acoustic drums). Nevertheless: if you think you can convince me to change my mind, feel free to try!

Hardware

Building the Cybo-Drummer hardware only requires basic soldering skills (only though-hole components). The PCBs can be ordered cheaply from Chinese PCB services like JLCPCB (no affiliate).

Note

The initial hardware is a crude, though functional prototype, without casing. I’m planning to design improved hardware including front panel and 3d printable case.

BOM (Bill of Materials)

First Board: Raspberry Pi Pico Multi MIDI Router

The Raspberry Pi Pico Multi MIDI Router PCB
6× H11L1 optocouplers
6× 470Ω resistors
6× 220Ω resistors
6× 33Ω resistors
6× 10Ω resistors
6× 1N914 or 1N4148 diodes
6× 100uF ceramic capacitors
12× 5-pin DIN PCB mount sockets (check the footprint on the PCB!)
2× 20-pin header sockets (originally for the Pico, now for connecting to the second board)
Optional: 6× 6-way DIP sockets for the H11L1 optocouplers

Second Board

PCB: order from your favourite PCB service – a zip file with Gerber files can be found in the Gerber files folder
Raspberry Pi Pico with headers³
2.2" 176×220 TFT display board with ILI9225 driver – sold for example here
4× 10kΩ resistors
2× EC11 rotary encoders
3× 4-pin tactile momentary buttons 6×6mm
1× 11-pin header
2× 20-pin header sockets
2× 20-pin headers
7× 11mm spacers plus bolts/nuts

Note

The schematics for the second board can be found in the schematics folder.

Build Instructions

First Board: Raspberry Pi Pico Multi MIDI Router

For the 1st board, follow the excellent instructions by diyelectromusic (Kevin): Raspberry Pi Pico Multi MIDI Router

Second Board

Solder all components in the following order:
- Resistors
- Buttons (SW3, SW4, SW5)
- Male headers (J1, J2) on the back side of the PCB
- Female header sockets (J3, Pico)
- Rotary encoders (SW1, SW2)
Plug the display board into header socket J3 and fix it to the second board using four spacers (the top-right spacer will screw into the spacer that connects the first board to the second board)
Plug the second board to Pico header sockets of the first board and fix them together using four spacers
Plug the Raspberry Pi Pico into the 2x 20-pin header sockets on the second board

Software

The easiest way to install the software is by downloading the [latest firmware](releases/ as a single file and uploading it the Cybo-Drummer, but it can be run directly from source as well.

Note

Cybo-Drummer offers a couple of key combinations specifically for debugging and firmware upload purposes:
RESET: resets Cybo-Drummer
RESET + TRIGGER: avoids starting Cybo-Drummer’s main loops (the user interface and the router) and allows a PC to interact over USB – press the RESET button while keeping the TRIGGER button pressed until the PC made a connection (after the Raspberry Pi Pico’s LED flashed)
RESET + TRIGGER + PAGE: (alternative to BOOTSEL + RESET) start bootloader (show Cybo-Drummer as drive called RPI-RP2 on your PC for uploading firmware) – press the RESET while keeping the TRIGGER and PAGE buttons pressed until the RPI-RP2 drive appears on your PC (after the Raspberry Pi Pico’s LED flashed)

Uploading Firmware

Back up your user settings (see warning box below)
Download the [latest firmware release](releases/ (.uf2 file)
Connect Cybo-Drummer with a USB cable to your PC of choice (Windows/Linux/MacOS)
Do one of the following to make the Cybo-Drummer appear as a drive called RPI-RP2 on your PC:
- Press the RESET button and wait for the LED on the Raspberry Pi Pico to turn on; in the 1 second the LED is on, press and keep the TRIGGER and PAGE buttons pressed until the RPI-RP2 drive appears on your PC
- Keep the Raspberry Pi Pico’s BOOTSEL button pressed and keep the RESET button pressed until the RPI-RP2 drive appears on your PC
Copy the firmware file to the PRI-RP2 drive – Cybo-Drummer will automatically restart with the new firmware
Restore your user settings (see warning box below)

Warning

Uploading new firmware might delete your user settings (including user-defined programs) and reinstate default values! User settings are stored internally in a file folder called data_files. Currently the easiest way To back-up (download) or restore (upload) the file is by following these steps (assuming you’re using a Windows PC):

If you haven’t before: Install Python – follow the instructions provided here and make sure to select ‘Add Python 3.x to PATH’
If you haven’t before: Download the source code of MicroPython release v1.24.0. (typically the zip version) and unzip it somewhere on your PC
In File Explorer go to the micropython-1.24.0\tools\mpremote folder (in the location where you unzipped MicroPython)
Right click somewhere in the folder (not on a file) and from the context menu select ‘Open in Terminal’
If you do it for the first time: type the following to install required Python modules:
```
pip install pyserial
pip instal importlib_metadata
```
To back up user settings:
- On your PC type py mpremote.py fs cp -r :data_files/ . without pressing ENTER (so not executing it yet)
To restore user settings:
- Copy your data_files to the micropython-1.24.0\tools\mpremote folder
- On your PC type py mpremote.py fs cp -r data_files/ : without pressing ENTER (so not executing it yet)
While you keep Cybo-Drummer’s TRIGGER button pressed:
- Press RESET button on Cybo-Drummer
- Press ENTER on your PC to start downloading (backing up) or uploading (restoring)

Running From Source

It is possible to run Cybo-Drummer from source by uploading the content from the src folder to the Raspberry Pi Pico running stock MicroPython.

Keep in mind that when running from source (instead of frozen into firmware), Cybo-Drummer takes more time to start up and screen refreshing. To resolve this while playing around with the code it is also possible to freeze only part of the source code, following the instructions under building firmware from source.

Building Firmware From Source

So far I haven’t found any way to build MicroPython on a Windows PC, only on a device running Debian Linux, so I’m using a Raspberry Pi 400 for this purpose, but any Raspberry Pi 4 or 5 running Raspberry OS will do.

To build Cybo-Drummer follow these steps:

First time you build Cybo-Drummer: In the Raspberry Pi console type (this creates a /home/pi/pico folder to with the MicroPython source code):

cd ~/
mkdir pico
cd pico
git clone https://github.com/micropython/micropython.git --branch master
cd micropython
git checkout v1.24.0
sudo apt update
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi build-essential
make -C mpy-cross

Copy all files from the src folder except screen_log.py and the data_files folder to the /home/pi/pico/micropython/mpy-cross/ folder
Remove all files (from previous Cybo-Drummer builds) from the /home/pi/pico/micropython/ports/rp2/modules folder, except except the default files main.py, _boot.py, _boot_fat.py and rp2.py
In the Raspberry Pi console type the following to pre-compile each .py file you just copied (except main.py, which needs to be frozen as a .py file), delete them afterwards (the -O3 option, which stands for optimization level 3, makes sure __debug__ is False and all debugging code is left out) and move results to the /home/pi/pico/micropython/ports/rp2/modules folder (to freeze them into the firmware):

cd ~/pico/micropython/mpy-cross
for f in *.py; do [ "$f" != "main.py" ] && python3 -m mpy_cross -march=armv6m -O3 $f; [ "$f" != "main.py" ] && rm $f; done
mv {*.mpy,*.py} ../ports/rp2/modules/

Now to build the firmware type in the Raspberry Pi console:

cd ~/pico/micropython/ports/rp2
make submodules
make clean
make

The freshly built firmware is stored as /home/pi/pico/micropython/ports/rp2/build-RPI_PICO/firmware.uf2

Tip

An easy way to copy the Cybo-Drummer source code from a PC to the modules folder on a Raspberry Pi is by setting up Samba on the Raspberry Pi and turn the home/pi/pico folder into a shared folder.

How to Use Cybo-Drummer?

Overview

Cybo-Drummer has six MIDI input ports at the front and six MIDI output ports at the back. It has a micro USB port on the left side currently only used for power supply and for updating the firmware.

The user interface displayed on the 2.2 inch TFT screen is organized as follows:

Page tabs: The right edge of the screen shows which of the five pages is selected
Title bar: The top edge of screen shows a title bar, consisting of three elements:
- On the left the active program number is always visible (an asterisk is shown behind the number if the program has unsaved changes)
- Centrally the title of the active sub-page is shown
- On the right the number of the active sub-page and how many sub-pages the active page has
Sub-page: The remainder of the screen is taken by the sub-page itself
- Blocks: all sub-pages except those on the monitor page are structured in locks which can be selected to enter input; the active block is highlighted using a dark and light sea green colour

To control Cybo-Drummer’s user interface it has two buttons and two rotary encoders, which usually behave as follows:

PAGE/YES:
- Short press: Toggle page select mode on or off
- Long press: Show pop-up to select program
TRIGGER/NO:
- Short press: Trigger last selected output trigger preset (for testing purposes)
- Long press: Show pop-up to select trigger preset
NAV/↕ | DEL:
- Turn: Navigate / select active block
- Press (when a program, device, preset or trigger name block is selected): Delete program, device, preset or trigger (a confirmation pop-up will show)
VAL/↔ | SEL/OPT:
- Turn: Change value of active block or pop-up
- Press:
  - When a value was changed but not confirmed yet: Confirm value and process the change (not yet confirmed value is indicated by a purple square around the text)
  - When a program, device, preset or trigger name block is selected: Rename or show options menu (press twice if the value was changed, but not yet confirmed: the first time will confirm it, the second time triggers rename or options menu)
  - When a button block is selected: Press/execute button

Pages and sub-pages

Cybo-Drummer’s user interface is organized in five pages:

PRG (Program): Select and edit routing programs
IN (Input): Edit input port assignments, input device setting, input trigger settings and input preset settings
OUT (Output): Edit output port assignments, output device setting, output trigger settings and output preset settings
MON (Monitor): Show router and MIDI monitors
SET (Settings): Adjust global settings

To change the pages and sub-pages, short-press the PAGE button to enter page select mode. Now turn the VAL/↔ knob (right knob) to change the page and the NAV/↕ know (left knob) to change the sub-page. Short-press the PAGE button again to leave page select mode. While in page select mode the page tabs and title bar are highlighted in dark and light sea green.

Caution

The PRG (program) page does not save automatically, all other pages do (after confirming a changed value). If there are unsaved changes to a program an asterisk will show behind the active program number. To save changes, go to the first program page (program: mapping), select the program block, short-press the SEL/OPT button and choose ‘save’. This will show a pop-up to ask for confirmation and another pop-up to ask if you want to replace the active program – select ‘yes’ to save changes to the active program or select ‘no’ to save the changes to a new program directly after the active program.

Tip

To duplicate the active program, make a change and save without replacing, this creates a new program directly after the active program.

Trigger presets

Short-press the TRIGGER button to trigger the last selected output trigger preset (for testing purposes). Long-press the TRIGGER button to show a trigger preset selection pop-up.

While the trigger selection pop-up is shown: Turn the VAL/↔ knob to selected an output trigger preset and press the YES button (left button) to confirm and close the pop-up, or the NO button (right button) to close the pop-up without changing the selected trigger.

Confirmation Pop-Ups

Cybo-Drummer doesn’t have an undo feature, so to avoid accidentally losing data confirmation pop-ups will show up before deleting something, changing an unsaved program, restoring a back-up or doing a factory reset. Answer the question in the pop-up by pressing the left button for YES and the right button for NO.

Description of All Pages and Sub-Pages

PRG (Program)

The program page is the first page that shows when powering up Cybo-Drummer. Use this page to select or edit the active program.

Tip

Programs can also be changed from any page/sub-page by long pressing the PAGE button. This will show the program selection pop-up. While the program selection pop-up is shown: Turn the VAL/↔ knob to selected a program and press the YES button (left button) to confirm and close the pop-up, or the NO button (right button) to close the pop-up without changing the active program.

PRG 1/5 – Program: Mapping

program

Select the active program
Select ‘[add new]’ (the value after the last existing program) to add a new program
Press the SEL/OPT button to show an options menu, turn the VAL/↔ knob to select an option and press the SEL/OPT button or the YES button to execute (or press the NO button to leave the options menu)
Press the DEL button to delete the active program
Menu options:
- save: save the active program (only if there are unsaved changed) – shows a pop-up to ask for confirmation and another pop-up to ask if you want to replace the active program (select ‘yes’ to save changes to the active program or select ‘no’ to save the changes to a new program directly after the active program)
- rename: show a text edit pop-up to rename the active program
- move backward: move the active program one place backward (if not the first program)
- move forward: move the active program one place forward (if not the last program)
- move to…: move the active program to a specific position – shows a pop-up to select the position (turn the VAL/↔ knob to select a number and press the SEL/OPT button or the YES button to confirm or the NO button to cancel)

input device / input preset

Select the input device and input preset to to map one or more output presets to

Tip

If MIDI learn is turned on, input device and input preset can be set to an already mapped device/preset by selecting the respective block and playing the trigger/note on your input device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

output device 1 to 4 / output preset 1 to 4

Select up to 4 output device/preset combinations that will be triggered when the router receives the selected input trigger
Multiple output devices can be combined

Important

Output device 1 to 4 and output preset 1 to 4 are the output mapping for the above selected input preset. So, to map an input preset to an output preset, first select the input device and input preset, then assign the output devices and output presets. This is indicated by the orange bar between input device/preset and output devices/presets.

PRG 2/5 – Program: Mapping Note

program

Select the active program
See program in PRG 1/5 – Program: Mapping for more details

input device / input preset

Select the input device and input preset to to map one or more output presets to

Tip

If MIDI learn is turned on, input device and input preset can be set to an already mapped device/preset by selecting the respective block and playing the trigger/note on your input device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

device: trigger 1 to 4 - note

Optionally set a note to be sent out to the preset, overwriting any preset or trigger level note settings
Set to ‘___’ to use the preset or trigger’s default note
Preset note overrides trigger note, program note overrides both

Tip

If a device doesn’t respond to the notes your assigned, try one octave lower or one octave higher. There is no official MIDI standard for octave numbers. Cybo-Drummer follows the Scientific Pitch Notation standard, which defines the middle C as C4, so in Cybo-Drummer MIDI note 60 is C4, but some manufacturers define MIDI note as C3 and some as C5.

Tip

If MIDI learn is turned on, note can be set by paying a note from a device connected to the set MIDI learn port.

PRG 3/5 – Program: Mapping Note Off

program

Select the active program
See program in PRG 1/5 – Program: Mapping for more details

input device / input preset

Select the input device and input preset to to map one or more output presets to

Tip

If MIDI learn is turned on, input device and input preset can be set to an already mapped device/preset by selecting the respective block and playing the trigger/note on your input device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

device: trigger 1 to 4 - note off

Optionally set whether and when to send note off messages (overwriting trigger-level note off settings):
- ____: use trigger’s default setting
- off: disable sending note off messages (default)
- pulse: send a note off message immediately after sending a note on message
- toggle: send a note off message if triggered again (first trigger received sends a note on message, second trigger a note off message)
- 80 ms – 1000 ms: send a note off message with a delay of 80 to 1000 milliseconds

Note

The MIDI specification prescribes to always send note off messages, however most drum computers ignore them, so it is more efficiently not to send them. Turn on if you experience problems or for example if you’re triggering a synth pad instead of a percussive sound.

PRG 4/5 – Program: Program Change

p1 to p6

Optionally set a program change value (1 to 128) which will be sent to a device assigned to a particular port
Select ‘___’ to not send a program change message
Program change messages are sent on router program change (after sending bank select, if assigned)

Note

Program change data is stored by device, so if a device is assigned to a different port, it will remain linked to that device, not the port.

PRG 5/5 – Program: Bank Select

p1 to p6 msb / lsb

Optionally set a bank select value (1 to 16,384) which will be sent to a device assigned to a particular port
Bank select uses two MIDI CC messages (MSB on CC 0 and LSB on CC 32, both allowing values 0 to 127) to allow more than 128 values: a ‘most significant byte’ (MSB) or coarse select and a ‘least significant byte’ (LSB) or fine select
Select ‘___’ to not send a bank select message – if LSB is set to a value and MSB is not, only LSB is sent (and vice versa)
Bank select messages are sent on router program change (before sending program change, if assigned)

Note

Bank select data is stored by device, so if a device is assigned to a different port, it will remain linked to that device, not the port.

Tip

Cybo-Drummer uses raw 0 to 127 MSB and LSB values for bank select, because MIDI devices implement bank select in many different ways, including in cases using only one of the two MIDI CC messages. Refer to your device’s manual and MIDI specifications for details on how to set bank select (and if it is used). If bank select is used to set a single number in the range 0 to 16,383 or 1 to 16,384, that number would typically be calculated as MSB × 128 + LSB or MSB × 128 + LSB + 1.

IN (Input)

Use the input page to review or edit input port assignments, input device setting, input trigger settings and input preset settings.

IN 1/3 – Input Ports

p1 to p6 device

Assign input devices to each of the 6 MIDI in ports

Note

If you assign a device which is already assigned to a different port, that assignment will not be stored until you deassign it from the other port.

Caution

Cybo-Drummer does require an input channel to be specified to work.

p1 to p6 channel

Set the channel (1 to 16) on which to receive MIDI data from the selected input device

Tip

If MIDI learn is turned on, channel can be set sending anything from that channel from a device connected to the set MIDI learn port.

IN 2/3 – Input Devices/Triggers

input device

Select the input device to assign triggers to or edit triggers assigned to it
Select ‘[add new]’ (the value after the last existing device) to add a new device
Press the SEL/OPT button to show a text edit pop-up to rename the device
Press the DEL button to delete the device

Tip

If MIDI learn is turned on, input device can be set to an already mapped device by playing a trigger/note on your input device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

input trigger

Select the input trigger (of the selected input device) you want to set up or edit
Select ‘[add new]’ (the value after the last existing trigger) to add a new trigger
Press the SEL/OPT button to show a text edit pop-up to rename the trigger
Press the DEL button to delete the trigger

note

Select the note to which the trigger responds

Tip

If a device doesn’t respond to the notes your assigned, try one octave lower or one octave higher. There is no official MIDI standard for octave numbers. Cybo-Drummer follows the Scientific Pitch Notation standard, which defines the middle C as C4, so in Cybo-Drummer MIDI note 60 is C4, but some manufacturers define MIDI note as C3 and some as C5.

pedal cc

Optionally set a CC number (1 to 128) on which the trigger can be made dependent
Many electronic drum kits send the openness of the hi-hat foot pedal using CC 5, which needs to be used to distinguish between open and closed hi-hat triggers
Set pedal CC to ‘__’ if not relevant for the selected trigger

Important

Note and pedal CC relate to the above selected input trigger. This is indicated by the orange bar between input device/trigger and note.

Tip

If MIDI learn is turned on, note and pedal CC can be set by paying a note or sending CC messages from a device connected to the set MIDI learn port.

IN 3/3 – Input Presets

input device

Select the input device for which you want to add or edit an input trigger

input preset

Select the input preset you want to set up or edit
Select ‘[add new]’ (the value after the last existing preset) to add a new preset
Press the SEL/OPT button to show a text edit pop-up to rename the preset
Press the DEL button to delete the preset

Tip

If MIDI learn is turned on, input device and input preset can be set to an already mapped device/preset by selecting the respective block and playing the trigger/note on your input device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

pedal cc min / pedal cc max

Optionally set a minimum and maximum pedal CC value (0 to 127) between which the preset will be triggered
Many electronic drum kits send the openness of the hi-hat foot pedal using CC 5, which needs to be used to distinguish between open and closed hi-hat triggers
Set pedal CC min/max to ‘__’ if not relevant for the selected trigger (that sets the minimum to 0 and/or the maximum to 127)

Tip

If MIDI learn is turned on, pedal CC min/max can be set by sending CC messages from a device connected to the set MIDI learn port.

trigger 1 to 6

Select up to 6 input triggers (belonging to the selected input device) which will trigger the selected input preset

Important

Pedal CC min/max and input trigger 1 to 6 are the input trigger mapping for the above selected input preset. So, to map a trigger to a preset, first select the input device and input preset, then assign the CC range and triggers. This is indicated by the orange bar between input device/preset and pedal CC min/max.

OUT (Output)

Use the output page to review or edit output port assignments, output device setting, output trigger settings and output preset settings

Tip

Output channel can be set at device level (OUT 2/4) or at trigger level (OUT 3/4). Set the device-level channel setting if all a device’s triggers use the same channel (typically assigned to different notes on the same channel). Set the trigger-level channel setting if each trigger uses a different midi channel. Trigger-level channel overrides device-level channel. If neither device-level, nor trigger-level channel is set, triggers are sent to channel 10. The channel number set at device-level is used to send control data (program change, bank select).

Tip

Output note values can be set at trigger level (OUT 3/4) and at preset level (OUT 4/4). The trigger-level setting is the default for each preset which maps to that trigger, while if a preset-level note is set, that overrules the note setting for that particular preset. This can be used to play tonally (for those drum computers or other MIDI instruments which support that), for example by assigning the same trigger to multiple toms on the input device, but set different notes to tune them differently. If neither trigger-level nor preset-level note is set, note number 60 (C4, middle C) is used. Output note values can be overwritten in a program definitions.

OUT 1/4 – Output Ports

p1 to p6 device

Assign output devices to each of the 6 MIDI out ports

Note

If you assign a device which is already assigned to a different port, that assignment will not be stored until you deassign it from the other port.

OUT 2/4 – Output Devices

output device

Select the output device to assign triggers to or edit triggers assigned to it
Select ‘[add new]’ (the value after the last existing device) to add a new device
Press the SEL/OPT button to show a text edit pop-up to rename the device
Press the DEL button to delete the device

Tip

If MIDI learn is turned on, output device can be set to an already mapped device by playing the trigger/note on your input device that is mapped to that output device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

channel

Optionally set the channel (1 to 16) on which to send MIDI data to the selected output device
Set the channel for devices which receive all triggers on the same channel
Set the channel to ‘__’ for devices which receive different triggers on different channels
This is the channel at which control data (program change, bank select) is sent (if not specified it will be sent to channel 10)

Tip

If MIDI learn is turned on, channel can be set sending anything from that channel from a device connected to the set MIDI learn port.

0 velocity as note off

Set to ‘on’ to send note on messages with velocity 0 instead of note off messages or ‘off’ to force the use of note off messages (default: on)

Note

0 Velocity as note off requires less MIDI data if combined with running status. To be fully compliant to the MIDI specification a device should recognizing note on messages with 0 velocity as note off, so by far most devices do support this – only turn it off if you experience problems.

running status

Set to ‘on’ enable running status or ‘off’ to disable it (default: on)

Note

Running status is a way to maximize MIDI data efficiency by leaving out the status byte if consecutive MIDI messages share the same status byte. This leads to even more efficiency if combined with sending note on messages with 0 velocity instead of note off messages. To be fully compliant to the MIDI specification a device should recognize running status, so by far most devices do support this – only turn it off if you experience problems.

Important

Channel and note off settings and running status settings relate to the above selected output device. This is indicated by the orange bar between output device and channel.

OUT 3/4 – Output Triggers

output device

Select the output device for which you want to add or edit an output trigger

Tip

If MIDI learn is turned on, output device can be set to an already mapped device by playing the trigger/note on your input device that is mapped to that output device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

output trigger

Select the output trigger you want to set up or edit
Select ‘[add new]’ (the value after the last existing trigger) to add a new trigger
Press the SEL/OPT button to show a text edit pop-up to rename the trigger
Press the DEL button to delete the trigger

channel

Optionally set the channel (1 to 16) on which to send MIDI data to the selected output device
Set the channel for devices which receive different triggers on different channels
Set the channel to ‘__’ for devices which receive all triggers on the same channel

Note

Trigger channel overrides device channel

Tip

If MIDI learn is turned on, channel can be set sending anything from that channel from a device connected to the set MIDI learn port.

note

Optionally set the note to be sent out by the trigger
Set to ‘___’ to use the trigger-level default note
Preset note overrides trigger note, program note overrides both

Tip

If a device doesn’t respond to the notes your assigned, try one octave lower or one octave higher. There is no official MIDI standard for octave numbers. Cybo-Drummer follows the Scientific Pitch Notation standard, which defines the middle C as C4, so in Cybo-Drummer MIDI note 60 is C4, but some manufacturers define MIDI note as C3 and some as C5.

Tip

If MIDI learn is turned on, note can be set by paying a note from a device connected to the set MIDI learn port.

note off

Set whether and when to send note off messages:
- off: disable sending note off messages (default)
- pulse: send a note off message immediately after sending a note on message
- toggle: send a note off message if triggered again (first trigger received sends a note on message, second trigger a note off message)
- 80 ms – 1000 ms: send a note off message with a delay of 80 to 1000 milliseconds

Note

The MIDI specification prescribes to always send note off messages, however most drum computers ignore them, so it is more efficiently not to send them. Turn on if you experience problems or for example if you’re triggering a synth pad instead of a percussive sound.

vel threshold

Set a velocity level (0 to 127) under which received triggers are filtered out

Tip

Velocity threshold can be used to avoid loud double triggers on a drum computer with just one or two velocity levels when (accidentally) playing soft ghost notes.

Note

The velocity threshold is independent of the velocity curve setting: it cuts it off without scaling.

velocity curve

Adjust the velocity dynamics in three increasingly positive steps (‘positive 1’, ‘positive 2’, ‘positive 3’) and three increasingly negative steps (‘negative 1’, ‘negative 2’, ‘negative 3’) or select ‘linear’ (the default) not to change the velocity (velocity out level = velocity in level)
Positive curves make the output velocity louder (like a compressor), negative curves make it weaker

Tip

For drum computers with just two velocity levels, you can adjust the threshold between the first and second level by adjusting the curve: a positive curve makes the second level come in earlier (at a lower input velocity), a negative curve makes it come in later (at a higher input velocity).

Caution

MIDI velocity only has a resolution of 127 steps (1 to 127 – 0 is note off). Adjusting the velocity curve significantly reduces that resolution:

positive 1 / negative 1: from 127 to 95 steps
positive 2 / negative 2: from 127 to 64 steps
positive 3 / negative 3: from 127 to 32 steps

min velocity / max velocity

Set a minimum or maximum velocity to adjust the range of velocity values set out to the output trigger
Minimum velocity sets the lowest value sent out (at the minimum input velocity of 1)
Maximum velocity sets the highest value sent out (at the maximum input velocity of 127)

Note

Minimum and maximum velocity are linked to the velocity curve setting: the velocity curve is scaled to the output range set by minimum and maximum velocity.

Caution

MIDI velocity only has a resolution of 127 steps (1 to 127 – 0 is note off). Adjusting the velocity curve significantly reduces that resolution and adjusting minimum and/or maximum velocity reduces it even further.

Important

Channel, note, note off settings and velocity dynamics settings cc relate to the above selected output trigger. This is indicated by the orange bar between output device/trigger and channel.

OUT 4/4 – Output Presets

output device

Select the output device for which you want to add or edit an output preset

Tip

If MIDI learn is turned on, output device can be set to an already mapped device by playing the trigger/note on your input device that is mapped to that output device (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

output preset

Select the output preset you want to set up or edit
Select ‘[add new]’ (the value after the last existing preset) to add a new preset
Press the SEL/OPT button to show a text edit pop-up to rename the preset
Press the DEL button to delete the preset

Tip

If MIDI learn is turned on, output preset can be set to an already mapped preset by playing the trigger/note on your input device that is mapped to the output preset (please note that this is an exception where MIDI learn is not listening to the set MIDI learn port).

trigger 1 to 6

Select up to 6 output triggers (belonging to the selected output device) which will be triggered by the selected output preset

note (1 to 6)

Optionally set a note to be sent out to the preset
Set to ‘___’ to use the preset-level default note
Preset note overrides trigger note, program note overrides both

Tip

If a device doesn’t respond to the notes your assigned, try one octave lower or one octave higher. There is no official MIDI standard for octave numbers. Cybo-Drummer follows the Scientific Pitch Notation standard, which defines the middle C as C4, so in Cybo-Drummer MIDI note 60 is C4, but some manufacturers define MIDI note as C3 and some as C5.

Tip

If MIDI learn is turned on, note can be set by paying a note from a device connected to the set MIDI learn port.

Important

Output trigger 1 to 6 and note (1 to 6) are the output trigger mapping for the above selected output preset. So, to map a trigger to a preset, first select the output device and output preset, then assign the triggers. This is indicated by the orange bar between output device/preset and trigger 1 / note.

MON (Monitor)

Use the monitor page to monitor the router, MIDI data coming in or MIDI data going out.

MON 1/3 – Monitor Routing

Shows what is going on in the router
Display format: ‘Input Device Input Preset > Output Device Output Preset’ (for example: ‘2Box Kick > Drumbrute Kick 1’)

Note

If an input preset triggers more than one output presets the router will show as many lines as output presets are triggers.

MON 2/3 – Monitor MIDI In

Shows the MIDI data coming in from any of the MIDI input ports
Display format: ‘P0 C00 MessageName data [HH HH HH]’, where
- P0 is the input port (P1 to P6)
- C00 is the input channel (C 1 to C16) – not shown for system common messages
- MessageData is the name of the MIDI message (for example ‘NoteOn’)
- data is one or two data values (for example for note on or note off: note and velocity)
- [HH HH HH] is the raw MIDI message in hexadecimal format

Note

SysEx (system exclusive) data is filtered out by the router and won’t show, MIDI clock data and active sensing are filtered out by the monitor and won’t show either.

MON 3/3 – Monitor MIDI Out

Shows the MIDI data sent out to any of the MIDI input ports
Display format: ‘P0 C00 MessageName data [HH HH HH]’, where
- P0 is the output port (P1 to P6)
- C00 is the output channel (C 1 to C16) – not shown for system common messages
- MessageData is the name of the MIDI message (for example ‘NoteOn’)
- data is one or two data values (for example for note on or note off: note and velocity)
- [HH HH HH] is the raw MIDI message in hexadecimal format

Note

MIDI clock data and active sensing are filtered out by the monitor and won’t show.

SET (Settings)

Use the settings page to adjust global settings, to backup or recover data or to find the firmware version number.

SET 1/2 – Settings: MIDI Thru

midi thru

Set to ‘on’ to enable MIDI thru from the set input port/channel to the set output port/channel or ‘off’ to disable MIDI thru

Caution

MIDI thru needs input port, input channel, output port and output channel to be specified to work.

Note

SysEx (system exclusive) data is filtered out by the router and will not be sent to the MIDI thru output port.

input port / input channel

Set from which input port (1 to 6) and channel (1 to 16) to receive MIDI data to be sent to the MIDI thru output port

output port / output channel

Set to which output port (1 to 6) and channel (1 to 16) to send MIDI data received from the MIDI thru input port

SET 2/2 – Settings: Other

midi learn

Set to ‘on’ to enable MIDI learn or to ‘off’ to disable it

Caution

MIDI learn needs midi learn port to be specified to work.

Tip

Connect the MIDI out of a drum computer to MIDI learn port and press the trigger button on it for each sound to easily assign the drum triggers.

midi learn port

Set from which input port (1 to 6) to receive MIDI data to be used for MIDI learn

default output velocity

Set the default velocity used when pressing the TRIGGER button

store back-up

Store all programs, device/trigger/preset definitions and settings to back-up files
Device/trigger/preset definitions and settings from /data_files/data.json are copied to /data_files/back_up.json and program files from the /data_files/programs/ folder are copied to /data_files/programs_bak/

restore back-up

Restore all programs, device/trigger/preset definitions and settings from previously stored back-up files (if any)

factory reset

Restore all programs, device/trigger/preset definitions and settings to initial values
Initial values consist of default settings and empty lists of programs, devices, triggers and presets

about

Show what version of Cybo-Drummer you’re using

Text edit pop-up

When renaming a program, device, trigger or setting a text edit pop-up is shown. It shows the text and a selection of characters plus a space bar.

Turn the NAV/↕ knob to change navigate by row and the VAL/↔ knob to navigate by column and press the SEL/OPT button to add a character.

Press the DEL button to remove the last character (backspace).

Press the YES button to confirm the changes or the NO button to cancel renaming.

Example Presets

Since Cybo-Drummer doesn’t make any sound on its own, but merely routes signals from one device to another, it isn’t possible to make meaningful factory presets. The presets shared in the example presets folder are based on my personal set-up, but can be useful as examples. Currently they reflect a baseline for equipment I own, but that will probably evolve over time.

Tip

To upload the example presets to Cybo-Drummer, follow the same instructions as given for restoring a back-up when uploading firmware:

If you haven’t before: Install Python – follow the instructions provided here and make sure to select ‘Add Python 3.x to PATH’
If you haven’t before: Download the source code of MicroPython release v1.24.0. (typically the zip version) and unzip it somewhere on your PC
In File Explorer go to the micropython-1.24.0\tools\mpremote folder (in the location where you unzipped MicroPython)
Right click somewhere in the folder (not on a file) and from the context menu select ‘Open in Terminal’
If you do it for the first time: type the following to install required Python modules:
```
pip install pyserial
pip instal importlib_metadata
```
Copy the data_files folder from the example presets folder to the micropython-1.24.0\tools\mpremote folder
On your PC type py mpremote.py fs cp -r data_files/ : without pressing ENTER (so not executing it yet)
While you keep Cybo-Drummer’s TRIGGER button pressed:
- Press RESET button on Cybo-Drummer
- Press ENTER on your PC to start downloading (backing up) or uploading (restoring)

Below I share some details on the different devices in the example presets, including what I learned so far about setting them up for Cybo-Drummer.

Input Device: 2Box

My drum kit is a Fame Hybrid Pro, which is produced by 2Box and which is in fact a derivative of 2Box’ DrumIt series (it uses the same firmware). The default 2Box input triggers are based on 2Box’ default MIDI mapping, with one addition specific to the Fame module: 2Box calls numbers the three cymbals 1, 2 and 3, but which of those are the ride, 1^st crash and 2^nd crash seems to be different depending on which type of module.

Note

By default 2Box modules use MIDI CC 4 to send the position of the hi-hat foot pedal (default setting: 0 = fully open, 127 = fully closed). The hi-hat sends the same MIDI note when open or closed, so the CC 4 value needs to be checked to distinguish between both.

Output Device: Drumbrute

This device is set up for the factory settings of the Arturia Drumbrute, but since the Drumbrute can’t store presets, that only means the default MIDI channel and default note mapping.

Note

The Arturia Drumbrute doesn’t respond to MIDI program change nor bank select messages.

Output Device: Drumlogue

This device is set up for the factory settings of the Korg Drumlogue, with only one adjustment: the MIDI mode is set to multi-channel 7-2 (on the Drumlogue: SHIFT + GLOBAL → 7 → set CH to 7-2), so the Multi Engine can be played tonally. There are 64 Drumlogue presets, linked to the Drumlogue’s 64 factory kits.

Note

The Korg Drumlogue does not respond to MIDI bank select messages, only to program change, but with a twist: MIDI program change value 2 (counting from 1) is kit A1, 3 is kit A2, 18 is B1, etc.

Caution

The Korg Drumlogue has a bug in the latest version of the firmware (version 1.2.0 – I haven’t tested earlier versions): it doesn’t respond to MIDI program change values 16, 32, 48, 64, etc. (counting from 0), which should select the Drumlogue’s kits A16, B16, C16, D16, etc. (weirdly the Drumlogue starts program change values from 1, not 0). This means that the last position of each of the Drumlogue’s banks is not usable if it needs to be selectable by program change. Hopefully this gets fixed if Korg ever releases another update for the Drumlogue…

Output Device: LXR-02

This device is set up for the first factory project of the Sonic Portions × Erica Synths LXR-02 (HrtlKits). It assumes the global MIDI channel to be set to the default 1, which the LXR-02 calls 0 (on the LXR-02: SHIFT + CONFIG → set CH to 0) and the LXR-02 is set to receive program change, control change and note messages (on the LXR-02: SHIFT + CONFIG → turn DATA knob to scroll to second page → set MRX to ‘all’ or ‘PCN’).

Note

The Sonic Portions × Erica Synths LXR-02 responds both to program change and bank select messages: program change messages change patterns, bank select messages (not mentioned in the user manual: MSB only) change kits. Kits are saved per project and it isn’t possible to change the project via MIDI.

The LXR-02’s manual description of the MIDI implementation and what is saved where (kits, patterns, projects) is rather incomplete. It doesn’t indicate, for example, where output routing and FX settings are stored. Searching the internet provides some hints based on other people’s experience it’s stored with kits, but I haven’t yet tested it myself.

Caution

Make sure not to assign one of the LXR-02’s voices to same MIDI channel which is assigned to the LXR-02’s global channel, because triggering that channel will trigger the selected voice on the LXR-02.

Tip

Best is to prepare a special project to use LXR-02 effectively with Cybo-Drummer:

Initiate a new project: press LOAD + PROJECT → select an EMPTY project → press DATA knob
Set kit change mode to ‘off’ to separate kits from patterns: press SHIFT + CONFIG → turn DATA knob to scroll to third page → set KCM to ‘off’
In pattern 1 (the default pattern after initiating a new project), assign voices to MIDI channels 2 to 8 (channel 0 is used as global channel, so triggering that channel will trigger the selected voice on the LXR-02) and set each voice to respond any note (allowing to tune it from Cybo-Drummer or to play it tonally):
- Press VOICE → press MIX → turn DATA knob to scroll to second page
- Press DRUM1 button (below sliders) → set CH to 2 and set NTE to ‘any’
- Press DRUM2 button (below sliders) → set CH to 3 and set NTE to ‘any’
- Press DRUM3 button (below sliders) → set CH to 4 and set NTE to ‘any’
- Press SNARE button (below sliders) → set CH to 5 and set NTE to ‘any’
- Press CLP/CYM button (below sliders) → set CH to 6 and set NTE to ‘any’
- Press CL HH button (below sliders) → set CH to 7 and set NTE to ‘any’
- Press OP HH button (below sliders) → set CH to 8 and set NTE to ‘any’
Save project:
- Press SAVE + PROJECT → press DATA knob
- Turn DATA knob to select ‘Y’ → press DATA knob
- Change name: Turn DATA knob to select character to change → press DATA knob → turn DATA knob to select character → press DATA knob to confirm; → finish editing by selecting ‘ok’ (turn DATA knob clockwise until it is selected) and pressing DATA knob
Turn off the LXR-02, take out the SD card and use a PC to copy the kits (files with .SND extension) you’d like to use into the newly created project folder (called PROJ##, where ## is the project number) and rename them so they start with ‘01-’ to ‘63-’
Put the SD card back into the LXR-02 and load the project: press LOAD + PROJECT → select the project → press DATA knob

Output Device: Volca Drum

This device is set up for a Korg Volca Drum in default split channel mode (in which parts 1 to 6 are assigned to MIDI channels 1 to 6 respectively). There are 16 Volca Drum programs, linked to program 1 to 16 of the Volca Drum.

Note

The Volca drum does not respond to MIDI bank select messages, only to program change. Program changes messages 1 to 16 (counting from 1) select Volca Drum programs 1 to 16, each of which has a sequence and a kit assigned, so to make best use of the Volca Drum with Cybo-Drummer, assign each kit to a separate program.

Why in MicroPython?

A MIDI router/mapper is a time-sensitive application, so why not using the programming language which leads to the fastest possible code (that would be C++ on a Raspberry Pi Pico)? Well… I do am aware that MicroPython is much slower, but I decided to use it anyway, because besides solving my challenge to connect my electronic drum kit to my drum computers, I had a second goal: finally learning how to use Python. You see, I’ve used several programming languages over time (starting with BASIC when I was a child, then Turbo Pascal as a teenager in the 90s, later a bit or C/C++ at university, some JavaScript, a lot of VBA and more recently some Arduino code. But now, for my job, I’m managing analysts who are using Python as their go-to language, so I decided it was time to finally master that language as well. This project was a great learning journey!

I spent a lot of time optimizing the code (for speed and memory usage) and it turns out MicroPython on a Raspberry Pi Pico is fast enough after all. Keep in mind MIDI is a 40+ year old protocol, so it is pretty slow by today’s standards – enough time between two MIDI bytes to run a bit of Python code.

To keep latency to a minimum the second core is dedicated to MIDI handling, while the primary core takes care of the graphic user interface and button and rotary encoder input. In that way the second core runs a light loop doing only time-sensitive MIDI routing, while the primary core does all the heavy stuff.

Known Issues

Add program doesn’t check if maximum number of programs (255) is reached
Add device doesn’t check if maximum number of devices (4,096) is reached
Add preset doesn’t check if maximum number of presets (4,096) is reached
Text input doesn’t limit the length of a program/device/trigger/preset name
There is currently no easy way to download and upload user settings (including user-defined programs) when updating the firmware for users who are not accustomed to using Python
Program change and bank select assume the output device interprets value 0 as 1, but that’s not always the case (resulting in the value on Cybo-Drummer’s screen to be 1 off compared to what the output device shows – to solve this a device-level setting needs to be added to set the device’s behaviour

Ideas for Features and Improvements to be Added

Licencing

This project is free hardware/software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This project is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

See LICENSE for the full license text.

This font may be freely distributed and is free for all non-commercial uses. This font is e-mailware; that is, if you like it, please e-mail the author at:

iconian@aol.com

The font used in the graphic user interface is 6x10, from the X11 Linux Window System, copyright X.Org Foundation, published with the following copyright statement:

Public domain terminal emulator font. Share and enjoy.

The available memory also limits the number of programs, devices presets and triggers ↩
Except SysEx ↩
Use the Raspberry Pi Pico and solder headers onto it yourself or the Pico H, which comes with pre-soldered headers; the pre-compiled Cybo-Drummer firmware does not support the Pico W, Pico WH nor Pico 2 (I will add support for the Pico 2 at a later stage) ↩

Name		Name	Last commit message	Last commit date
Latest commit History 193 Commits
example presets/data_files		example presets/data_files
gerber files		gerber files
images		images
logos		logos
schematics		schematics
screenshots		screenshots
src		src
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md

License

HLammers/cybo-drummer

Folders and files

Latest commit

History

Repository files navigation

Cybo-Drummer

Introduction

Overview

Features

Hardware

Mapping

Other Features

Building Instructions

Hardware

BOM (Bill of Materials)

First Board: Raspberry Pi Pico Multi MIDI Router

Second Board

Build Instructions

First Board: Raspberry Pi Pico Multi MIDI Router

Second Board

Software

Uploading Firmware

Running From Source

Building Firmware From Source

How to Use Cybo-Drummer?

Overview

Pages and sub-pages

Trigger presets

Confirmation Pop-Ups

Description of All Pages and Sub-Pages

PRG (Program)

PRG 1/5 – Program: Mapping

program

input device / input preset

output device 1 to 4 / output preset 1 to 4

PRG 2/5 – Program: Mapping Note

program

input device / input preset

device: trigger 1 to 4 - note

PRG 3/5 – Program: Mapping Note Off

program

input device / input preset

device: trigger 1 to 4 - note off

PRG 4/5 – Program: Program Change

p1 to p6

PRG 5/5 – Program: Bank Select

p1 to p6 msb / lsb

IN (Input)

IN 1/3 – Input Ports

p1 to p6 device

p1 to p6 channel

IN 2/3 – Input Devices/Triggers

input device

input trigger

note

pedal cc

IN 3/3 – Input Presets

input device

input preset

pedal cc min / pedal cc max

trigger 1 to 6

OUT (Output)

OUT 1/4 – Output Ports

p1 to p6 device

OUT 2/4 – Output Devices

output device

channel

0 velocity as note off

running status

OUT 3/4 – Output Triggers

output device

output trigger

channel

note

note off

vel threshold

velocity curve

min velocity / max velocity

OUT 4/4 – Output Presets