Encoding doesn't start - "missing input"

[kocane]

Sometimes I can encode just fine but when making adjustment, deleting, re-adding and starting jobs it simply does not start and looks like on screenshot belowl.



When I check the debug log (attached) I see that it complains about a missing input file which seemingly is pointing towards one of the autogenerated files from a previous job. I can't really figure it out, what I'm doing wrong.



I'm using Hybrid 2021.12.10.1 apparently (despite having downloaded and installed the newest version, the exe says modified 12-12-2012 but the version remains 12.10.1) on Windows 11 x64 21H2. I've tried reinstalling Hybrid, clearing settings etc and ensuring the folder in roaming appdata is gone.



Thanks

EDIT: Um, after some minutes of nothing it suddenly started encoding. I 've sworn I've waited longer the other times I experienced this issue, where nothing happens.

2022.02.04 - 12:59:33_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: Setting m_startingJobs(1) to FALSE
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: x264 output: y4m [info]: 768x576p 1:1 @ 50/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 4:2:2, level 4.1, 4:2:2, 8-bit
1 frames: 2.29 fps, 676.80 kb/s
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: Ignored: y4m [info]: 768x576p 1:1 @ 50/1 fps (cfr)
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: 2022-02-04@12_59_33_7510_02_video ### X:\Analogue\Video\Encoded\TAPE_(20220120-1710).mp4 ### x264 [info]: using SAR=1/1
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: 2022-02-04@12_59_33_7510_02_video ### X:\Analogue\Video\Encoded\TAPE_(20220120-1710).mp4 ### x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: 2022-02-04@12_59_33_7510_02_video ### X:\Analogue\Video\Encoded\TAPE_(20220120-1710).mp4 ### x264 [info]: profile High 4:2:2, level 4.1, 4:2:2, 8-bit
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: x264 output: 40 frames: 57.22 fps, 88.79 kb/s
2022.02.04 - 13:03:40_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: x264 output: 79 frames: 82.64 fps, 82.25 kb/s
2022.02.04 - 13:03:41_Windows 10 Version 2009 (64bit)_2021.12.10.1 - level 9: x264 output: 125 frames: 102.46 fps, 82.32 kb/s

[Selur]

Vapoursynth script:

# Imports
import os
import sys
import ctypes
# Loading Support Files
Dllref = ctypes.windll.LoadLibrary("C:/Program Files/Hybrid/64bit/vsfilters/Support/libfftw3f-3.dll")
import vapoursynth as vs
# getting Vapoursynth core
core = vs.core
# Import scripts folder
scriptPath = 'C:/Program Files/Hybrid/64bit/vsscripts'
sys.path.insert(0, os.path.abspath(scriptPath))
# Loading Plugins
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/GrainFilter/RemoveGrain/RemoveGrainVS.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/GrainFilter/AddGrain/AddGrain.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/DenoiseFilter/NEO_FFT3DFilter/neo-fft3d.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/DenoiseFilter/DFTTest/DFTTest.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/Support/EEDI3m.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/ResizeFilter/nnedi3/vsznedi3.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/Support/libmvtools.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/Support/temporalsoften.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/Support/scenechange.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/Support/fmtconv.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/MiscFilter/MiscFilters/MiscFilters.dll")
core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/vslsmashsource.dll")
# Import scripts
import havsfunc
# source: 'X:\Analogue\Video\Capture\TAPE_(20220120-1710).avi'
# current color space: YUV422P8, bit depth: 8, resolution: 720x576, fps: 25, color matrix: 470bg, yuv luminance scale: limited, scanorder: top field first
# Loading X:\Analogue\Video\Capture\TAPE_(20220120-1710).avi using LWLibavSource
clip = core.lsmas.LWLibavSource(source="X:/Analogue/Video/Capture/TAPE_(20220120-1710).avi", format="YUV422P8", cache=0, prefer_hw=0)
# making sure input color matrix is set as 470bg
clip = core.resize.Bicubic(clip, matrix_in_s="470bg",range_s="limited")
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip=clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# setting field order to what QTGMC should assume (top field first)
clip = core.std.SetFrameProp(clip=clip, prop="_FieldBased", intval=2)
# Deinterlacing using QTGMC
clip = havsfunc.QTGMC(Input=clip, Preset="Faster", TFF=True) # new fps: 50
# make sure content is preceived as frame based
clip = core.std.SetFieldBased(clip, 0)
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=768, h=576, interlaced=False, interlacedd=False)
# adjusting output color from: YUV422P16 to YUV422P8 for x264Model
clip = core.resize.Bicubic(clip=clip, format=vs.YUV422P8, range_s="limited")
# set output frame rate to 50.000fps
clip = core.std.AssumeFPS(clip=clip, fpsnum=50, fpsden=1)
# Output
clip.set_output()

