This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

FIXED - incorrect x265 HDR signaling config load
Hybrid 2022.03.20.1 Win64
I have 2 stored configurations for x265, the 1st with HDR, the 2nd without HDR.

I apply 1st, command line looks like:

x265 --input - --output-depth 10 --y4m --profile main10 --crf 19.00 --qpfile GENERATED_QP_FILE --aq-strength 0.7 --no-sao --selective-sao 0 --range limited --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --chromaloc 2 --hdr10 --hdr10-opt --sar 1 --output OUTPUTFILE

Then I apply 2nd, command line looks:

x265 --input - --output-depth 10 --y4m --profile main10 --crf 19.00 --qpfile GENERATED_QP_FILE --aq-strength 0.7 --no-sao --selective-sao 0 --hdr10 --sar 1 --output OUTPUTFILE
--hdr10 should not be there!

Then I apply 2nd again, command line looks finally correct:

x265 --input - --output-depth 10 --y4m --profile main10 --crf 19.00 --qpfile GENERATED_QP_FILE --aq-strength 0.7 --no-sao --selective-sao 0 --sar 1 --output OUTPUTFILE

Thank you.

Attached Files
.zip (Size: 4,19 KB / Downloads: 8)
I can rproduce the issue.
Starting Hybrid, appliyng 'm5'-profile, '--hdr10' is not there.
Applying first 'm5 HDR' profile and then the 'm5'-profile, HDR isn't reset properly, applying 'm5'-profile again, settings are correct.

Cu Selur
Assuming you use Windows I send you a link to a Windows dev version via pm which should fix the issue.

Cu Selur
Thumbs Up 
Thank you, I can confirm it is fixed in dev build.

Forum Jump:

Users browsing this thread: 1 Guest(s)