141–150 of 185 posts
Maybe solving your problem in other ways: 0: I use `ddcutil` (on Linux), it takes about 2 seconds for the switch: `ddcutil -b $bus setvcp 0x60 $source` 1: Use something like NoMachine or VLC - would probably cause more problems if you've got devices that go into power-save mode 2: Ensuring that your devices are outputting the exact same mode may decrease the time.
HDMI Switching like that takes long because there is a EDID negotiation going on between the minitor and the input devices. If you want to switch fast and often your best bet is getting an HDMI switcher that is basically always connected to the monitor and both sources and then toggles between the two. Beware of the supported resolutions and framerates. A cheap hack would also be to connect your second source to the…
Tangentially related: I find many monitors that look great on paper are a real annoyance when it comes to controls, be it brightness/contrast or input switching, making those 4s irrelevant in comparison. Between recent models of Acer/Dell/Eizo/LG, I found Eizos to pose the least friction so far, with the LG (may be model-specific) a surprising worst. Reply to this comment with your anecdotes! EDIT: To address the OP:…
Now that I have two inputs, and I switch a few times a day, I'm considering getting a new monitor, in some part to move to one with better input controls.
OK, remember when modems were like EEEEEEEkRrRrRrRrRrRrRbaBONGbaBONG.... That was handshaking, and it was how modems figured out which speeds and protocols each other supported so they could figure out how fast to transfer data and how to encode it. Monitors are kind of the same. There's handshaking that goes on each time you connect a monitor to a video source. Like (and I'm totally making this up): - Hi, I'm an AMD…
The amount of actual information transmitted there the handshake should be as close to what we perceive instant.
We know the cable can handle it because a modern desktop resolution at 60fps goes down the same cable.
OK, remember when modems were like EEEEEEEkRrRrRrRrRrRrRbaBONGbaBONG.... That was handshaking, and it was how modems figured out which speeds and protocols each other supported so they could figure out how fast to transfer data and how to encode it. Monitors are kind of the same. There's handshaking that goes on each time you connect a monitor to a video source. Like (and I'm totally making this up): - Hi, I'm an AMD…
I appreciate this question, I would also appreciate a solution, and the explanation of why it happens is interesting. However, what I really want is just to be able to switch the input via command line. I know that there is a protocol that supposedly allows this (ddc?), But it seems that support for it is not standardized. This means the feature I want can't be found in the product specs. So my question: what's a mon…
I also keep a public monitor database here where you can check if a specific monitor usually works with DDC or not: https://db.lunar.fyi/
The problem with LG is that they report very generic names so they can't be filtered well in the database. You can see what I mean with this query:
SELECT DISTINCT ON ("DisplayProductID")
name, ddc,
"resolutionString",
"refreshString",
"dotsPerInch",
"isHiDPI",
"isRetina",
"DisplayProductID"
FROM
displays
WHERE
ddc AND "is4K" AND width IS NOT NULL
AND NOT "kCGDisplayIsVirtualDevice" AND NOT "isAirPlayDisplay" AND NOT "isTV"
AND "DisplayProductID" != 0 AND name NOT LIKE 'Unknown Display%' -- Filter out those in a semi-connected state
AND name LIKE 'LG%' AND "DisplayProductName" LIKE 'LG%'
ORDER BY
"DisplayProductID" DESC
LIMIT 10;
Weird how you say that then the thing that was “that’s just the way it is” is often completely solved in the next day or two.
100% convinced we wouldn’t live in a world with trash like this if just a few more people would say “it’s very slow, can you make it faster? No I don’t care what the excuse for it being slow is I still think it can be faster, currently it feels cheap and awful” Weird how you say that then the thing that was “that’s just the way it is” is often completely solved in the next day or two.
I appreciate this question, I would also appreciate a solution, and the explanation of why it happens is interesting. However, what I really want is just to be able to switch the input via command line. I know that there is a protocol that supposedly allows this (ddc?), But it seems that support for it is not standardized. This means the feature I want can't be found in the product specs. So my question: what's a mon…
In 5 years of getting support emails for Lunar ( https://lunar.fyi/ ), LG monitors were the least mentioned of all. They seem to have the best DDC compatibility of all monitors. I also keep a public monitor database here where you can check if a specific monitor usually works with DDC or not: https://db.lunar.fyi/ The problem with LG is that they report very generic names so they can't be filtered well in the databas…