Install, connect, and check desktop audio

On this page
  1. Install and make the first start
  2. Connect to a radio through this computer's Core
  3. Connect to another computer's Core
  4. Inspect a saved Core and the actual connection path
  5. Start a Core service on this computer
  6. Choose this computer's receive and transmit audio routes
  7. Choose audio quality for this window's Core connection
  8. Choose whether a saved target connects at startup
  9. Recover a lost connection

This chapter gets the desktop client to the intended radio and confirms that receive audio and a microphone route exist. It covers the radio target for this window and audio devices attached to this computer. To host a Core for phones or another desktop, see Share a Core with other devices. For transmit setup and a controlled on-air check, continue to Set up and transmit.

Install and make the first start

Download the package matching your operating system and processor from the NereusSDR releases page, and use that release's notes for package-specific requirements. On macOS, install from the DMG or PKG and launch NereusSDR from Applications. On Windows, run the x64 installer or extract the portable ZIP and keep its files together. On Linux, make the AppImage executable and launch it. If a platform's package manager or security prompt blocks launch, resolve that operating-system prompt before diagnosing radio discovery.

The first local launch may show NereusSDR: FFTW Wisdom while it creates optimized DSP tables. Allow this one-time work to finish; closing the application interrupts startup and the next launch may repeat it. The wisdom cache is local to this computer. It is not a radio setting and does not travel with a saved radio entry. If a later release changes the DSP build, a new wisdom pass may be needed. First-start time varies with the computer, so the progress display is the readback; there is no fixed completion time to promise.

Before connecting, power the radio and attach it to the network. A local desktop needs network reachability to the radio. A remote desktop needs reachability to the Core computer, while that Core computer needs reachability to its radio. The desktop's Connections picker chooses this window's target; it does not start the Core service on another computer. Open it through Radio > Connections… in a picker-managed window. Windows using the local radio panel call that command Manage Radios…; a dedicated remote window can instead open This Core. The connection procedures below use the picker name where applicable.

Connect to a radio through this computer's Core

  1. Open Radio > Connections…. This opens the Connections picker. In a normal local window, its This computer's Core row means that the local Core is selected as the operating context; it is not itself a radio. Select a radio under Radios on this network. If the list is stale, press Scan and wait for discovery to refresh. The window stays usable while it searches. Discovery pauses while a radio connection starts and for about 3 seconds after a connect or disconnect, so the list can fill in a few seconds late. The picker's columns can be resized by dragging their dividers; hover a cell to read its full text.
  2. Select the radio row and press Connect. If the model or address is not discovered, use Add Radio…, enter the radio address and model requested by the editor, save it, then select the saved row and connect. Check the address and model against the radio/Core information you have; a saved row is only a target record, not proof that the endpoint is reachable.
  3. The picker closes by itself once the radio you chose connects. While the attempt is pending, or if it fails, the picker stays open so you can read why. To check the result later, reopen Radio > Connections… and read Current connection. For a radio on this computer's Core it reads Connected using this computer's Core, followed by the radio's IP address and port; it does not show the radio's name, so confirm the radio from the address. Wait for the panadapter trace to update. Open RX or select the active VFO's audio controls and unmute a suitable output; a moving spectrum alone confirms data, not that the selected speaker is audible.

Some desktop windows present Connect to Radio directly instead of the full picker. In that dialog select a row under Discovered Radios, use ↻ Scan to refresh, or choose Add Manually... to enter a target, then press Connect. The dialog's own Connected state is the readback. Follow the labels actually displayed by the window.

The selected target is saved so the application can reconnect to it. If you need a different radio, reopen Radio > Connections…, select the other row, and connect. Use Edit… to correct a saved target and Forget… to remove a saved entry you no longer use. Forgetting removes the saved target from this computer's picker; it is not a factory reset of the radio. Do not use the standalone Radio > Connect action to choose a different target: in an ordinary local window it reconnects to the last-used saved radio. Radio > Disconnect ends the current radio link. In a picker-managed window, Connect opens the picker workflow.

Connect to another computer's Core

