mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Issue with Jellyfin on LG55C6V: Remuxing Instead of Direct Play #6852
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kitopopo on GitHub (Mar 27, 2025).
Description of the bug
Hi dear friends,
I have an LG 55C6V with webOS 3.4.2-610708, and the webOS APK version is 1.2.2. Jellyfin performs remuxing (container conversion) on most movies, even when the TV supports the video and audio formats.
Observed Behavior:
Jellyfin converts most movies to HLS, even if the original file is MKV.
Plex plays movies in "Direct Play" mode without remuxing or transcoding on the same TV.
When played from a USB drive, the TV handles all files without issues (MKV, H264, H265, DTS, AC3, etc.).
On a newer LG TV, Jellyfin performs "Direct Play" without remuxing or transcoding.
Disabling remuxing in Jellyfin causes playback to fail on this TV.
Changing client settings has not resolved the issue.
I have disabled the video and audio transcoding options because if I don’t, Jellyfin transcodes the movie, which I do not want. However, it still performs remuxing.
In the log appears: "SupportsDirectStream":true
Playback Issue:
Initially, the movie starts in "Direct Play" mode for about 10 seconds, but after those 10 seconds, Jellyfin begins performing remuxing.
Suggestion:
Perhaps if they added an option to force direct playback or a way to configure my TV model in the server settings to detect that it can perform direct playback, it would be useful.
Request for Help:
I hope you can help me find the issue. If you need any additional data or logs from movies that are played without remuxing, I can provide them, but as mentioned, most movies are the ones that perform remuxing.
Thanks for this amazing project and for maintaining it, as it is exceptional. Best regards and thank you.
Reproduction steps
Install Jellyfin server and client on the LG TV with webOS 3.4.2-610708.
Add a movie in MKV format with compatible video and audio codecs (e.g., H264, AC3, DTS).
Play the movie through Jellyfin.
Observe that the movie initially plays in "Direct Play" mode for about 10 seconds.
After 10 seconds, Jellyfin switches to remuxing, even though the TV supports the video and audio formats natively.
Notice that playback continues with remuxing and no longer remains in "Direct Play."
What is the current bug behavior?
Jellyfin remuxes most movies to HLS format, even if the original file is an MKV with supported video and audio formats (such as H264, H265, DTS, AC3).
Despite the TV being capable of handling these formats natively, Jellyfin still switches to remuxing after initially playing in "Direct Play" mode for about 10 seconds.
This behavior occurs even when transcoding and remuxing settings are disabled in Jellyfin, and playback from a USB drive works fine without any remuxing.
What is the expected correct behavior?
Jellyfin should play the movies directly without remuxing or transcoding, as the TV supports the video and audio formats (such as H264, H265, DTS, AC3) natively.
The movie should start in "Direct Play" mode and remain in that mode without switching to remuxing.
Jellyfin should detect that the TV can handle the formats properly and not perform unnecessary remuxing or transcoding.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.6
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@kitopopo commented on GitHub (Apr 1, 2025):
hi dear friends,
I've been testing Jellyfin on my LG 55C6V and noticed a strange behavior when playing files with multiple audio tracks.
To investigate, I took two movies with multiple audio tracks in different formats and used a well-known program to multiplex each movie in two ways:
Multiplexed with a single audio track → Jellyfin plays the file without any issues, no remuxing occurs.
Multiplexed with two or more audio tracks → Jellyfin starts remuxing instead of playing the file directly.
Surprisingly, each audio track works perfectly when multiplexed individually with the video and subtitles. However, when the file contains multiple audio tracks, Jellyfin seems to struggle with handling them correctly and starts remuxing.
My question is: Why does Jellyfin not remux when there's only one audio track, but it does when there are multiple tracks? It seems like Jellyfin can't separate the audio tracks properly and remuxes the entire file instead. Is there a way to prevent this and allow multiple audio tracks without remuxing?
I hope this issue can be fixed in the next Jellyfin version or future updates. Thanks for your hard work and dedication!
@felix920506 commented on GitHub (Apr 28, 2025):
Working as intended. MKV is problematic on WebOS.
@kitopopo commented on GitHub (Apr 28, 2025):
Thank you for your reply.
However, I would like to point out that I have another LG TV (model 49SM9000PLA with WebOS) where Jellyfin works perfectly in "Direct Play" without remuxing, using the same server, settings, and media files.
This suggests that the problem is not strictly due to WebOS in general, but may vary depending on the specific WebOS version, device model, or how Jellyfin identifies the client capabilities.
Therefore, I kindly request not to close the issue yet.
It would be very helpful if you could implement an option to force Direct Play at the user's own risk, or to allow manual configuration of client capabilities in the server settings, so we can bypass automatic detection when necessary.
I would also like to highlight that when playing movies directly from a USB drive on the TV, all files play correctly using direct playback (Direct Play), and when using Plex, the files also play without any need for remuxing or transcoding.
As a final note, thank you very much for maintaining this amazing project. Jellyfin is an exceptional platform and I truly appreciate your work.
Best regards.
@Troyzig commented on GitHub (Sep 4, 2025):
I am having the same issue on lg webos 24 (LG oled65" b4 tv), served by jellyfin 10.10.7 on a windows 11 pc. Please find a solution.
@kitopopo commented on GitHub (Sep 4, 2025):
Hi, I’m still experiencing this issue on my LG55C6V. Could you please look into it and consider reopening the issue? I’d really appreciate any solution or guidance.
Thank you!
@akritm commented on GitHub (Sep 29, 2025):
I've noticed similar problem, but on web client. On my test files (both mkv and mp4) jellyfin somehow works differently on Chrome / Edge / Jellyfin Media player on same windows machine with same user. MKV includes multiple tracks : including AC-3 Stereo, AC-3 5.1 and E-AC-3 JOC 5.1 (Dolby Digital Plus with Dolby Atmos). They all works the same.
Logs are showing TranscodeManager line with -codec:a:0 libfdk_aac parameter (transcoding AC_3 ->AAC)
Logs are showing TranscodeManager line with -codec:a:0 copy parameter (no transcoding of audio)
updated: to confirm point 4 I manually converted mkv to mp4 container with no transcodding of video and audio - and now it uses direct play.