UnkNow404 3 Posted August 11, 2025 Posted August 11, 2025 由于服务器返回的m3u8中将VIDEO-RANGE设置为"DolbyVision"或者"HDR 10",不在hls.js中允许的VideoRange内(VideoRangeValues=['SDR', 'PQ', 'HLG']),导致hls.js无法解析和播放HDR视频流。 Because the VIDEO-RANGE is set to "DolbyVision" or "HDR 10" in the m3u8 returned by the server, it is not within the VideoRange allowed in the hls.js (VideoRangeValues=['SDR', 'PQ', 'HLG']), so the hls.js cannot resolve the HDR video stream to play it. 经过测试,需要手动修改hls.js增加VideoRangeValues字段防止未知的VideoRange,或者服务器返回正确的VideoRange才能解决此问题。有关杜比视界的HLS标准可参考:https://professionalsupport.dolby.com/s/article/How-to-signal-Dolby-Vision-in-HLS Tested that manual modifications hls.js increase the VideoRangeValues field to prevent unknown VideoRanges, or the server returns the correct VideoRange is required to resolve this issue. For HLS standards for Dolby Vision, please refer to: https://professionalsupport.dolby.com/s/article/How-to-signal-Dolby-Vision-in-HLS
brothom 177 Posted August 11, 2025 Posted August 11, 2025 If I'm not mistaken; DolbyVision or DV is a patented technology and you can't just "add support" for it. For example some LG TV's support DV but almost none of the Samsung TV's support it because Samsung didn't want to get the DolbyVision license. This issue is much broader than just adding a value to al ist of values and enters copyright regions much like certain AAC codecs like libfdk_aac aren't natively supported by FFMPEG either. Even converting from DV to HDR is a pain because its requires the dovi integration in FFMPEG. 1
UnkNow404 3 Posted August 11, 2025 Author Posted August 11, 2025 (edited) 11 hours ago, brothom said: If I'm not mistaken; DolbyVision or DV is a patented technology and you can't just "add support" for it. For example some LG TV's support DV but almost none of the Samsung TV's support it because Samsung didn't want to get the DolbyVision license. This issue is much broader than just adding a value to al ist of values and enters copyright regions much like certain AAC codecs like libfdk_aac aren't natively supported by FFMPEG either. Even converting from DV to HDR is a pain because its requires the dovi integration in FFMPEG. 不,我想你没有理解我的问题。问题在于当播放HDR10内容时也会出现返回不受hls.js支持的VIDEO-RANGE,不仅是Dolby Vision会出现这个问题。 No, I don't think you understand my question. The problem is that when playing HDR10 content, there is also a return to VIDEO-RANGE that is not supported by hls.js, and not only Dolby Vision has this problem. Edited August 11, 2025 by UnkNow404
UnkNow404 3 Posted August 11, 2025 Author Posted August 11, 2025 Just now, Luke said: Hi, what changes did you make to hls.js? Add new values to VideoRangeValues in "types/level.ts" export const VideoRangeValues = [‘SDR’, ‘PQ’, ‘HLG’, ‘DolbyVision’, ‘HDR 10’] as const; However, I would prefer the server to return the canonical VIDEO-RANGE to fix this issue 1
Solution UnkNow404 3 Posted October 30, 2025 Author Solution Posted October 30, 2025 The latest version has resolved this issue. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now