Use this route when another computer owns the radio connection and DSP. In Radio > Connections…, select a paired Core under Your Cores, or choose a nearby entry under Cores on this network. The selected row's action may read Connect or Pair. For first-time pairing, use Add a Core by code… and enter the code shown by the Core, or Type an address… when you were given a network address. A pairing code is an enrollment credential; enter it only for the Core you intend to trust.

After pairing, select that Core and press Connect; the picker closes once the Core signs you in, even if the Core's radio is offline. Before operating, reopen Radio > Connections… and confirm the Core's name and connection state in Current connection; the radio is remote through that Core. Later, Radio > Connect in a dedicated remote window reconnects the window's Core target. Reopen Connections… when choosing among saved targets. Radio > Disconnect leaves the Core session. A connection attempt can fail even when the target is saved: verify that the Core is online, the address/path is current, and that the Core has remote access enabled. Retry from the picker after correcting reachability rather than repeatedly changing the radio's saved identity.

In a dedicated remote window that retains Radio > Manage Radios…, that command can open the This Core radio-management page (also under File > Settings... > General > This Core). Its Change radio section lists the radios the Core can see; Use this radio, Scan again and Forget radio act on the radio configured on that Core, rather than this computer's local radio list, and the Model: box sets the model the Core runs the selected radio as. The Radio menu carries the same three actions as Change radio…, Edit radio… and Forget radio. In a window that runs its own radio they are grayed with the reason This computer runs its own radio. Change it in Radio > Connections. or, in a window without the picker, Change it in the Connection panel (Radio > Manage Radios).; change that radio there instead. A change to the radio attached to a shared Core changes the station endpoint for its connected operators. The action can be held while transmitting, while a Core change is busy, or when the Core does not offer that operation; read the reason displayed by the page and resolve that condition first. Reconnect the window when the page says a Core radio change requires it.

Inspect a saved Core and the actual connection path

Open File > Settings... > Cores > Your Cores, or select a saved Core in Connections and click Manage…. This is the Core Settings area. Selecting an entry for inspection does not connect this window or change its target. The selected Core has Overview, Addresses, Radio and Devices tabs.

  1. Select the intended saved Core and read Overview > Connection in this window. Status tells you whether this window is connected to that Core. Reached through, Controls, Audio and display, Core listener IP and Radio report the available current-session facts. Controls and media may use different paths. A retained address is a candidate for a connection, not proof of the path currently in use.
  2. Open Connection details… or Diagnostics… for this window's live connection evidence. Audio with the Core… also concerns this window's current Core, even when the saved entry being inspected is a different Core. Check that context before changing audio quality.
  3. Use Radio and Devices to administer the inspected Core only when this window is connected to it. Otherwise these tabs explain why their actions are unavailable. Changing its radio restarts the station connection and affects connected windows/devices; coordinate first and wait for reconnect.

Retain a direct address for a paired Core

Use this when the already paired Core has a reachable listener on a LAN or VPN, or its known listener address has changed. It is separate from adding or pairing a different Core.

  1. Select the saved Core, open Addresses, then choose Add address…. Enter Hostname or IP address and Core connection port, using the Core listener's details. IPv4, hostnames and IPv6 are accepted; IPv6 can be entered with or without brackets. The radio's IP and the RV service's address are different endpoints.
  2. Click Add and wait for the identity check. The address is saved only when the answering endpoint is verified as this paired Core. A refusal leaves it unsaved; correct the address/port and use the offered Retry.
  3. Confirm it appears under Added by you. Up to four manual addresses can be retained. Previously worked is a separate successful-connection history of up to four; Supplied by the Core is its reported inventory, which may contain addresses this computer cannot reach. One row can carry several of these labels. An address the Core stops naming, including when it reports that it has none, leaves Supplied by the Core and Previously worked. The one this window is connected on goes once a connection on another address is made. Addresses you added stay.
  4. Changes apply to future connection attempts. They do not switch the current connection or mark a newly retained address as previously successful. When ready to reconnect, use Connections, select this Core and verify Overview again after it connects.

