I have that use case stable and working really well. The sound is very good. But, it can be a lot better by using the poly as renderer. I know this because I have been connecting the mojo directly to my blue sound node 2i and the sound is glorious. I am so close. With 8player my only issue is logging into tidal from the poly. From mconnnect, it cannot see the poly as renderer.
Ex poly user , and now a Hugo2 /2go user
same issues . Workarounds are...
1) mconnect is flakey to see the chord at the best of times . I got a WiFirepeater to boost the signal in the room it’s in (attic) which gives me about a 70% success rate of finding the chord as a device first time . If not I just put my phone in AirPlane mode and close mconnect and then start again. Seems to be WiFi signal and luck dependant.
As for Tidal . I remember when I first got a poly and tidal login on Gofigure was fine and the qobuz one wasn’t , and qobuz later issued an update on their systems which resolved it allowing the chord to connect.
However now I’m a Hugo2/2go user , the Gofigure qobuz settings are fine and I can get the 2go to do all the streaming work but the tidal side just comes up with the usual service error.
obvs the work around is to use the native mconnect tidal login and the mconnect tailored tidal front end , it’s ok, and outputs MQA untainted. (Not that the mojo you have would see it)
the mconnect qobuz front end is also bespoke and is ok , and I would say it is way quicker than using the browser to open the qobuz directly on the 2go . I guess that’s a measure of the processing power of my iPhone 8 being better than the chord .
The drawback being if I walk out the room with my phone and WiFi goes wobbly , or mconnect goes into it’s own self standby , it all goes messed up .
There’s no easy solution - I had limited success with the Linn app but it was a lot of hassle