[HELP] Problems with QTGMC (Avisynth)

[rashit577]

I used Hybrid 20191201 and QTGMC (Avisynth) with default settings (it is optimal for me) on Windows 10 1903
Then i installed Windows 10 1909 and fresh version Hybrid and got problems with default settings QTGMC (Avisynth) for all video files.

Filtering input files,..
Analysing 1 input files,...
Analyzing '999.mkv'.
Checking a/v ids with FFMpeg VideoAnalyser,...
Grabbing audio ids for D:\Video\999.mkv.
-> Found the following audio ids: 0
Analyzing audio streams,...
  Analyzing audio stream with id '0'.
   Analyzing audio stream with MPlayer AudioAnalyser for id '0',...
   Grabbing audio data and delay infos,...
Grabbing video ids,...
  -> Video ids found: 0
Analyzing video streams...
  Analyzing video stream (0).
-> Forcing time code extraction, since input is detected as vfr!
Extracting time codes from mkv for track with id 0.
Adjusting frame count (752) to time code entry count (754).
starting auto routines for source number: 1
Detected interlaced Material with 29,../59,.. fps, but didn't detect the material to be telecine. You might want to run 'Filtering->(De-)Interlace/Telecine->Deinterlace/Telecine Settings->Analyse'.
-> finished auto routines for source number: 1
Input is completely analysed,...
Creating job for current source
-> Creating jobs for source: (1)
-> Generating calls for: D:\999.mkv
  Ignore time codes for output since Avisynth 'FPS adjust' is used.
  adding x264 calls for source: 1
  createJobs for D:\999.mkv
   creating audio subjobs,...
   creating attachment extraction subjobs
   creating video subjobs
   creating muxing subjobs
   optimizing the subJobs
-> finished creating subjobs for current source
  added new job with id 12_04_50_7510
-> should be there after processing: D:\Other\Temp\iId_1_aid_0_lang_ja_12_04_50_7510_01.ac3
starting 12_04_50_7510_01_audio@12:04:50.834 - D:\999.mkv
finished after 00:00:00.134
-> should be there after processing: D:\Other\Temp\iId_1_aid_0_lang_ja_12_04_50_7510_02.ac3
starting 12_04_50_7510_02_audio@12:04:50.972 - D:\999.mkv
finished after 00:00:00.357
delete D:\Other\Temp\iId_1_aid_0_lang_ja_12_04_50_7510_01.ac3
-> should be there after processing: D:\Other\Temp\12_04_50_7510_07.264
starting 12_04_50_7510_07_video@12:04:51.518 - D:\999.mkv
finished after 00:00:00.803
-> 12_04_50_7510_07_video crashed: ERROR: D:\Other\Temp\12_04_50_7510_07.264 is too small! (byteSize: 0byte)
Aborting '12_04_50_7510_07_video' due to: ERROR: D:\Other\Temp\12_04_50_7510_07.264 is too small! (byteSize: 0byte)

I always have a coding error, if enable "Overwrite input scan type to: progressive" - no problem, but not good for me. 

Then i installed Hybrid 20191201 and old version and enable QTGMC (Avisynth) with default settings, there is an error in the encoding.

How to fix my problem?

[Selur]

• try the Avisynth preview to see if there is an error
  

• Ignore time codes for output since Avisynth 'FPS adjust' is used.

  are you trying to deinterlaced and change the output fps?
  Whatever you are doing seems strange, if you have interlaced 29.97fps tff content which you want to get to progressive 59.94fps, why not simply dob the content?
  
• Do you want to troll me or why would you post parts of a log which starts with:
  

  This log is only intended for user information.
  It should not be part of a bug/problem report!!

  ?
  

-> if you want help instead of posting screenshots:
a. read the [INFO] Infos needed to fix&reproduce bugs,.. sticky
b. provide a debug output (level 9 is probably the best in your case) which contains the whole process starting with the loading of the source
c. write step by step what you do
d. if you can, share a sample which allows me to reproduce the issue

Cu Selur

[rashit577]

Selur, hello

[attachment=874]

1. Using Windows 10 64 bit and Hybrid 2020.05.01.1 64 bit

2. I'm doing my desired settings. It is optimal for me, With these settings worked before.

x264 --preset veryfast --bitrate 3500 --profile high --level 4.2 --ref 3 --direct auto --b-adapt 0 --sync-lookahead 6 --ratetol 2.0 --qcomp 0.5 --rc-lookahead 40 --qpmax 81 --partitions i4x4,p8x8,b8x8 --no-fast-pskip --subme 5 --aq-mode 0 --vbv-maxrate 3500 --vbv-bufsize 78125 --sar 8:9 --qpfile GENERATED_QP_FILE --non-deterministic --range tv --colormatrix bt709 --demuxer raw --input-res 720x480 --input-csp i420 --input-range tv --input-depth 8 --fps 60000/1001 --output-depth 8 --output "D:\Other\Temp\MO-02.264" -

3. I save the settings

4. I'm adding a video file and run the job

5. I wait and after audio encoding, video encoding start and at once error ".......is too small! (byteSize: 0byte)"

Sample https://drive.google.com/open?id=1zVKIRp...cPsdL2V6Rx

[Selur]

Seeing that you use SVP/Interframe with Avisynth the most common problem it that SVP might have a problem with the current driver/gpu combination (completely deinstalling the drivers and installing the latest driver version often helps) .
-> Does the Avisynth Preview work?

[rashit577]

-> Does the Avisynth Preview work?

Yes.

Until the full reinstallation of Windows - everything worked. At the beginning, there were also errors, but after one successful coding, there were no more errors. Latest drivers installed.

[Selur]

At the beginning, there were also errors,....

That sounds wrong, what are those errors?

What happens if you call:

"D:\Other\Hybrid\32bit\ffmpeg.exe" -y -loglevel fatal -noautorotate -nostdin -threads 4 -i "D:\Other\Temp\encodingTempSynthSkript_15_03_33_4510.avs" -an -sn -vf zscale=rangein=tv:range=tv -pix_fmt yuv420p -vsync 0  -f rawvideo - | "D:\Other\Hybrid\64bit\x264.exe" --preset veryfast --bitrate 3500 --profile high --level 4.2 --ref 3 --direct auto --b-adapt 0 --sync-lookahead 6 --ratetol 2.0 --qcomp 0.5 --rc-lookahead 40 --qpmax 81 --partitions i4x4,p8x8,b8x8 --no-fast-pskip --subme 5 --aq-mode 0 --vbv-maxrate 3500 --vbv-bufsize 78125 --sar 8:9 --non-deterministic --range tv --colormatrix bt709 --demuxer raw --input-res 720x480 --input-csp i420 --input-range tv --input-depth 8 --fps 60000/1001 --output-depth 8 --output "D:\Other\Temp\15_03_33_4510_06.264" -

inside a Windows command prompt?

Also when deinterlacing, using 'Bob' in QTGMC would make sense to keep more of the original data,...

[rashit577]

That sounds wrong, what are those errors?

Always only "is too small! (byteSize: 0byte)" errors.

inside a Windows command prompt?

GUI in Hybrid.

---

Screen recording https://drive.google.com/open?id=1ELYP4_...GtCqvtSgJ4

[Selur]

According to the debug output it looks like decoder crashed, but since you didn't tell me what happens with the above call and you say that the Avisynth preview works fine I have no clue.
The video doesn't provide any more data than the debug output.
-> Unless you answer the question regarding the command line call I can't help any further.

Cu Selur