https://bugs.kde.org/show_bug.cgi?id=467554
--- Comment #2 from Chema <rondo...@gmail.com> ---
The HDMI EDID emulator is used for 2 functions:

1- If you use a remote control application like AnyDesk or similar, the remote
computer must be receiving an HDMI signal for it to work correctly. If the
computer stops receiving this signal, for example because you unplug the HDMI
cable, the remote control of the computer stops working.

If you have both computers plugged into a KVM switch, and from the first
computer you want to remote control the second computer using one of these
remote control programs, you can't do it without using a hardware emulator like
this because when you activate the first computer on the KVM switch computer
from which you control the second computer remotely, this remote connection
does not work because the second computer stops receiving the HDMI signal
(since you are receiving the HDMI signal on the first computer). What the HDMI
EDID emulator does is that even if the HDMI cable is unplugged, it emulates the
signal as if it continued to reach the computer, so it is believed that it is
connected to a monitor and then the remote control works, although the computer
does not really is connected to a monitor (or is not receiving the signal from
the HDMI cable).

But unlike a normal EDID emulator, this one is bi-directional, which allows the
HDMI cable to be connected to it and you can quickly switch on the KVM switch
to the remote computer and start receiving the HDMI signal from the monitor,
just in case there is some problem that cannot be fixed from the remote
control.

2- By emulating HDMI resolutions, switching between devices on the KVM switch
is almost instantaneous, it only takes 1 or 2 seconds. Without this kind of
emulator, switching the display between computers on the KVM switch takes a
long time, about 15-20 seconds, because it has to re-receive the HDMI signal,
readjust the resolution, etc. while with the HDMI EDID emulator it never loses
the signal or the resolution that the equipment had, it is believed that it is
always connected to a monitor, so switching between the equipment screens is
almost instantaneous.

In Windows this hardware works perfectly, allowing me to select any resolution
that the system detects. In Linux I am having the problem that of all the
resolutions that Wayland detects and offers, only Full HD, 2K and 4K
resolutions work, intermediate resolutions do not work with this adapter
plugged in, but this does not happen only in KDE, it happens to me also in
GNOME, so I think it's more of a bug with the Linux kernel graphic driver that
for some reason is not able to work correctly with this hardware.

With versions prior to KDE 5.27.3, this hardware worked fine in the resolutions
that I have mentioned, with the only problem that when suspending the computer
in 4K resolution and turning it on, it did not receive the HDMI signal and you
had to change the console by pressing Ctrl + F2, when doing so, it received the
HDMI signal again and it was possible to switch to the session with KDE by
pressing Ctrl + F1 and everything worked fine (but this problem did not occur
in GNOME).

But since KDE version 5.27.3 the 4K resolution has stopped working, when I
activate it the screen stays black and does not return to the previous
resolution even after 1 minute passes, forcing me to change to another console
and restart the computer.

Please, I don't want to sound selfish with what I'm going to say now, but this
connector is only $20 on Amazon, is there any chance that I would donate the
money to some KDE developer to buy this hardware so he can carry out the
relevant tests? I've been having problems with this connector for more than a
year and we haven't found a solution, from here the tests I can do are very
limited due to my knowledge of Linux and I think that because of this, it would
take a long time to find a solution.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to