Hi Dale,
Very interesting, and yes, we have ended up surprisingly close. I didn’t realise how far you had taken the mAP optimisation itself.
We actually ran into an interesting limitation of the WiFi client idea (your mAP, our WR902 client). In one already highly optimized network/system, the WR902 in client mode was ultimately outperformed by a very basic low power switch. That was important because it showed us that simply breaking the electrical connection isn’t necessarily enough. The result depends on what noise mechanisms you’re removing & what is already removed, but also what remains upstream, what the client and its power introduce, and what happens downstream.
That eventually pushed us much further into optimizing the WR902 itself: very, very clean power, 3.3V battery versus the internal conversion, a rewritten minimal OS, router setup and power, dedicated WiFi access point setup and power, WiFi band and channel, and then the last metre towards the streamer. The idea was also to minimise unnecessary activity at the client and make the dedicated AP-to-client link as clean and efficient as possible, with as little interference and contention as we could achieve. In other words, rather close to what you’ve been doing, although from a different starting point.
The two paths make the last part easier to see:
Router → switch → last Ethernet cable → streamer/DAC
Router → AP → WiFi → WR902 client → last Ethernet cable → switch or filter→ streamer/DAC
What became particularly interesting to me is that there doesn’t seem to be one universal network-noise solution.
The last metre may actually deserve special attention here, both for a network switch and a WiFi bridge/client. There are published measurements showing common-mode noise reduction in the last Ethernet connection to the DAC, alongside what we hear. So electrical isolation further upstream doesn’t make what happens close to the endpoint irrelevant.
That’s why I find Mattijs’ switch interesting beyond the 5Gb argument. He has gone unusually far on power, regulation, clock and I/O inside the switch itself. Your work, ours with the WR902, and this switch seem to be approaching the same problem from different places.