as answer to you PM:
x265 aborts the encoding with:
aborts with:
but according to the documentation:
the option does exist and Hybrid does not abort here with that option.
The only thing I see that is wrong is '--transfer=16' no clue where that comes from, aside from a custom command line addition (or a failed import from Mediainfo) Hybrid should not produce this.
When I load the sample you linked to transfer is used through '--transfer smpte2084' and no additional '--transfer=16' is added.
The DeSharpen-category was removed quite a while ago, clearing your defaults should fix the issue.
This error should only appear if you did not reset your defaults half a year ago or so when it was last requested or you are using some really old Global Profile.
-> if you use an old global profile load the profile, ignore the error and save it again.
Cu Selur
x265 aborts the encoding with:
"C:\PROGRA~1\Hybrid\x265.exe" --preset ultrafast --log-level 2 --input - --output-depth 10 --y4m --profile main10 --level-idc 5.1 --no-hme --pass 1 --slow-firstpass --bitrate 12800 --qpfile "J:\2160p HDR Output_01_16_55_1710_02.qp" --vbv-maxrate 160000 --vbv-bufsize 160000 --sao --range limited --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --chromaloc 2 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50)" --hdr --hdr-opt --transfer=16 --stats "J:\2160p HDR Output_01_16_55_1710_03.stats" --no-multi-pass-opt-analysis --output "J:\2160p HDR Output.265"Quote:unknown option --no-hme
but according to the documentation:
Quote:--hme, --no-hmesource: https://x265.readthedocs.io/en/latest/cl...option-hme
Enable 3-level Hierarchical motion estimation at One-Sixteenth, Quarter and Full resolution. Default disabled.
the option does exist and Hybrid does not abort here with that option.
The only thing I see that is wrong is '--transfer=16' no clue where that comes from, aside from a custom command line addition (or a failed import from Mediainfo) Hybrid should not produce this.
When I load the sample you linked to transfer is used through '--transfer smpte2084' and no additional '--transfer=16' is added.
Quote:I've been using the same customized preset prior to and after experiencing this error, and the same DeSharpen Error pops up with any of the preset x265 (fast, very fast, medium etc) options.The DeSharpen error has nothing to do with x265 presets.
The DeSharpen-category was removed quite a while ago, clearing your defaults should fix the issue.
This error should only appear if you did not reset your defaults half a year ago or so when it was last requested or you are using some really old Global Profile.
-> if you use an old global profile load the profile, ignore the error and save it again.
Cu Selur