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.

That's how you onboard.

I'm hoping this attracts the right crowd.

I've been struggling with getting carplay to show it's alternate screen on my car's cluster display. Everything is fine for the first three seconds or so, then because apple doesn't use a nice annex-b stream (android auto's cluster display works fine), but avcc, shoving it into mpeg-ts requires some work.

Apple's encoder stops sending frames if nothing is happening on the screen, and at least my instrument cluster's h264 decoder loses sync after 3 seconds of no frames being delivered.

I've tried different kinds of filler, null ts packets, P-frames with no changes, etc. The decoder just doesn't want to resume playback when the frames start flowing again.

Any ideas?

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.

Related: "MPEG-2 Transport Stream Packaging for Media over QUIC Transport (ietf.org)" 07.may.2026 https://news.ycombinator.com/item?id=48049963 23 comments

[flagged]