looks fine.
Encoding call:

C:\Program Files\Hybrid\64bit\Vapoursynth\vspipe.exe" "X:\Analogue\Video\Encoded\Temp\encodingTempSynthSkript_2022-02-04@12_51_21_6310.vpy" - -c y4m | "C:\Program Files\Hybrid\64bit\x264.exe" --preset slow --crf 20.00 --profile high422 --level 4.1 --sync-lookahead 18 --qcomp 0.80 --ipratio 1.10 --pbratio 1.10 --no-dct-decimate --psy-rd 1.00:0.25 --aq-strength 0.50 --vbv-maxrate 50000 --vbv-bufsize 187500 --deadzone-inter 6 --deadzone-intra 6 --sar 1:1 --deblock -2:-2 --non-deterministic --range tv --colormatrix bt470bg --demuxer y4m --input-range tv --fps 50/1 --output-csp i422 --output-depth 8 --output "X:\Analogue\Video\Encoded\Temp\2022-02-04@12_51_21_6310_02.264" -

looks fine too.

No clue why it would take 4min on your system to start the encoding.
Wild guess would be that you got some anti virus software or similar running which is interfering with the processing.

Cu Selur

[kocane]

Odd.. the source here had been encoded with Lagarith. With sources that use HuffYUV it hasn't happen yet...

It spends a lot of time creating a .ffindex file, which didnt occur with Lagarith - why can that be?

[Selur]

Different source filter.
FFVideoSource uses ffindex files.
LWLibavSource (in Hybrid) only is used with index files in memory.
If the source is on a network drive it can slow down things,...

----
btw. the missing input stuff in the debug output is from the job processing which checked whether another subjob could be started, but wasn't since the output of the encoding wasn't there.

[kocane]

Different source filter.
FFVideoSource uses ffindex files.
LWLibavSource (in Hybrid) only is used with index files in memory.
If the source is on a network drive it can slow down things,...

Could imagine it would be slow on a network drive. I just threw the file onto my SSD instead of the HDD and while it's faster it still takes a while. 

Is that just how it is with HuffYUV or can it be adjusted?

btw. the missing input stuff in the debug output is from the job processing which checked whether another subjob could be started, but wasn't since the output of the encoding wasn't there.

Is that a misconfiguration on my part?

[Selur]

Is that a misconfiguration on my part?

No, that's a normal behaviour. Hybrid checks the sub-jobs and avoids starting those where the inputs are missing.

Is that just how it is with HuffYUV or can it be adjusted?

No clue, it's normal that the progress indication in Hybrid takes a bit since:
1. when LWLibavSource is used it still needs to index the file, it just keeps the index in memory and usually can start without having to index the whole file.
2. encoders usually request a bunch of frames (lookaheads) before they start encoding
3. Hybrid should only start showing a progress if the progress > 1%.
4. depending on the filters, an the order and amount in which they requires frames, especially the start can take a bit. (especially on hdds this will slow things down)
5. If anti virus or similar software are also trying to check the data all the above steps will be slowed.

Still the time to start seems unusually long, but I have not clue what's causing it on your system. If you think Hybrid is not starting checking the cpu usage is usually a good indicator,..

Cu Selur