Earlier quoted context omitted.
Well except for some of the Apple Silicon machines. The M1 (and maybe M2?) only have two video output blocks, of which one is already used for the internal display. It’s honestly the biggest complaint I have about my M1 MBP. Yes DisplayLink or whatever it’s called exists but the performance is bad.
I assume you got one of the original M1 MBPs. The more recent models have more display blocks. M1 Pro can drive two external displays, and I think the M1 Max can do three or four. I’m still slightly pissed Apple ever shipped the original M1 MBPs, they were horrible machines.
Displayport: A Better Video Interface
111–120 of 426 posts
Re: Displayport: A Better Video Interface
#112Earlier quoted context omitted.
Technically macOS does support MST. But it only supports it to stitch together for a single display. It does not support daisy chaining two displays. Thankfully, every Mac for the last 7 years has Thunderbolt3 at least, so getting dual-4K-display from a single port/cable is still very doable, you just need a TB3 to dual DisplayPort or HDMI adapter.
Well except for some of the Apple Silicon machines. The M1 (and maybe M2?) only have two video output blocks, of which one is already used for the internal display. It’s honestly the biggest complaint I have about my M1 MBP. Yes DisplayLink or whatever it’s called exists but the performance is bad.
They hard-code one DisplayPort stream to *something* other than Thunderbolt.
On laptops, they hard-code one via eDP to the display, which is useless if it's in clamshell mode.
On Mac Mini, Mac Studio, and the MacBook Pro with HDMI port, one stream from the GPU is hard-coded to the HDMI port. If you want maximum displays, always has to be from HDMI.
But neither the 2019 or 2023 Mac Pro have this limitation. Even on the 2019 model where the HDMI ports were physically on the card - they could route all video streams via system TB3 ports.
I just checked and the base M2 Mini, and the M2 Pro MBP seem to finally allow using two video streams over the TB4 ports, - but the M2 Ultra Studio, with the exact same SoC as the M2 Ultra Mac Pro, still has this stupid artificial limit.
Re: Displayport: A Better Video Interface
#113With HDMI, I have both video and audio traveling over a single cable. That is _extremely_ convenient. DP _theoretically_ supports audio too, but AFAIK that's not widely implemented.
Re: Displayport: A Better Video Interface
#114Are there any KVM switches that do Displayport well (i.e. where switching between inputs does not look like a display disconnect to the PC)? I'm still using HDMI because I like to share my home multi-monitor setup between my personal machine and my work laptop, and the KVM switches are able to fool the PCs into thinking the monitor are always connected. Years ago I tried a Displayport switch, but it could not -- I as…
The magic words you're looking for are "EDID emulation". The KVM will continue to send the EDID data from the monitor even after you've switched away, which will fix that issue. It's relatively uncommon and not always implemented super well, but it's a requirement for any DP KVM to be not super annoying IMO. There was one particular KVM brand that was supposed to do it well whose name is escaping me now :/. I was loo…
https://store.level1techs.com/products/14-kvm-switch-triple-...
Re: Displayport: A Better Video Interface
#115Earlier quoted context omitted.
If this were true, then people would be running datacenter networking over HDMI. Data is data - there is no benefit to designing two entirely different transport mechanisms for video vs other data. You could argue that video data has a deadline to meet - but ethernet already has lots of mechanisms for QoS and bandwidth reservations to make sure that someones torrents don't interrupt something latency sensitive. Sure,…
> If this were true, then people would be running datacenter networking over HDMI. Why would they? If they need more bandwidth than what Ethernet provides, they'd probably just bite the bullet and go with fiber. ...which punts the previous question to why the industry hasn't gone all-in with fiber optic display connectors, like it has with TOSLINK for S/PDIF in the audio world.
Re: Displayport: A Better Video Interface
#116Earlier quoted context omitted.
It's not an OS problem, that's how DP is supposed to work and that's in fact stupid
It’s an OS problem for not handling monitors being disconnected and reconnected properly. What is stupid is having half your windows unreachable because they are on a monitor that is turned off. How does that help anyone? Imagine how annoying it would be on a laptop? I use my laptop in a meeting, and have a few windows open on its screen, then I arrive at my desk and plug in my 2 external monitors and keep my laptop…
I have a cheap laptop that doesn't understand a turned-off monitor as unusable, and it's actually way nicer that way.
Re: Displayport: A Better Video Interface
#117Earlier quoted context omitted.
The magic words you're looking for are "EDID emulation". The KVM will continue to send the EDID data from the monitor even after you've switched away, which will fix that issue. It's relatively uncommon and not always implemented super well, but it's a requirement for any DP KVM to be not super annoying IMO. There was one particular KVM brand that was supposed to do it well whose name is escaping me now :/. I was loo…
Were you thinking of Level1techs? https://store.level1techs.com/products/14-kvm-switch-triple-...
Re: Displayport: A Better Video Interface
#118HDMI predates DP by 5 years, switching wouldn't enable any specific use case, and that 5 years head start means HDMI has market inertia. Yes we should use it because it's better but the practicality? There's so much gear that's HDMI that would have to be replaced or require new active adaptors. It's so much industry and consumer effort for such a marginal gain.
Forget all the other pros/cons - MST makes it worth any industry & consumer effort alone.
Re: Displayport: A Better Video Interface
#119Funny, a stream of data at a constant rate makes much more sense to me intuitively than packets, specifically for uncompressed video.
Are there any downsides to packetization, like increased latency or dropped frames or anything? Or not really, is it all upsides in being able to trivially combine multiple data streams or integrate easily into hubs?
Re: Displayport: A Better Video Interface
#120Earlier quoted context omitted.
> If you have multiple screens and a single screen KVM (fairly common) it will do the re-arrangement that you've experienced. With EDID support it keeps both output alive resulting in no re-arrangement. Can you tell me some KVM switches that have a working implementation of that feature? I'm looking for one. I'm still using a DVI KVM, because when I tried to upgrade to Displayport (years ago), I ran into the problem…
I have a TESmart (TES-HDK0402A1U-USBK) from https://www.amazon.com/gp/product/B08259QL5J/ref=ppx_yo_dt_b... which works fine in this regard. This was probably the 4th DisplayPort KVM I tried due to keyboard issues with the others.