Release notes
Machinedrum Editor + Monomachine Editor 0.5.1
Released 2026-10-11
A release on top of 0.5.0: a CPU meter and an output meter with a master volume, less emulation work, fixes from your reports, and the editors' own plug-in identity.
Screenshots, features and FAQ: https://mdmm.dev · User guide: https://mdmm.dev/guide/
Read this first: insert the editor again in old DAW projects
- The editors have their own plug-in identity now (both editors, macOS, Windows, Linux). Up to 0.5.0 the editors used the same Audio Unit codes and VST3 IDs as the original Gearmulator Machinedrum and Monomachine plug-ins, so a Mac or a DAW could keep only one of the two, and sometimes opened the wrong one (B-048). From 0.5.1 the editors are registered as Future Native Audio plug-ins. You can install the original Gearmulator MD and MM beside the editors; each opens as itself, and the installer leaves the originals alone.
- A DAW project saved with 0.5.0 or earlier does not find the editor. Open the project, insert the Machinedrum Editor or the Monomachine Editor again on its track, once, and save the project. Your machine's memory (patterns, kits, songs, globals) is not in the DAW project and is not lost. The standalone apps are not affected.
New
- A CPU meter in the top bar (both editors, plug-in and standalone, I-018). After the version, a small bar shows how much of each audio block's time the editor uses, smoothed over half a second, with a mark for the worst block of the last 3 seconds. A block over its time shows as a thicker, hatched bar. Hover for the number. A click opens the details: average, worst block, machine speed, the host's sample rate and block size, which speed-ups are on, native or Rosetta, and the speed-up switches, so you can compare them there. The top bar still fits at 1280 px wide.
- An output meter and master volume at the LCD's right end (both editors, plug-in and standalone, I-021). Two thin bars show the left and right output after the volume, each with a peak line, and a clip mark at the top that lights when any output went over 0 dBFS (a click clears it). The volume is the line across both bars: drag it up or down (Shift for fine steps), scroll, or double-click for 0 dB; at the foot it is off. The dB value shows under the LCD while you change it. The volume is saved with the DAW project and in the standalone. It is applied after the emulation, so the machine's sound is not changed. It is not a host-automatable parameter.
- Developer > Speed-ups (faster, same sound) (both editors). The speed-ups switch is now a positive tick: ticked means the speed-ups run (the default). Developer > Speed-ups (each) turns one speed-up off at a time while the others stay on, for testers who want to find which one changes something; each one also has an environment switch (doc/md_mm_performance_diagnostics.md, "Switches for testers"). While the main switch is off, the single switches are grey.
- The native editor menu works (both editors). The menu shown when the page is not up closed without doing anything when you picked an entry. Every entry now does what it says. Every speed-up switch change and every menu pick is a line in the start-up log.
Faster
- Less emulation work (both editors). Four more small bit-exact changes: the DSP link rings and the codec output ring no longer use semaphores (both ends are on one thread), the ColdFire's idle-loop skip is tested right after its branch, a ColdFire slice with no input waiting skips the per-step input tests, and the Machinedrum's NOP-loop skip also tests the instruction target. Host work per audio frame against 0.5.0's code: the Machinedrum about 4 % less, the Monomachine about 7 to 8 % less, stopped and playing. The sound is the same, bit for bit. Each one has its own switch under Developer > Speed-ups (each).
- The macOS profile (PGO) is trained again on this code, so the macOS build uses it for every changed function.
Fixes
- Monomachine: a transpose changed while the pattern plays is heard at once (B-060). A tester on Discord said a transpose took effect only after STOP and PLAY; on the real machine it acts at once. The machine stores a transpose that comes over SysEx, but its sequencer keeps the transposes it took at PLAY. While the pattern plays, the editor now applies the change as the machine's own panel does (the TRANSPOSE screen's TRACK knob), for each track the edit changed, and goes back to the track that was in focus. Stopped, nothing extra happens: PLAY takes the new value. On a real Monomachine over MIDI this is not possible: the edit's note says it is heard from the next start, or press TRANSPOSE on the machine.
- Monomachine: a held key of the transpose keyboard no longer keeps sounding when the window loses focus (B-059). With the mouse button down on a key of the Sequence dock's transpose keyboard, leaving the window left the note on, and with the arpeggiator on the track went on playing. Leaving the window, or a move with no button, now ends the note. A tester on Discord saw the editor "play by itself" when its window was deactivated; we could not reproduce that as told, and this was the one way we found.
- Monomachine: pasting copied steps with nothing selected keeps the rest of the page (B-057). Pasting puts down only the copied steps, from the page's first step, as on the Machinedrum. COPY PAGE then PASTE PAGE still copies the whole page.
- A project with a damaged flash image no longer hangs the emulation (both editors, B-054). A DSP that stops on bad code is now set aside and the rest of the machine runs on, and a host port that nobody reads no longer blocks. When it loads a project, the editor puts the ROM's own bytes back in any flash sector of the operating system that does not match the ROM; the sample area stays as the project holds it. A running firmware never reaches any of this: the sound is the same, bit for bit.
- The start-up card's animation skipped now and then in a test (B-052). This was the test, not the editor: its audio thread ran without pause and kept the message thread waiting. The test now paces its audio as a DAW does. No change in the editor.
Tips
- Both editors open at once in Ableton Live: Live shows only the selected track's plug-in windows while Auto-Hide Plug-In Windows is on, so picking the Machinedrum track hides the Monomachine Editor and the other way round. In Live › Settings › Plug-Ins, turn Multiple Plug-In Windows on and Auto-Hide Plug-In Windows off. The user guide says this too.
Known
- Machinedrum: in a small window the top bar's right end is cut (B-061). In a window smaller than about 1440 x 720 the page is zoomed out, the web view makes small text larger, and the CPU meter, GLOBAL and MKI/MKII can run past the right edge. Make the window larger.
- Machinedrum: a lock on a step without a trig is kept but not played (I-019). OS 1.63 does this on the real machine too; the guide says a Machinedrum lock needs a trig.
- Monomachine GLOBAL: master tune is not on the page yet, and some bytes of the global are still not decoded.
- Machinedrum: a pattern pick during a SysEx import asks about unsaved kit edits you never made (B-045). It goes away when the import finishes.
- Monomachine: a LOOP row in a song written by the editor goes back to row 1 (B-038).
- Drag and drop works on macOS only (I-017). On Windows and Linux, use the buttons.
- The update banner still offers Download (the site), never Update. Installing from inside the app waits for our update signing key (I-005).
For developers
- Plug-in identity is set once in
scripts/mdmm-product.env: AU manufacturerFNAu, subtypesMded(Machinedrum) andMmed(Monomachine), VST3 class IDs from them. The old codes stay in the file for the installer and the tests only.scripts/check_mdmm_plugin_ids.py(ctestmdmmIdentityTest) checks the built AU and VST3 against the file and fails on the old codes. - Journeys reset GLOBAL first (B-058). Before its first journey each editor resets the active global of its sandboxed machine to the factory settings, so a personal or imported global (CHANNEL SPAN 0, another base channel) no longer fails the mute and note journeys. The person's own settings are never written.
MDMM_JOURNEY_CONFIG_MD/_MMstart the sandbox from another settings file. - New journeys:
*-top-cpu-meter,*-dev-speedups,*-lcd-volume,mm-seq-transpose-playing,mm-seq-transpose-key-blur,mm-top-leave-window-stopped,mm-seq-paste-steps-keeps-page. New firmware tests:mmTransposeLiveFirmwareTest,mdDamagedFlashFirmwareTest. - One switch per speed-up:
GEARMULATOR_MDMM_<lever>=0(L1, L11, L2B, L5, L4_NOP, L4_POLL, L4_CYCLE, L4_PORTC, CMPM, and the four new ones LINK_RINGS, UC_IDLE_PROBE, UC_QUIET, NOP_GATE);GEARMULATOR_MDMM_SPEEDUPS=0still turns all off. Measurements: doc/modern-ux/RESEARCH-emulation-cpu.md, "Small wins (0.6)".
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/