Dehli Musikk microSAMPLER Editor / Librarian

Getting started

What you need, how to install it on each platform, and the first-run steps to get the editor talking to your microSAMPLER.

Requirements

Hardware

microSAMPLER rear panel showing the USB-B port and audio jacks
The microSAMPLER's rear panel — the USB port is what connects to your computer.

Software

ComponentNotes
Operating systemmacOS (tested), Linux (should work), Windows (untested)
Python 3.8+macOS: via the Xcode Command Line Tools (xcode-select --install) or python.org — the only thing you install
pyusb (BSD) + libusb (LGPL)Bundled with the app — no pip or Homebrew step (a system copy is used instead if you have one)
A modern browserChrome / Chromium recommended (Web MIDI needs Chrome, Edge or Firefox)

The editor itself needs no installation and no build step — it's plain web files served by a small local helper (the "bridge").

Get the app

Grab it from GitHub — download the latest release ZIP, or clone the repository.

Download the latest release →

Unzip it, then open a terminal in the unzipped folder. Prefer git? Clone instead:

git clone https://github.com/benjamindehli/microsampler-editor-librarian.git
cd microsampler-editor-librarian

Install — macOS (the easy way)

Nothing to install — pyusb and libusb are bundled. Just use the launcher:

  1. Connect the microSAMPLER to your Mac with the USB cable and power it on.
  2. Open the macOS/ folder and double-click microSAMPLER Editor Librarian.command.
  3. Enter your password when asked — administrator rights are required to claim the USB connection from macOS.
  4. The editor opens in your browser automatically.
FIRST RUN: "UNIDENTIFIED DEVELOPER"

The launcher is unsigned (it's a free, open-source project), so the first time you open it macOS blocks it with "cannot be opened because it is from an unidentified developer". Approve it once:

Comfortable with Terminal? Clear the download quarantine on the whole unzipped folder instead, then double-click as normal — you only need to do this once:

xattr -dr com.apple.quarantine microsampler-editor-librarian

Install — Linux

pyusb and libusb are bundled (x86-64 and ARM64) — just use the launcher:

  1. Connect the microSAMPLER and power it on.
  2. Open the Linux/ folder and double-click microSAMPLER Editor Librarian.sh. Some file managers open .sh files in an editor — mark it executable / "Allow launching" first, or run ./'Linux/microSAMPLER Editor Librarian.sh' from a terminal.
  3. Enter your password when asked (root is needed to claim the USB device).
  4. The editor opens in your browser automatically.

Install — Windows (experimental)

UNTESTED — EXTRA SETUP REQUIRED

Windows hasn't been verified, and libusb can't open the device until its USB driver is switched to WinUSB using Zadig.

  1. Install Python 3 (tick "Add to PATH"). pyusb and a 64-bit libusb DLL are bundled — nothing else to install.
  2. With the microSAMPLER connected, run Zadig and replace its driver with WinUSB (or libusbK).
  3. Open the Windows/ folder and double-click microSAMPLER Editor Librarian.bat.

Any platform — manual & mock

Run the bridge directly, then open http://localhost:8765:

sudo python3 native-tools/bridge.py
WHY SUDO?

The operating system's MIDI driver owns the device's USB interface; the bridge needs elevated rights to take it over while it runs. It hands control back when it exits.

To explore the interface with no device connected, run the bridge in mock mode (no password needed):

python3 native-tools/bridge.py --mock

First run

  1. With the device connected and the bridge running, open the editor in your browser.
  2. Check the CONNECTED light (top-right) is green.
  3. Press RECEIVE (top-right) to read the current bank from the device — its 36 sample slots and settings appear.
  4. Click any pad to start editing.
microSAMPLER connected to a computer running the editor
The bridge runs locally and the editor talks to the device over USB.

Device setup

Two device settings matter:

The device GLOBAL page showing MIDI CLK set to AUTO
Set MIDI CLK to AUTO so the sequencer follows the editor's transport.

New to the hardware? The Concepts page explains banks, the two play modes, BPM-sync and the sequencer. Stuck? See Troubleshooting.