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.

[BUG] Video Crashed "" was not created!
as answer to you PM:

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"
aborts with:
Quote:unknown option --no-hme

but according to the documentation:
Quote:--hme, --no-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

Messages In This Thread
RE: Video Crashed "" was not created! - by Selur - 07.01.2020, 18:34

Forum Jump:

Users browsing this thread: 1 Guest(s)