Use a manual row's Edit… to correct it. Remove asks to remove its manual retention; the same address can still remain in the automatic sources. Read the confirmation, then verify the row's labels. Removing retention does not terminate this window's connection or revoke its pairing.

Rename the Core for all devices

In the selected Core's Overview, choose Rename Core…. Enter the callsign and optional /name using the characters and length described beside the field, then press Save. This changes the name on the shared Core. It is not a private alias on this computer.

Wait for acceptance and check the displayed name. The desktop can use an eligible existing authenticated session or a temporary sign-in to a reachable paired Core. It needs this computer's existing device key; the page explains missing pairing/key, incompatible administration, a connection retry or a rename session still closing. Cancel or correct the reported condition before retrying. If the Core accepted the name but saving its local presentation failed, follow that message and verify the actual Core name rather than issuing a second rename merely because the saved label has not caught up.

Start a Core service on this computer

To host a local radio for phone/tablet clients or remote desktop clients, connect this desktop to the local radio first, then open File > Settings... > CAT & Network > Remote Access. Under Core on this computer, enable Run a Core on this computer. The Core section reports the Core name and reachability. Keep it running when NereusSDR is closed and Start it with the computer control the service lifecycle beyond this application session; enable them only when that persistent behavior is intended. The Connections… button on this page only opens the target picker. It does not enable the Core.

Use Rename to give the Core a recognizable station name. For phone enrollment, use Add a device or provide the current pairing code shown on the page. Codes rotate and should be read from the current Core page. Paired devices lists enrolled devices; Connected now reports active sessions. The key-backup section gives its own file location and I've backed it up acknowledgement. Follow the displayed backup instruction and store that Core key safely: ordinary desktop settings export is not a substitute for a Core key backup. If the Core controls are disabled, the page states why, for example that no local radio is connected, a Core change is in progress, or the station is transmitting. See Core sharing and device management for pairing, ownership, and revocation procedures.

Choose this computer's receive and transmit audio routes

Open File > Settings... > Audio > Outputs. The Sound system line at the top names what this computer plays through: Core Audio on a Mac; Windows audio (WASAPI) on Windows, which becomes Windows audio (WASAPI) and ASIO () when an ASIO driver is in use; and on Linux PipeWire. NereusSDR talks to it directly. or, when PipeWire was not found, PulseAudio. PipeWire was not found, so NereusSDR talks to PulseAudio directly. If neither is running on Linux it reads None found. Start PipeWire or PulseAudio, then click Rescan devices. If a card uses an older driver, the line adds Older drivers in use: and their names.

The page has a card for each output. This computer is the speakers: set Volume, Mute and Device here. It is the same control as PC in the header. Headphones is a separate destination; tick Enabled to use it. The PC volume does not change the headphones. Radio speaker is the radio's own speaker output: in a local window its note begins Same control as RADIO in the header. and it adds a Speaker amplifier: choice of Normal, Off while transmitting or Always off, which is grayed with its reason when the radio has no speaker amplifier to switch. In a window connected to a remote Core a Core speaker card sits between them; see the Core speaker. These are this computer's output routes. They do not choose a radio input or change another connected device's output.

Desktop Outputs page with the Sound system line and the This computer, Headphones and Radio speaker cards

Audio Outputs in the workspace look, rendered offscreen on a Mac with no radio connected. The Driver box is grayed because Core Audio is the only choice there. Rescan devices is grayed with its reason beside it. Both Device details sections are collapsed.

Pick the driver, then the device

On each card, Driver sits directly above Device and is always showing. Device details, below them, holds the sample rate, bit depth, channels, buffer size, Delay and Negotiated. Driver lists only what exists on this computer, and a choice that does not apply is grayed with its reason when you point at it.

System Driver list
Mac Core Audio, grayed: The only sound system on the Mac.
Windows Windows audio, shared, Windows audio, exclusive, ASIO (grayed with No ASIO driver is installed on this computer. when none is installed), then the older drivers under Older drivers: MME, DirectSound and WDM-KS.
Linux desktop PipeWire; PulseAudio is listed only while PipeWire is not running. A sound system that is not running reads PipeWire (not running) or PulseAudio (not running), grayed with is not running on this computer. Older drivers (JACK, ALSA) follow under Older drivers.
Headless Linux Core ALSA, direct, grayed: The Core runs without a desktop, so it plays straight to the sound card.

