Convert TS to MP4
TS is the MPEG Transport Stream - the container broadcasters and HLS streams use. It almost always carries H.264 or HEVC video plus AAC or AC-3 audio. Wave repackages the same streams into MP4 with no re-encoding.
What actually changes
MPEG Transport Stream was designed to survive dropped packets during broadcast, so it interleaves small chunks of video, audio, and metadata. That structure isn't suited to random-access playback, which is why local players sometimes struggle with TS files. MP4's indexed structure fixes this.
Because the video and audio codecs inside a TS (typically H.264 or HEVC + AAC / AC-3) are all MP4-compatible, the conversion is a re-mux. Wave rebuilds the MP4 index from scratch - no re-encoding, no quality loss - and adds a fast-start atom so the file seeks instantly.
Three steps.
-
01
Step 1
Drop the TS file onto the card.
-
02
Step 2
Wave inspects the streams and confirms the fast-copy path.
-
03
Step 3
Convert and save the MP4.
Answers, specifically.
Why does my TS file play but seek slowly?
TS has no random-access index. Every seek forces the player to scan forward. MP4 with a proper moov atom seeks instantly.
I have a bunch of .ts chunks from an HLS stream. Can I convert one big file?
Concatenating HLS chunks isn't the current build's scope - you'd need to stitch them first (ffmpeg concat, or a small script). Wave then converts the stitched TS to MP4 as a single remux.
Will Dolby audio survive?
AC-3 and E-AC-3 (Dolby Digital / Digital Plus) copy into MP4 as-is. Playback support is broader on Apple than on Windows, but the file itself is fine.
Broadcast recordings have multiple audio tracks. Do they all come across?
The current build outputs a single audio track. Multi-track passthrough is on the roadmap.
Does closed-captioning transfer?
CEA-608 and CEA-708 captions embedded in the video stream survive because Wave copies the stream bit-for-bit. Standalone caption tracks aren't remuxed in the current build.