Streaming to passive speakers: how to build a network audio chain that actually works

Most of the room-acoustics problems I'm asked to diagnose start with a speaker placement issue. But lately, a different kind of call has been coming through more often: someone's built what looks like a sensible passive hi-fi system around a network streamer and they can't work out why it sounds flat, or inconsistent between rooms, or just quietly wrong. The boxes are fine. The chain between them isn't.

Passive speakers are still the default choice for serious listeners — more variety, better value at most price points, and a longer useful life than most active or wireless alternatives. But streaming audio to them involves a chain of decisions that all-in-one and active systems handle invisibly. When you DIY the chain, every link matters.

What the chain actually looks like

Before anything else, it helps to be clear about what a passive streaming setup actually involves. At minimum, you need: a source device (a phone, tablet, NAS, or dedicated streamer), a network transport protocol moving audio data from that source to a playback device, a DAC converting the digital signal to analogue, a preamplifier stage setting the volume and output level, a power amplifier driving the speakers, and finally the speakers themselves and the room they're in.

In an integrated amplifier with built-in streaming — something like the Marantz Model 40n (check price) or the Naim Uniti Atom (check price) — several of those links collapse into a single box. That's not a compromise; those machines are genuinely good. But plenty of people have existing amplifiers and speakers they're happy with and want to add streaming to, or they want to separate the functions deliberately. That's where understanding the chain pays off.

Choosing your streaming protocol: this decision matters more than the hardware

This is the part most buyers skip. They'll spend weeks agonising over a DAC and five minutes picking a streaming protocol. That's backwards.

The three main contenders for passive hi-fi setups in Australia are Roon (with RAAT transport), UPnP/DLNA, and proprietary ecosystems like Naim's N-Streaming platform, Cambridge Audio's StreamMagic, or Linn's Kazoo/Songcast. Each has meaningful tradeoffs — and if you're curious about the detail of how they compare sonically and architecturally, we covered that properly in our Roon vs UPnP vs proprietary apps guide.

The short version for passive-speaker builders: if you're running a single-zone setup centred on one streamer, proprietary often wins for reliability and sound quality, because the manufacturer has controlled the entire signal path from network to analogue out. If you have multiple sources, multiple zones, or you want library management, Roon becomes worth the subscription cost. UPnP is free and works, but it's the least consistent of the three in practice — bit-perfect delivery depends on both the server and renderer software behaving themselves, and they often don't.

What I'd avoid: treating the streaming protocol as an afterthought, bolting on a cheap Chromecast Audio or an AirPlay dongle to a serious DAC, and then wondering why it doesn't sound as good as your mate's dedicated streamer. The network transport is doing real work. Treat it accordingly.

The DAC question — and when a dedicated unit actually earns its place

If you already own a network streamer, it almost certainly has a built-in DAC. The Cambridge Audio CXN100 (check price) is a good example — its ESS Sabre-based DAC is genuinely competent, and for most systems it's the right call to use it. Adding an external DAC downstream just to say you've done it is a purchase that rarely pays off acoustically.

Where a separate DAC does earn its keep: when you're running multiple digital sources into a single high-quality conversion stage; when your streamer is a Raspberry Pi–based DIY unit or a budget renderer with a clearly average onboard DAC; or when you're moving into a price bracket — roughly above $1,500 for the DAC alone — where specialist conversion genuinely outperforms the integrated option. Our roundup of DACs and network streamers goes into this in depth if you're at that decision point.

One thing I've seen go wrong repeatedly: people adding an external DAC but connecting it via a poor-quality USB or optical cable run across the room. If the galvanic isolation or clock recovery on the DAC input isn't up to scratch, the interface can introduce more noise than the original onboard DAC produced. The DAC's input stage matters as much as the conversion stage. Check the manufacturer's recommendations on preferred input before you assume optical is automatically safer than USB.

Amplifier matching: the passive speaker's real requirement

