Skip to guide
← Tool guides

Audio, explained · 33 / 36

Network Send

Send one branch to another AudioRouter PC over UDP.

Visual walkthrough3 configuration controlsSynced audio walkthrough
See how it works ↓

Consumes graph audio and transmits only to the configured address.

01 / Understand

The idea, before the settings.

Network Send waits for Network Receive in a second AudioRouter session on PC B, another computer. Both nodes name the other PC and use the same UDP port and pairing key. After pairing, audio packets cross the IP network into PC B's route.

PC A source → SendNetworkPC B Receive → Output

Use it in AudioRouter

  1. On PC A, connect a source to Network Send and enter PC B's literal IP address.
  2. On PC B, add Network Receive with PC A's sender address and connect it to an output.
  3. Match the UDP port and privately copied generated pairing key on both PCs.
  4. Save and Play both routes, then inspect receiver activity and output.

What success looks like

Pairing precedes packet flow. The receiver is another AudioRouter on another PC; the sender running does not prove successful reception.

If it does not work

Check address direction, matching port/key, firewall access and receiver state before increasing buffers.

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.

The first 2.4 seconds show pairing with no received audio. Then a delayed copy crosses the illustrated network to PC B. This is a local timing model with no packets or remote connection.

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

Receiving computer’s IP address

host

Enter the destination PC IPv4 or IPv6 literal. Host names are not resolved.

Range / choicesDepends on your selectionDefaultChoose explicitly

Try thisIf the second PC is 192.168.1.42, put that address in Network Send.

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

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.