v0.3.6: renamed to Machinemodule

The project is now Machinemodule (was Machinedrum Module); the taps are Machinemodule Tap and Machinemodule Tap FX. Plugin ids and the repo name are unchanged, so it replaces the old entries on install.

The advanced, optional MPC OS patch (release/build_release.sh ... -p) now matches the new plugin name, so rebuild it and uninstall any older patch first. Tested on the Force, MPC OS 3.9.1.2.

v0.3.5: 16 red drum pads (advanced MPC OS patch)

Improvement to the advanced, optional MPC OS patch (release/build_release.sh ... -p): Machinedrum Module now gets the drum-pad layout with all 16 pads lit red (close to the Machinedrum's LCD) and playing, instead of 8 lit pads.

• The patch colours all 16 pads of any plugin drum program, so Akai's DrumSynth Multi also shows 16 red pads (1-8 sound). Telling plugins apart at colour time isn't reachable from the colour code; see the handoff.
• Unchanged: it modifies the factory /usr/bin/MPC, MPC OS 3.9.1.2 only (checked by md5, refuses anything else), backs up to the SD card, and a firmware update removes it. uninstall.sh undoes it.
• The plugin itself is identical to 0.3.4.

Tested on an Akai Force (MPC OS 3.9.1.2): 16 red pads lit and playing; other plugins unchanged; uninstall restores the stock binary.

No downloadable build: it needs your own Machinedrum firmware, so you build the installer yourself (see the README).

v0.3.4: 16 drum pads (advanced MPC OS patch), saved state

• Saved state: a project or preset now stores and restores the whole Machinedrum Module instance (machines, parameters, kit, bank).
• Notes 0-15 also play tracks 1-16 (36-51 still do), for MPC's drum-pad layout.
• Advanced, optional: 16 drum pads. release/build_release.sh ... -p stages dist/mpc-os-patch/, an on-device patch of the factory MPC OS that gives Machinedrum Module the drum-pad layout with all 16 pads lit and playing. It modifies /usr/bin/MPC, works on MPC OS 3.9.1.2 only (it checks the exact file and refuses anything else), backs up the original to the SD card, and a firmware update removes it. uninstall.sh undoes it. Side effect: Akai's DrumSynth Multi also shows 16 lit pads (1-8 sound). Read the README section before using it. The patch file holds only our own bytes, never Akai's.

Tested on an Akai Force (MPC OS 3.9.1.2): full build passes the bit-exact gate and catalog check; with the patch, 16 pads lit and play, other plugins unchanged; uninstall restores the stock md5.

No downloadable build: it needs your own Machinedrum firmware, so you build the installer yourself (see the README).

v0.3.3: flash image optional

The flash image is now optional. release/build_release.sh "<OS .syx>" builds with the OS file alone: every machine except the ROM sample machines plays (ROM machine tracks stay silent) and there are no factory kits. Give the script the flash image too for those. A full build sounds the same as 0.3.2. Tested on an Akai Force (MPC OS 3.9.1): flash-less build passes the bit-exact gate and catalog check, non-ROM machines play, ROM tracks stay silent.

No downloadable build: it needs your own Machinedrum firmware, so you build the installer yourself (see the README).

v0.3.2: installers for the taps

The two tap plugins now have their own installer zips. release/build_release.sh makes three: Machinedrum-Module-, Machinedrum-Tap- and Machinedrum-Tap-FX-<version>-mpc-armv7.zip (each passes the catalog check), and -d <device-ip> installs all three (MPC restarts once per zip). Each plugin lives in its own folder in /sdcard/Synths; a tap finds the Module wherever it is installed. Installing replaces an earlier hand-copied setup in /sdcard/vst.

Tested on an Akai Force, MPC OS 3.9.1. There is no downloadable build: it needs your own Machinedrum firmware, so you build it yourself (see the README).

v0.3.1: less crackle when played live

Much less crackle when you play it live.

• A drum that has died away (below -96 dBFS for 100 ms) now stops using CPU until it is played again. Before, every track you had hit kept costing its full CPU time, so after playing freely the Force stayed overloaded even in silence. A hit after this release sounds the same as a normal retrigger.
• The voices render on three threads instead of two (each about 40% lighter on the Force).
• New instances start at VOICES 6 with ROM machines on. Projects you saved keep their own settings.
• GLOBAL page: VOICES and ROM on the top row, the four randomise toggles below.
• Build: the skin uses Monomodule's art file when you have it (the original toggle icon), otherwise the Machinedrum OS dump as before.

Tested on an Akai Force, MPC OS 3.9.1: VOICES 6-8 with ROM on ran at 2.3-2.9 ms per 2.9 ms block with underruns mostly flat.

There is no downloadable build: it needs your own Machinedrum firmware, so you build it yourself (see the README). The installer zip still ships the Module only; the Tap plugins are copied by hand (see the README).

v0.3.0: Machinedrum Tap and Tap FX

New: Machinedrum Tap and Machinedrum Tap FX. MPC only uses the first stereo pair of a plugin, so these extra plugins read any tracks and the reverb and delay sends from the Machinedrum Module in the same project and put them on their own MPC tracks, submixes or return tracks, where MPC's mixer and effects can process them. Tracks and sends can be mixed on one tap (on/off cells, LCD-style skin). A tapped track leaves only the Module's dry main mix and still feeds its reverb/delay sends. Timing against the main output was measured on a Force (sample-aligned); the Module's output is bit-identical when no tap is in use.

No master effects baked in (by design: the sends go out through the taps for MPC's own effects). A faithful build with the Machinedrum's master section is planned for faster devices.

Tested on an Akai Force, MPC OS 3.9.1.

Not in the installer yet: the installer zip ships the Module only. Build all three plugins with vst/build_so.sh and copy the tap .so files and skins by hand (see the README).

There is no downloadable build: it needs your own Machinedrum firmware, so you build it yourself (see the README).