Discovery cannot find the Pi
- Allow first-start initialization and its automatic reboot to finish.
- Check power and the network connection. Keep the computer and Pi on the same LAN; guest Wi-Fi or client isolation can prevent discovery.
- Allow Discovery local-network access and select Refresh.
- Look up the Pi in the router's DHCP list and enter its IPv4 address under Manual address.
- If Live is unavailable, open
http://PI-ADDRESS:8003/directly. Discovery depends on the Live service; the Configurator is independent.
The dashboard opens but there is no sound
- Check the License page and ensure authorization is active.
- Read the bottom status bar and select Start if audio is stopped.
- Check Settings → Audio interface, Input pair and Output pair, along with the physical connectors.
- Confirm a line-level signal from your phono stage reaches the interface and that the amplifier uses the connected output.
- Select Repaired or Original. Removed monitoring can be nearly silent when there is little to remove.
- Check output gain and meters. Download diagnostics if the audio session reports that it cannot open the device.
Distortion, echo or a hollow sound
Reduce the interface's input gain if the raw signal clips. Lowering Master gain cannot undo clipping that already occurred at the input. Check that you have a proper phono stage and the correct line-input mode.
Disable any parallel direct-monitoring route if it mixes the original analogue path with the delayed processed output. Use input calibration for channel balance and headroom.
Dropouts or increasing counters
Check power, USB connections and cooling. Start at the recommended 48 kHz and a conservative buffering profile, then Stop/Start to apply a buffering change. Read the actual running format rather than only the saved sample-rate preference.
Engine Misses concern processing deadlines. XRuns concern audio-buffer underflow or overflow; transport Errors describe device failures. These counters are not interchangeable. Download diagnostics before rebooting and note the interface, sample rate and material that triggers the issue.
Noise reduction is not learning a local profile
Start playback from a lead-in without music. The acquisition window begins near the start of a side and excludes the initial settling second. Verify the silence threshold and NR capture ceiling with calibration. A generic profile may remain in use when a suitable local sample is unavailable.
Do not raise the capture ceiling so far that it accepts music. After changing setup, begin a new listening session from the lead-in and inspect the Activity profile state.
Some repairs are missing at high sample rates
On Pi 5, 88.2 and 96 kHz intentionally use ordinary-click DeClick only. Return to 48 kHz to enable stereo plops, per-channel plops and short residual impulse repair as well. Pi 4's Configurator is limited to 48 kHz. See Restoration and grading.
No track artwork or recognition
Check the Pi's Internet connection and allow time for a recognisable passage. Recognition depends on a match; silence, uncommon recordings or alternate versions may not produce one. A recognition failure does not stop restoration.
License or update connection failure
Check network access, date and timezone. In the License page, read the validation message and deadline; use Validate now after restoring connectivity. In the Configurator, review Last update and try Check for updates again. Do not interrupt an active maintenance/reboot cycle.
Ask for help
Download and review the Configurator's diagnostic report, then describe the symptom, device, sample rate and steps that reproduce it. Contact us through About Us, or discuss setup and listening experiences in the VinylRest Facebook community. Keep license keys, passwords and completed Wi-Fi setup files out of public posts.