Live data from Hacker News

Ask HN: Can you recommend an “instant-switch” Monitor? Does one exist?

news.ycombinator.com

181–185 of 185 posts

Re: Ask HN: Can you recommend an “instant-switch” Monitor? Does one exist?

#181
post #45

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…

Workstation GPUs (Nvidia Quadro[1][2] / AMD Radeon Pro[3]) can emulate/force an EDID in the driver settings and the OS will "think" a display is attached. At least in theory that should get around the handshake.

[1] https://www.nvidia.com/content/Control-Panel-Help/vLatest/en...

[2] https://nvidia.custhelp.com/app/answers/detail/a_id/3569/~/m...

[3] https://portal.7thsense.one/user-guides/MC264-display-config...

Re: Ask HN: Can you recommend an “instant-switch” Monitor? Does one exist?

#182
post #178

Earlier quoted context omitted.

I've found the simplest way is to just use a mouse and keyboard that support bluetooth and RF and just keep the RF dongle on one PC and the bluetooth paired to the other PC. If you're running Windows, Mouse Without Borders is a handy utility and I'm sure there's an equivalent for Linux. I often find myself just using Moonlight streaming as a remote desktop since my tower is a lot more powerful than my laptop.

On linux you can use Barrier / Input Leap. No Wayland support though, still work in progress for unforeseeable future. Can't find any KVM app that works on Wayland yet. RKVM used to work on Wayland but not anymore.

No Wayland support though, still work in progress for unforeseeable future

Linux isn't my daily driver so this might be a dumb question, but what's up with Wayland? I feel like I've been hearing for a solid decade that X is dead yet whenever someone recommends me a piece of software it never works on Wayland. Wayland is fourteen damn years old at this point.

Re: Ask HN: Can you recommend an “instant-switch” Monitor? Does one exist?

#183
post #46

Earlier quoted context omitted.

What could they possibly be doing that takes 4 seconds? That's ~4,000,000,000 instructions on a typical embedded processor. It's much more likely that the handshaking was implemented by an incompetent organization that doesn't care about quality.

It is extremely odd to see so many people in this thread ignore that a handshake requires billions of instructions to be executed for some reason....

One of the grandparents of this comment thread explicitly ignored it; this is a discussion on frame buffering.

Re: Ask HN: Can you recommend an “instant-switch” Monitor? Does one exist?

#184
post #182

Earlier quoted context omitted.

On linux you can use Barrier / Input Leap. No Wayland support though, still work in progress for unforeseeable future. Can't find any KVM app that works on Wayland yet. RKVM used to work on Wayland but not anymore.

No Wayland support though, still work in progress for unforeseeable future Linux isn't my daily driver so this might be a dumb question, but what's up with Wayland? I feel like I've been hearing for a solid decade that X is dead yet whenever someone recommends me a piece of software it never works on Wayland. Wayland is fourteen damn years old at this point.

Wayland itself is actually pretty solid right now as long as you're not using nvidia card. In the past, applications that need to interact with other applications (e.g. remote desktop, screen recording, keystroke injection, etc) can't be ported to wayland due the lack of api. Those api now already exist in wayland, but completely different which requires huge effort by application developers to rewrite their app. So right now we're just mostly waiting until those apps finally run on wayland, and nvidia finally stop being buggy on wayland.

Most app developers are dragging their feet when it comes to supporting wayland, but with big distros now shipping wayland by default, the pressure to make sure their apps work in wayland is really high in the past two years. For example, just last week vscode finally fix rendering issues that plagued wayland + nvidia users for years (had to use insiders version with some extra args but at least I can use vscode in wayland now). I think the rate of developers finally adding wayland support in their apps is finally accelerating.

Post reply on HN