Machinedrum Editor + Monomachine Editor 0.4.0

Machinedrum Editor + Monomachine Editor 0.4.0

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-Ins and ~/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_arch and translated, so a report settles it.
• Drag and drop files onto the window (both editors, macOS only for now). A ROM (.bin, or a .zip with 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.sh says 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...

Machinedrum Editor + Monomachine Editor 0.3.5

Machinedrum Editor + Monomachine Editor 0.3.5

A fix release on top of 0.3.4.

Screenshots, features and FAQ: https://mdmm.dev · User guide: https://mdmm.dev/guide/

SysEx import

• The file goes to the machine as it is, and the machine decides. The editor no longer guesses which OS a dump is from. Old backups, public ones among them, now import in full: kits, patterns, songs and globals from earlier OS versions that used to be refused as "wrong OS".
• The preview tells you what will happen: what each item overwrites, what plays now, and that an import has no Undo (Export SysEx first). Untick a whole kind or click single items away.
• A report per item once the machine has read everything back: taken, converted by the machine, ignored, or different from the file.
• A new import window (both editors): one tab per kind (kits, patterns, songs, globals) with the machine's own slot grid, so you see which slots get overwritten and what plays now. Click a slot to leave it out (Shift-click for a range), or use All, Empty slots only and None. While it runs, each tab shows its own progress; the report marks every slot and can show the problems only.
• Globals are off unless you tick them: they change the machine's MIDI channels and settings. An imported global for the slot the machine uses is made active at once, so the machine and the editor agree on the MIDI channel, and the report says what each global changed. If a global sets the MIDI base channel to OFF, the editor says so instead of showing mutes the machine never took; GLOBAL sets a channel again.

Fixes

• Start-up diagnostics in the plug-in too (both editors, B-035). While the machine starts, the start-up card says when the DAW is not running audio for the plug-in, or when the machine runs slower than real time; the start-up log (Open Log Folder) gets a line a second for the first 30 s, in the app and in a DAW.
• The Monomachine Editor's play head costs less (B-036): it moves without repainting the step cells and the piano rolls at every step, and the editor asks the emulator less often while the machine starts, as the Machinedrum Editor does.
• TEMPO shows the DAW's tempo in a DAW (both editors, B-030). The machine already followed the host's clock, but the LCD showed its own stored tempo. Now it shows the host's BPM (also while the DAW is stopped), marked DAW, and refuses edits: change the tempo in the DAW. The app is unchanged.
• No more glitch when you save a project or close the app (Machinedrum Editor): saving no longer holds up the audio for 25 to 30 ms. The app now fades out before it closes, so closing while a pattern plays no longer clicks.
• Set up sampling no longer loses tracks 13 and 14 (Machinedrum Editor). In 0.3.4, chopping right after Set up sampling with the machine stopped put the tracks back to the kit's stored machines, together with every unsaved kit edit.
• The arpeggiator range goes up to 9 octaves (Monomachine Editor), as on the machine, and shows the right number: it used to read one octave too many.
• Full screen and maximise work in the app, and the app menu no longer has a Settings entry that did nothing.
• ? works without clicking into the window first (both editors); in the Monomachine Editor it now opens the keyboard view.
• Shortcuts work while a value is focused, so ⌘Z (Ctrl+Z) undoes a Control All drag at once.
• Perform no longer jumps while you drag the envelope (Monomachine Editor).
• A SysEx file chosen as the ROM now says it is SysEx, not the ROM image, and where to import it.
• Windows: a faster, more reliable start. The editors try WebView2 again when it fails to start, write a start-up log, and say on screen what went wrong. Open Log Folder in the right-click menu finds the log to send us.

New

• The Song page shows what plays (both editors). Its left column now goes from the top: What plays (a big PATTERN | SONG switch and one live line: PATTERN B07, SONG 01 · row 017 of 65 · B01, or CHAIN A03»A05), the song, the pattern palette, the selected row. While a song plays, the arrangement is framed as playing; in PATTERN mode it stays as it is, ready to edit, and the header says the song is not playing. The switch lights what the machine reports.
• A song playhead (both editors): while the machine plays a song, the row it plays is marked in the arrangement, read from the machine itself, so it follows repeats, loops and jumps; the time bar above the grid fills up to it, and the LCD's pattern slot reads SONG 01 · 017.
• PAT / SONG on the LCD's second line, on every page: click it to switch between pattern and song mode. The LCD keeps its size in both modes.
• Song edits just play (both editors): no more "Reload song". An edit made while stopped is heard at the next PLAY; one made while the song plays, from the next start; one made in pattern mode, when you switch to SONG.
• GLOBAL key in the top bar (Machinedrum Editor), where FN was: the machine's MIDI channel, sync, note map and routing. The AUDIO / MIDI panel points to it. FN is gone: ⌥, ⇧ and ⌘ remain, and the step menu keeps every ⌥ action.
• The editor menu in the editors' own style (both editors): right-click anywhere the page has no menu of its own. Zoom (the page, and Window Size for the window itself), Updates, Open Log Folder, Audio/MIDI Settings… in the app, and a Developer submenu. It works with the keyboard and looks the same in every DAW.
• The GLOBAL panel's note map names every target (Machinedrum Editor): tracks, patterns A01 to H16, START and STOP. Map a note sends any note to any pattern, START or STOP. Maps from older backups now show as they are instead of being cut short.

Platforms

• macOS 12 or later (Intel and Apple silicon), not signed by Apple yet: the first install needs Open Anyway.
• Windows x64 and Linux x64: not tested by a person yet. Feedback welcome: https://mdmm.dev/contact/

Machinedrum Editor + Monomachine Editor 0.3.4

Machinedrum Editor + Monomachine Editor 0.3.4

A fix release on top of 0.3.3, with a new keyboard map for the Machinedrum Editor.

Screenshots, features and FAQ: https://mdmm.dev · User guide: https://mdmm.dev/guide/

Fixes

• No more drop-outs while editing in a DAW (both editors). Every edit used to reach the machine at once: a parameter-lock drag sent the whole pattern up to five times a second, and each one kept the emulation busy on the audio thread, so a slower Mac missed audio buffers. While the machine plays, everything the editor sends now goes in one queue at the speed of a real MIDI cable, and the newest value wins while it waits. In a six-second lock drag the machine now takes 5 patterns instead of 31, and the audio thread runs hot about a sixth as long as before. The first edit is heard at once; during a long drag the machine follows at most about two seconds behind.
• Big imports run at full speed while the machine is stopped; while it plays they go at MIDI-cable speed so the audio never drops out. A full Machinedrum backup's 128 patterns take about 14 seconds while stopped, and about four minutes while playing.
• SysEx imports finish cleanly. A big import used to end with a flood of "Push failed" messages and old patterns on screen, although the machine had taken them in. The editor now checks the documents a couple at a time.
• ⌘C, ⌘V and ⌘X work in DAWs and in the app (Ctrl+C, Ctrl+V, Ctrl+X on Windows and Linux). Before, the plug-in window swallowed them on macOS.
• Lighter page graphics while playing (Machinedrum Editor): the moving play head no longer redraws a column of steps at every step, so the editor's window costs far less while the pattern plays.

New

• The version is shown: next to Setup in the top bar, in the keyboard view, as the first line of the right-click menu (with the Updates entries under it), and in the app's About box (the app menu on macOS, Help on Windows and Linux).

New: the keyboard map (Machinedrum Editor)

• ⌘-click and ⌘-drag select steps (Ctrl on Windows and Linux); ⌘⇧-click extends the selection.
• Right-click a step for the step menu: trig, accent, slide, copy, paste, duplicate, clear, and the fill (every 2nd or 4th step) that used to be on ⌘-click.
• FN button in the top bar: the next click, drag or key acts on every track, like holding ⌥ (double-click keeps it on).
• ? shows a keyboard view with every key and what it does.
• Delete with nothing selected no longer clears the page; it tells you how (Clr, or ⌥Delete for the whole pattern).
• COPY, CLR and PASTE in the LCD act on the selected steps when steps are selected.
• The Monomachine Editor gets the same selection and step menu next.

Platforms

• macOS 12 or later (Intel and Apple silicon), not signed by Apple yet: the first install needs Open Anyway.
• Windows x64 and Linux x64: not tested by a person yet. Feedback welcome: https://mdmm.dev/contact/

Windows and Linux: not tested. The *-Windows-x64-not-tested.zip and *-Linux-x64-not-tested.tar.gz archives are built and unit-tested by CI only; nobody has used them yet. Each has a README (install paths, required packages). Bring your own ROM.

Machinedrum Editor + Monomachine Editor 0.3.3

Machinedrum Editor + Monomachine Editor 0.3.3

A fix release on top of 0.3.2, with the first steps towards updating from inside the app.

Screenshots, features and FAQ: https://mdmm.dev · User guide: https://mdmm.dev/guide/

Fixes

• No more swing while editing parameter locks (Machinedrum). Each lock edit sends the whole pattern to the machine; it used to arrive all at once and stall the machine's sequencer for up to 17 ms. It now goes in at a steady pace, and the editor checks the machine once after you stop editing. Timing while dragging a lock lane: worst error 16.9 ms before, under 4 ms now.
• The Sampler fills on the very first start of a new install (it stayed empty until the editor was restarted).
• A SysEx message that a host delivers in pieces now reaches the machine once, not twice (from upstream Gearmulator).

New

• Update check: once a day the editor asks https://mdmm.dev/latest.json whether a newer version exists and shows a small notice; it starts showing notices once the update service is switched on, in a later release. Nothing else is sent; turn it off in the new Updates menu. Installing from inside the app also comes later.

Testing

• Every release is now checked on the exact files we ship before they are published: the apps and plug-ins start and show their editor on macOS, Windows and Linux, Apple's AU validation, and pluginval (strictness 5) on every VST3 and AU.

Platforms

• macOS 12 or later (Intel and Apple silicon), not signed by Apple yet: the first install needs Open Anyway.
• Windows x64 and Linux x64: not tested by a person yet. Feedback welcome: https://mdmm.dev/contact/

Windows and Linux: not tested. The *-Windows-x64-not-tested.zip and *-Linux-x64-not-tested.tar.gz archives are built and unit-tested by CI only; nobody has used them yet. Each has a README (install paths, required packages). Bring your own ROM.

Machinedrum Editor + Monomachine Editor 0.3.2

Machinedrum Editor + Monomachine Editor 0.3.2

Fixes and polish on top of 0.3.1: the Windows editor now opens, a new name, step selection on the Machinedrum, and rendering fixes for older Macs.

Screenshots, features and FAQ: https://mdmm.dev
User guide: https://mdmm.dev/guide/

What's new

Names

• The editors are now Machinedrum Editor and Monomachine Editor, by Future Native Audio, in your DAW's plug-in list, in Finder and in the window titles.
• The installers remove the old Gearmulator MD and Gearmulator MM bundles they put in place, so a DAW does not list the editor twice. Your ROMs, settings and old DAW projects are untouched: projects still load.

Windows and Linux

• The Windows editor now works (WebView2): the window is no longer empty. Windows is still not tested in a real DAW.
• A Linux x64 build is available (not tested).

Machinedrum

• Select steps with Option-click, Option-drag or the ruler, then copy, cut, paste, duplicate and delete them (Cmd-C, Cmd-X, Cmd-V, Cmd-D, Delete). Slide moved to Option-Shift-click.
• The LCD's values follow a drag.
• The first start loads the ROM once, not twice.

Window and display

• Page Zoom in the right-click menu, and Cmd -, Cmd +, Cmd 0. The page always fits its window, and the plug-in window fits the screen (no more oversized window in Ableton Live).
• The MIX faders keep a sensible size at every window size.
• Older macOS (12 and later): the rendering fixes for the older Safari, and a visible play head on the white skin.
• The right-click menu no longer has a dead Settings entry. The standalone app has "Audio/MIDI Settings...".

Standalone

• A Record menu writes the window and its sound to an .mp4 (macOS 15 and later).

Requirements

• macOS 12 or later (Intel and Apple silicon). The installer now checks this.
• CPU use is unchanged: about half a core per instance.

Known limits

• Not notarised by Apple: on macOS 15 and later use Open Anyway in System Settings > Privacy & Security.
• High CPU in some hosts is not fixed yet.

Report a problem: https://mdmm.dev/contact/

Windows and Linux: not tested. The *-Windows-x64-not-tested.zip and *-Linux-x64-not-tested.tar.gz archives are built and unit-tested by CI only; nobody has used them yet. Each has a README (install paths, required packages). Bring your own ROM.

Machinedrum Editor + Monomachine Editor 0.3.1

Machinedrum Editor + Monomachine Editor 0.3.1

A fix release on top of 0.3.0.

Screenshots, features and FAQ: https://mdmm.dev

Fixes (Machinedrum)

• Unsaved kit edits are no longer lost when you click a step elsewhere.
• Kit values always reach the machine: undo after Control All is heard, and a value set right after a machine change stays.
• "Set up sampling" sets the recorder's volume to 0, so the recorder never records itself (no feedback loop).

macOS

• Each machine also comes as a drag-and-drop disk image (.dmg), next to the installer (.pkg).
• The editors have their own bundle identifiers and settings files, apart from upstream Gearmulator. Settings from 0.3.0 and earlier are copied over on first start.
• The release pipeline is ready for Developer ID signing and notarization.

Install

Bring your own ROM: nothing is bundled. If macOS says the app cannot be opened, go to
System Settings › Privacy & Security and click Open Anyway.

Windows and Linux: not tested

• Windows x64: MD-MM-Editors-Windows-x64-not-tested.zip (standalone apps + VST3). It passed the automatic tests, but no person has tried it yet.
• Linux: coming in a later release.

Machinedrum Editor + Monomachine Editor 0.1.0 alpha

Machinedrum Editor + Monomachine Editor 0.1.0 alpha

The first public release of two screen-native editors for the Elektron Machinedrum and
Monomachine. Each one runs the machine's real firmware in an emulator and puts the whole machine
on one page: step grid, parameter-lock lanes, kit and pattern library, song chains, mutes, app
LFOs, and a HW MIDI mode that drives a real machine instead of the emulator.

• Machinedrum Editor: a step grid, lock lanes by page and
  index, kit/pattern library, chains, GLOBAL settings, a ? key list, and LFOs that keep running
  with the editor closed.
• Monomachine Editor: a piano-roll sequencer, lock
  lanes, POLY, song picker, live and grid recording, and undo that covers library writes.

Both come as a standalone app, a VST3 and an Audio Unit for macOS (Apple silicon and Intel).

Screenshots, features and FAQ: https://mdmm.nativekloud.com

• Machinedrum sequencer
• Machinedrum kit library
• Monomachine sequencer
• Monomachine mixer

This fork's editors are separate from upstream's mdmm-v0.1.0-alpha.N "Gearmulator MD/MM"
builds, which ship the hardware-panel emulation. Those remain at
joelanders/gearmulator-md-mm.

Pay what you want

The editors are free software. If they are useful to you, you can pay what you want at
https://mdmm.nativekloud.com/get/. Paying is optional; the download is the same.

Install (macOS)

File	Installs
Machinedrum-Editor-macOS.pkg	/Applications/Machinedrum Editor.app, /Library/Audio/Plug-Ins/VST3/Gearmulator MD.vst3, /Library/Audio/Plug-Ins/Components/Gearmulator MD.component
Monomachine-Editor-macOS.pkg	/Applications/Monomachine Editor.app, /Library/Audio/Plug-Ins/VST3/Gearmulator MM.vst3, /Library/Audio/Plug-Ins/Components/Gearmulator MM.component

1. Download the package for your machine.

2. The packages are not signed yet (there is no Apple Developer ID for the project), so macOS
   blocks them on a plain double-click. Open one in any of these ways:

   • Right-click (or Control-click) the .pkg in Finder, choose Open, then Open again.
   • Or double-click it, dismiss the warning, then go to System Settings › Privacy & Security,
     scroll down and click Open Anyway next to the package's name.
   • Or in Terminal: xattr -d com.apple.quarantine ~/Downloads/Machinedrum-Editor-macOS.pkg

3. Follow the installer. Customize lets you leave out the app, the VST3 or the AU. It asks for
   your password because it writes to /Applications and /Library.

4. If the app is blocked the first time you open it, do the same: right-click it in Applications and
   choose Open, or use Open Anyway, or run:

   xattr -dr com.apple.quarantine "/Applications/Machinedrum Editor.app"
   xattr -dr com.apple.quarantine "/Applications/Monomachine Editor.app"

5. Rescan plug-ins in your DAW. The plug-ins are listed as Gearmulator MD and Gearmulator MM
   (instruments). If you installed an earlier build by hand into ~/Library/Audio/Plug-Ins, delete
   those copies so the DAW does not list two.

Terminal install, for scripts:

sudo installer -pkg Machinedrum-Editor-macOS.pkg -target /
sudo installer -pkg Monomachine-Editor-macOS.pkg -target /

To remove: delete the three bundles listed above. Your firmware and settings in ~/Documents stay.

Bring your own ROM

No firmware is included, and none will be provided. The Elektron firmware is Elektron's
copyright; the editors are for people who own the machine.

Copy the complete 8 MiB firmware image (.bin) from your own machine into:

Machine	Folder
Machinedrum	~/Documents/Gearmulator Preview/Machinedrum/roms/
Monomachine	~/Documents/Gearmulator Preview/Monomachine/roms/

If no firmware is found, the editor says so and opens the folder for you. Then restart the app or
reload the plug-in. Tested firmware: Machinedrum UW OS 1.63 and Monomachine SFX-60 OS 1.32B.

Please do not ask for, share or link firmware files in the issues or on Discord.

Known limits

This is an alpha. Save often and keep backups.

• HW MIDI is beta and untested on real hardware. It was verified only against the emulator
  acting as the MIDI peer; no real Machinedrum or Monomachine has been connected yet. Reports are
  very welcome.
• Over HW MIDI, some controls are disabled because the machine has no MIDI message for them (the
  editor says why), edits made on the machine before connecting are not seen until SAVE KIT, and
  the Monomachine's MIDI track mutes shown are the editor's own.
• Machinedrum: LOCAL CTRL and TRIG IN A/B are stored and shown, but their effect is not verified.
  In the MAP EDITOR, START and QUE were not told apart, and CTRL keymap values (32 and up), if any,
  are not shown.
• Monomachine: STEP RECORDING (STOP + RECORD) is not on the page; the record key uses GRID and LIVE.
• The page is the only UI. The older hardware-panel skins are not part of these builds.
• Names inside the apps still read "Gearmulator MD" / "Gearmulator MM" (menu bar, DAW plug-in list)
  and the data folder is ~/Documents/Gearmulator Preview.
• The standalone apps use stereo output. Extra output pairs are available in a multi-output VST3
  host.
• macOS only for now. Tested on macOS 27 on Apple silicon; the Intel slice is built and checked but
  not played on an Intel Mac. The packages are unsigned and not notarized.

Credits

• joelanders: the Machinedrum and
  Monomachine emulation this is built on, running the real firmware.
• The Usual Suspects and the Gearmulator
  contributors: the emulation framework, the DSP56300 and 68k cores, and the plug-in
  infrastructure.
• The editors (the Machinedrum Editor and Monomachine Editor pages, HW MIDI mode, installers):
  Radek Dymacz, NativeKloud.

Licence and trademarks

GPL-3.0, like upstream Gearmulator. The full source for this release is at
radekdymacz/gearmulator-md-mm under the
mdmm-v0.1.0-alpha tag; the licence text is in LICENSE.md.

Machinedrum, Monomachine and Elektron are trademarks of Elektron Music Machines MAV AB. This
project is not affiliated with, endorsed by, or supported by Elektron, The Usual Suspects or
joelanders. Please do not contact them for support: use
the issues.