Labor Day, a Facebook Rescue, and Windows Plus NDI Support Shipped
A genuinely relaxed holiday with my wife, a house call to get an old co-worker back into her Facebook account, some yard work, an evening with friends — and, once the day wound down, closing out two real pieces of OmniBridge work: full Windows support for transcode mode, and a root-caused fix for NDI source discovery that had been quietly finding nothing.
A relaxed Labor Day
Took the holiday for what it's meant to be — my wife and I mostly just relaxed together at home for the day.
A Facebook rescue for an old co-worker
Spent 10:45 to 11:30 a.m. at an old co-worker's house getting her back into her Facebook account on her desktop computer — the kind of small favor that eats half an hour but matters a lot to the person on the other end of it.
Yard work
Mowed the lawn from 4:30 to 5:30 p.m. — the ordinary maintenance that still has to happen on a day off.
An evening with friends
From 6:00 to 8:30 p.m., hung out with some friends at their house — a good way to close out a slower day before getting back to the keyboard.
Windows and NDI support closed out for OmniBridge
Once the evening wrapped up, picked back up on OmniBridge. Finished full Windows support for transcode mode — a Windows named-pipe equivalent to the Unix FIFO-based pipeline, reviewed through several real rounds that caught genuine gaps (a missing platform gate that would have hard-failed a Windows build, a name-squatting risk on the pipe itself) before it shipped.
Then dug into a real, live bug: NDI source discovery finding zero sources on a network known to have them. Rather than guess, pulled up a live packet capture on the actual test host — confirmed the network itself was healthy (real multicast traffic from other devices flowing fine), but OmniBridge's own process was emitting nothing at all. Traced it to a genuine one-line gap: the code was only ever reading a passive snapshot from the NDI SDK, never the call that actually drives its discovery probes out onto the network. Fixed with a small background task that keeps discovery genuinely running for the life of the process.
Rounded it out with a real documentation upgrade — migrated the product site's docs section onto Eleventy so the header, sidebar, and footer live in one shared template instead of being hand-copied across a dozen pages, and added a new NDI setup guide covering the network requirements that trip people up (same network segment, host firewalls, switch multicast settings). Caught and fixed two real issues in that migration before it went live — dozens of internal anchor links that would have quietly stopped working, and a table that would have broken the mobile layout — both found through an independent review before deploying, not after.