[HELP] Rendering aborts aber some seconds suddenly...
#1
Hi,

I am using Hybrid version 2018.06.18.1
I want to render my 25fps drone flight into a 60fps one.

Issue:
After some seconds of rendering, the job aborts suddenly.

My configs:
Input: 1gb mov 25 fps 60Mbps
Output: x264 custom, mp4, 5.2 preset/tune none
Filtering: Avisynth, Frame, InterFrame, Medium Smooth smooth 60fps

Log output:
x264 (1st pass bitrate) processing started...
starting 09_03_17_5010_03_video@09:03:20.374 - C:\Users\tof\Desktop\60FPS\5.mp4
"C:\PROGRA~1\Hybrid\64bit\x264.exe" --preset superfast --pass 1 --bitrate 120000 --profile high --level 5.2 --direct auto --qcomp 0.5 --rc-lookahead 40 --aq-mode 0 --sar 1:1 --non-deterministic --range tv --stats "C:\Users\tof\AppData\Local\Temp\5_09_03_17_5010_03.stats" --demuxer raw --input-res 3840x2160 --input-csp i420 --input-range tv --input-depth 8 --fps 60/1 --output-depth 8 --output NUL -
raw [info]: 3840x2160p 1:1 @ 60/1 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x264 [info]: profile Main, level 5.2
x264 [info]: frame I:1     Avg QP:27.00  size:1336330
x264 [info]: frame P:18    Avg QP:19.06  size:544434
x264 [info]: frame B:24    Avg QP:23.92  size: 57404
x264 [info]: consecutive B-frames: 25.6%  0.0%  0.0% 74.4%
x264 [info]: mb I  I16..4: 49.1%  0.0% 50.9%
x264 [info]: mb P  I16..4:  0.7%  0.0%  0.0%  P16..4: 93.4%  0.0%  0.0%  0.0%  0.0%    skip: 5.9%
x264 [info]: mb B  I16..4:  0.0%  0.0%  0.0%  B16..8: 22.3%  0.0%  0.0%  direct:16.9%  skip:60.8%  L0:15.2% L1:24.5% BI:60.3%
x264 [info]: final ratefactor: 16.94
x264 [info]: direct mvs  spatial:50.0% temporal:50.0%
x264 [info]: coded y,uvDC,uvAC intra: 95.9% 19.9% 2.8% inter: 34.6% 8.2% 0.1%
x264 [info]: i16 v,h,dc,p:  4%  8% 77% 11%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 21% 13% 21%  7%  7%  8%  7%  8%  8%
x264 [info]: i8c dc,h,v,p: 60% 21% 15%  5%
x264 [info]: Weighted P-Frames: Y:0.0% UV:0.0%
x264 [info]: kb/s:139689.39
encoded 43 frames, 2.70 fps, 139689.40 kb/s
finished after 00:00:16.490
finished...

x264 (2nd pass bitrate) processing started...
starting 09_03_17_5010_04_video@09:03:36.936 - C:\Users\tof\Desktop\60FPS\5.mp4
"C:\PROGRA~1\Hybrid\64bit\x264.exe" --preset fast --pass 2 --bitrate 120000 --profile high --level 5.2 --direct auto --qcomp 0.5 --no-mbtree --rc-lookahead 40 --partitions i4x4,p8x8,b8x8 --no-fast-pskip --subme 5 --trellis 0 --aq-mode 0 --vbv-maxrate 300000 --vbv-bufsize 300000 --sar 1:1 --non-deterministic --range tv --colormatrix bt709 --stats "C:\Users\tof\AppData\Local\Temp\5_09_03_17_5010_03.stats" --demuxer raw --input-res 3840x2160 --input-csp i420 --input-range tv --input-depth 8 --fps 60/1 --output-depth 8 --output "C:\Users\tof\AppData\Local\Temp\09_03_17_5010_04.264" -
raw [info]: 3840x2160p 1:1 @ 60/1 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x264 [info]: profile High, level 5.2
Helper(1) finished with exitCode: -529697949 and exitStatus: 0

Any idea what happen here?

Grüße
Eusi
Reply
#2
Since you are one of those which post parts of their, log I have to say that each logs starts with:
Quote:This log is only intended for user information. It should not be part of a bug/problem report!!
Hybrid: homepage
Forum: public forum
Regarding problems please read: needed infos
Donate: via PayPal
This log is only intended for user information. It should not be part of a bug/problem report!!
So I got no clue why you would post something from that log.

Quote:Any idea what happen here?
Sure. Seems like either the decoder crashed.

Typical reasons fo this:
a. broken source
b. Interframe used with GPU enabled and some driver problem. (depending on your settings CPU even might be faster)
c. something interfering with the encoding (some overly protective desktop firewall, virus scanner)
d. something in the Avisynth script you used causes problem.

Only thing I see in that log is that the first pass finished after 43 frames, which seems awfully short, not even two seconds @25fps, especially if the input is "1gb mov 25 fps 60Mbps" this is strange.
-> Wild guess: Might be that the used source filter is having problems with your source. Using another source filter or switching to Vapoursynth (which is 64bit and not 32bit like Avisynth) might fix the issue.

Cu Selur
Reply
#3
(21.06.2018, 19:04)Selur Wrote: Since you are one of those which post parts of their...
So I got no clue why you would post something from that log.
Easy question: Because Hybrid did not log more than that ^^. That was the entire debug log.
I enabled in config "create debug log file" (as explained in "Infos needed to fix&reproduce bugs,..") and started rendering. Then I disabled the debugging again.



(21.06.2018, 19:04)Selur Wrote:
Quote:Any idea what happen here?
Sure. Seems like either the decoder crashed.

Typical reasons fo this:
a. broken source
b. Interframe used with GPU enabled and some driver problem. (depending on your settings CPU even might be faster)
c. something interfering with the encoding (some overly protective desktop firewall, virus scanner)
d. something in the Avisynth script you used causes problem.

a) source should be fine, on my pc it works
b) no GPU used (crash was on my server, it's very powerful via cpu, but no gpu)
c) actually hybrid is running in a virtual machine on the server (very clean win10 installation, no antivir/firewall, only further apps: filezilla ftp server, teamviewer and compact tray meter)
d) hmm.. no idea



(21.06.2018, 19:04)Selur Wrote: -> Wild guess: Might be that the used source filter is having problems with your source. Using another source filter or switching to Vapoursynth (which is 64bit and not 32bit like Avisynth) might fix the issue.
Changed to Vapoursynth and FrameInterpolation...

Aaaaaaand... it worked!

Thanks for the (letz say) fix :-)
Reply
#4
Quote:Easy question: Because Hybrid did not log more than that ^^. That was the entire debug log.
I enabled in config "create debug log file" (as explained in "Infos needed to fix&reproduce bugs,..") and started rendering. Then I disabled the debugging again.
Debug output is written into a file. What you posted is not from the debug output.

-> Current guess atm. is that 4k with Interframe crashes against the 32bit limitation of Avisynth.

Cu Selur

Ps.: For 4+ core systems I would always encourage to use Vapoursynth over Avisynth since Vapoursynth scales way better with more CPU cores.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)