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, I picked back up on OmniBridge. Finished full Windows support for its video-switching mode, which had only worked on Mac and Linux before. A review before shipping caught two real gaps: a missing check that would have broken Windows builds outright, and a security risk in how it named its own internal connection.
Then I dug into a real, live bug: the feature that finds video sources on the network (NDI) was finding zero, on a network known to have them. Rather than guess, I watched the real network traffic on the test machine and confirmed the network itself was healthy — other devices were finding sources just fine — but OmniBridge itself wasn't sending anything out to look for them. Traced it to a real one-line gap: the code was only reading a one-time snapshot instead of actually running the search. Fixed it with a small background task that keeps the search running the whole time the program is up.
Rounded it out with a real documentation upgrade — rebuilt the product site's docs section so the header, sidebar, and footer live in one shared template instead of being copied by hand across a dozen pages, and added a new setup guide covering the network requirements that trip people up (same network, firewalls, router settings). A second look before publishing caught two real problems first — a batch of internal links that would have quietly stopped working, and a table that would have broken on phones.