rockowitz

On 12/14/19 2:49 PM, jonpas wrote: > > I assume since you mention ClickMonitorDDC that you're running Windows > in a VM. So as a first step, check whether ddcutil...

Well, that pretty much nails it.  It's the monitor's implementation of feature x60. To further confirm, you might try using Windows program softMCCS by enTech. (https://www.entechtaiwan.com/lib/softmccs.shtm). enTech is a maker...

Thanks for the logs.  I stand corrected.  From the logs I see that the monitor is properly not setting the supported feature bit for feature x00 (by definition not a...

There's nothing in my toolbox to solve the problem. Since it appears in ClickMonitorDDC and softMCCS as well as ddcutil it's clearly a hardware problem in the monitor. All I...

I'm not clear how to interpret "executing the command from my only connected device (my Manjaro PC) while being on the other (unused) HDMI input".  What computers (or virtual machines...

I'm afraid I have nothing to add here. Seems like another LG idiosyncratic DDC implementation.

I do have one further thought on this problem, though it's just a hunch. Picture By Picture mode complicates the logic of switching inputs. Feature x60 was not designed with...

You could try executing the watch loop using individual ddcutil commands. That MAY allow you to learn something about what features are changed before the OSD disappears. Basically, here's pseudo-code...

Take a look at ***--brief*** output for **detect** and **getvcp**. It's intended to be machine readable. The **getvcp** output is the same form as is used by **dumpvcp**/**loadvcp**. Does this...

As I've said, I think this enhancement makes sense. I don't, however, see it rising to the top of my todo list any time soon. The enhancement would entail modifying...