Hi HomePod Fans,
I read of an solution for roon, like this
-put every HP in an seperate Zone
-set an DSP, Speaker Setting, Mute channel Left on One
-set an DSP (same, but Mute channel Right) on the other.
-put both in a new Zone/Group !
Play your music on this „combined“ Zone!
How good the sound stage will be, you have to check…
Hi Bill,
you can set every device on „Max Volume“ and manage the volume for the HP-Zone on the main
roon page for the hole zone.
I tried it once and could not live with a delay on some device, all Airplay, but my Mains are managed thru a Trinnov Room Prozessor (about 150ms delay) … This delay could be defined with the DSP distance settings for a HP Device. Thats twiddeling a lot, but could work.
Airplay2 is only available an iOs or MacOs devices it won’t run on Windows or Linux, Roon is mulitplatform and therefore a good chunk of its user base could not use the feature. Roon supports Airplay as there was open source code developed that reversed engineered the Airplay stack to allow non Apple devices to act as sender’s. Currently there isn’t one for Airplay 2. Some group has been attempting it for 3 years nearly and still not got it reliably working it’s also limited to being a receiver not a sender. For it to work in Roon it has to be an Airplay 2 sender. Roon wont be writing this code them selves as it leaves them open to legal action, hence why they use open source code for Airplay. So unless Apple develop an API that’s cross platform for Airplay2 forget it, they are a walled garden.
Having just got a stereo pair of HomePod mini’s, I suddenly understand what all the Airplay 2 fuss is about. The left/right grouping hack doesn’t work for me, Airplay 2 is a Roon requirement.
Roon Labs should just accept that this feature (AirPlay 2 sending) can only be provided when the Roon Core runs on a Mac: then they can use Apple’s official native Mac-only libraries to implement it. No hacks, no license violations, end of story. It will make Mac users happy, who with higher probability are those wanting to send to stereo pairs of HomePods.
That use case is covered already: set sound output on the Mac core to the paired HomePods and choose the core’s system output as zone. Works perfectly well (you can do the same with any macOS or iOS remote).
And divides the user base. They don’t release platform specific features and I fully agree with that policy. Why should a user pay for a feature to be developed they can never use without buying into another eco system. It’s very different to having a feature you may not use because you have no interest in using it or it doesn’t appeal it’s still there as an option.
i’m sure Roon Labs approaches this much more pragmatically: as a decision to invest in a feature that a subset of their customers are asking for because it is quite important for their Roon usage (knowing that the feature will be useless to another subset of their customers).