1. Onboarding by diving deep into specifications
New engineers were often given raw standards documents to study before doing any hands‑on work.
- Balooga: “Graduated from college and day one in my first real job, I was handed a hardcopy of the MPEG‑2 transport stream spec and told to read it and come back with questions.”
- PorciiVorbesc: “Yeah, 15‑30 years ago, when professional experienced SW devs weren’t dime a dozen … you get to read and learn a lot of source code, requirements, specs, design documents and standards, before actually building things.”
2. Applying low‑level spec knowledge to solve concrete problems
Once the spec was understood, engineers used it to implement fixes—bit‑flipping, aspect‑ratio adjustments, or synchronizing streams.
- KaiserPro: “I turned to my toolset … spending the next few days workout out how to flip the aspect ratio bit of the mpeg2 … I did this using perl and binary regex.”
- korhojoa: “I've been struggling with getting carplay to show it's alternate screen … I've tried different kinds of filler, null ts packets, P-frames with no changes, etc.”
3. Debate over MPEG‑TS overhead vs. backward compatibility
Participants argued that the main issue with transport streams is their unnecessary overhead, acknowledging the trade‑off with legacy support.
- wmf: “The real argument about Transport Stream isn't its age but unnecessary overhead. If backwards compatibility is more important than overhead, fine. But acknowledge that there is a tradeoff.”