01.09.2018, 07:45
(12.08.2018, 13:25)Selur Wrote: Using:
(just changed, the path to the tools and the location of the temp folder), the call works fine for me."I:\Hybrid\64bit\ffmpeg.exe" -y -threads 8 -i "D:\TestClips&Co\files\test.avi" -map 0:0 -an -sn -vf zscale=rangein=tv:range=tv -pix_fmt yuv420p10le -strict -1 -vsync 0 -f yuv4mpegpipe - | "i:\Hybrid\64bit\x265.exe" --input - --output-depth 10 --y4m --profile main10 --no-high-tier --level-idc 5.1 --qg-size 8 --limit-modes --no-open-gop --opt-ref-list-length-pps --keyint 60 --min-keyint 1 --lookahead-slices 0 --bitrate 40000 --crf-min 0.00 --crf-max 0.00 --opt-qp-pps --cbqpoffs -2 --crqpoffs -2 --limit-refs 0 --ssim-rd --psy-rd 2.50 --rdoq-level 2 --psy-rdoq 10.00 --aq-mode 0 --vbv-maxrate 40000 --vbv-bufsize 40000 --hrd --aud --deblock=-1:-1 --limit-sao --repeat-headers --range limited --colorprim bt2020 --colormatrix bt2020nc --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "1000,180" --hdr --output "d:\06_39_58_5510_04.265"
I get the same errors you did when the temp folder doesn't exist.
(tried different sources and couldn't reproduce the issue)
-> Does the folder: ""C:\Users\User\AppData\Local\Temp\" exist and can your user write to it?
Apologies for butting in but isn't the problem the renaming of the --transfer option to smpte2084 in an updated x264 where the GUI puts the old option name in there?
There doesn't look like there's a --transfer option in the above at all.
Oh, oops!
I'm confused, sorry.