My vintage Rotel RSP-1576 (pre/Proc) had such horrendous delays (in the order of ~250mS) that caused much problems in the house that was being fed by it.
Bad equipment is bad equipment. That has nothing to do with data transmission speeds and variations (jitter) of wired vs. wireless on a sufficiently adequate network.
But again, I think you are trying to decimate just one part of my earlier post and intentionally leaving out the rest of post (e.g. noise level, Red-Book...).
Honestly, I actually have no clue what your point really is. Your writing is bizarre, obtuse, and jumps all over the place. I still do not see any clear argument of fact in what you are writing, so I'm simply reacting to the unsupported "facts" you are tossing around.
If you look at that wireless signal in a histogram that (even w/extended buffering) the compounded delays, latency and drop-outs are not constant (no specs ever discussed or stated and can extend out to over 300mS in congested WiFi locales.
But is that relevant? Except for synchronized live music recording from multiple source or first-person real time gaming, why does such latency variation matter? Devices have been dealing with latency and jitter (latency variation) for decades now. A simple buffer (with slight delay in playback to allow the buffer to fill up) addresses those issues. Unless, of course, you are using poorly implemented devices (as you said you were using above) or an inadequate network.
Now, drop outs (lost data) is a real issue if you are using a protocol that does not include re-transmit (i.e., UDP). But if your network is routinely dropping packets, then that is a factor that must be addressed in your network. A competently implemented Wi-Fi or wired network will not face that issue; and a high audio quality stream will address lost packets as part of its protocol process.
If our hearing can detect the difference between an echo and reverberation, then maybe you feel comfort in your own settings, as I do in mine.
This seems to me to be a very stupid statement. Either your network is delivering the packets (within acceptable latency relative to buffering on the device) or it is not — either there is packet loss (i.e. missing bits of digitized sound) or there is not. Echo, reverberation female vocal treble, snare drum transients, etc. will all be there if the data stream is correct; and all of them will be adversely affected if it is not.
I am such an old fart and full of BS...
Sorry, but BS really isn't what ASR is about. Facts are welcome, BS opinions are not.
... that I actually have a parted network (the wired kind) one ETH handles the LAN assets and the ETH other is the WAN, separate and firewalled.
So do I. In fact, as part of searching for a rental house, a major factor for me is whether or not I could easily implement wired ethernet between various places in the house, and run it all back to the WAN-side router. And I also run multiple VLANs for: my work-related data, our home data, IoT devices, VoIP devices, and also an external guest DMZ.
But you know what: I do that out of preference, knowing full well that I can equally create a WiFi mesh that will fully cover 100% of my needs. I strongly prefer wired; but that doesn't mean wireless is not sufficient for what I need. Which is why — as a dyed-in-the-wool wired-head — I'm calling BS on your rant. Oh wait, I also have a WiFi mesh (Ubiquity AC Pros) that is fully integrated into my VLANS for devices that are wireless-native (e.g., iPhone, tablets, etc.). I wire where I can; and I don't where I can't. But I know full well that wired and wireless are both more than sufficient.
YMMV but does not mean a wired network is a relic and less rock-solid than a WiFi with all it's pitfalls, as have been already mentioned.
You still have not explained why your so-called pitfalls are a real problem for your situation or anyone else's (outside of using poorly designed hardware).