TV says 'format not supported'? What to check before converting

You copied a movie to a USB stick, plugged it into the TV, and got a polite refusal: "video format not supported" or "audio codec not supported." The same file plays fine on your phone and on your computer. The usual advice at this point is "convert it with HandBrake," which works but costs you a re-encode every single time. Often the file isn't the problem. The player is.

What a video file actually is

A video file has two layers. The container (MP4, MKV, MOV) is the box: it holds the compressed streams plus an index saying where each piece lives. Inside sit the streams: video compressed with a codec like H.264, HEVC, or AV1, audio compressed with AAC, AC3, or DTS, maybe subtitles. A player fails when it can't read the box, can't find its way around inside it, or lacks the license/hardware to decompress one of the streams. These fail differently, and it pays to know which one hit you.

The three common failures

• Picture plays, no sound. Classic audio-codec gap. Many TVs decode AAC but not DTS, which shows up constantly in MKV files. The video is fine; one stream has no decoder.
• File rejected outright, or plays for a second then freezes on seek. Often the index. Some MP4s carry their index (the moov atom) at the end of the file. Full players like VLC scan for it; simple USB players give up because they only read front-to-back. This is the classic "plays everywhere except the TV" case.
• Nothing plays it anywhere. A genuine codec gap on every device you own, like H.264 High 10 profile or an exotic audio track. This is the case that truly needs a re-encode, and it's rarer than it feels.

Why the standard advice annoys me

Re-encoding treats every failure as a codec failure. It isn't. A two-hour film takes real time to convert, loses a little quality or doubles in size, and you repeat the ritual for every new file. When the actual problem is the player being lazy about indexes, conversion is pure waste.

Skip the conversion: change who reads the file

The file doesn't have to go through the TV's USB player at all. Feed it to the screen through a smarter path and let a proper decoder handle it. That's the slot Chusko fills: your phone streams the raw bytes to the screen device, which serves them to its own player with full range-request seeking. There's no remuxing step, so an MP4 whose index sits at the end plays fine; the player just requests the pieces it needs as it needs them.

Two ways this solves the two non-codec failures:

• Index-at-end MP4s and other container quirks stop mattering, because the receiving side reads the file progressively instead of demanding a front-loaded index.
• You can pick a screen that decodes more than the TV does. A laptop hooked to the TV over HDMI, running Chusko in the browser as the Screen, will play things the TV's built-in player won't.

A quick decision guide

1. Rejected from USB but plays in VLC? Player limitation. Stream it instead of converting.
2. Video works, silence? Check the audio track. If it's DTS or AC3 and your TV can't decode it, either use a screen that can or convert just the audio track, which takes minutes instead of hours.
3. Fails identically on every device you own? Now convert. HandBrake with an H.264 + AAC output plays on everything.

For how the streaming side works under the hood, see how Chusko casts video peer-to-peer. Formats, pairing, and encryption have short answers in the FAQ.