New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDR Metadata Missing #10363
Comments
The files you linked result in 404 errors for me. |
I will write both the files here OBS 30.0.2 file MediaInfoGeneral Video Audio OBS 30.1.0 file MediaInfoGeneral Video Audio |
Please provide a test video created with OBS Studio 30.0.2 and one produced with OBS Studio 30.1.0. |
I can confirm that checking with ffprobe 6.1.1, HDR recordings from OBS Studio 30.0.2 seem to have HDR metadata (CLL, luminance, mastering, etc.) while recordings from OBS Studio 30.1.0 do not. We'll investigate. Thanks. |
Sorry for the late response. If you guys need anything else for troubleshoot, I can provide. Thanks for the amazing work. |
It looks like this might be specific to NVENC. When encoding HDR with QSV or AMF, it works fine. |
Tested also with both AOM AV1 and SVT-AV1. Same behaviour, no metadata using the latest obs version. |
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
30.1.0
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/ODa2WnwU5iRmtFBX
OBS Studio Crash Log URL
No response
Expected Behavior
In the previous OBS Version (30.0.2) the recorded files would show correctly set as HDR10 compatible and contain the mastering display metadata.
Media Info Export 1.txt
Current Behavior
In the current OBS Version (30.1.0) the recorded file is missing the mastering display metadata, causing playback issues in MPC-HC and potentially in other softwares as well.
Media Info Export 2.txt
Steps to Reproduce
Anything else we should know?
I guess that's something related to the Lavf version used in the new OBS, as it was the only change I could see in both files info.
I also tested with HEVC and changed the container to MP4, same behaviour.
The text was updated successfully, but these errors were encountered: