Transcode Failure for MPEG-TS Recordings on Samsung TV — "No compatible streams available"

[Ladiesman0217 15]

Environment:

• Emby Server: v4.9.5.0 (Docker container)
• Client: Emby app on Samsung Smart TV
• File Format: MPEG-TS (.ts)
• Server OS: Linux

Issue Description:

When attempting to play a MPEG-TS live recording on a Samsung Smart TV via the Emby app, users receive the error:

"No compatible streams are currently available. Please try again later or contact your system administrator for details"

Reproduction Steps:

1. Record a live MPEG-TS stream (.ts file) via Emby Live TV
2. Attempt to play the recording on a Samsung Smart TV using the Emby app
3. Error occurs immediately

Expected Behavior:
The Emby server should transcode the MPEG-TS file to a format compatible with the Samsung TV client

Actual Behavior:
Transcode fails with ContainerNotSupported error. Server has no fallback and cannot serve the stream.

Logs:
Server logs show transcode failures:

• ContainerNotSupported
• SubtitleCodecNotSupported

Workaround:
Playing the same file on Android (Pixel 7 Pro) works perfectly — device has native MPEG-TS codec support.

Additional Info:
Samsung TV appears to lack native MPEG-TS support and relies on server-side transcoding, which is currently failing.

Relevent logs (redacted sensitive info)

Successful Android (Pixel) Playback:

2026-08-11 23:09:01.822 Info PlaystateService-0HNNNNQ5LMFTJ:00000001: http/1.1 POST http://[REDACTED_DOMAIN]/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=Living Room TV&X-Emby-Device-Id=[REDACTED_DEVICE_ID]&X-Emby-Client-Version=3.5.36&X-Emby-Token=[REDACTED_TOKEN]&X-Emby-Language=en-us&reqformat=json. Source Ip: [REDACTED_IP], UserAgent: Mozilla/5.0 (Linux; Android 11; Philips 4K A1 Build/RTM8.240401.161; wv)

2026-08-11 23:09:01.823 Info PlaystateService-0HNNNNQ5LMFTJ:00000001: http/1.1 Response 204 to [REDACTED_IP]. Time: 1ms. POST http://[REDACTED_DOMAIN]/emby/Sessions/Playing/Progress

 

Samsung TV Playback Attempt (with TranscodeReasons=ContainerNotSupported):

2026-08-11 23:09:03.681 Info DynamicHlsService-0HNNNNQ5LMFTN:00000001: http/1.1 GET http://[REDACTED_DOMAIN]/emby/videos/6991495/hls1/subs/749.vtt?PlaySessionId=f27d09f507764925afe7d1b42cb6bece&VttTimestampMap=900000&CurrentSubtitleStreamIndex=2. Source Ip: [REDACTED_IP], User-Agent=samsung-agent/1.1

2026-08-11 23:09:03.683 Info DynamicHlsService-0HNNNNQ5LMFTN:00000001: http/1.1 Response 200 to [REDACTED_IP]. Time: 2ms. GET http://[REDACTED_DOMAIN]/emby/videos/6991495/hls1/subs/749.vtt

 

Web Client Transcode Failure (ContainerNotSupported):

2026-08-11 23:09:04.692 Info DynamicHlsService-0HNNNNQ5LMFTQ:00000001: TranscodeReasons=ContainerNotSupported... Source Ip: [REDACTED_IP], User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64)... Chrome/151... Microsoft Edge

 

If you'd rather just have the raw log file let me know how to send it privately.

 

 

 

[Luke 42920]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[SamES 1124]

What year/model is the Samsung TV?

[Ladiesman0217 15]

Looking at the Devices list, I see this:

Samsung Smart TV (UN65AU8000FXZA)
Emby for Samsung 2.2.8

Luke, I'll need them to reproduce the error again so I can grab the logs before they roll off.  Will post a proper play issue report at that time, thanks!

[Ladiesman0217 15]

Attaching log file.  I had them test it again, and the streaming failure in this log is at/around 2026-08-12 23:24

embyserver-63922176000.txt

[Luke 42920]

HI, are you able to try the usb version of the app and see how the latest build compares?

[Ladiesman0217 15]

I'll have them try that. Why would the latest version in the Smart TV App Store be so old? Looks like 2.2.8 (their version) was 12 release versions ago!

 

 

[Luke 42920]

We release new usb builds fairly frequently and it takes a long time to get updates through the store review process.

[SamES 1124]

14 hours ago, Ladiesman0217 said:

Attaching log file.  I had them test it again, and the streaming failure in this log is at/around 2026-08-12 23:24

embyserver-63922176000.txt 37.33 MB · 1 download

Are there any ffmpeg/transcode logs when they attempt to play?

[Ladiesman0217 15]

9 hours ago, SamES said:

Are there any ffmpeg/transcode logs when they attempt to play?

Atttached.

ffmpeg-transcode-8692bd51-f89b-4d46-be5c-3111623cf393_1.txt ffmpeg-transcode-5adea92a-3fed-4f43-9e1a-abf51fe2e425_1.txt ffmpeg-transcode-ab24b7e7-6667-42db-b6ed-9039459b02cc_1.txt ffmpeg-transcode-032d317d-c834-4aeb-8ab4-0e7f1d8efd96_1.txt ffmpeg-transcode-9ad9f133-55ae-4e91-9f29-8e3a2c4895a5_1.txt ffmpeg-transcode-fafcdc0f-9907-4940-865c-cbffe7897aa3_1.txt ffmpeg-transcode-31015bd5-b0c1-42bf-aa67-e37c5d4d691f_1.txt ffmpeg-directstream-c6b8a140-d8d3-4b88-80c4-782919e2d005_1.txt ffmpeg-transcode-59c83425-ea29-4072-9cd8-653213e7601b_1.txt

[Luke 42920]

OK we are looking into it. Thanks.