LinCaster

A Linux-first, Rust-based "virtual driver" that recreates the core functionality of the Windows Virtual Devices driver workflow for the RØDECaster Duo and Pro II: multiple named software outputs ("System", "Chat", "Game", "Music", "A", "B"), per-application routing to those outputs, fader-like controls (gain/mute/solo) per virtual device, USB HID communication for sound pad configuration, and a GUI for visual control.

Built around PipeWire as the primary audio graph and policy integration layer.

Features

6 virtual audio sinks: System, Chat, Game, Music, Virtual A, Virtual B
Per-application routing: Regex-based stream matching with priority rules; direct pw-link port-level linking with WirePlumber correction
Fader controls: Gain, mute, and solo per bus (with solo-safe semantics) — implemented without capture data and currently untested
USB HID device control: Sound pad configuration, bank switching, colour setting, transfer mode, sound file import — all via the reverse-engineered EP5 protocol
GUI application: egui-based interface with a routing view (drag-and-drop stream assignment) and a sound pad editor (8-bank grid, import, clear, colour picker)
DBus API: Session bus service for bus control, stream routing, sound pad management, and device status
CLI tool: lincasterctl for command-line control (bus state, stream routing, pad import/clear, transfer mode)
State persistence: Fader positions and mute states survive restarts
Two modes: Hardware multitrack (preferred) or software-only fallback

Prerequisites

# Debian/Ubuntu
sudo apt install libpipewire-0.3-dev libasound2-dev libusb-1.0-0-dev libdbus-1-dev libclang-dev pkg-config

# Fedora
sudo dnf install pipewire-devel alsa-lib-devel libusb1-devel dbus-devel clang-devel

# Arch Linux
sudo pacman -S pipewire alsa-lib libusb dbus clang pkgconf

PipeWire + WirePlumber must be running as the user session's audio server. You also need Rust installed (curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh).

Quick Start

1. Build & Install

cargo build --release
sudo install -m 755 target/release/lincasterd target/release/lincasterctl target/release/lincaster /usr/local/bin/

PATH tip: If you prefer cargo install --path over sudo install, make sure ~/.cargo/bin is in your PATH:
export PATH="$HOME/.cargo/bin:$PATH"  # add to ~/.bashrc or ~/.zshrc to persist

2. Install udev Rules (required)

sudo cp contrib/99-rodecaster.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules && sudo udevadm trigger

These rules serve two purposes:

USB device access — allows non-root processes to open the RØDECaster for HID communication via libusb.
Prevent device freeze — the hidraw MODE="0666" rules are critical. When lincasterd exits, the device remains in host-session mode and generates EP5 IN notifications for every physical interaction (button press, dial turn). On Linux, the usbhid driver only polls EP5 IN when something has the /dev/hidrawX device open. If nothing drains these notifications, the firmware FIFO fills after ~2 button presses and all physical controls freeze until the device is power-cycled or USB connection to computer is unplugged.

By default, lincasterd spawns a lightweight background drain process (cat /dev/hidrawN > /dev/null) on disconnect that holds the hidraw device open and keeps the FIFO drained. The hidraw udev rules give that process (and other userspace HID consumers) permission to open the device.

Kernel parameter alternative: If you prefer not to rely on the drain process (e.g. you want freeze protection even if lincasterd crashes unexpectedly), you can add a kernel boot parameter that tells usbhid to always poll the endpoint. Use the quirk for your device:

Model Kernel parameter

Duo usbhid.quirks=0x19F7:0x0079:0x0400

Pro II usbhid.quirks=0x19F7:0x0078:0x0400

The PIDs above assume the default onboard multitrack configuration (USB 1 Output: Off, USB 1 Input: Expanded). If your device is configured differently, see Product IDs (PID) Per Onboard Multitrack Configuration for the full PID table.

Add this to your bootloader's kernel command line (e.g. /etc/kernel/cmdline, GRUB config, or Limine config). 0x0400 is HID_QUIRK_ALWAYS_POLL. With this parameter, the drain process is unnecessary — disable it at runtime:
lincasterd --no-drain

3. Configure (optional)