Windows exclusive adds the note Other apps cannot play through this device while NereusSDR has it. An older driver adds An older driver: more delay, and its list updates only with Rescan devices. Prefer the system's own engine unless a device only works on an older driver.

Device follows the chosen driver. (platform default) is first, then each device the driver reports. A device with more than two channels lists each pair as its own entry, grouped under the interface, for example Outputs 3-4. A device you plug in or remove appears or disappears within about a second, with no Rescan and without interrupting sound on another device.

If the device you chose is gone, speakers and headphones keep playing on the system default and the card says so in amber:

The choice is never changed for you. It moves back when the device returns. The list entry reads (not connected) or (in use by another program) until then. With no other device to fall back on the card says is not connected. and sound stays silent.

If two cards choose the same pair of an interface, the page says Speakers and headphones are on the same pair, so they play together.

Delay and ASIO details

Delay is Automatic or 2, 3, 5, 10, 20 or 40 ms, with a live readout such as Now 25 ms from the radio to . It reads Now -- ms until a stream plays. Automatic lets NereusSDR pick the delay; the fixed values set it yourself. Check Negotiated for the format the engine actually opened.

On ASIO, Buffer size and Sample rate belong to the driver and are shared with every role on that driver. A line says Buffer size and sample rate are shared with , on the same ASIO driver. A buffer size the driver fixes shows Set in the ASIO control panel, and ASIO control panel opens the driver's own window; it is grayed until an ASIO driver is chosen, with ASIO drivers are Windows only. as its reason outside Windows. After a driver change the card says Restarted with the driver's new settings. A driver whose sample format NereusSDR cannot play or record says uses a sample format NereusSDR can't play or record. and its pairs are grayed.

NereusSDR uses one ASIO driver at a time. If you pick a pair on a second driver, One ASIO driver at a time lists the other roles that move with it. Switch all to moves them all; Cancel keeps everything as it was. To keep a device where it is, cancel and give it a Windows audio device or cable first.

Rescan devices

Rescan devices matters only for the older drivers. Their lists update only when you press it, and their streams close and reopen. The note beside it says so: Only the older drivers need this. plus which lists update by themselves. On the Mac it is grayed and reads Core Audio lists update by themselves, so there is nothing to rescan.

Choose the microphone

Computer playback and microphone capture are separate from the radio's speaker output. Open File > Settings... > Audio > Microphone, choose PC Mic, and set the PC microphone card: Driver, Device and Mic is on: Left, Right or Both, which is grayed with its reason when the mic is off or has one channel. The Delay line reads Now N ms from to the radio. The page shows capture status and Retry microphone if the stream failed. See Set up and transmit for the mic test, gain, TX ownership and keying sequence.

A microphone that is missing or held by another program never switches to another mic. The card says is not connected. The mic stays silent until it comes back; NereusSDR never switches to another mic on its own. (or is in use by another program), and capture resumes by itself when the device returns. The TX applet's badge reads PC mic not connected or PC mic in use by another program in amber.

A Bluetooth headset switches to phone-call quality, for listening too, while it is your mic. When you pick one by name the card says Bluetooth headsets switch to phone-call quality, for listening too, while they are your mic. For the best sound, listen on and talk on a wired or built-in mic. NereusSDR never opens a Bluetooth mic unless you pick it by name.

Choose cables for digital modes

Open File > Settings... > Audio > Digital modes. The VAX part has a card for each of VAX 1 to VAX 4.

Rescan at the foot of the VAX list looks again for cables. Detected virtual cables names what was found. On Windows the first-run window Set up VAX channels appears in one of two forms. When cables are found it offers Apply suggested, Customize… or Skip. When none are found it offers Why do I need this? and Continue without VAX, and an Already have one? card with Rescan now to use after you install one. If NereusSDR later notices a new cable, the window Virtual cables detected offers Skip for now and Apply to VAX N & M (for example Apply to VAX 1 & 2 when two cables are new); it falls back to Apply suggested when nothing can be bound.

