Cambridge CXN100 audio loading slowly on Roon Ready (ref#4QL9CI)

That’s the old architecture on Wolfson DACs, the new models use ESS so this isn’t done anymore you can see it doesn’t show it in the signal path.

1 Like

Mine is very old, it’s been out of action for ages as it’s not Roon Ready

The CXN100 doesn’t upsample stuff to 384 kbit anymore like the CXN V1 and V2 do. As @CrystalGipsy already mentioned. According to Cambridge they felt that the ESS Saber chip in the CXN100 didn’t need ATF and so they left it out.

@Darren_Jackson I would seriously recommend connecting the CXN100 to Ethernet. It probably doesn’t have the same WiFi hardware that my CXN V2 has. But as I’ve mentioned earlier, getting my V2 connected to a permanent Ethernet connection did wonders here.

2 Likes

I also had to connect my CXN v2 to Ethernet because I had the same issues with WiFi.

No matter how good your WiFi is… i highly recommend connecting the core/server and as many endpoints as possible to Ethernet.

1 Like

Thanks, everyone - ethernet it is! The problem with that as I have mentioned is that it seems to disable the Tidal Connect, Spotify Connect etc functionality on the CXN100 for some but not all of the smartphones in the household.

I can’t work out why it works with my daughter’s phone but not with mine or my wife’s. Which doesn’t bother me, because I will just use Roon, but I have to accommodate the preferences of others in the household!

Thanks again.

Sounds like you might have two WiFi networks in play one from the router and one from the mesh system each operating on a different subnet. Check ip addresses of device that work and ones that don’t and see if the first 3 set of numbers match. Which may also be part of your WiFi problem.

1 Like