MIDI Setup
Route DrumBeet MIDI out of the browser.
Live MIDI depends on browser and operating-system Web MIDI support. MIDI download stays available when live devices are unavailable.
Chrome and Edge are the safest choices for the live Web MIDI path. Safari does not currently expose the Web MIDI route DrumBeet uses.
| System | Virtual MIDI path | DrumBeet action |
|---|---|---|
| Windows | Create a port with loopMIDI. | Select the loopMIDI port in DrumBeet, then choose the same port in your DAW or VCV Rack. |
| macOS | Enable the IAC Driver Bus in Audio MIDI Setup. | Select the IAC bus in a Web MIDI browser and route the receiving app to that bus. |
| Linux | Use ALSA, JACK, or PipeWire MIDI depending on your audio stack. | Select the exposed MIDI port after your routing layer makes it visible to the browser. |
Fallback path
When live MIDI is unavailable, export a MIDI file from DrumBeet and import it into your DAW, sampler, hardware librarian, or VCV Rack workflow by hand.
VCV Rack
The patch catalog includes ready-to-open Rack patches and dependency notes. Use those with a virtual MIDI port when you want DrumBeet to drive Rack on channel 10.
Local corpus note
DrumBeet can mine a selected MIDI folder into a private browser-local corpus on that machine. The hosted public corpus remains Groove MIDI; private MIDI libraries are not uploaded to DrumBeet for MIDI routing.