Skip to guide
← Tool guides

Audio, explained · 34 / 36

Network Receive

Receive audio from one selected AudioRouter PC.

Visual walkthrough4 configuration controlsSynced audio walkthrough
See how it works ↓

Accepts the configured sender address and plays through a bounded jitter buffer; missing packets become silence.

01 / Understand

The idea, before the settings.

PC B’s Network Receive waits for Network Send in a second AudioRouter session on PC A. It accepts only the configured sender address, UDP port and matching pairing key, then plays packets through a bounded receive buffer. A larger buffer adds a little delay and tolerance for packet timing variation; missing packets become silence.

PC A source → SendNetworkPC B Receive → Output

Use it in AudioRouter

  1. On PC B, enter the literal address of the sending PC in Sender and choose the receiving UDP port.
  2. Match the sender's port and pairing key; connect Receive to a local output.
  3. Save and Play both PCs. Begin with Buffer 40 ms and inspect incoming activity.
  4. Increase Buffer only if timing variation causes gaps; recheck the added delay.

What success looks like

Only the configured sender/key feeds this source. More buffer trades latency for tolerance to packet timing variation.

If it does not work

No received packets usually means address, key, port or firewall; a larger buffer cannot fix mismatched pairing.

Select the node to open Properties. Click its name to rename it. While playing, supported parameter-only edits save after a short pause. For structural edits, use Save when the canvas marks a change. Enabled and Bypass are distinct live controls; see the in-app help for their behavior.

02 / Explore

Make the behavior visible.

Pairing completes before received sound starts at PC B. Increase Buffer and compare with the sender reference to hear the extra local simulated delay; no real network is used.

The example repeats until you press Stop, and control changes are heard immediately. The picture shows the tool's shape rather than time; follow the timing in Follow the sound below. This is not a DSP measurement or control for your running AudioRouter session.

03 / Configure

Every control, with a reason.

01

Sending computer’s IP address

sender

Enter the source PC IPv4 or IPv6 literal. Audio from other addresses is ignored.

Range / choicesDepends on your selectionDefaultChoose explicitly

Try thisIf the first PC is 192.168.1.21, put that address in Network Receive.

Keep in mind Use the actual network address shown for the other PC; do not exchange source and destination.

02

UDP port

port

Identifies the receiving UDP listener. Set the same port on both nodes.

Range / choices1 → 65535Default47800

Try thisKeep 47800 on both PCs for a single stream.

Keep in mind A firewall or another listener can prevent delivery.

03

Receive buffer

bufferMs

Keeps a small amount of audio ready to absorb packet timing variation. More buffer adds delay; less leaves less margin before gaps.

Range / choices10 ms → 500 msDefault40 ms

↓ Lower / alternativeReduces buffering delay but leaves less tolerance for packet timing variation.

↑ Higher / alternativeKeeps more incoming audio ready, adding delay and margin for jitter.

Try thisStart at 40 ms. Increase to 80 ms if a busy local network produces gaps.

Keep in mind This changes network buffering, not microphone capture latency.

04

Pairing key

pairingKey

Use the same generated key on both nodes to authenticate packets. Blank is unpaired; printable ASCII only, without outer spaces.

Range / choicesDepends on your selectionDefault

Try thisUse Generate, then privately copy the resulting key to the other node.

Keep in mind Pairing does not encrypt audio. Use a trusted local network. Never include a real pairing key in examples or diagnostics.

04 / Put it to work

Start with a useful example.

Example 1

Connect two PCs

  1. On the first PC, connect a source or mix to Network Send.
  2. Enter the second PC address; on that PC add Network Receive with the first PC address.
  3. Match port and generated pairing key. Connect Receive to an output, Save and Play both routes.
Example 2

Resolve waiting for audio

  1. Check source and destination addresses are in the correct fields.
  2. Check port and pairing match, including whether either key is blank.
  3. Inspect node counts and firewall access; a running sender alone does not prove reception.

These are starting points. Compare at a comfortable monitoring level and adjust for your own source.

05 / Get unstuck

Small details that matter.

  • A matching pairing key authenticates packets but leaves samples unencrypted.
  • Host names are unsupported; enter literal IP addresses.
  • The receiver buffer trades delay for resilience.