"...(apparently, the M1 was a real winner)."
Not at the time it came out.
There have been threads about this since day one of AS. With similar and different issues.
i.e. (Bandwidth taken away from data devices and pre-allocated for additional external monitors only even if they aren't being used...)
"The Apple tech told me these issues have been a problem since the M2..."
And probably will continue to be with M5 and M6 and 26 and 27.
Because Apple have settled on designs that appears to do one thing well (PCIe-based TB3/4/5) and fixing less high-speed protocols isn't a high priority.
Maybe? because it interferes with the optimum performance of the first?
So would never be a priority...
I mean, the introduction of AS brought the introduction of TB4, which 'tunnels' the USB 3.x signals in the TB4/5 40/80Gbps data stream.
This presumably imposed far more strict timing constraints on the parameters of the signal stream than older third-party USB 3.x chipsets are capable of conforming to?
Does imposing this strict regime on the data signal sent to or received from older external USB 3.x devices inherently cause potential problems?
The same sort of 'unfixable' set of problems seem to exist with HiDPI scaling on non-Apple monitors, particularly high resolution wide aspect 21:9 60Hz monitors.
Apple's hardware is designed to exactly support multiple XDR Pro Displays, and not a pixel more seems to be available except for the very specific HDMI 8K?
Which conflicts with HiDPI scaling on everything else non-Apple... ☹️
And which doesn't get fixed with each hardware and software iteration.
Because fixing it would require a different set of hardware design priorities?
Anyway. There are appropriate workarounds for most things.
Disclaimer: The question marks mean I have no real knowledge about these things, but am trying to work out the big picture?
Not at the time it came out.
There have been threads about this since day one of AS. With similar and different issues.
i.e. (Bandwidth taken away from data devices and pre-allocated for additional external monitors only even if they aren't being used...)
"The Apple tech told me these issues have been a problem since the M2..."
And probably will continue to be with M5 and M6 and 26 and 27.
Because Apple have settled on designs that appears to do one thing well (PCIe-based TB3/4/5) and fixing less high-speed protocols isn't a high priority.
Maybe? because it interferes with the optimum performance of the first?
So would never be a priority...
I mean, the introduction of AS brought the introduction of TB4, which 'tunnels' the USB 3.x signals in the TB4/5 40/80Gbps data stream.
This presumably imposed far more strict timing constraints on the parameters of the signal stream than older third-party USB 3.x chipsets are capable of conforming to?
Does imposing this strict regime on the data signal sent to or received from older external USB 3.x devices inherently cause potential problems?
The same sort of 'unfixable' set of problems seem to exist with HiDPI scaling on non-Apple monitors, particularly high resolution wide aspect 21:9 60Hz monitors.
Apple's hardware is designed to exactly support multiple XDR Pro Displays, and not a pixel more seems to be available except for the very specific HDMI 8K?
Which conflicts with HiDPI scaling on everything else non-Apple... ☹️
And which doesn't get fixed with each hardware and software iteration.
Because fixing it would require a different set of hardware design priorities?
Anyway. There are appropriate workarounds for most things.
Disclaimer: The question marks mean I have no real knowledge about these things, but am trying to work out the big picture?
Last edited:
