I’ve had Claude get hung up and refuse to proceed for security reasons when I asked it to implement screen capture in my app using the built-in Win32 APIs.
Perhaps René, the maintainer of T/2 Linux, will end up vibe coding an NVIDIA driver one of these days. He’s been reverse engineering and vibe coding a bunch of drivers for old graphics lately and live streaming everything.
I disagree. I’m currently working on a full native multi-threaded desktop app for video, with GPU video processing in frag shaders, hardware accelerated encoding, audio mixing, etc. I’ve been vibing it for a couple months after mocking up the core architecture prior to AI.
This has been done for many years in the arcade preservation community, allowing specific arcade boards to be fully documented and preserved in MAME and now MiSTer. Specifically Guru’s ROM dump has documented decap efforts since 2007 it looks like.
I too was in the Cyrix camp when Quake came out. My first video card was a Permedia 2. It ran GLQuake when that came down the pipe but not very well. The Christmas when I got my 3dfx Voodoo1 card was magical.
You’re likely referring to SMPTE timecode, a method of conveying timing information about a video signal (eg. HH:MM:SS:FF), which is SMPTE 12M. There are various ways that timecode is conveyed in media such as LTC (linear timecode, usually carried as an audio signal), VITC (vertical interval timecode, in the vertical blanking interval of a video signal), and others.
I was just reading about this topic last night on Maister’s Graphics Adventures: https://themaister.net/blog/2025/06. They created PyroWave, a GPU-accelerated DWT codec in Vulkan compute shaders for performing very low latency game streaming. Very fascinating read, and builds on similar work from their master’s thesis too.
What drives me crazy is that recently I had to download three separate bloated Electron app packages just to turn off the RGB in my new mobo, RAM and GPU because in 2025/26 we still don’t have vendors using a common protocol to control RGB.