On first run, lincasterd automatically creates ~/.config/lincaster/config.json with sensible defaults (6 busses, app routing rules for Discord/Zoom/Steam/Spotify, etc.).

It also installs a WirePlumber config to ~/.config/wireplumber/wireplumber.conf.d/51-rodecaster-rename.conf that gives your RODECaster devices friendly names (e.g. "RODECaster Duo Main" instead of cryptic ALSA identifiers). Supports RODECaster Duo and Pro II.

To customise before first run:

mkdir -p ~/.config/lincaster
cp configs/config.json ~/.config/lincaster/config.json

Edit ~/.config/lincaster/config.json to taste. See Configuration below for details.

4. Run

Option A — Manually:

lincasterd

(uses ~/.config/lincaster/config.json by default — override with --config /path/to/config.json)

Option B — As a systemd user service (recommended):

mkdir -p ~/.config/systemd/user
cp contrib/lincasterd.service ~/.config/systemd/user/
systemctl --user daemon-reload
systemctl --user enable --now lincasterd

Check it's running:

systemctl --user status lincasterd
lincasterctl status

Usage

Daemon

# Run with your config
lincasterd --config ~/.config/lincaster/config.json

# One-shot status check (probe device and print PipeWire graph info)
lincasterd --status-only

# Or run directly from source without installing (for development)
cargo run -p lincasterd -- --config ./configs/config.json

CLI

lincasterctl status              # Show daemon status
lincasterctl list-busses         # List all virtual busses
lincasterctl get-bus system      # Get state of a specific bus
lincasterctl set-gain system 0.8 # Set System bus gain to 80%  (untested — no capture data)
lincasterctl mute chat on        # Mute the Chat bus           (untested — no capture data)
lincasterctl solo game on        # Solo the Game bus            (untested — no capture data)
lincasterctl reload-config ./configs/config.json

# Stream routing
lincasterctl list-streams              # List active audio streams and their routing
lincasterctl route-stream 42 game      # Route PipeWire node 42 to the Game bus
lincasterctl unroute-stream 42         # Unroute stream 42 (return to default device)
lincasterctl set-manual-override on    # Disable auto-routing rules (manual mode)
lincasterctl set-manual-override off   # Re-enable auto-routing rules

# Sound pad management
lincasterctl transfer-mode       # Enter transfer mode (mount device storage)
lincasterctl exit-transfer-mode  # Exit transfer mode
lincasterctl import-sound 1 ~/sounds/airhorn.mp3 --color 0       # Import sound to pad 1 (absolute)
lincasterctl import-sound --bank 1 --pad 1 ~/sounds/airhorn.mp3  # Same, using bank/pad flags
lincasterctl clear-pad 1                  # Clear pad 1 (absolute)
lincasterctl clear-pad --bank 2 --pad 1   # Same as pad 9, using bank/pad flags
lincasterctl set-pad-color 1 blue         # Set pad 1 colour to blue (absolute)
lincasterctl set-pad-color --bank 1 --pad 1 blue  # Same, using bank/pad flags
lincasterctl set-pad-bank 0      # Switch to bank 1 on device (0-indexed)
lincasterctl refresh-state       # Re-read pad state from device

Pad numbering

Pads can be addressed in two equivalent ways:

Absolute number (1–64): pads are numbered 1-based left-to-right across all 8 banks.
--bank / --pad flags: --bank <1-8> --pad <1-8>. The two forms are mutually exclusive; --bank and --pad must always appear together.

Bank 1:  pads  1-8    Bank 2:  pads  9-16
Bank 3:  pads 17-24   Bank 4:  pads 25-32
Bank 5:  pads 33-40   Bank 6:  pads 41-48
Bank 7:  pads 49-56   Bank 8:  pads 57-64

For example, --bank 2 --pad 1 is equivalent to pad 9.

Mixer pads

Mixer pads apply real-time audio effects to the mix. --trigger (latch/momentary) and --mode are required.

# Censor — mute mic and play a beep tone (device built-in tone)
lincasterctl apply-pad-config 1 mixer --trigger latch --mode censor
lincasterctl apply-pad-config --bank 1 --pad 1 mixer --trigger latch --mode censor

