TS files are designed for broadcast and streaming transport where packets may be lost or joined. Echoryte recognizes the mpegts demuxer, requires audio, and normalizes timing for transcript review.
Where this workflow fits
- Broadcast captures
- HLS segment archives
- Live event recordings
Transport timing can reset
MPEG transport streams use fixed-size packets and timing references suited to transmission. Their resilience does not make every capture continuous, so the pipeline validates duration and audio while editors still inspect discontinuities.
Audit program and segment boundaries
For news or event captures, compare the transcript before and after ad breaks, reception faults, and concatenated segments. A small timing jump can otherwise shift every later subtitle cue.
Before you upload
- Identify the intended program and language before uploading a multiplexed broadcast capture.
- Check around every segment boundary, program-map change, or reception glitch and retain the original packet stream plus its capture log.
Limits worth knowing
- Segment joins, packet loss, and timestamp resets can create gaps or drift in long captures.
- Several programs or language tracks may be present without a user-friendly label.
Questions from the workflow
Why can a TS file expose multiple audio tracks?
A transport stream can carry several programs and audio tracks. The selected source must include a decodable speech track in the intended program.
Reviewed sources
- IANA Media Types registry · checked 2026-07-20
- RFC 3555: MPEG transport stream media type · checked 2026-07-20