mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: 10.9.2 incorrectly remuxing Dolby Vision Profile 8 for WebOS #5792
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 @chibears85 on GitHub (May 18, 2024).
Please describe your bug
Dolby Vision content that is Profile 8 is remuxing for the WebOS client. On 10.8.x this context want direct played using HDR fallback. Since 10.9, this content is remuxed, however it is not triggering Dolby Vision and instead comes through as HDR. Ideally this should either be a flag that the user can set or at the very least if it won't correctly remux with DV, then it should direct play with HDR fallback.
Reproduction Steps
Jellyfin Version
10.9.0
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@jellyfin-bot commented on GitHub (May 18, 2024):
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
@gnattu commented on GitHub (May 18, 2024):
Some LG TVs incorrectly report that they don't support profile 8.
This works for some users with LG C3, but it does not work for a lot of CX users. I have no idea how this should be handled if the TV itself has such inconsistencies.
@GeorgeH005 commented on GitHub (May 18, 2024):
@gnattu He doesn't seem to be affected. His ffmpeg logs show that the stream is being tagged as dvh1. But the hls_segment_type is mpegts for some reason. Shouldn't that be fmp4?
@GeorgeH005 commented on GitHub (May 18, 2024):
@chibears85 In the client, when clicking the profile icon, then settings, then playback, is "Prefer fmp4 hls container..." ticked? It should be, but the logs might be showing otherwise.
@gnattu commented on GitHub (May 18, 2024):
Users can disable it, or it inherits the old settings from a previous version.
@GeorgeH005 commented on GitHub (May 18, 2024):
Seems reasonable.
@chibears85 Consensus for now is, check your client playback settings for something mentioning "fmp4" and make sure it is checked.
@chibears85 commented on GitHub (May 18, 2024):
@GeorgeH005 thank you. I have already tried that and the outcome was the same. I'll test out with some other files and subsequently post the logs to confirm it's not limited to the current file.
@GeorgeH005 commented on GitHub (May 18, 2024):
@chibears85 The file itself seems to be handled correctly, as for jellyfin to tag the stream as dvh1, the server must have detected the format correctly, and the client must have reported support for that format. The curious thing is that the stream is being done in a ts container, for which lg doesn't support Dolby vision.
@gnattu commented on GitHub (May 18, 2024):
Don't only look at the video itself. What @GeorgeH005 wants is the ffmpeg log file when fMP4 is enabled
@fanginoort commented on GitHub (May 18, 2024):
I can confirm that enabling fMP4 also triggers DV playback instead of HDR fallback on my LG B2. However it's a bit of a hit and miss. Sometimes it just works and sometimes it transcodes because it thinks the dynamic range is not supported. However when I disable video transcoding for the user, it plays back with with DV just fine.
I do disable the fMP4 option though, since it's somewhat broken on WebOS. When it's enabled, seeking or resuming is not possible anymore. Whenever seeking more than just a couple of minutes playback just freezes. On disabled fMP4 this does not occur. At least for 4K DV/HDR media.
@chibears85 commented on GitHub (May 18, 2024):
I enabled the fMP4 option. When playing back a title from the beginning it does trigger DV and behave as expected. However, when resuming a title from the middle, the DV popup appears as does the Jellyfin UI but the video playback is just a black screen. My TV is an LG C2 with the latest WebOS and Jellyfin installed if that is helpful. ffmpeg log below.
@abhijithshaji commented on GitHub (May 18, 2024):
I just updated Jellyfin to 10.9.2 in my ubuntu server and started facing the same issue.
When playing back a title from the beginning it does trigger DV and behave as expected. However, when resuming a title from the middle, the DV popup appears as does the Jellyfin UI but the video playback is just a black screen. My TV is an LG C2 with the latest WebOS and Jellyfin@lgndvd commented on GitHub (May 18, 2024):
@GeorgeH005: LG CX supports natively DV5 and DV8 content in both MP4 and TS containers :)
I used to convert a lot of MKV to TS to trigger Dolby Vision (I prefer TS to MP4 for remuxing convenience). Until 10.8.x, when direct playing those containers I got Dolby Vision metadata work as expected.
After 10.9.x, as mentioned in #10468 and #11681, I get these results:
MKV DV5: triggers Dolby Vision (progression)
TS DV5: triggers Dolby Vision (same as 10.8)
MP4 DV5: triggers Dolby Vision (same as 10.8)
MKV DV8: triggers HDR (same as 10.8)
TS DV8: triggers HDR (regression)
MP4 DV8: triggers HDR (regression)
@GeorgeH005 commented on GitHub (May 18, 2024):
@lgndvd I will make a patch that overrides the support status reported by the tv. It is up to the maintainers' discretion whether it should be merged or not.
@lgndvd commented on GitHub (May 18, 2024):
@GeorgeH005 let me know if I could help for any kind of testing (I'm no coder and relatively new to github, but I'm used to give feedback hoping to improve everyone's experience).
In any case, thank you for your contribution!
@GeorgeH005 commented on GitHub (May 19, 2024):
This should be a separate issue.
@gado4525 commented on GitHub (May 19, 2024):
I’m having the same/similar issue on Ubuntu server since 10.9.0 and LG C1, I wasn’t having problems with DV/HDR in mkv using the fmp4 option, now it triggers DV but get a lot of hangs (sometimes it shows the movie art then continue playing) then when it resumes DV is not longer triggered in the tv, movies continues playing with washed/dull colors. It used to report direct playing now is showing repacking
@megosugit commented on GitHub (May 30, 2024):
did you find a solution for this ? I have the same issue with a LG G3.
Unfortunately, some movies only have DV and no HDR as fallback, so if I disable fMP4 option, I can seek or resume but the colors are washed up.
Disabling fMP4 works for other movies having both DV and HDR.
Is there an issue opened about this seek/resume with DV issue ? I couldn't find one and this one seems to be unrelated.
@gnattu commented on GitHub (May 30, 2024):
We have an on-going effort here: https://github.com/jellyfin/jellyfin-web/pull/5553
@jellyfin-bot commented on GitHub (Oct 30, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (Nov 20, 2024):
This issue was closed due to inactivity.