A
Select an app from the source list. The app must already be producing audio so Windows exposes a live session.
Install + Route
Getting Started
VDO Cable is designed for one job: take audio from specific Windows applications and publish each app as its own VDO.Ninja feed.
1. Install the signed Windows build
Use the installer unless you explicitly need a portable package for QA or temporary use.
2. Add one route per application
Open VDO Cable, refresh the source list, then create one route for each Windows audio session you want published separately.
B
Click Add Route, then set a Stream ID. Use Room and Password only when the route should join a shared workflow.
C
Start the route. Each route publishes independently and returns its own VDO.Ninja view link.
If two routes resolve to the same published Stream ID, the app marks the field in red and blocks the second publish before it hits the server.
3. Use the feeds downstream
Once a route is live, the generated view link can be opened directly in a browser or consumed by downstream tools like REAPER using separate VDO.Ninja inputs.
In v1, the app is audio-only by design. There is no virtual driver and no combined multi-track output device.
QA and support expectations
The release pipeline is set up for signed Windows artifacts, VirusTotal submission, GitHub Pages docs, native smoke loops, and logic fuzz coverage. Live network behavior still depends on your local Windows audio sessions and VDO.Ninja availability.
When signaling drops, the app uses bounded backoff and avoids websocket ping spam. If the server reports that a Stream ID is already in use, the route stops and the UI raises an explicit warning.