HLS troubleshooting by symptom

Playlist loads but playback stays blank

Inspect the child playlist and first segment requests. A master response alone does not prove that its referenced media playlist or codecs can play.

Confirm the player supports HLS natively or is using an appropriate JavaScript playback library. Then check the console for media and decode errors.

• Confirm #EXTM3U is the first line
• Open the child playlist URL
• Check the first segment response body
• Verify codec support on the target device

Segments return 404

Resolve each URI relative to the playlist URL. Letter case, flattened directories, renamed files, and an incorrect base URL are common causes.

For Master output, index.m3u8 and its segments belong under the 720p or audio directory exactly as generated.

Playlist URL: https://cdn.example.com/show/720p/index.m3u8
URI in file: segment_001.ts
Resolved URL: https://cdn.example.com/show/720p/segment_001.ts

CORS or mixed-content error

Allow the player origin on both playlist and segment responses when media is cross-origin. If the page uses HTTPS, serve the media over HTTPS too.

Test the failing request directly and inspect response headers; changing only the page's JavaScript cannot add permission to another origin's response.

Conversion stops or output is wrong

A memory failure often improves with a shorter or lower-resolution source and fewer concurrent applications. Missing audio or decode errors can indicate an unusual source codec or a damaged file.

Try a short known-good sample, keep the original, and compare Standard with Master. Report reproducible problems with browser version, operating system, input format, duration, selected mode, and the exact visible error—never send private media unless you choose to.