Troubleshoot streaming and audio
Read the complete error notification before you change settings. It usually identifies the failed source or device action.
Start with the visible result
| Symptom | Next check | Success criterion |
|---|---|---|
| Waterfall moves but reception is silent | Check RX mute, volume, mode, and passband in first reception. | Intelligible audio from a strong known signal. |
| FM reception is silent | From 0.9.3-beta.1, check FM status. If Closed, compare the detected tone or code with the selected requirement. If Open, check RX mute, volume, and output. | Squelch opens for the wanted signal and audio is audible. |
| RX tone works but signal audio does not | Check source samples, tuning, and demodulation. The tone bypasses those stages. | The selected signal is inside the passband and audible. |
| Audio distorts or clips | Inspect the audio instruments. Reduce gain before the stage showing clipping. | Clear audio without persistent clip indication. |
| Rig USB receive input is unavailable | Check its device, channel, and competing applications, then turn Rig USB audio off and on to retry. If the status reads No audio from the radio, check that the radio is switched on. |
The RIG RECEIVER status shows Active during analog RX playback. |
| CAT connects but uses the wrong mode | Check Track and the rig mode preference. | The actual radio shows the intended sideband or data mode. |
| VOX ACTIVE appears but there is no RF | Check the radio's VOX, modulation input, and TX output route in transmit setup. | The radio keys and the independent RF check succeeds. |
| Radio remains keyed after a CAT error | Stop transmission at the radio and restore the control connection. | The radio is receiving before another attempt. |
| Tuning, pan, or zoom appears locked | Check for active IQ recording. | Stop the recording, then tuning works again. |
| Network reception has gaps or long delay | Check live buffering status and reconnect after changing presets. | Stable reception with no continuing counter increase. |
| A saved QSO is missing | Check the active logbook and filters. | The record appears in the intended database. |
| Map markers or background are missing | Check map filters, positions, and cache. | Expected contacts and the required map area appear. |
| Callsign personal details do not populate | Check the lookup service and credentials, then select Retry lookup. |
The name, QTH, or grid fills in, or the entry shows the service error. |
| An update fails | Read the update state and recovery steps. | The intended version appears after restart. |
SDR capture stalled
Radio Bench stops a hardware stream after about eight seconds without samples. This prevents a silent frozen waterfall from appearing active.
- Reconnect the SDR and start the stream again.
- Use a direct USB port instead of an unpowered hub.
- Test another data-rated USB cable.
- Close every other SDR application.
An Airspy HF+ can restart automatically after some interruptions. Repeated failure after three attempts usually indicates an unreliable USB link.
Another program holds RTL-SDR
Close SDR applications and stale rtl_tcp helper processes. Reconnect the dongle after the other process releases it.
On Linux, confirm that permissions and the DVB-T kernel driver are correct. See RTL-SDR setup.
Audio test fails
Select the device again in Settings > Audio, then select Play tone. Confirm the operating system can play other audio through that device.
On macOS, set a failing USB codec to a 24-bit format in Audio MIDI Setup. Some 16-bit configurations can trigger a CoreAudio rejection.
Audio lags with RTL-SDR
Low RTL-SDR sample rates increase USB block latency. Select 1.024 MS/s or more for a faster tuning response.
Create a support report when the problem continues.
FT8/FT4
FT8 and FT4 are included from 0.9.0-beta.1. See the FT8/FT4 troubleshooting table.
Before retrying a failed transmission, confirm that PTT has released. Include the exact error, protocol, source, and audio-device configuration in your support report.
Give support the missing context
Create a support report, then describe the action and visible result separately. Include the app version, operating system, hardware model, source protocol, selected audio routes, and relevant error text.
The curated report omits raw errors, network addresses, and personal station data. Supply only the additional details needed to reproduce the problem. Remove credentials before sharing screenshots or error text.