This is the part I care most about — not because amplifiers are endlessly interesting on their own (they're not always), but because a mismatch here is audible in ways that a suboptimal streaming protocol usually isn't.

Passive speakers need current. Sensitivity and impedance specs give you the starting numbers, but they don't tell the whole story about how a speaker loads an amplifier under dynamic conditions. A nominal 4-ohm speaker that dips to 2.7 ohms at 80 Hz is a fundamentally different proposition than a nominal 4-ohm speaker that stays above 3.5 ohms across its whole range. We've covered the arithmetic behind this in the sensitivity, impedance and power matching guide, and it's worth going through if you're pairing a network streamer's integrated amp section with speakers rated at or below 85 dB sensitivity.

The practical upshot for streaming setups: if you're using a streaming integrated amplifier rated at, say, 50 watts into 8 ohms, check what it does into 4 ohms. Good designs double down; mediocre ones clip early or limit output. A speaker like the KEF LS50 Meta (check price) is a genuinely demanding load despite looking like a small standmount, and it will expose an underpowered or high-output-impedance amplifier section in a way that a more benign speaker won't.

Network infrastructure: less glamorous, more important than you think

I'll be direct: I've been in listening rooms on Glenmore Road in Paddington and in purpose-built home-theatre spaces in Toorak where the streaming chain was unreliable because the Wi-Fi infrastructure was undersized. A $4,000 streamer on a congested 2.4 GHz network shared with seven other devices is going to drop out, buffer, and occasionally deliver mangled audio. None of that is the streamer's fault.

The standard recommendation is Ethernet where possible. Our Wi-Fi vs Ethernet guide unpacks whether the cable actually changes the sound (less clear-cut than the forums suggest) versus whether it changes reliability (it does, consistently). For passive speaker setups in serious listening rooms, I'd treat a wired connection as the baseline, not a luxury.

If you're running multiroom zones — some wired, some wireless — the reliability gap between zones becomes a real management problem. Mesh systems help, but they introduce their own timing and latency considerations. If tight synchronisation between zones matters to you, a wired backbone with Wi-Fi only at the endpoints is worth the installation effort.

Volume control: where the signal path gets messy

In a streaming-to-passive setup, volume can be controlled at several points: in the app (digital attenuation in the source), in the streamer's digital domain, in an optional preamplifier stage, or in the power amplifier's input sensitivity control. Every one of those options has a different sonic consequence, and most people never think about it.

Digital attenuation in the source — adjusting volume in Spotify, Tidal, or a streaming app — is generally the worst option for a high-quality passive system. At anything more than a few dB of reduction, you're discarding bits and reducing the signal-to-noise ratio before the DAC has even seen the data. The exception is if your system uses a properly implemented volume control operating on a high bit-depth word before truncation — Roon's volume levelling does this reasonably well when configured correctly, and some streamers implement DSP volume with genuine care.

The cleanest chain for a passive system: fixed digital output from the streamer (bit-perfect to the DAC), analogue volume control in a dedicated preamplifier or in the integrated amp's analogue stage. That keeps the digital domain clean and puts volume control where it belongs: in the analogue signal path, after conversion. It's not always possible with compact or integrated streaming solutions, but it's worth pursuing when you're building a separates chain.

I'll admit I got this wrong for a couple of years. I was running volume from the app on a system I should have known better about, and I assumed the slightly soft dynamics were a speaker-room problem. They weren't. The short version is: check where your volume control is actually operating before you start blaming the room.

File formats, streaming quality and what passive speakers actually hear

High-resolution streaming — 24-bit/96 kHz or higher from Tidal, Qobuz or Apple Music in lossless — is genuinely worth having if the rest of your chain is up to it. But the argument about whether 24/192 sounds better than 24/96 is largely irrelevant to how a passive speaker system performs. Your speakers, your room, and your amplifier's ability to control the driver under dynamic load will swamp any difference at those sample rates.

What does matter: making sure your streaming service isn't silently downsampling. Qobuz and Tidal (via FLAC or MQA-free delivery) both pass full-resolution content to a capable renderer. Apple Music's lossless tier is 16/44.1 ALAC at base level, scaling up through 24/48 and then to hi-res ALAC — but the hi-res tier requires a DAC that can receive it, which isn't guaranteed through every connection type. Check your renderer's actual output format, not just what the app claims to be sending.

The honest position on lossy streaming — AAC at 256 kbps or Spotify's highest-quality Ogg Vorbis — is that on a revealing passive system with treated acoustics, there are tracks where you'll hear the compression artefacts, particularly on sparse, well-recorded acoustic music. On a less-resolving system or a bass-heavy mix, probably not. Whether that justifies the lossless subscription premium is a personal call. For me, with a system I've spent genuine time optimising, yes.

Putting it together: the order of decisions

If I were building a streaming-to-passive-speakers chain from scratch, this is the sequence I'd follow. First, fix the room and speaker placement — nothing downstream compensates for that. Second, choose the amplifier for the specific speakers, not the other way around. Third, decide whether to use a streaming integrated or separates. Fourth, pick the streaming ecosystem before buying any hardware, because some streamers are locked to their own protocol. Fifth, add an external DAC only if the streamer's onboard DAC is genuinely the weak link, which it often isn't above the budget tier.

The gear list doesn't drive this. The chain logic does. A well-matched, well-placed passive system fed by a competent network streamer will outperform a more expensive system that's been assembled without thinking about how the signal travels from the network to the driver cone. That's not a theoretical claim — it's what I hear, room after room, every time someone's upgraded their way into a problem they didn't need to have.

The best reference I'd point you to for the technical underpinning of network audio transport is the AES E-Library, which has published research on jitter, clocking and digital transport quality that's worth reading if you want the engineering behind the listening. And if you're evaluating which streaming-capable integrated might anchor your passive setup, our best streaming amplifiers guide covers the current field in detail.

— Hannah Reid, Loudspeakers & Acoustics Editor