How to Fix Media Playback That Stops at the Same Chapter Only With PGS Subtitles Enabled

Eva Wong

IceWhale author

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

How to Fix Media Playback That Stops at the Same Chapter Only With PGS Subtitles Enabled - Zima Store Online

Playback that stops at the same chapter only with PGS subtitles enabled usually points to the subtitle burn-in transcode path, not the chapter marker itself.

Keep the same movie, client, chapter, audio track, and network path while changing only the subtitle state. If playback passes the failure point with subtitles off or with a text subtitle such as SRT, the useful branch is image-subtitle handling: burn-in, hardware decode and encode transitions, tone mapping, temporary transcode files, and client compatibility. Do not remux or replace the whole movie until the subtitle-triggered path is proven.

Prove the Failure Follows PGS Subtitles

Replay the same segment with PGS disabled, then with the same PGS track enabled. If available, repeat with an SRT subtitle while keeping the client and video track unchanged. Record whether the server reports direct play, direct stream, or full transcode in each test.

A Jellyfin playback explainer notes that PGS uses subtitle burn-in rather than being carried as a simple text overlay.

If every subtitle state fails at the same chapter, return to the generic fixed-position playback diagnosis. If only the PGS path fails, keep the repair focused on subtitle rendering and transcode behavior.

Check Whether Burn-In Overloads the Server

Watch CPU, GPU, memory, transcode speed, and dropped-frame indicators as playback approaches the failure point. Compare those values with the same chapter played without PGS or with a text subtitle.

A focused Jellyfin guide explains that PGS can overload low-power servers when the client cannot render the image stream itself.

If transcode speed falls below real time before playback ends, increase capacity only after proving the bottleneck. A text-subtitle alternative can be a valid compatibility test without modifying the original Blu-ray subtitle track.

Inspect the Transcoder Log at the Exact Stop Point

Capture the server and FFmpeg log from several minutes before the stop through the session end. Look for filter errors, broken subtitle packets, encoder resets, temporary-file failures, or the server incorrectly treating the transcode as complete.

An Emby case documents that transcoded playback can end early while the underlying media file could still be resumed later.

If the server closes the transcode at the same timestamp, save that log before changing settings. If the server continues producing output while only one client stops, move the next test to client playback compatibility instead.

Featured

ZimaCube 2 Personal Cloud Home NAS

ZimaCube2

Compare Hardware and Software Subtitle Paths

Run one controlled test with hardware acceleration enabled and one with the smallest supported software fallback. Keep output resolution and subtitle track the same so the only major difference is the decode-filter-encode path.

A Plex troubleshooting thread shows that PGS can break hardware transcoding even when ordinary hardware transcoding works.

If software reaches the chapter cleanly while the accelerated path stops, keep the original file and adjust the hardware-transcode path, driver, or server version. Do not permanently disable acceleration for every title without a wider test.

Confirm the Subtitle Must Be Burned Into the Video

Check whether the client can render PGS directly. If it cannot, the server may have to overlay the bitmap subtitle onto decoded video frames and encode a new video stream for that session.

An FFmpeg discussion makes the processing boundary clear: burn-in requires video re-encoding when the subtitle is hardcoded into the image.

Test another client with native PGS support before changing the library. If that client direct-plays through the chapter, the source file is less likely to be corrupt and client capability becomes the safer remediation target.

Verify the Fix on the Original Chapter

Apply only the confirmed change: a working acceleration path, compatible subtitle format for that client, updated server or client, or sufficient transcode resources. Replay from several minutes before the original stop point and continue beyond it twice.

A Firecore discussion notes that PGS support varies by client rather than every playback device handling the same subtitle stream identically.

The issue is resolved when the same client passes the chapter repeatedly with the intended subtitle enabled. The related ZimaSpace guide to the broader home media workflow is the adjacent branch when failures are no longer specific to PGS subtitle playback.

Frequently Asked Questions

Does a chapter marker itself make PGS playback stop?

Usually not. The chapter provides a repeatable timestamp, but the failure may be a subtitle packet, transcode state, filter step, or client transition reached at that point.

Should I convert every PGS subtitle to SRT?

No. Use an SRT copy as a discriminator or client-specific compatibility option. Keep the original image subtitle when its styling, forced signs, or language layout matters.

Why can the movie direct-play correctly with subtitles off?

Disabling an unsupported image subtitle can remove the burn-in requirement, allowing the client to receive the original video stream without the failing transcode path.