Release notes
Machinedrum Editor + Monomachine Editor 0.4.0
Released 2026-10-10
A release on top of 0.3.5: a lighter emulation, drag and drop on the Mac, the machines' MIDI out, and the fixes from a code review and from your reports.
Screenshots, features and FAQ: https://mdmm.dev · User guide: https://mdmm.dev/guide/
Faster
- The emulation does less work (both editors, B-005, B-028). Four speed-ups in the emulated processor, and the sound is bit for bit the same. Per audio frame the Machinedrum needs about 15 % less work stopped and 16 % playing, the Monomachine 19 % and 21 %. One instance takes 16 to 19 % less CPU, and the longest buffer while you edit is 17 to 27 % shorter. Measured on an M4 Pro; not yet checked in a DAW on an M1.
- To compare, choose Developer > Speed-ups off (legacy emulation, slower) in the right-click menu, or start your DAW with
GEARMULATOR_MDMM_SPEEDUPS=0. Both give the same sound; only the CPU differs. If a click or a timing difference goes away with them off, tell us.
Fixes
- The buttons on the plug-in's messages work again (both editors). Since 0.3.0, pressing a button on a message or question from the plug-in did nothing, the update banner's Update, Download and Restart included. The answer now reaches the plug-in, and a question is answered once.
- Saving a project holds up the audio for a fraction of a millisecond (both editors, B-034). The machine's state is copied under the plug-in's lock and encoded after it: 0.13 to 0.24 ms in the Machinedrum Editor, 0.04 to 0.45 ms in the Monomachine Editor. 0.3.5 shortened the save's hold on the audio, but with a factory baseline cached on disk every save still decoded that cache under the lock: 48 to 59 ms in the Machinedrum Editor, 21 to 25 ms in the Monomachine Editor.
- The Monomachine Editor keeps a machine change (B-027). Choosing another machine for a track on Sound and then editing a step on Sequence used to put the machine back, with every other unsaved kit value. The machine plays the stored kit for about a quarter of a second after the edit; then your edits come back.
- Picking a pattern after a big SysEx import works (Machinedrum Editor, B-031). The editor no longer queues a status or dump request that is already waiting. A long backlog used to end in a burst of about 200 requests, and the Machinedrum's OS 1.63 loses input when that much arrives while it builds a reply: the pick never reached the machine and some read-backs failed ("Push failed"). 0.3.5's paced import hid it; a long backlog from any other source no longer causes it.
- A full MIDI queue no longer replays an old event (both editors). A burst of MIDI that filled the plug-in's queue could play an old event again and lose the new one, which could leave a note stuck.
- The DAW hears the new latency (both editors). After the resampler mode or the sample rate changes, the plug-in tells the host its new latency at once, so delay compensation is right.
- Windows: closing and reopening the plug-in's window no longer leaves it blank (B-029), and the standalone no longer starts with a blank window when its window is made again while it starts (B-022). The editor makes its web view again in the new window. We could not try this in a real Windows DAW yet; the Windows start test now closes and reopens the editor. If it still happens, send the
editor-*.log(Open Log Folder). - Windows: the standalone says when a MIDI port did not open (B-037). On Windows a MIDI port works in one program at a time: if a DAW or another editor uses it, the AUDIO / MIDI panel now says which port, why, and to switch it off there. The start-up log lists the audio device and the MIDI ports whenever they change. The Machinedrum Editor's start-up log gets its boot line once a second, as 0.3.5 said, not every 4 s (B-035).
- A note on MIDI in: in the app no MIDI input is on until you switch it on in AUDIO / MIDI, on every system.
- macOS: the installer removes the old plug-ins (B-032). It removes the old Gearmulator MD and Gearmulator MM VST3, AU and app bundles, in the install location and in your home folder, so a DAW lists each editor once. It leaves other names and links alone. If your DAW still lists an editor twice, tell us what is in
/Library/Audio/Plug-Insand~/Library/Audio/Plug-Ins. - The download page says which file is the installer (B-040): on macOS the big button reads "Download the installer (.pkg)", the .dmg is marked as loose files, and every release's notes on GitHub say it too.
- The Windows and Linux READMEs send reports to https://mdmm.dev/contact/ and Discord (#bugs), not to GitHub issues, which are off (B-042).
- Linux: the page stays up (both editors). A window that was not at the design size sent its zoom in a way that crashes WebKitGTK's web process, so a laptop screen below 1440 x 924 could blank the page; it now goes as an ordinary message. A file write that fails no longer freezes the page: it is tried again, in order, and the start-up log says why. A page that starts again shows the questions still waiting. Not tried on a real Linux desktop yet; it may be the blank window one tester saw on 0.3.4 (B-033). If your window is still blank, tell us your distribution and WebKitGTK version.
- The MCP server only answers your own computer. It is off unless you switch it on. It now listens on 127.0.0.1 only, checks the Host and Origin of every request and sends no CORS headers, so a web page in your browser can no longer call it; it stops at once when the editor closes, and limits the size and number of requests. It still has no password, so leave it off unless you use it.
- A broken network message ends its connection, not your DAW. In the MCP server and the DSP bridge (upstream's network-DSP feature: its server is a separate program we do not ship; its client is compiled into the plug-ins, but these editors have no switch for it), a malformed or oversized message, or an error on a network thread, now closes that one connection. The bridge server names a ROM it caches by its content only (1 byte to 16 MiB) and no longer takes a path from the other end.
New
- A notice when the editor runs under Rosetta (both editors, B-043). Testers on M1 Macs see about twice the CPU of M2 Macs. The likely cause is a DAW opened as an Intel app, which runs the whole emulator translated. The editor now says so once a session: "Running under Rosetta" with Don't show again and OK (on Windows on Arm: "Running in emulation"). It replaces the "Rosetta detected" box the editors inherited, which came back every time a window opened and could not be switched off. The performance report and the first line of the start-up log record
process_arch,machine_archandtranslated, so a report settles it. - Drag and drop files onto the window (both editors, macOS only for now). A ROM (
.bin, or a.zipwith it) installs after a question ("Install ... as the firmware? The machine starts again with it."), at once on the start-up card when no firmware runs yet. A SysEx file (.syx) opens the import window with its preview, as Import SysEx... does; one file a drop. Samples (.wav,.aif,.aiff; Machinedrum Editor, with the Sampler open) go into ROM slots: the one you drop on, or the selected one, then the slots after it, one file at a time, after one question. Anything else is named in a note. While files are over the window, a frame says what it takes. On Windows and Linux a dropped file is not opened; the card says to click the button. New in this release: if a drop is not taken, tell us. - The machine's own MIDI out reaches your DAW and the standalone's MIDI output (both editors, B-037). Notes, CCs, program changes, pitch bend and pressure, and clock, start, stop and continue, go where a real machine's MIDI OUT goes. Its SysEx never does: its dumps and answers to the editor must not reach a real Elektron on the port. In a DAW it arrives on the plug-in's MIDI output, which carried none of the machine's MIDI until now. In HW MIDI mode nothing changes.
Known
- Windows 10: both VST3s stay on the boot screen in Ableton, and the Monomachine standalone crackles (B-035, B-036). Most likely the machine runs below real time on that PC. We need the start-up log: Open Log Folder,
editor-*.log, after a minute in the DAW or the app. - Machinedrum: changing a machine in the stock patterns (B-039). We could not reproduce a machine change being lost; if it happens to you, tell us the pattern, the kit and what you did.
- 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: in a backup we test with, picking pattern H16 leaves the machine on kit 58, not its linked kit 74 (B-046). The firmware decides this; not investigated.
- Monomachine: a LOOP row in a song written by the editor goes back to row 1, not to the row it names (B-038). The machine plays it so; where it stores the loop target is still to be probed.
- The update banner still offers Download (the site), never Update. Installing from inside the app waits for our update signing key.
For developers
- A local release gate.
scripts/mdmm-local-gate.shsays red or green for a release candidate on a Mac with the firmware that CI never has (doc/release/LOCAL-GATE.md). - CI: the macOS, Windows and core lists name the new tests; Linux fails on a test program that does not build; the integration policy gate of the upstream fork runs only in its own repository.
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/