FOR CLASSIC DRUM MACHINES

YESTERDAY’S
HARDWARE
TOMORROW’S
FEATURES

Tick96 running on macOS
01 / SCROLL TO PRODUCTS ↓
SELECTED SYSTEMS2026 —
01
MACOS / AVAILABLE NOW

TICK96

The first native 96 PPQ sequence editor and hardware bridge for the Akai MPC2000 and MPC2000XL.

Windows version and Roland W-30 / SP-404SX support: October 2026.

BUY ON GUMROADTICK96 DETAILS
Tick96 native 96 PPQ sequence editor and hardware bridge for Akai MPC2000 and MPC2000XL
02
MACOS / AVAILABLE NOW

TICK24

The first native 24 PPQ sequence editor and hardware bridge for the E-mu SP-12 and SP-1200.

BUY ON GUMROADTICK24 DETAILS
Tick24 native 24 PPQ sequence editor and hardware bridge for E-mu SP-12 and SP-1200
03
IN DEVELOPMENT

HANAMEL
OVERDUB
SYSTEM

A new overdub system for classic drum machine workflows.

DETAILS COMING SOON
HOS / 001
HANAMEL
OVERDUB
SYSTEM
IN DEVELOPMENT
04
AKAI S950 / IN DEVELOPMENT

GRANULAR
OS

A custom operating system exploring granular sample processing on the original Akai S950 hardware.

DETAILS COMING SOON
S950 / GOS
GRANULAR
OS
IN DEVELOPMENT
APPROACH

HOW HANAMEL DEVELOPS

01
PARTICIPATORY DEVELOPMENT
The continued development of existing Hanamel products is shaped through open community participation. Users can propose improvements and new features, bring proposals forward for public voting, and help determine which additions should be explored. Community priorities are then evaluated for technical feasibility before entering development.
OPEN THE PROPOSALS BOARD ↗
02
PRESERVE THE TIMING & SONIC CHARACTER
New functionality must never compromise the timing, feel or sonic character of the original machine. Timing-critical functions are verified through jitter and timing analysis, while audio-critical functions are evaluated against the original hardware.
03
EXTENSION, NOT EMULATION
Hanamel Systems builds no emulations, software recreations or approximations of classic hardware. Every product extends the function of the original instrument, because its sonic character cannot be recreated, only preserved.
STANDARDS

ENGINEERING STANDARDS

01
HARDWARE VALIDATION
Every release is tested on original hardware. Original hardware behavior is treated as the reference baseline, and core functions are exercised repeatedly under normal and edge-case operating conditions.
02
REFERENCE BEHAVIOR & TIMING ANALYSIS
Timing-critical functions are measured against a defined original-hardware reference configuration. MIDI latency, jitter, clock stability and event placement are captured across repeated trials using documented test conditions.

Replacement operating systems and external control systems can introduce timing changes even when their new functionality works as intended. Hanamel therefore treats timing behavior as a measurable release criterion rather than an assumption.
03
REQUIREMENTS TRACEABILITY
Every release requirement is linked to a defined verification method and recorded test result. Changes to requirements, implementation or hardware interfaces are reviewed for their impact on existing behavior and validation coverage. A feature is not considered complete until its specified behavior has been verified on the target hardware.
04
REGRESSION TESTING
Existing functions are re-tested after changes. New features must not introduce timing regressions, corrupt sequence data or interfere with established hardware behavior. Affected verification procedures are repeated whenever validated behavior may have changed.
05
BOUNDARY & FAILURE TESTING
Interfaces and editing operations are tested at documented boundary conditions and under malformed, interrupted and unexpected input. Communication loss, invalid data, maximum and minimum values and interrupted operations are tested to verify predictable behavior and recovery without corruption of user data.
06
DATA INTEGRITY
Projects, sequences and edited events are tested through repeated save, load, transfer and edit cycles. Boundary values, dense sequences and unusual event combinations are included. Validation checks that operations preserve data not explicitly targeted by an edit.
07
STRESS & SOAK TESTING
Systems are tested under dense MIDI traffic, repeated editing and extended continuous operation. Long-duration soak tests are used to identify timing drift, communication failures, event loss and other faults that may only emerge after prolonged use.
08
CONFIGURATION CONTROL
Every release is tied to a uniquely identified software build, source revision, test configuration and supported hardware configuration. Development tools and build dependencies that can affect the released software are versioned or recorded so that validated builds remain reproducible.
09
DEFECT CONTROL
Failures discovered during validation are recorded, reproduced and tracked to resolution. Release-blocking defects must be resolved and the affected verification procedures repeated before a build can be approved for release.
10
RELEASE CANDIDATES
A release candidate is frozen and tested as a complete build before public release. Any change following validation requires the affected tests to be run again. Public releases must correspond to the configuration that completed release validation.
HANAMEL / 001ABOUT HANAMEL SYSTEMS

INDEPENDENT DEVELOPMENT
FOR ORIGINAL HARDWARE

Hanamel Systems is an independent development project creating new ways to integrate classic drum machines and samplers into modern production environments. Our systems bridge original hardware and modern workflows while preserving the timing, sonic character and hands-on experience of the machines themselves.
Developed by Attila David Katona