My display hackery is pushed to GitHub now

also it has checks for the specific exact same model and firmware version because 'hackery' is not an understatement, I am reading+writing the memory directly for my ends lol

📢 The Draft Plan for HUDI’s Relaunch: 🌐 HUDI goes multichain 🛸 Mega airdrop 🔥 Token burn 🔥 🤖 Product launch: HUDI AI to talk with your data and beyond 💡 What do you think? Suggestions or ideas? 🐸 Let’s make HUDI great again! 🚀 #HUDI #Crypto #binance #token #bitmart #bnb #token #launch #AirdropAlert

Nice! I also made a program to change the input source of my LG screen (27GL850B), but I took a different approach and decompiled the OnScreen Control application to understand the protocol, then used named pipes to send my commands to OSCApplicationManager

yeah I tried decompiling OSC initially, but it turned out that the PIP mode VCP was completely broken and hardcoded for ultrawides lol

(Genuine, non-snarky question): Unless this was for fun, which is perfectly valid, what does this approach to controlling your monitor get you compared to using DDC?

LG's 0x60 VCP is broken, and the PBP mode (showing multiple inputs split on the screen) VCP was hardcoded to widescreen, so modifying the firmware was the only way to get the PBP and audio source switches.

i am now determined to do this to my dell u2415s.

What exactly is happening here ? 👀

So could this be used to embed and hide practical malware on a monitor? Nice.

you actually went through the effort of getting ACE on your monitor just to change settings without using the monitor itself? that seems like an insane amount of work lol

how's the latency in pbp mode? I'd have expected it to add a few ms which could be lethal when fighting hordes of salmon :)

it seems to be all in hardware (as it should be) because if I crash the CPU it still draws, so probably same as not PBP