# Censor — with a custom audio file instead of the built-in tone
lincasterctl apply-pad-config 1 mixer --trigger latch --mode censor --file ~/sounds/bleep.wav

# Trash Talk — mute all outputs except your microphone (private comms)
lincasterctl apply-pad-config 2 mixer --trigger momentary --mode trash_talk --color green

# Fade I/O — fade all audio in and out (0.5 s default; customise with --fade-in / --fade-out)
lincasterctl apply-pad-config 3 mixer --trigger latch --mode fade_io
lincasterctl apply-pad-config 3 mixer --trigger latch --mode fade_io --fade-in 1.0 --fade-out 2.0

# Fade I/O — exclude the host/PC output from the fade
lincasterctl apply-pad-config 3 mixer --trigger latch --mode fade_io --exclude-host

# Back Channel — route selected inputs to a secondary output (--channel is repeatable)
# Available targets: mic_2, mic_3, mic_4, usb_1_comms, usb_2_main, bluetooth,
#                    callme_1, callme_2, callme_3
lincasterctl apply-pad-config 4 mixer --trigger latch --mode back_channel --channel mic_2
lincasterctl apply-pad-config 4 mixer --trigger latch --mode back_channel \
  --channel mic_2 --channel bluetooth --channel usb_1_comms

# Ducking — lower all non-mic audio while active (range: -12.0 to -6.0 dB; default -9.0)
lincasterctl apply-pad-config 5 mixer --trigger momentary --mode ducking
lincasterctl apply-pad-config 5 mixer --trigger momentary --mode ducking --depth -12.0

FX pads

FX pads apply voice effects to a microphone input. --trigger is required; any combination of effects can be enabled simultaneously.

# Reverb (room size, mix, filter)
lincasterctl apply-pad-config 1 fx --trigger latch --reverb
lincasterctl apply-pad-config --bank 1 --pad 1 fx --trigger latch --reverb
lincasterctl apply-pad-config 1 fx --trigger latch --reverb --reverb-mix 0.7 \
  --reverb-model large_hall

# Echo (delay, feedback, mix, filter)
lincasterctl apply-pad-config 2 fx --trigger latch --echo
lincasterctl apply-pad-config 2 fx --trigger latch --echo --echo-delay 0.3 --echo-decay 0.6

# Megaphone / distortion
lincasterctl apply-pad-config 3 fx --trigger latch --megaphone
lincasterctl apply-pad-config 3 fx --trigger latch --megaphone --megaphone-intensity 1.0

# Robot voice (mix: 0.0 = low, 0.333 = medium, 0.667 = high)
lincasterctl apply-pad-config 4 fx --trigger latch --robot --robot-mix 0.333

# Pitch shift (-12.0 to +12.0 semitones)
lincasterctl apply-pad-config 5 fx --trigger latch --pitch-shift --pitch-semitones -5.0

# Voice disguise (no additional parameters)
lincasterctl apply-pad-config 6 fx --trigger momentary --disguise

# Stack multiple effects; set input source and colour
lincasterctl apply-pad-config 7 fx --trigger latch --input mic_2 \
  --reverb --reverb-mix 0.5 --echo --echo-delay 0.2 --color purple

# Available input sources: mic_1 (default), mic_2, wireless_1, wireless_2
# Available reverb models: small_room, medium_room, large_room, small_hall (default), large_hall

GUI

# Run the GUI (requires the daemon to be running)
lincaster

# Or from source
cargo run -p lincaster

The GUI has two tabs:

Routing — shows active audio streams and lets you drag them to virtual busses
Sound Pads — 8-bank grid editor for configuring pads (import sounds, set colours, clear)

DBus

The daemon exposes com.lincaster.Daemon on the session bus:

# List busses
dbus-send --session --print-reply --dest=com.lincaster.Daemon \
  /com/lincaster/Daemon com.lincaster.Daemon.ListBusses

# Set gain
dbus-send --session --print-reply --dest=com.lincaster.Daemon \
  /com/lincaster/Daemon com.lincaster.Daemon.SetBusGain \
  string:"system" double:0.75

