12 ms·
It should be. As soon as video data is in packets, it should be routable over a network like any other data. Give up the custom connectors, custom cables, etc
by londons_explore 3y ago
It should be.
As soon as video data is in packets, it should be routable over a network like any other data.
Give up the custom connectors, custom cables, etc.
Need a wireless display? No worries, we can route the data over wifi too.
Need 5 displays? Thats what an ethernet switch is for. Screen mirroring? We have multicast.
Need a KVM? Well you can probably write a few scripts to change which computer your screen gets it data feed from.
I believe this hasn't happened simply because audio/video people like going to conferences to design their own standards every year, keep their licensing royalties, keep their closed club - a software-only solution over any IP network isn't going to fly.
- NavinF 3y agoNaw it's because >=40G Ethernet never saw much consumer adoption. QSFP DACs and optics are also kinda bulky by consumer standards so a lot of people would want a new connector. Even LC connectors would be too large for laptops.
- tverbeure 3y agoThey write that DP uses packets, but it's still an isochronous connection with guaranteed BW allocation. For video timings with high pixel clocks, the bandwidth used to transfer a signal is very close to what's theoretically available. There's no way you'd be able to do that reliably over something like an Ethernet cable. There's nothing sinister about how video standards are designed. From DP1.0 to DP1.4, which spans more than 10 years, all changes have been incremental and most just a matter increasing data rates while the coding method stayed the same. They need a system that's very high and guaranteed bandwidth, high utilization, very low bit error rate, and cheap. Even today, a 10Gbps Ethernet card will set you back $90. And that will carry less than half the data that can be transported by DP 1.4 which is old school by now.
- kccqzy 3y agoHave you tried VNC over an Ethernet cable at all? What you are proposing is basically having a VNC-like protocol over IP over Ethernet. Now try it out and see how well it works. To be even more reductive, a thought experiment is to consider the classic USB. Why did people even invent USB in the first place in the 1990s? The first USB had only 12Mbps, not much better than the first Ethernet at 10Mbps which had existed since 1980! Why didn't people who invented USB simply use Ethernet?
- londons_explore 3y agoThe main delay in VNC is the software stack encoding and decoding the data. A video-over-ethernet solution would likely have the GPU directly packetize the data into IP packets and route them direct to the network hardware without the CPU touching anything. The network would have QoS to guarantee the necessary bandwidth and guarantee a fixed latency and no packet loss (ie. there is no chance of a packet being dropped due to a queue overflowing, because we have already arranged a fixed bandwidth allocation for the whole network route).