What is being worked on
Open questions, active work, and the questions that closed. Updated when the work moves, not on a schedule.
01
How something makes the list
A question earns a place here when three things hold: a broadcast or streaming engineer running their own pipeline would hit it, it can be measured in software with open source tooling and cloud compute, and there is a specific way the answer could turn out to be no. The last one is the point.
Every piece of work states, before any data is collected, what would prove it wrong. A negative result is still published, since it saves the next engineer the same time.
02
Active
| Track | Question | Status |
|---|---|---|
| MuxNode | How many ways can a common measurement tool produce a confident wrong number, and what catches each one? | Building |
| Genlock | Do timing cues in caption tracks survive a normal encode and package chain? | Building |
| Genlock | Where does each contribution protocol stop delivering a usable feed, and what does the recovery cost in latency? | Building |
| Genlock and MuxNode | Does a timing fault flagged at ingest show up again as an encoding artifact after transcode, with the shared ledger as the only path between the two stages? | Building |
03
Dropped on purpose
Ad-insertion signalling was sound engineering, but the market it serves is not the one this lab is built for, so the research moved toward other kinds of timed metadata.
More will appear here as questions close. Publishing what did not work is part of the method.