Troubleshooting
Start with the runner’s own window: the Audio row shows device errors in red, and Show log → Copy gives you the full log to paste into a report. The same log is in ~/.plinken/logs/plinken-run.log (%USERPROFILE%\.plinken\logs\ on Windows), overwritten on every launch.
Plinken says the runner is not running, but it is
Section titled “Plinken says the runner is not running, but it is”| Check | Fix |
|---|---|
| The first connect must be a click | Click the header runner button or Connect / Check again on Settings → Runner. A page load alone cannot show the browser’s permission prompt. |
| The local-network permission was dismissed or denied | In Chrome, open the site’s permission settings (the icon left of the address bar → Site settings), allow access to devices on the local network, reload, click again. |
The app is not on an official address or not on https:// | Use https://app.plinken.com. The runner only accepts connections from Plinken’s own origins. |
| Browser and runner are on different machines | They must be on the same computer. An iPad, a phone or a second PC cannot reach the runner. |
| Another program holds port 27480 | The runner window reports it cannot bind the port. Quit the other program (often an older Plinken Run that is still open) and reopen the runner. The port cannot be changed. |
The runner connects, but there is no sound
Section titled “The runner connects, but there is no sound”- Look at the runner window’s Audio row. If it shows an error, fix that first (sample rate and device problems are below).
- A runner whose audio failed to start can leave the app showing connected while nothing plays and the browser engine stays muted. Click Disconnect; the browser engine un-mutes at once. Fix the device problem, then reconnect.
- Check the output device under Settings → Audio → Grid / Mixer devices.
”… would not switch to 48000 Hz”
Section titled “”… would not switch to 48000 Hz””Plinken runs at 48 kHz only. Open your interface’s control panel (or Audio MIDI Setup on the Mac), set 48000 Hz, then click Connect again. If the rate changes while connected, the session ends; reconnect after setting it back.
macOS: “same-device required for low-latency duplex”
Section titled “macOS: “same-device required for low-latency duplex””Audio In and Audio Out must be the same interface. Choose one interface for both.
Windows
Section titled “Windows”| Symptom | Fix |
|---|---|
| ”no ASIO driver is installed” | Install the driver that came with your interface, then reopen Plinken Run. There is no fallback to the Windows mixer. |
| Windows protected your PC | SmartScreen. Click More info → Run anyway. To avoid it, right-click the zip → Properties → Unblock before extracting. |
| This app has been blocked with no Run anyway | Smart App Control. Turn it off under Windows Security → App & browser control, then run the exe again. |
| Firewall prompt | Allow on private networks. The runner only listens on 127.0.0.1. |
| Crackles or dropouts | Raise Settings → Runner → Audio buffer one step, or change the buffer in Open ASIO control panel…. |
| A WCLAP plugin window does not open | The WebView2 runtime is missing. Install it from Microsoft; the plugin keeps running without its window. |
| HEVC import or bounce fails by name | Install Microsoft’s HEVC Video Extensions from the Store. |
| ProRes is greyed out | ProRes is macOS-only. Bounce H.264 or HEVC on Windows. |
Plugins are missing
Section titled “Plugins are missing”| Symptom | Fix |
|---|---|
| No native plugins in the picker | Connect the runner first; native plugins show only while it is connected. |
| A newly installed plugin does not appear | Settings → Plugins → Rescan all. The first scan of a large collection takes a while. |
| A VST3 plugin never appears | It has no moduleinfo.json inside the bundle (pre-3.7.5 build). Update the plugin, or use its CLAP or AU version. |
| A plugin appears in the wrong format | Pick the format per plugin under Settings → Plugins. The default order is CLAP, then AU, then VST3. |
| AU plugins on Windows | AU is a macOS format; use the CLAP or VST3 build. |
| The scan hangs on one plugin | Reset excludes everything; Validate rows one at a time to find the offender, then re-include the rest. |
Update required
Section titled “Update required”“This runner is below the minimum supported version” or a refused video job means the app has moved ahead of your runner. Install the latest build from Settings → Runner; see Updates.
The video output window will not close
Section titled “The video output window will not close”Press Escape while the output window has focus, or use the close button on the Native Engine page. Quitting the runner closes it as well.
Still stuck
Section titled “Still stuck”Copy the log from the runner window (Show log → Copy), note your platform, interface and browser, and send it to info@plinken.com or open an issue at github.com/taluvi-dev/plinken-feedback.