@chervokas exactemundo!
- ...
- 46 posts total
When using the Qobuz integration with Roon, the Qobuz stream is downloaded to the Roon server and then dispatched via RAAT (Roon's own protocol) to the Roon endpoint (i.e. streaming device). It has to work that way because Roon supports DSP processing of streams (for Room correction, conversions, filters, etc). That happens whether the DSP features are or are not enabled. |
Lots if streamers do DSP too, everything from room correction to volume control, but of course the DSP is local in the streamer after the data comes in from the cloud server. The processing isn't done to the data packets coming from the cloud server, it's being done to the audio data after it's received. |
@chervokas Yes, I understand that. I'm just telling you how Roon works. Once the data stream hits the streamer it's too late for the Roon DSP processing, so that's why Qobuz via Roon has to have the path: Qobuz server -> Roon server -> streamer. I use Roon, but none of it's DSP features. My Roon endpoint is a Weiss DAC501-MK2. It has a bunch of DSP features, but I don't use any of them. I don't even understand most of them. The manual is written for pros. LOL |
@dwette Got it. So does Roon even support any "Connect" service? I gotta say, for the way I listen to music, I don't have any use case for Roon and I don't like the idea of a paying a SaaS sub fee just to be able to play local music in my own home, so I have no personal experience with Roon and have never had occasion to look into its protocols. |
- 46 posts total