Desktop Digital modes page with the VAX 1 to 4 cards and the TCI audio settings

Digital modes in the workspace look, rendered offscreen for the native audio build on a Mac. No VAX channel is on and no program is using one. Each card's Used by line reads Not reported on this computer here because no program had opened a channel.

Used by: reads An app is reading this channel or No app is reading this channel where the system reports it. See Digital audio and external applications for routing a slice to a channel.

If Linux audio will not open, Help > Diagnose audio backend… (present only on Linux) is the available Linux-specific diagnostic. It reports backend information and provides a starting point for checking PipeWire or PulseAudio selection; it is not a general connection test. For broader link diagnosis, use Tools > Network Diagnostics... after the radio or Core target has been selected.

Choose audio quality for this window's Core connection

Open File > Settings... > Cores > Audio with the Core, or use the matching button in Your Cores > Overview. Check the heading naming this window's Core; inspecting another saved Core does not redirect this page.

  1. Under Audio quality, choose High (48 kbps), Save data (24 kbps) or Lossless when available. This preference is saved on this computer and applies to received Core audio and this computer's microphone uplink. Lossless needs about 1.6 Mbit/s and can fall back to Opus when the link cannot carry it. The requested choice alone is not proof of the actual format.
  2. Read Receive from Core for the current format/health and the measured Received audio payload rate. No measurement or an unavailable reason means there is no current evidence to interpret as a working stream.
  3. Read Microphone to Core separately. Radio Mic at the station has no microphone stream from this computer; see TX input. Receiver audio for apps reports requested application streams, whose compressed streams keep their separate 48 kbps target.
  4. If receive media failed while controls still work, use Retry audio when enabled, wait for the health readback, then check local playback/mute and actual receive sound. Changing an OS speaker device and retrying Core media address different parts of the path. After a speaker fault the window asks the Core again on its own until the speakers play, so you do not need to mute and unmute. A device set to a format remote playback cannot play (channels, sample rate or sample type) says so and waits until you change it.

Choose whether a saved target connects at startup

After successfully saving/connecting the intended target, open File > Settings... > General > Startup & Preferences and set Auto-connect to last radio. Read its tooltip to confirm which target it names. The first time you connect to a radio, Auto-connect is turned on for it; after that, connecting keeps whatever you chose. In a local window it saves the last radio's launch choice; in a dedicated remote window it saves the selected Core target's choice on this computer. It does not start a Core service or change another computer's startup policy.

If the toggle is disabled, connect/save the target first and reopen the page; the reason distinguishes a missing saved radio from a missing Core target. Check the choice remains set when revisiting the page. On a later application start, verify the connected identity before operating. If the saved target is unreachable, use the normal Connections workflow to correct/reconnect it; the startup flag does not repair a route. Clear the toggle to return to deliberate connection at launch.

Recover a lost connection

When the link drops, inspect the title/status area and reopen Radio > Connections…. Read Current connection for the target and progress or failure detail. If a retry is already running, wait for its state to change. Use Radio > Connect to retry the last-used target in a normal window, or select the intended saved target in Manage Radios…. A stale radio IP is corrected with Edit…; a remote Core address or pairing issue is corrected in the Core target editor. If radio discovery is empty, verify the radio is powered, on the same reachable LAN/VLAN, then scan; for routed or VPN networks, use the saved/manual address rather than relying on broadcast discovery.

After reconnection, confirm the connected target again, then confirm a live panadapter trace and audible receive output. Shared Core settings and radio state may have changed while this client was away. Before transmitting, recheck the selected TX slice, transmit holder, microphone source, antenna, power, and the protection/readiness message as described in the transmit chapter. If the Core itself is reachable but its radio is not, the radio operator on that Core must restore the radio link; changing local playback devices will not repair the station connection.

In a window connected to a Core, Audio and display: Audio from the Core stopped. Starting audio and display again. or Audio and display: The display from the Core stopped. Starting audio and display again. means the window lost the Core's audio or display and is restarting both by itself. Muting, unmuting or a failed speaker on this computer does not cause this.