OP
- Thread Starter
- #21
Ha! "Design brief"! : ) Flatttery will get you everywhere.Forgive me if I've misunderstood the design brief,
Chromecast is actually the limiting factor, as we're an Android household. I've looked at Ropiee and used Shairplay, but am hoping to make Pi-based elements the smallest part of the signal path I can, not for quality issues of any sort, but just general management. That said, I'll give it another look / consideration.but it seems to me that Roon driving a fleet of RPi/HifiBerry I2C DAC units running Ropieee gets you everything you've asked for except DSP correction of Airplay / Spotify guests. Ropieee offers the streaming protocols alongside being a Roon endpoint, but can't do the DSP. Admittedly, the hardware is not especially luxe looking and the Hifiberry sinad numbers aren't especially bragworthy, but it works quite nicely.
Separately, I hadn't seen the Hifiberry SINAD numbers until you prompted me. DAC+ 86 and DAC2 HD here. Sounds like this is arguing for a non-Pi-based DAC, which kind of stinks and drives the price point and space factors higher than I'd like. Hifiberry vs DAC2 thread. To me, this one is a no-brainer, as the prices are too close.
Appreciate this - the whole "what's controlling the volume" is an Achilles' heel for usability.That's basically what I do; the only bit of friction is handing off volume levels between Roon and Shairplay; the underlying Alsa process retains the last volume setting in roon as the top of the scale for Shairplay. So in practice, I stop the music in Roon, bump the zone volume up, quit Roon, and then connect to the Airplay endpoint with iphone volume low, and adjust to taste.
From a post filled with good feedback, this may be the most valuable nugget. I hadn't considered the issue of DSP-related processing delays across zones. Were you just comparing non-DSP'd zones to DSP'd zones or across zones with DSP but different processing requirements? If the latter, that would be a big deal. I'm hoping it's mainly a some DSP to no DSP comparison.With regard to clocking the whole system - It doesn't always get the marketing attention, but Roon's RAAT protocol handles network sync between zones quietly and capably. That puts the music rendering endpoints on the end of Cat6 cables (or wifi) rather than running digital or analog audio around the building on dedicated wiring. Each device adjust its digital clocking independently and imperceptibly. I gather there are non-IP standards for passing digital audio over cat6 in the professional studio world, but that's out of scope for residential use.
Finally - Be mindful of the latency for the DSP processing for each room. I'm imagining 4 different DSP correction filters might end up having different lengths / latencies, and that might be tricky to reconcile. I mention it because I've got a bunch of pi/hat stacks scattered about, but my main rig runs CamillaDSP for crossover & correction. I can't group it to other zones in Roon because the Camilla process is 'after' Roon, and so can't be automatically kept in sync. It sounds just delayed enough to be unlistenable. All the other basic realtime DAC devices group together just fine.
Again - many thanks!!