Easiest
macOS
Drop three files in, add the surface. Nothing else. The dylibs are Developer-ID signed and Apple-notarised, so Gatekeeper accepts them on first load.
Rea-Sixty is a REAPER extension — one file plus two runtime libraries. ReaPack is the recommended route on all three platforms and keeps you updated automatically.
Rea-Sixty and SSL 360° cannot share the hardware. SSL 360° claims the UF8/UC1 vendor-USB interface exclusively, so it must be quit before REAPER starts. On Windows the two drivers are mutually exclusive at the USB-stack level. Keep SSL 360° installed regardless — you still need it for firmware updates.
Three things, all platforms:
SSL360Core; find it in Activity Monitor and quit it. If SSL 360° is running when REAPER starts, the surface never appears and REAPER's Console shows an error.You need a UF8 or a UC1 over USB-C. UF8-only, UC1-only and both-at-once rigs are all supported.
https://github.com/acklin83/reaper-scripts/raw/main/index.xmlRea-Sixty → right-click → InstallThe ReaPack index lives in a separate reaper-scriptsrepository. That is expected, not a typo.
Grab your platform's archive from the latest release and unpack it into REAPER'sUserPlugins directory:
| Platform | Goes into |
|---|---|
| macOS | ~/Library/Application Support/REAPER/UserPlugins/ |
| Windows | %APPDATA%\REAPER\UserPlugins\ |
| Linux | ~/.config/REAPER/UserPlugins/ — then follow the tarball's INSTALL.txt |
libusb and hidapi ship inside the macOS and Windows archives — no separate install. On Linux they come from your distro.
The three platforms are not equally easy, and pretending otherwise wastes your evening.
Easiest
Drop three files in, add the surface. Nothing else. The dylibs are Developer-ID signed and Apple-notarised, so Gatekeeper accepts them on first load.
One extra step
Needs a one-time WinUSB driver swap with a UAC prompt and an "unknown publisher" warning. This takes the device away from SSL 360° until you reverse it.
One extra step
Needs a udev rule and two distro packages. Do not daisy-chain the UC1 through the UF8 — plug both into the computer.
Nothing extra. IOKit already grants libusb access to the device class. Go straight to step 4.
SSL 360°'s kernel driver owns the devices, so libusb cannot open them until you hand them over:
?) →Rea-Sixty: Open / Close Rea-Sixty SettingsThis takes the devices away from SSL 360°. The two drivers are mutually exclusive at the Windows USB-stack level. To go back, re-run SSL 360°'s installer — it reinstalls its driver and reclaims the hardware, and Rea-Sixty will not see the devices again until you repeat the WinUSB install.
ReaPack can drop the .so into UserPlugins but cannot write to /etc/udev/rules.d/. Install the rule from inside REAPER:
?) →Rea-Sixty: Open / Close Rea-Sixty SettingsYou will also need the distro runtime libraries:
sudo apt install libusb-1.0-0 libhidapi-hidraw0Or the equivalent on your distribution.
Plug each SSL surface into its own port on the computer.Daisy-chaining the UC1 through the UF8's downstream port triggersusb usb1-port5: disabled by hub (EMI?), re-enabling…cycles under Linux 6.17 / xhci_hcd. The same hardware daisy-chains fine on Windows and macOS — this one is Linux-specific.
If you installed by hand from the tarball you already added the udev rule via the shell — skip the steps above.
Installing the file is not enough. In REAPER:
Preferences → Control/OSC/Web → Add → Rea-Sixty
No MIDI device assignment, no port to pick. The extension claims the UF8/UC1 over USB by itself.
First, confirm the extension loaded at all: Action List (?) → search Rea-Sixty. You should see entries like Rea-Sixty: Open / Close Rea-Sixty Settings. If they are missing, the extension did not load — check that every file from the archive is in UserPlugins, and on Windows that the WinUSB swap completed.
Then, with the surface added, all three of these should be true:
If something is off, the Troubleshooting chapter in the manual goes deeper — or open an issue. Include the version string from Settings → About; it makes the report far more useful.