# Route a stream to a bus
dbus-send --session --print-reply --dest=com.lincaster.Daemon \
  /com/lincaster/Daemon com.lincaster.Daemon.RouteStream \
  uint32:42 string:"game"

# Get pad configurations
dbus-send --session --print-reply --dest=com.lincaster.Daemon \
  /com/lincaster/Daemon com.lincaster.Daemon.GetPadConfigs

Configuration

See configs/config.json for a complete example. Key sections:

device: USB vendor/product IDs and ALSA card hints for device detection
busses: Virtual bus definitions (name, channels, default gain)
routes: Mapping from busses to hardware channel pairs
app_rules: Per-application routing rules with regex matching
latency_mode: ultra_low (64 frames) or low (256 frames) — stored in config and reported in status, but not yet applied to PipeWire

Project Structure

crates/
├── lincaster/         GUI application (egui/eframe)
├── lincaster-proto/   Shared types, config, HID protocol encoding, state dump parser
├── lincasterd/        Daemon (device discovery, PipeWire graph, routing, USB HID, DBus)
└── lincasterctl/      CLI tool
configs/                Example configuration files
contrib/                udev rules, WirePlumber config, systemd service
docs/                   Architecture and USB protocol documentation
captures/               USB pcap captures used for protocol reverse-engineering

Troubleshooting

Pad colour won't change

The device firmware occasionally ignores a direct colour write if the pad's internal state is in an unexpected condition. Clear the pad first, then reapply the full config with the desired colour:

lincasterctl clear-pad <PAD>
lincasterctl apply-pad-config <PAD> mixer --trigger latch --mode censor --color green
# or for FX pads:
lincasterctl apply-pad-config <PAD> fx --trigger latch --reverb --color green

lincasterctl set-pad-color 54 magenta

This also applies to colour changes made via the GUI — if the colour picker has no effect, clear the pad and reconfigure it.

Testing

cargo test --workspace                        # Run all tests
cargo fmt --all -- --check                    # Format check
cargo clippy --all-targets -- -D warnings     # Lint check

Disclaimer

This project was built using LLM technology. The PRD was generated with ChatGPT's deep research offering, and the source code was built using Claude Opus 4.6. There may be redundant bits in the code base, missing unit tests, security flaws, inconsistencies, or other general 'oopsies'. For this reason, the software should be ran in the user space only (best practice for a tool of this type regardless of AI involvement), and any edge cases you can think of should be tested. If bugs or broken functionality occur, an issue should be opened or a PR submitted.

License

Licensed under either of:

Apache License, Version 2.0 (LICENSE-APACHE)
MIT License (LICENSE-MIT)

at your option.

Name		Name	Last commit message	Last commit date
Latest commit History 25 Commits
.github/workflows		.github/workflows
configs		configs
contrib		contrib
crates		crates
docs		docs
.gitignore		.gitignore
Cargo.lock		Cargo.lock
Cargo.toml		Cargo.toml
LICENSE-APACHE		LICENSE-APACHE
LICENSE-MIT		LICENSE-MIT
README.md		README.md
rust-toolchain.toml		rust-toolchain.toml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

LinCaster

Features

Prerequisites

Quick Start

1. Build & Install

2. Install udev Rules (required)

3. Configure (optional)

4. Run

Usage

Daemon

CLI

Pad numbering

Mixer pads

FX pads

GUI

DBus

Configuration

Project Structure

Troubleshooting

Testing

Disclaimer

License

About

Licenses found

Uh oh!

Releases

Packages

Uh oh!

Contributors

Uh oh!

Languages

Model	Kernel parameter
Duo	`usbhid.quirks=0x19F7:0x0079:0x0400`
Pro II	`usbhid.quirks=0x19F7:0x0078:0x0400`

Folders and files

Latest commit

History

Repository files navigation

LinCaster

Features

Prerequisites

Quick Start

1. Build & Install

2. Install udev Rules (required)

3. Configure (optional)

4. Run

Usage

Daemon

CLI

Pad numbering

Mixer pads

FX pads

GUI

DBus

Configuration

Project Structure

Troubleshooting

Testing

Disclaimer

License

About

Resources

License

Licenses found

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages