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.

[HELP] Hybrid stops coding
#1
I absolutely do not understand what the problem is. In the program, in a video file or in the settings. Just in case I attach a log. Coding breaks already on the final credits when this zone is encoded with qp = 35
Tried to google this problem, but failed
Reply
#2
You forgot to attach a debug output log,...
Also I'm not sure what you mean with 'Coding breaks already on the final credits when this zone is encoded with qp = 35',...
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
Indeed, I forgot to attach the archive with the log. Fixed it in the first message.

Sorry for bad English. In the encoding settings, I specified the key "--zones 168042,173346, q = 35" and an error occurred when the video was encoded in this range.
Reply
#4
Ah okay, got it will look into it and report back.

The encoding call:
"C:\PROGRA~1\Hybrid\64bit\ffmpeg.exe" -y -loglevel fatal -threads 8 -i "Z:\True Romance.mkv" -map 0:0 -an -sn -vf crop=1920:816:0:132,zscale=rangein=tv:range=tv -pix_fmt yuv420p10le -strict -1 -vsync 0  -f yuv4mpegpipe - | "C:\PROGRA~1\Hybrid\64bit\x265.exe" --preset placebo --input - --output-depth 10 --y4m --profile main10 --level-idc 4.1 --limit-tu 1 --subme 7 --merange 57 --limit-modes --no-tskip --no-strong-intra-smoothing --keyint 240 --min-keyint 23 --bframes 13 --lookahead-slices 1 --qpmax 69 --crf 19.50 --qpfile "Z:\True Romance_new_18_07_23_9510_01.qp" --limit-refs 1 --rd 5 --psy-rdoq 1.10 --qcomp 0.75 --qp-adaptation-range 2 --aq-mode 0 --hevc-aq --no-cutree --vbv-maxrate 50000 --vbv-bufsize 50000 --deblock=-3:-3 --no-sao --zones 168042,173346,q=35 --range limited --colormatrix bt709 --output "Z:\18_07_23_9510_02.265"
Looks fine to me and the syntax of the 'zones' part (matches the definition, see: https://x265.readthedocs.io/en/default/c...tion-zones)
-> Do you get any error messages when calling the encoding call inside a Windows Command Prompt? (using the call here throws no error)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
(27.04.2019, 09:34)Selur Wrote: Ah okay, got it will look into it and report back.

The encoding call:
"C:\PROGRA~1\Hybrid\64bit\ffmpeg.exe" -y -loglevel fatal -threads 8 -i "Z:\True Romance.mkv" -map 0:0 -an -sn -vf crop=1920:816:0:132,zscale=rangein=tv:range=tv -pix_fmt yuv420p10le -strict -1 -vsync 0  -f yuv4mpegpipe - | "C:\PROGRA~1\Hybrid\64bit\x265.exe" --preset placebo --input - --output-depth 10 --y4m --profile main10 --level-idc 4.1 --limit-tu 1 --subme 7 --merange 57 --limit-modes --no-tskip --no-strong-intra-smoothing --keyint 240 --min-keyint 23 --bframes 13 --lookahead-slices 1 --qpmax 69 --crf 19.50 --qpfile "Z:\True Romance_new_18_07_23_9510_01.qp" --limit-refs 1 --rd 5 --psy-rdoq 1.10 --qcomp 0.75 --qp-adaptation-range 2 --aq-mode 0 --hevc-aq --no-cutree --vbv-maxrate 50000 --vbv-bufsize 50000 --deblock=-3:-3 --no-sao --zones 168042,173346,q=35 --range limited --colormatrix bt709 --output "Z:\18_07_23_9510_02.265"
Looks fine to me and the syntax of the 'zones' part (matches the definition, see: https://x265.readthedocs.io/en/default/c...tion-zones)
-> Do you get any error messages when calling the encoding call inside a Windows Command Prompt? (using the call here throws no error)

Cu Selur


No, no error messages, just started coding
Reply
#6
Okay.
According to the error log the encoder crashed after '09:42:01.355', could either be a bug in x265 in handling the zones or a memory and/or heat issue,..
The amount of RAM used is ~2GB here, so that shouldn't be an issue. My guess is that heat or faulty memory is the problem.
(as a side node: using placebo usually isn't worth the time spend, I would recommend to use 'slower' or 'very slow' instead.)

Cu Selur

Ps.: I guess is doesn't crash if you use 'ultra fast' as preset.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#7
'ultra fast' preset worked fine. Will try veryslow
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)