The Roland D-50 is one of the defining sounds of the late 1980s and one of the least pleasant instruments ever designed to programme. Linear Arithmetic synthesis gave it its character; a two-line LCD, a cursor and a single data slider gave it its reputation. Editing a D-50 patch from the front panel is a documented act of patience.
Ian Dixon’s Roland D-50 Editor Librarian is a free, browser-based fix.
Dixon’s own walkthrough: connecting the D-50 over MIDI, enabling SysEx, and reading the current edit buffer.
What it does
A Web MIDI tool that lets you back up, browse, import and edit D-50 sounds — handling MIDI connections, SysEx transfers, patch management and parameter editing across the synth’s sound structures.
It is free, available now at thedigitallifestyle.com, and works with the original hardware D-50. One commenter reports it also drives a Roland V-Synth XT running D-50 emulation.
And the line that matters most, from Dixon’s own description: “without sending your patch data to the cloud.”
Why browser-based is the right architecture here, not a compromise
The instinct is to read “runs in a browser” as a limitation — a lesser version of a native editor. For this specific job it is the better engineering, for four reasons.
Nothing to install, so nothing to rot. The historical problem with synth editors is not writing them; it is that they are native applications for a platform that moves. The great editor you bought in 2009 is a 32-bit binary that macOS stopped running in 2019. A web page has no installer, no code signing, no notarisation, and no OS version it was built against.
SysEx is a perfect fit for Web MIDI. The Web MIDI API exposes raw MIDI messages including System Exclusive, which is exactly the protocol these editors need. A D-50 patch dump is a SysEx message; the browser can send and receive it directly. This is not a workaround — it is the API doing its intended job.
The permission model is explicit. Web MIDI requires a user gesture and, for SysEx specifically, a separate permission prompt. The browser will not let a page touch your instruments without you saying so, which is a stronger guarantee than a native app that simply has access to everything.
And “no cloud” is a real claim, not a slogan. A browser page can be entirely client-side: the JavaScript runs locally, talks to your MIDI interface locally, and never makes a network request with your data. Dixon’s statement is checkable — open the network tab and watch nothing happen. For anyone who has watched a hardware company put their patch library behind an account, that distinction is the whole value proposition.
It is also the same mechanism we covered in our Web Serial tutorial a few days ago, applied to MIDI rather than serial. Same constraints — secure context, Chromium-family browsers, no iOS — and the same payoff: a URL instead of an install.
The series is the actual story
The D-50 editor is not a one-off. In the last few weeks Dixon has also shipped:
- Roland D-110 Editor Librarian — the rack-mount D-series sibling
- Korg MS2000 Editor Librarian
- Kawai K1m Editor
That is four instruments from the late-80s and early-2000s digital era, all getting the same treatment: free, browser-based, Web MIDI, patch management plus editing.
This is a meaningful piece of preservation work, and it is worth naming as such. These synths are thirty to forty years old. Their original editors were Atari ST and early Mac software. The patch libraries that exist for them are SysEx files on forums and dead FTP servers, and the main barrier to anyone actually using one of these machines is that organising and auditioning sounds is miserable.
A librarian solves that, and a librarian that will still run in ten years solves it durably. Native software for a 1987 synth has to be rewritten every decade; a page that uses a W3C API has a better shot at just continuing to work.
The one thing to be aware of
Web MIDI is Chromium-only. Chrome, Edge, Opera and friends support it; Firefox and Safari do not, which also rules out iOS and iPadOS entirely. If you are on Safari, this will not work, and that is not fixable by the developer.
Also worth knowing before you connect: enable SysEx reception on the instrument. On a D-50 that is a system setting, and it is off by default on a great many synths — which is the single most common reason a working editor appears to do nothing.
Back up before you edit. Use the librarian’s dump function to pull your current patches to a file before you start changing things. SysEx edits write to the edit buffer and, if you tell them to, to memory. There is no undo on a thirty-nine-year-old synth.