This page is read from MIDI Instrument Definitions, a Python library used in the author's other projects, in which every number is traced to a document its maker published. Its source is on GitHub.

Erica Synths HexDrums MIDI implementation

The MIDI implementation of the Erica Synths HexDrums: what it answers to.

At a glance

Firmware

Not recorded.

MIDI channel

Any one of 1 to 16.

Voices

Not recorded.

Notes

Each note plays a drum of its own, listed below.

Note range

36 to 45: C2 to A2, counting middle C as C4.

Velocity

Not recorded.

Aftertouch

Not recorded.

Pitch bend

Not recorded.

Program change

Not recorded.

MIDI clock

Sent and received.

Start and stop

Not recorded.

Control change

None.

NRPN

None.

System exclusive

Not recorded.

Drum notes

Each drum plays from the note beside it.

Where these facts come from

Source documents

• HexDrums User Manual, dated 16 February 2026, its user manual, read on 6 October 2026 (the file read).
• Hexdrums - Erica Synths, its download page, read on 6 October 2026.

How they were read

The HexDrums User Manual, 28 sheets, dated 16 February 2026 - and it is the whole of what this instrument's maker publishes in prose. The product page offers three downloads: this, its Japanese translation, and a firmware image.

THE MAP IS TEN LINES AND A SENTENCE, AND BOTH ARE HALFWAY DOWN p. 27. See the comment above the definition for where and why that matters. The ten lines on p. 27 are the note numbers; the sentence is the reason there is nothing else.

WHY control_change: none IS DIFFERENT HERE FROM EVERYWHERE ELSE IT APPEARS. In every other definition in this corpus that says none there, it records an absence somebody established - a chart's crossed boxes, an enumeration that did not mention a control change, a maker's list of what its socket accepts. This one records a decision somebody explains. That is a stronger claim and a different one, and a consumer can act on it with more confidence: not that no controller was found, but that the designer chose the parameters would not be addressable and said so.

THE JAPANESE EDITION IS CITED FOR AN ABSENCE AND IS NOT IN THIS LIBRARY. 28.8 MB for a remark about what a translation does not contain is not worth the library's weight, so its digest and the address that serves it are in the provenance record beside the English manual, and Notes/4626_extract_hexdrums.py fetches it to recheck rather than trusting a note. It is recorded because the obvious reading of it is the wrong one: that edition is four weeks older than the English manual and its p. 27 is headed for the sample upload alone, which points at a section added to the English manual after the translation was made rather than a section dropped from it. See the comment above the definition for what decides that and for why it is still an inference.

HOW ITS DOCUMENTS ARE ADDRESSED, WHICH IS NOT BY A FILE NAME. Erica Synths serves these through a download controller - /service/file/download/product_id/1009/file_id/608/ - and the file name arrives only in a content-disposition header. So the address says nothing about what it serves, the served type is application/octet-stream whatever the file is, and the firmware and the manual are told apart only by what comes back: one is a PDF and one is a UF2 image. erica_synths/perkons_hd_01 found its manual at a direct erp.ericasynths.lv/media/ address instead, so this maker has changed how it publishes between that instrument and this one.

NOT RECORDED: the velocity, which the word for does not appear once in 28 sheets - the manual calls what arrives trigger note messages (manual p. 5), which suggests the note is a trigger and nothing more, and suggesting is not saying. The transport: the manual's START and STOP are panel keys and no MIDI transport message is mentioned anywhere. Program change and system exclusive, likewise unmentioned - and unlike the controllers, not declared absent, so the fields are empty rather than none. The mode, for want of the chart sheet 5 asks for. And the polyphony, which no page gives.