MIDI Setup

Use drumbeet across operating systems.

The app runs in the browser. Preview, phrase search, editing, import, and MIDI download work broadly. Live MIDI routing depends on whether the browser exposes the Web MIDI API on your OS.

Browser Support

What is supported

Environment App, preview, import/export Live MIDI out/in
Chrome or Edge on Windows, macOS, Linux, ChromeOS Supported Supported when the OS exposes MIDI devices and site permission is allowed.
Firefox desktop Supported Limited. Web MIDI access can depend on browser settings, permissions, and OS device exposure.
Safari on macOS, iOS, and iPadOS Supported Not available in Safari. Use MIDI download/export instead.
Mobile Chrome and Android browsers Supported Best effort only. Hardware and OS MIDI routing vary by device.

Virtual MIDI

Route drumbeet into VCV Rack or a DAW

Windows

Install a virtual MIDI driver such as loopMIDI, create a port, then refresh MIDI in drumbeet.

Get loopMIDI

macOS

Open Audio MIDI Setup, enable the IAC Driver, and create an IAC bus for drumbeet to send into.

Apple IAC setup

Linux

Use ALSA/JACK/PipeWire MIDI routing. Common targets are Midi Through, a2jmidid, or qpwgraph.

Linux MIDI overview

ChromeOS

Chrome can expose compatible USB MIDI devices. Virtual routing support is device and container dependent.

Testing notes

VCV Rack

Patch routing

Drumbeet VCV patches are mapped to GM drum notes on channel 10. The patch files can open with an example MIDI device selected, but each OS uses different MIDI port names. In VCV Rack, retarget the MIDI module to the port you created, then choose the same output in drumbeet.

Security

How browser MIDI is constrained

Real Device Testing

What still needs human verification

Browser capability checks can cover most regressions, but live MIDI still needs device testing on Windows, macOS, Linux, ChromeOS, Android, and Firefox desktop. The expected fallback on unsupported browsers is no live port access, with preview and MIDI download still working.