2025-04-06, 06:19 AM
(This post was last modified: 2025-04-06, 07:03 AM by forbis. Edited 1 time in total.)
I just finished using Handbrake to encode a 4K Dolby Vision Profile 8.1 (HDR10) source using the x265 10-bit encoder. The output file format was set to MP4. I placed this file in my Jellyfin library's folder.
When I attempt to play this file in the Jellyfin Web interface (using Chrome 134 on Windows), it forces remuxing stating that the container is not supported - and in "Playback info" the container is identified as "mov". I observe the same behavior in Jellyfin Media Player (v1.12.0 for Windows). Interestingly, when I play on my Android phone using the Jellyfin app, the container is properly displayed as "mp4" in the "Playback info" screen, and is direct playing. Jellyfin server and web version is 10.10.6.
Is this expected/normal behavior? Is there a limitation on Windows to not be able to directly play HDR10/Dolby Vision in MP4 format, or is the container somehow being misidentified as "mov" - and if so, why is it only happening on Windows? Any assistance in further diagnosing this would be greatly appreciated.
Thanks in advance for your input.
When I attempt to play this file in the Jellyfin Web interface (using Chrome 134 on Windows), it forces remuxing stating that the container is not supported - and in "Playback info" the container is identified as "mov". I observe the same behavior in Jellyfin Media Player (v1.12.0 for Windows). Interestingly, when I play on my Android phone using the Jellyfin app, the container is properly displayed as "mp4" in the "Playback info" screen, and is direct playing. Jellyfin server and web version is 10.10.6.
Is this expected/normal behavior? Is there a limitation on Windows to not be able to directly play HDR10/Dolby Vision in MP4 format, or is the container somehow being misidentified as "mov" - and if so, why is it only happening on Windows? Any assistance in further diagnosing this would be greatly appreciated.
Thanks in advance for your input.