To support multiple Streaming services like Tidal and Qobuz, dCS works with airable who are a streaming services aggregator provider.
Despite Apple Music’s Musickit API framework being fairly comprehensive, they’re not currently one of the supported Streaming services from Airable; https://www.airablenow.com/b2b/services/
So, until and unless airable includes Apple Music as a service, I don’t think we’ll see dCS support Apple Music natively.
It was no contest. The Rossini is such a good streamer, using a network switch with it and streaming music via Roon sounds better than connecting a laptop via USB even if I really like Apple Lossless a lot.
Welcome aboard! Many of us have experienced the same outcome.
I must agree. Streaming from a computer does result in a hit to sound quality even if you use software like Audirvāna ( which is pretty good ).
Thanks for reply. Do you know if there is technical reason why airable does not work with Apple? Technical or maybe cost?
Yes, I think it’s about “costs”, and not so much technical. Apple Music’s API framework is quite comprehensive; https://developer.apple.com/documentation/musickit
As with all things Apple, I suspect the problem is less about technical capabilities, and more about commercial arrangements - Apple typically doesn’t make it easy for other businesses to have profitable relationships with other 3rd parties when using Apple APIs. For example, you can’t have an App on the Apple Store that has its’ own subscription service without giving Apple a 30% cut of those subscriptions!
In the case of Airable, they’re in the business of what I would call “API mediation service” - meaning, they provide one set of standard APIs to their customers (like Burmester, dCS, Linn, etc), and on airable’s backend, they re-interpret those API calls into a diverse set of API calls to the various music Streaming services; Tidal, Qobuz, Deezer, etc.
(Just purely speculation on my part, but) since airable would technically be making money off of Apple’s musickit API calls, I wouldn’t be surprised if Apple’s “terms of services” is to expects a % of revenue from airable’s business relationships 
This is not to be taken as bearing any kind of relevance to this specific instance but in the past I’ve dealt with integrating various services into products and sometimes there are things that you simply wouldn’t think of baked into a terms of service agreement…
One specific example being that some years ago I was on a project which was doing lookup of data when ripping CDs and one of the lookup providers specifically excluded using their lookup service in conjunction with other providers.
Another example (again, not from dCS) was that if a product was to offer certain functionality then the terms of the licencing agreement to be able to include that stipulated that the front panel of the product had the logo for that functionality printed on it. As we wanted to keep the front panel “clean” we ended up silk screening the logo for the function onto the units black front panel in black ink… 
So yes, there are lots of interesting gotchas and requirements that you might not even think about that can make implementing something that seems “easy” or “obvious” into a product impractical or impossible.
P