4 ms·
> hit or miss What a polite way to say it. CEC and DDC-CI, are these two things that should be absolutely nailed given in terms of low level commands how simp
by lloeki 6y ago
> hit or miss
What a polite way to say it.
CEC and DDC-CI, are these two things that should be absolutely nailed given in terms of low level commands how simple they really are and how long they've been around, yet are thoroughly broken through and through in so many subtle ways, from broken payloads to timing issues.
And even when the low level protocol is correctly implemented you can be sure that the high level behaviour of the devices is not doing what you'd want it to, with no workaround possible.
e.g one device turns -all- devices on/off no questions asked, another would not allow separate configuration of being controlled vs controlling, and/or power on vs power off, a third one would disable CEC the moment you select headset audio output because it goes in the way of their MegaMagicSync+ feature (which is just CEC with a bunch of useless proprietary stuff to talk to other devices of the same brand, coz gotta "add value" and "differentiate")...
- kingosticks 6y agoI agree with everything you've said here (especially "MegaMagicSync+"). But why is it such a mess? Was it added to the spec late? Or maybe because manufacturers implement it as an afterthought and don't bother testing it. They seem to get the regular part of HDMI mostly right. Although now that I say that I remember having problems with HDMI switches in the past... It's probably too late for HDMI-CEC, there are too many crappy pieces of hardware out there. I'm just wondering what stops this from happening next time. It's a great system when it works and so much better than trying to reverse engineer other protocols. Just a shame that it's so bad it doesn't even get a mention in a post like this where it should have been the perfect solution.