Release notes
Machinedrum Editor + Monomachine Editor 0.8.0
Released 2026-10-20
The MIDI release. Notes, clock, transport and program change now run through the plug-in the way they do on the machines, and the editor shows what MIDI it takes in and sends out. The audio thread no longer waits for the editor, the Monomachine tester items are done, and stacked LFOs on the Machinedrum no longer miss trigs.
A release on top of 0.7.0. Screenshots, features and FAQ: https://mdmm.dev · User guide: https://mdmm.dev/guide/
New, on both editors
- MIDI Learn is back. Click the Control key in Setup (right of LEARN), press LEARN (L), click a value and turn a knob on your controller both ways: the knob now moves that value, on any track. A button that sends 127 and 0 is learned as the value's highest and lowest. Mappings are control changes only, 128 at most, and are saved with the project. A learned CC wins over the machine's own CC on that channel: the Control page says what it hides (for example "Overrides the machine's CC 21 on channel 1: T1 DEC"), and removing the mapping gives the CC back. In a DAW the moves are recorded as automation. Learn is off while the HW MIDI engine is in use, and the Control page says why. Projects from the early alphas bring their old mappings once.
- MIDI Learn covers every value of the page (B-169). Besides the sound values of the tracks, you can learn what belongs to no track: on the Machinedrum the four master effects (Rhythm Echo, Gate Box, Master EQ, Dynamix), the tempo and the pattern's swing and accent; on the Monomachine the tempo, the master tune, the multi envelope and the pattern's swing. The Machinedrum's LFO page of every track (target, shapes, update mode) is learnable too, and on the Monomachine the pattern and track transpose, the whole arpeggiator, the assign table and the values of the MIDI tracks. A choice such as an LFO shape or an arpeggiator mode is learned over its entries. They have their own FX column on the Control page, and a learned CC moves them as a click on the page does (one undo step per turn).
- MIDI monitor. The log carries a
midi: in … out … dropped …line every 10 seconds while MIDI counts change, and the standalone's AUDIO / MIDI panel has a Monitor row with IN and OUT totals and rates. Hover a number for the types: notes, controllers, program changes, clock, transport, SysEx. - A MIDI loop warning. When a virtual bus (an IAC bus on macOS, a loopMIDI port on Windows, Midi Through on Linux) is on as an input and is also the output, the panel shows a red line and the log carries it. A real port in and out never warns.
- The AUDIO / MIDI panel says why an input stays on NONE (microphone access off, no input channels at this rate, a device setup error, or another program holding the device), and the standalone has the Bluetooth permission key.
- Pattern and Kit. The first two tabs are named Pattern and Kit (they were Sequence and Sound), in the editor, the key view, the tooltips, the guide and the site.
- Follow played track. Engine menu > FOLLOW PLAYED TRACK: a note from a MIDI controller selects the track it plays. Off at first, saved with the project.
- Kit arrows. The KIT field has ‹ and › that step to the previous and next kit.
- Click a note or trig and it stays selected. Double-click removes it, Delete removes the selection. On the Monomachine, up and down change the pitch of one selected note.
- Lock lane. A thicker kit-value line with its value as a number. Drag the line to change the kit value; locks show their numbers at their bars.
- Song rows show their tempo, mutes and transpose on the arrangement cell.
- SysEx import read-back is a choice. The tick Read back and compare is on at first. Off, the import ends after Send and the report says what was sent and that it was not read back.
- The transport menu opens by right-click on the play key (Play or Stop, Pause or Continue, Record, Panic); the small arrow key beside it is gone.
- MKI / MKII plate moved into the engine menu.
- Chain, Pattern and Song stay in step with the machine (B-162, see Fixes).
- The user guide covers MIDI and sync: inputs, the Windows single-client rule, the loop warning, what MIDI out sends, notes and the key map, program change, Tempo INT and EXT, the control change map and host automation, Ableton's "Multiple plug-in windows" and Logic's old
.componentfiles.
New, Monomachine
- Mix meters. The routing graph shows the level of each output pair (A/B, C/D, E/F), with a hold tick and a clip mark.
- A forwarded trig lights blue. A track that plays because another track's trig forwards to it shows a blue lamp on its rail number.
- The DigiPRO D waves have their names (SINE, HSIN, TRI, 2OID … FEMÖ), read from the machine, under their number on the boxes and the morph and wave screens.
- The trig mark of the lock lane says what it is: red fires all three envelopes, green only some or none.
- Pitchless trig is in the step menu (the guide says how, and how on the machine).
- The filter envelope shows the full BOFS and WOFS range, -64 to +63, in a big pane and a small square pane with ATK and DEC dots.
- The LFO preview follows the track's locks. It draws the pattern's whole length and shades the steps where a lock changes the LFO.
- Octave range. Z and X reach -4 to +6 and the Perform keyboard runs from MIDI note 0 to 127.
- Slides in the lock lane are drawn as a ramp between real locks only, above the bars. Shift-drag from a lock to draw a slide to the parameter's next lock (a rubber band); click the line to remove it.
Changed
- Machinedrum: notes from a DAW or a port go to the machine's own MIDI input. The editor used to turn notes 36 to 51 on any channel into TRIG key presses. Now a note plays the track that the Global key map gives it, on the four channels from the base channel, as on the real machine. A change in GLOBAL > Map editor works from a DAW, and host notes no longer write steps when GRID RECORD is on. A note on a channel outside the four base channels plays nothing, so a drum track on channel 10 needs the base channel set so that channel 10 is among the four (B-163).
- Monomachine: deleting a note writes no NOTE OFF (cut and moved selections too). The note before runs on through the gap, as on the machine.
- Machinedrum: the background timing is finer (30 µs instead of 125 µs, the Monomachine's value). Patterns that depended on missed hits may sound slightly different (B-161).
Fixes
- Machinedrum: stacked LFOs no longer miss trigs. Three LFOs on a kick's pitch now sweep on every hit (B-161, from Discord).
- Both: switching between Chain, Pattern and Song no longer leaves the page and the machine in different modes or changes parameters (B-162, from Discord).
- Audio thread: it no longer waits for the editor. The page's commands go through a queue, machine memory is copied in parts, and the machine's facts are a snapshot. The longest wait on the audio thread under load is 0 ms in the real-time gate. This may also help the Windows crackle (B-156): please retest.
- Both: the Song page fits narrow windows (B-165). Its columns stack below 1240 px wide and the page scrolls as a whole; nothing is cut at 1100 x 800.
- Host saves keep the project's own machine state. A save that cannot read the machine at that moment writes the last good state, never an empty machine chunk; machine memory is copied in bounded parts.
- Standalone: choosing Bluetooth MIDI no longer takes the app down on macOS (B-155), and the input list says why it stays on NONE.
- Standalone: noise with Ableton over IAC (B-154) was a feedback loop of the app's MIDI out into its in; the panel now warns about it. An external 24 PPQN clock alone is clean.
- Monomachine: a lock the panel counts is now drawn (B-164). A lock on a step without a trig shows as a ghost bar, a lock of 0 keeps a mark, and the counts say their unit.
- Monomachine: the page no longer says the machine ignores a lock on a step without a trig (B-168). A firmware probe showed it plays it (volume, filter, tune), from that step to the next trig. The ghost bar stays; its tooltip and the guide now say so.
- Monomachine: BOFS and WOFS are signed (-64 to +63, B-148), FM+ frequencies show as the machine shows them (B-149), the DigiPRO waves are numbered D01 to D64 and S01 to S32 (B-150), PCH2 to PCH4 are the machine's list (B-151), and a pitchless trig can be made in the editor (B-152). The D wave names are done too.
- Monomachine: a track kept playing after the host's transport stopped is confirmed fixed through the processor, with All Notes Off on every channel (B-121).
- Emulator: 28 fixes from the upstream DSP emulator (dsp56300), copied one at a time: the JIT, DMA, host port and ESSI. The sound is unchanged (every reference recording equal) and the CPU use is about 1 % lower. The list, and what was left out and why: doc/modern-ux/UPSTREAM.md.
- Linux: the README has the SteamOS line, and a start test in CI runs the tarball on SteamOS 3 (B-153).
- CI: Windows, Linux and macOS run the same MIDI tests (B-044, B-047). The seqlock test no longer counts a start value as a torn read.
Known
- Machinedrum: after a sample is sent to the machine by SDS (Load sample, a dropped file, a rename), live recording records nothing until you restart the editor (B-133). The cause is a bug in the machine's OS 1.63 screen list; the editor keeps the hardware's behaviour. Restart the editor after loading a sample, then live record.
- Monomachine: a song's LOOP row goes back to row 1 (B-038), and a pattern pick during a SysEx import asks about kit edits you never made (B-045).
- Machinedrum: a SysEx import and the empty reset cannot be undone (B-130). Export a backup first.
- Monomachine Sound: the UNISON and SUB screens' stems can look thicker than they should in the standalone (B-132).
- Two reports we could not reproduce: Ableton Live seeming to route one editor's MIDI into the other (B-119), and crackle on Windows when steps are entered during playback (B-156, please retest). If you have steps, please send them: https://mdmm.dev/contact/
Tips
- Both editors open at once in Ableton Live: in Live > Settings > Plug-Ins, turn Multiple Plug-In Windows on and Auto-Hide Plug-In Windows off.
- Logic lists the editor twice or loads an old one: delete
GearmulatorMD.componentandGearmulatorMM.componentfrom/Library/Audio/Plug-Ins/Components, then restart Logic. - On Windows a MIDI port belongs to one program at a time. If Live holds the port, the standalone cannot open it, and the panel says so.
For developers
- MIDI Learn: the mappings are a member of the setup (
MDSK), the audio thread reads a fixed table through a seqlock and pushes learned CCs into a ring that the session drains, and no callback exists. Design indoc/midilearn/DESIGN-learn-0.8.md, threads inTHREADING.md. Global targets (B-169) cross the ring as ids and are applied by the desk as the page's own commands. Tests:deskLearnTest,mdLearnRouterTest(with a ThreadSanitizer stress run),mdLearnFirmwareTest, andEDITFLOW_LEARNin the real-time gate. - Tests for the MIDI path: host notes through the key map, the DAW transport and clock through the processor with a scripted play head, the B-154 loopback, the MIDI monitor, the loop rule, Mix meters, and the stacked-LFO firmware test.
- Monomachine machine-tier journeys still depend on run order (B-160).
Platforms
- macOS 12 or later (Intel and Apple silicon), not signed by Apple yet: the first install needs Open Anyway (on macOS 12 to 14: right-click the installer > Open).
- Windows x64 and Linux x64: not tested by a person yet. Feedback welcome: https://mdmm.dev/contact/