To preempt the inevitable “Why doesn’t my dCS appear on Qobuz Connect?”, or “Why does dCS take so long to appear in my Qobuz App”.
Qobuz doesn’t publish how its Connect service works, so, here’s an IP-Packet flow diagram that explains exactly how the Qobuz App actually discovers the dCS, shows it as available for Qobuz Connect, and what happens when dCS is subsequently selected.
As explained previously, network discovery, whether it’s dCS Mosaic, UPnP Servers, Roon end-points, or any of the “Connect” services (Qobuz, Tidal, Spotify), they all rely on IP Multicast for device discovery.
If your dCS DAC doesn’t appear or takes a long time to appear, you probably have Multicast problems in your home network.
After discovery works as it should, thereafter, the music streaming works in the same way it does with Mosaic/Qobuz. The only difference is that instead of Mosaic instructing the dCS to fetch the tracks/albums from Qobuz Servers, it’s Qobuz Connect that instructs your dCS to fetch those tracks/albums from the Qobuz Servers.