I have a setup that requires me to be able to communicate using DDC/CI.
It shouldn’t be difficult to passthrough this communication to the connecting interface, such as a Windows machine’s GPU, through the Comet Pro KVM.
As long as the monitor has been identified properly by scraping its EDID, it should be seen in Windows/Linux properly to use DDC/CI.
I feel like the mechanism would not be too difficult. The communication method is not secure, so the Comet Pro can just man-in-the-middle the communication between the host machine and the monitor. The host would see the monitor, the monitor would see the host.
An additional feature would probably just allow the Comet Pro to pull the EDID of the connected monitor for the user to use (at their risk). I don’t think it’s too difficult for the Comet Pro to receive the EDID information from the monitor it is plugged into, instead of the manual method of requiring users to get that information themselves, either online or through tools like MonInfo (Windows).
Specifics:
I use Twinkle Tray to control my monitor via the host, since it is mounted on my wall and I cannot be arsed to dim it at the monitor. Passing through the KVM through my secondary monitor (AW3418DW) and making my GPU recognize it as that is not an issue if I set the Custom EDID. However, monitor communication cannot happen.