Simple x264/x265 Launcher v3.02 (2022-06-16)

[LoRd_MuldeR]

well, okay, but that doesn't answer the question why basically the exact script and the exact same encoding settings that work with avisynth script + simple x264/265 gui do not work with .vpy script.

That's probably a completely different issue.

First of all, try to resolve your obvious x264 crash problem. VapourSynth input can not work, as long as x264 is crashing on you! It would be best to just stick with the vanilla x264.exe that ships with Simple x264/x265 Launcher.

Secondly, encoding from ".vpy" script requires that an up-to-date version VapourSynth is installed on your machine – x264.exe can not read ".vpy" scripts directly, the frames need to be pipe'd via vspipe.exe.

Simple x264/x265 Launcher does that automatically for you. But, if you think that Simple x264/x265 Launcher did not detect VapourSynth even though it is installed, then run x264_launcher.exe with parameter "--console" and…

:logfile:

It is supposed to look like this: https://i.imgur.com/dfyuEwa.png

[aldix]

but the same x264 does not crash with an avisynth script, though. i really don't know how more clearly can i put it lol.

[LoRd_MuldeR]

but the same x264 does not crash with an avisynth script, though. i really don't know how more clearly can i put it lol.

If you refuse to systematically track down your problems, one after the other, or if you don't provide the necessary information, then I can not help.

If the x264.exe process crashes on you – which it did according to the log you posted earlier – you obviously have a problem with x264. As long as you do not fix that problem, anything else will be futile! Whether the source was pipe'd in from avs2yuv.exe (Avisynth) or from vspipe.exe (VapourSynth) does not matter. And, as said before, the exit code STATUS_ILLEGAL_INSTRUCTION indicates that x264 has crashed because it tried to execute an instruction not supported by your CPU. This means whatever x264.exe you are using was compiled with "optimizations" not compatible with your CPU. Does x264 still crash, if you use the x264.exe that ships with Simple x264/x265 Launcher?

If VapourSynth input is not working – which probably is a completely unrelated problem – then the first thing you need to check is whether VapourSynth is installed properly on your system and whether it has been detected correctly. I already told you how to launch x264_launcher.exe with the debug console enabled. So, go check the debug output and see whether VapourSynth has been detected. Or, at the very least, post your debug output!

[aldix]

indeed, my sincere apologies.

was indeed for some brain-fart reason trying to get the boardwell version of the tmod to work until this very moment. the regular, latest build works issue-free just as the vanilla x264 does.

thank you for your software!

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.91
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.91

Version 2.91 [2019-07-14]
* Updated x265 to version 3.1+2
* Updated build environment to Visual Studio 2019 with Update-1
* Various improvements to Avisynth/VapourSynth detection

[RTW47]

for me Simple x264 Launcher v2.91.1170 (64-bit) is unable to detect 32-bit and 64-bit VapourSynth. (Windows 7 SP1)
At this point only VapourSynth (64-Bit) R46 (non-portable) was installed using this new separate installer for 64-bit. (since R46 (http://www.vapoursynth.com/2019/06/r46-windows-installer-fun/)).

64-bit vapoursynth installation:

C:\Program Files\VapourSynth\
├─ core
├─ docs
├─ pismo
└─ etc…

yet Simple x264 Launcher tried looking for vspipe.exe and vapoursynth.dll inside non-existing core64 folder:

[Check for VapourSynth support]
VapourSynth thread has been created, please wait...
VapourSynth Dir: C:/Program Files/VapourSynth
VapourSynth EXE: C:/Program Files/VapourSynth/core32/vspipe.exe
VapourSynth DLL: C:/Program Files/VapourSynth/core32/vapoursynth.dll
VapourSynth 32-Bit edition *not* found!
VapourSynth EXE: C:/Program Files/VapourSynth/core64/vspipe.exe
VapourSynth DLL: C:/Program Files/VapourSynth/core64/vapoursynth.dll
VapourSynth 64-Bit edition *not* found!
VapourSynth thread finished.
VapourSynth could not be found -> VapourSynth support disabled!

renaming core to core64, would make detection work for 64-bit vapoursynth, however everything else such as vapoursynth editor would fail by default.
---
After instaling Python 3.7.4 (32-bit) and VapourSynth (32-bit) R46, now both 32-bit and 64-bit (non-portable) versions of vapoursynth are installed:

32-bit vapoursynth installation:

C:\Program Files (x86)\VapourSynth-32\
├─ core
├─ docs
├─ pismo
└─ etc…

Simple x264 Launcher now keeps looking elsewhere, but paths are still not correct to detect 32-bit VS and (or) 64-bit VS:

[Check for VapourSynth support]
VapourSynth thread has been created, please wait...
VapourSynth Dir: C:/Program Files (x86)/VapourSynth-32
VapourSynth EXE: C:/Program Files (x86)/VapourSynth-32/core32/vspipe.exe
VapourSynth DLL: C:/Program Files (x86)/VapourSynth-32/core32/vapoursynth.dll
VapourSynth 32-Bit edition *not* found!
VapourSynth EXE: C:/Program Files (x86)/VapourSynth-32/core64/vspipe.exe
VapourSynth DLL: C:/Program Files (x86)/VapourSynth-32/core64/vapoursynth.dll
VapourSynth 64-Bit edition *not* found!
VapourSynth thread finished.
VapourSynth could not be found -> VapourSynth support disabled!that new installer likely changed some folder names etc., since I clearly remember seeing core32 / core64 folders (at least for non-portable vapoursynth).

[LoRd_MuldeR]

for me Simple x264 Launcher v2.91.1170 (64-bit) is unable to detect 32-bit and 64-bit VapourSynth. (Windows 7 SP1)
At this point only VapourSynth (64-Bit) R46 (non-portable) was installed using this new separate installer for 64-bit. (since R46 (http://www.vapoursynth.com/2019/06/r46-windows-installer-fun/)).

It appears there were some significant changes in latest VapourSynth release, which broke "our" detection routines :o

I will have to look into that, as soon as I have some spare time. This is probably not going to happen before next week, because I am very busy right now and I will be on a trip this weekend...

[RTW47]

I will have to look into that, as soon as I have some spare time. This is probably not going to happen before next week, because I am very busy right now and I will be on a trip this weekend...
I'm not in a hurry, take your time and have a safe journey.

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.92
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.92

Version 2.92 [2019-07-22]
* Updated x264 to revision 2984 (API v158)
* Updated x265 to version 3.1+8
* Fixed detection of VapourSynth R46
* Note: Minimum supported VapourSynth version is R46 now!Hotfix for Simple x264/x265 Launcher v2.92 to remedy an erroneous "critical error" message:
https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2019-07-22.hotfix-1.zip/download

[Dion]

Getting this error with this new version.
https://images2.imgbox.com/da/f1/DxDYncGx_o.png

I don't have Vapoursynth installed or use it. Is there no way to suppress this fully?

[LoRd_MuldeR]

Getting this error with this new version.
https://images2.imgbox.com/da/f1/DxDYncGx_o.png

I don't have Vapoursynth installed or use it. Is there no way to suppress this fully?

https://i.imgur.com/piZl2kZ.png

Sorry, there is a stupid regression in the latest release, when VapourSynth is not found at all. You can safely ignore the "critical error" message.

Anyway, please try with the "hotfix" version from here:
x264_launcher.2019-07-22.hotfix-1.zip (https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2019-07-22.hotfix-1.zip/download)

[RTW47]

Simple x264/x265 Launcher v2.92
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.92can confirm that new build now successfully detects both (32-bit & 64-bit) non-portable VapourSynth R46. (#1807 (https://forum.doom9.org/showpost.php?p=1879450&postcount=1807))
thanks LM^^

[Chouonsoku]

Edit: Nevermind, user error. :D

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.93
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.93

Version 2.93 [2019-08-06]
* Fixed a regression in VapourSynth detection code
* Updated NVEncC to version 4.43
* Updated build environment to Visual Studio 2019 with Update-2

[redbtn]

Something strange in log file. Launcher v2.93, x265 v3.1+14


[2019-09-11][07:24:09] x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.65
[2019-09-11][07:24:09] x265 [info]: VBV/HRD buffer / max-rate / init : 160000 / 160000 / 0.900
[2019-09-11][07:24:09] x265 [info]: tools: rect amp limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=2.00
[2019-09-11][07:24:09] x265 [info]: tools: rskip limit-tu=4 signhide tmvp b-intra deblock(tC=-3:B=-3)
[2019-09-11][07:46:49] 92 fps, 10111.82 kb/s, eta 17:40:01
[2019-09-11][07:53:16] , 2.84 fps, 11286.77 kb/s, eta 18:03:51
[2019-09-11][09:29:39] [9.7%] 18339/189480 fram
[2019-09-11][09:29:39] es, 2.43 fps, 19276.08 kb/s, eta 19:31:29
[2019-09-11][09:39:19] [10.3%] 19556/189480 fr
[2019-09-11][09:39:19] ames, 2.41 fps, 19775.16 kb/s, eta 19:34:43
[2019-09-11][09:47:19] [10.9%]
[2019-09-11][09:47:19] 20745/189480 frames, 2.41 fps, 19664.61 kb/s, eta 19:24:41
[2019-09-11][10:17:49] 19267.50 kb/s, eta 18:56:01
[2019-09-11][11:19:28] ps, 18573.33 kb/s, eta 17:40:10
[2019-09-11][13:38:17] [29.0%]
[2019-09-11][13:38:17] 54899/189480 frames, 2.45 fps, 18180.11 kb/s, eta 15:17:14
[2019-09-11][13:41:21] 73.79 kb/s, eta 15:14:14
[2019-09-11][14:13:59] 6.31 kb/s, eta 14:50:27
[2019-09-11][14:14:44] 2 kb/s, eta 14:49:52
[2019-09-11][14:19:23] 18461.43 kb/s, eta 14:47:00
[2019-09-11][14:46:51] 3:37
[2019-09-11][15:12:06] [36
[2019-09-11][15:12:06] .1%] 68451/189480 frames, 2.44 fps, 18191.34 kb/s, eta 13:47:26
[2019-09-11][15:43:05] 2.54 kb/s, eta 13:13:47
https://i.imgur.com/dltOCdB.png

[LoRd_MuldeR]

Something strange in log file. Launcher v2.93, x265 v3.1+14

So, I suppose you manually updated the x265 binary to v3.1+14. Does it only happen with x265 v3.1+14, but not with the x265 binary that originally shipped with Simple x264 Launcher? Is the "issue" reproducible?

Also: Which specific x265 build are you using? Are there any "custom" patches included in that build? If you run that binary in the terminal (no GUI), does the output look normal?

[redbtn]

So, I suppose you manually updated the x265 binary to v3.1+14. Does it only happen with x265 v3.1+14, but not with the x265 binary that originally shipped with Simple x264 Launcher? Is the "issue" reproducible?

Also: Which specific x265 build are you using? Are there any "custom" patches included in that build? If you run that binary in the terminal (no GUI), does the output look normal?
Yes, the "issue" is reproducible. I used builds from msystem.waw.pl/x265

I've made few tests:

1) x265 that shipped with Simple x264 Launcher - OK
2) x265 (3.1+14 and 3.1+19) AVX2 VS2019 from msystem.waw.pl/x265 - Have this bug
3) x265 (3.1+19) AVX2 GCC9.2 from from msystem.waw.pl/x265 - OK
4) x265 (3.1+19) build by Barough - OK

So, it seems like a VS2019 compile bug. So, LoRd_MuldeR , i'm sorry for disturbing.

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.94
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.94

Version 2.94 [2019-10-05]
* Updated x265 to version 3.2+5, incl. AQ mode 4 slowdown fix
* Updated NVEncC to version 4.50 (v2)
* Updated build environment to Visual Studio 2019 with Update-3

[Metal-HTPC]

sadly the simple x264 launcher doesn't work anymore after the latest update.
I'm still using the 2.60 (https://www.videohelp.com/software/Avisynth) version of Avisynth and really didn't chance anything in my configuration.

The problem is the following. I can't re-encode any of my commercial released blu-rays anymore. It only outputs about 21-25 mb and the encodes all come out as this mess:

https://ufile.io/0mptrzot

screenshot of x264 during the encode:

https://s19.directupload.net/images/191027/egtou4k2.png

any help would be appreciated.

[LoRd_MuldeR]

sadly the simple x264 launcher doesn't work anymore after the latest update.
I'm still using the 2.60 (https://www.videohelp.com/software/Avisynth) version of Avisynth and really didn't chance anything in my configuration.

The problem is the following. I can't re-encode any of my commercial released blu-rays anymore. It only outputs about 21-25 mb and the encodes all come out as this mess:

https://ufile.io/0mptrzot

screenshot of x264 during the encode:

any help would be appreciated.

Well, you have to keep in mind that Simple x264 Launcher is just a GUI front-end that invokes x264 with your Avisynth script. No more and no less.

The included x264 binaries were not even changed in the last two releases of my Simple x264 Launcher package. The last time that the x264 binaries were updated was in version 2.92 [2019-07-22].

So, IMO, there is nothing in the last (or second last) release of Simple x264 Launcher that could possibly have changed encoding with x264 and Avisynth input!

You didn't replace the x264 binaries manually, right?

I can only speculate about the cause of your problem. Might be that the Avisynth process crashed; might be that the x264 process crashed. Hard to tell, since your screenshot excludes the most important part of the log – the very end.

It would be helpful if you posted a complete log of your encoding task that shows everything from start to finish...

Anyway, if you open the very same Avisynth script that you are trying to encode in Simple x264 Launcher in, e.g., VirtualDub (http://virtualdub2.com/), does it open and "play" (seek) properly all the way to the end without problem?

[Metal-HTPC]

I don't have virtual dub but I can play the AVSscript flawless in AVSPmod. Also mpeg2 DVD's can be encoded flawless even with x264 launcher.
So only x264/avc seems to be crashed.

I made a short encode so I have a proper log for you to see:


[2019-10-27][13:42:42] Simple x264 Launcher (Build #1194), built 2019-10-05
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Job started at 2019-10-27, 13:42:42.
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Source file : T:\BDencode\Scripte\Sleepaway Camp.avs
[2019-10-27][13:42:42] Output file : T:\BDencode\H264-encode\Sleepaway Camp.264
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] --- SYSTEMINFO ---
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Binary Path : C:\Program Files (x86)\Video\Encoder\x264
[2019-10-27][13:42:42] Avisynth : Yes
[2019-10-27][13:42:42] VapourSynth : No
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] --- SETTINGS ---
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Encoder : x264 (AVC/H.264), 32-Bit (x86), 8-Bit
[2019-10-27][13:42:42] Source : Avisynth (avs)
[2019-10-27][13:42:42] RC Mode : 2-Pass
[2019-10-27][13:42:42] Preset : slow
[2019-10-27][13:42:42] Tuning : Film
[2019-10-27][13:42:42] Profile : High
[2019-10-27][13:42:42] Custom : --bluray-compat --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] --- CHECK VERSION ---
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Detect video encoder version:
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Creating process:
[2019-10-27][13:42:42] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\x264_x86.exe" --version
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] x264 0.158.2984 3759fcb
[2019-10-27][13:42:42] (libswscale 5.4.101)
[2019-10-27][13:42:42] (libavformat 58.28.102)
[2019-10-27][13:42:42] (ffmpegsource 2.31.0.0)
[2019-10-27][13:42:42] built on Jul 19 2019, gcc: 9.1.0
[2019-10-27][13:42:42] x264 configuration: --chroma-format=all
[2019-10-27][13:42:42] libx264 configuration: --chroma-format=all
[2019-10-27][13:42:42] x264 license: GPL version 2 or later
[2019-10-27][13:42:42] libswscale/libavformat/ffmpegsource license: GPL version 2 or later
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Detect video source version:
[2019-10-27][13:42:42]
[2019-10-27][13:42:42] Creating process:
[2019-10-27][13:42:42] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\avs2yuv_x86.exe"
[2019-10-27][13:42:42]
[2019-10-27][13:42:43] Avs2YUV 0.24bm5
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] > x264 revision: 2984 (core #158)
[2019-10-27][13:42:43] > Avs2YUV version: 0.24.5
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] --- GET SOURCE INFO ---
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] Creating process:
[2019-10-27][13:42:43] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\avs2yuv_x86.exe" -frames 1 "T:\BDencode\Scripte\sleepaway camp.avs" NUL
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] T:\BDencode\Scripte\sleepaway camp.avs: 1920x1080, YV12, 8-bits, progressive, 25000 fps, 1965 frames
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] Resolution: 1920 x 1080
[2019-10-27][13:42:43] Frame Rate: 25000
[2019-10-27][13:42:43] No. Frames: 1965
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] --- ENCODING PASS #1 ---
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] Creating input process:
[2019-10-27][13:42:43] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\avs2yuv_x86.exe" "T:\BDencode\Scripte\sleepaway camp.avs" -
[2019-10-27][13:42:43]
[2019-10-27][13:42:43] Creating encoder process:
[2019-10-27][13:42:43] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\x264_x86.exe" --output-depth 8 --bitrate 38200 --pass 1 --stats "T:\BDencode\H264-encode\Sleepaway Camp.stats" --preset slow --tune film --profile high --bluray-compat --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim bt709 --transfer bt709 --colormatrix bt709 --sar 1:1 --output "T:\BDencode\H264-encode\Sleepaway Camp.264" --frames 1965 --demuxer y4m --stdin y4m -
[2019-10-27][13:42:43]
[2019-10-27][13:42:45] y4m [info]: 1920x1080p 1:1 @ 25000/1 fps (cfr)
[2019-10-27][13:42:45] x264 [warning]: NAL HRD parameters require VBV parameters
[2019-10-27][13:42:45] x264 [info]: using SAR=1/1
[2019-10-27][13:42:45] x264 [warning]: MB rate (204000000) > level limit (245760)
[2019-10-27][13:42:45] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[2019-10-27][13:42:45] x264 [info]: profile Main, level 4.1, 4:2:0, 8-bit
[2019-10-27][13:43:51] x264 [info]: frame I:80 Avg QP:51.00 size: 2773
[2019-10-27][13:43:51] x264 [info]: frame P:481 Avg QP:51.00 size: 160
[2019-10-27][13:43:51] x264 [info]: frame B:1404 Avg QP:51.00 size: 123
[2019-10-27][13:43:51] x264 [info]: consecutive B-frames: 4.4% 0.6% 1.4% 93.6%
[2019-10-27][13:43:51] x264 [info]: mb I I16..4: 100.0% 0.0% 0.0%
[2019-10-27][13:43:51] x264 [info]: mb P I16..4: 0.0% 0.0% 0.0% P16..4: 0.1% 0.0% 0.0% 0.0% 0.0% skip:99.8%
[2019-10-27][13:43:51] x264 [info]: mb B I16..4: 0.0% 0.0% 0.0% B16..8: 0.0% 0.0% 0.0% direct: 0.0% skip:100.0% L0:41.4% L1:58.6% BI: 0.0%
[2019-10-27][13:43:51] x264 [info]: final ratefactor: 58.36
[2019-10-27][13:43:51] x264 [info]: direct mvs spatial:47.5% temporal:52.5%
[2019-10-27][13:43:51] x264 [info]: coded y,uvDC,uvAC intra: 1.3% 3.7% 0.0% inter: 0.0% 0.0% 0.0%
[2019-10-27][13:43:51] x264 [info]: i16 v,h,dc,p: 81% 12% 7% 0%
[2019-10-27][13:43:51] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 3% 1% 96% 0% 0% 0% 0% 0% 0%
[2019-10-27][13:43:51] x264 [info]: i8c dc,h,v,p: 100% 0% 0% 0%
[2019-10-27][13:43:51] x264 [info]: Weighted P-Frames: Y:12.7% UV:6.4%
[2019-10-27][13:43:51] x264 [info]: kb/s:47932.93
[2019-10-27][13:43:51] encoded 1965 frames, 29.30 fps, 47932.93 kb/s
[2019-10-27][13:43:51] av2y [info]: T:\BDencode\Scripte\sleepaway camp.avs: 1920x1080, YV12, 8-bits, progressive, 25000 fps, 1965 frames
[2019-10-27][13:43:51] Final file size is 459.9 KB bytes.
[2019-10-27][13:43:51]
[2019-10-27][13:43:51] --- ENCODING PASS #2 ---
[2019-10-27][13:43:51]
[2019-10-27][13:43:51] Creating input process:
[2019-10-27][13:43:51] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\avs2yuv_x86.exe" "T:\BDencode\Scripte\sleepaway camp.avs" -
[2019-10-27][13:43:51]
[2019-10-27][13:43:51] Creating encoder process:
[2019-10-27][13:43:51] "C:\Program Files (x86)\Video\Encoder\x264\toolset\x86\x264_x86.exe" --output-depth 8 --bitrate 38200 --pass 2 --stats "T:\BDencode\H264-encode\Sleepaway Camp.stats" --preset slow --tune film --profile high --bluray-compat --level 4.1 --keyint 25 --open-gop --slices 4 --fake-interlaced --colorprim bt709 --transfer bt709 --colormatrix bt709 --sar 1:1 --output "T:\BDencode\H264-encode\Sleepaway Camp.264" --frames 1965 --demuxer y4m --stdin y4m -
[2019-10-27][13:43:51]
[2019-10-27][13:43:52] y4m [info]: 1920x1080p 1:1 @ 25000/1 fps (cfr)
[2019-10-27][13:43:52] x264 [warning]: NAL HRD parameters require VBV parameters
[2019-10-27][13:43:52] x264 [info]: using SAR=1/1
[2019-10-27][13:43:52] x264 [warning]: MB rate (204000000) > level limit (245760)
[2019-10-27][13:43:52] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[2019-10-27][13:43:52] x264 [info]: profile High, level 4.1, 4:2:0, 8-bit
[2019-10-27][13:45:03] x264 [info]: frame I:80 Avg QP:51.00 size: 684
[2019-10-27][13:45:03] x264 [info]: frame P:481 Avg QP:51.00 size: 138
[2019-10-27][13:45:03] x264 [info]: frame B:1404 Avg QP:51.00 size: 119
[2019-10-27][13:45:03] x264 [info]: consecutive B-frames: 4.4% 0.6% 1.4% 93.6%
[2019-10-27][13:45:03] x264 [info]: mb I I16..4: 0.0% 100.0% 0.0%
[2019-10-27][13:45:03] x264 [info]: mb P I16..4: 0.0% 0.0% 0.0% P16..4: 0.0% 0.0% 0.0% 0.0% 0.0% skip:100.0%
[2019-10-27][13:45:03] x264 [info]: mb B I16..4: 0.0% 0.0% 0.0% B16..8: 0.1% 0.0% 0.0% direct: 0.0% skip:99.9% L0:100.0% L1: 0.0% BI: 0.0%
[2019-10-27][13:45:03] x264 [info]: 8x8 transform intra:100.0%
[2019-10-27][13:45:03] x264 [info]: direct mvs spatial:49.2% temporal:50.8%
[2019-10-27][13:45:03] x264 [info]: coded y,uvDC,uvAC intra: 0.0% 0.0% 0.0% inter: 0.0% 0.0% 0.0%
[2019-10-27][13:45:03] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 0% 0% 100% 0% 0% 0% 0% 0% 0%
[2019-10-27][13:45:03] x264 [info]: i8c dc,h,v,p: 100% 0% 0% 0%
[2019-10-27][13:45:03] x264 [info]: Weighted P-Frames: Y:12.7% UV:6.4%
[2019-10-27][13:45:03] x264 [info]: kb/s:29403.77
[2019-10-27][13:45:03] encoded 1965 frames, 27.71 fps, 29403.77 kb/s
[2019-10-27][13:45:03] av2y [info]: T:\BDencode\Scripte\sleepaway camp.avs: 1920x1080, YV12, 8-bits, progressive, 25000 fps, 1965 frames
[2019-10-27][13:45:03] Final file size is 282.1 KB bytes.
[2019-10-27][13:45:03]
[2019-10-27][13:45:03] --- COMPLETED ---
[2019-10-27][13:45:03]
[2019-10-27][13:45:03] Job finished at 2019-10-27, 13:45:03. Process took 2 minutes, 20 seconds.

[sneaker_ger]

You have 25000 fps instead of 25 fps.

[LoRd_MuldeR]

I don't have virtual dub

I highly recommend you grab VirtualDub2 from here:
VirtualDub2_43803.zip (https://sourceforge.net/projects/vdfiltermod/files/VirtualDub%20pack/version%2020/VirtualDub2_43803.zip/download)

but I can play the AVSscript flawless in AVSPmod. Also mpeg2 DVD's can be encoded flawless even with x264 launcher.
So only x264/avc seems to be crashed.

According to your log, nothing has crashed. Both encoding passes seem to have completed normally, as far as I can tell. But, as sneaker_ger (https://forum.doom9.org/showthread.php?p=1888806#post1888806) noted, a frame rate of 25000 is really weird! :eek:

Please run the following command manually in a terminal:
avs2yuv_x86.exe -frames 1 "C:\path\to\your\source.avs" NUL

...and then please tell us what the output is.

(You find "avs2yuv_x86.exe" in your Simple x264 Launcher install directory below "toolset\x86" and, of course, you have to adjust the path to your AVS file as needed!)

Output should be something like:
SES UHD Demo Channel.avs: 1920x816, YV12, 8-bits, progressive, 50 fps, 9178 frames

It would also be very interesting to know what the "File Information" dialog in VirtualDub(2) says about your AVS file ;)

[sneaker_ger]

a frame rate of 25000 is really weird! :eek:
It's not simply "weird". It is the root of the problem. He has set "--bitrate 38200" i.e. 38200 kilobits per second. If you distribute these 38200 kilobits to 25000 frames that will 1528 bits per frame. Of course the output will look like garbage if you apply only 1/1000th of the bits you intended to.

[LoRd_MuldeR]

It's not simply "weird". It is the root of the problem. He has set "--bitrate 38200" i.e. 38200 kilobits per second. If you distribute these 38200 kilobits to 25000 frames that will 1528 bits per frame. Of course the output will look like garbage if you apply only 1/1000th of the bits you intended to.

Sure. But I meant that it is weird to get such value at all. Must either be an error in the Avisynth script – which maybe didn't show up in other encoding tools, because those didn't honor the FPS reported by Avisynth and just assumed 25 fps – or a bug in Avs2YUV. I'm pretty sure it is not a problem of Simple x264 Launcher itself, because Simple x264 Launcher does not explicitly set the framerate. The framerate is passed implicitly from Avs2YUV to x264 via YUV4MPEG header.

[Metal-HTPC]

it really was the 25 fps command. I forgot the ".". Sorry for my inability. Everything is alright with your x264 launcher and I will continue to use it. thanks

[Forteen88]

I can't run the newest version of x265 (3.2.1+1-b5c86a6) in Simple x264/x265 Launcher v2.94 (2019-10-05), it complains that it's a too old version of x265.
Also, there is a newer version (not any important feature, but it's compiled with a more newer compiler) of Avs2YUV released than is included in that package,
http://avisynth.nl/index.php/Avs2YUV
Thanks.

EDIT: Thanks for the advice redbtn.

[redbtn]

I can't run the newest version of x265 (3.2.1+1-b5c86a6) in Simple x264/x265 Launcher v2.94 (2019-10-05), it complains that it's a too old version of x265.
Also, there is a newer version (not any important feature, but still) of Avs2YUV released than is included in that package,
http://avisynth.nl/index.php/Avs2YUV
Thanks.
You can use --skip-version-checks
--skip-version-checks ......... Skip x264/x265 version checks, NOT recommended!

[Forteen88]

I'm having errors when I'm encoding with x265 (I updated to x265-3.2+15) using 2-pass with Simple x264/x265 Launcher v2.94 (2019-10-05), it fails in the 2nd pass. Anyone else got this problem?
x265 in CRF-mode works great though.
I only want to use 2-pass mode (to get same average bitrate) to make tests on which --psy-rd & --psy-rdoq values I prefer most.

Maybe I should reinstall Simple x264/x265 Launcher with the old software (x265) to see if 2-pass mode works...

BTW, what happened to LoRd_MuldeR (who created this software)? He has not been online at Doom9 for a long time now (Last Activity: 29th October 2019), I hope that he's OK.

EDIT: Never mind, it seems that the version of x265 had problem with 2-pass encoding. I've not tried it though.

[RyaNJ]

@LoRd_MuldeR: Please add this option to x265 GUI, thank you.

I'd also like to request this too. Thanks :)

[LoRd_MuldeR]

4. Tune: introduce --tune animation option which improves encode quality for animated content

@LoRd_MuldeR: Please add this option to x265 GUI, thank you.
I'd also like to request this too. Thanks :)

Okay, I added this for the next release. I somehow overlooked this request.

BTW, what happened to LoRd_MuldeR (who created this software)? He has not been online at Doom9 for a long time now (Last Activity: 29th October 2019), I hope that he's OK.

Everything is okay. It's just real life kicking in, every now and then ;)

[redbtn]

I'm glad you ok! We were worried.

[Forteen88]

I'm glad you ok! We were worried.+1. Too many great devs here (Didée, Loren Merritt, DS. etc) disappeared.

[tormento]

Notice that http_//download.videolan.org/pub/x264/binaries/ is discontinued as service.

Please update to https_//artifacts.videolan.org/x264/ to get them.

Plus using latest x264 gives following warning:

[2019-12-28][11:02:33] x264 0.159.2991 1771b55
[2019-12-28][11:02:33] (libswscale 5.6.100)
[2019-12-28][11:02:33] (libavformat 58.33.100)
[2019-12-28][11:02:33] built on Dec 16 2019, gcc: 8.2-win32 20190215
[2019-12-28][11:02:33] x264 configuration: --chroma-format=all
[2019-12-28][11:02:33] libx264 configuration: --chroma-format=all
[2019-12-28][11:02:33] x264 license: GPL version 2 or later
[2019-12-28][11:02:33] libswscale/libavformat license: LGPL version 2.1 or later
[2019-12-28][11:02:33]
[2019-12-28][11:02:33] WARNING: Your x264 binary uses an untested core (API) version, take care!
[2019-12-28][11:02:33] This application works best with x264 core (API) version 158. Newer versions may work or not.

[LoRd_MuldeR]

Notice that http_//download.videolan.org/pub/x264/binaries/ is discontinued as service.

Please update to https_//artifacts.videolan.org/x264/ to get them.

I know ;)

But I have been using LigH's builds for quite some time now, because those have FFMS support enabled – which the Videolan.org builds do not have – and because Komisar's builds have not been updated in a long time.

Anyways, as far as I can tell, there have not been any relevant changes since r2984 (the last time I updated the included x264 binaries), except maybe for this VBV-related fix:
https://code.videolan.org/videolan/x264/commit/76669180821692303465b59de9c9e3933db32db2

(Unless you are using CFR+VBV, you don't need to care. And even if you do, the bug they fixed recently probably only occurs under very rare circumstances)

[Forteen88]

LoRd_MuldeR, there is a newer version (not any important features, but it's compiled with a more newer compiler) of Avs2YUV released than is included in that package,
http://avisynth.nl/index.php/Avs2YUV

How do I use that newer version of Avs2YUV in "Simple x264/x265 Launcher v2.94 (2019-10-05)"? I got an error last time I tried to use it after updating Avs2YUV.

BTW, Happy New Year!

[LoRd_MuldeR]

How do I use that newer version of Avs2YUV in "Simple x264/x265 Launcher v2.94 (2019-10-05)"? I got an error last time I tried to use it after updating Avs2YUV.

You can't – without also updating the expected version in the source code.

Also, the only change in Avs2YUV 0.24 "mod 6", since Avs2YUV 0.24 "mod 5" that is currently included with Simple x264 Launcher, is the addition of 4:0:0 (monochrome) output support.

Unless you need exactly that, you don't need to care. Anyhow, next Simple x264 Launcher release will probably be updated to Avs2YUV 0.24 "mod 6".

[LoRd_MuldeR]

Here is a new TEST build that has the latest x264 and Avs2YUV versions included:
x264_launcher-TEST.2020-01-03.exe (https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher-TEST.2020-01-03.exe/download)

[Forteen88]

Thanks for new version. I'll try it out soon.

[deco20]

Lord_Mulder, I have a problem with determining clip properties. It fails on "Get source info" step, but it seems that the command that is used is ok.
When I run it manually, I get following response:
K:\dg.avs: 1280x534, YV12, 8-bits, progressive, 24000/1001 fps, 154508 frames

From what I saw in the code, this step is about extracting some of these values using regex. Is my output somehow different from the one that is expected by the regex?

[LoRd_MuldeR]

Lord_Mulder, I have a problem with determining clip properties. It fails on "Get source info" step, but it seems that the command that is used is ok.
When I run it manually, I get following response:
K:\dg.avs: 1280x534, YV12, 8-bits, progressive, 24000/1001 fps, 154508 frames

From what I saw in the code, this step is about extracting some of these values using regex. Is my output somehow different from the one that is expected by the regex?

Your output from the manual invocation of Avs2YUV looks normal to me. Also, I tried with a similar setup and it seems to work fine for me:
https://i.imgur.com/7k1LJ48.png

I suspect something is going wrong with the Avs2YUV invocation that happens inside Simple x264 Launcher (maybe AVS script fails to load for some reason), so can you please post the complete log from Simple x264 Launcher?

[deco20]

The script itself looks like these:
DGSource("K:\ToEncode\00000.dgi")
Crop(0, 140, 0, -140)
Spline36Resize(1280, 534)

It is correctly interpreted by AvsPmod and I used to do similar things before.

As for the log, there it is:
[2020-01-04][15:39:30] --- SYSTEMINFO ---
[2020-01-04][15:39:30]
[2020-01-04][15:39:30] Binary Path : C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2
[2020-01-04][15:39:30] Avisynth : Yes
[2020-01-04][15:39:30] VapourSynth : No
[2020-01-04][15:39:30]
[2020-01-04][15:39:30] --- SETTINGS ---
[2020-01-04][15:39:30]
[2020-01-04][15:39:30] Encoder : x264 (AVC/H.264), 64-Bit (x64), 8-Bit
[2020-01-04][15:39:30] Source : Avisynth (avs)
[2020-01-04][15:39:30] RC Mode : CRF
[2020-01-04][15:39:30] Preset : veryslow
[2020-01-04][15:39:30] Tuning : <None>
[2020-01-04][15:39:30] Profile : High
[2020-01-04][15:39:30] Custom : --level 4.1 --sar 1:1 --no-fast-pskip --no-dct-decimate --no-mbtree --deblock -3:-3 --ipratio 1.2 --pbratio 1.1 --psy-rd 1.1 --aq-mode 3 --aq-strength 0.7 --aq2-strength 0 --aq2-sensitivity 0 --aq3-mode 0 --bframes 12
[2020-01-04][15:39:30]
[2020-01-04][15:39:30] --- CHECK VERSION ---
[2020-01-04][15:39:30]
[2020-01-04][15:39:30] Detect video encoder version:
[2020-01-04][15:39:30]
[2020-01-04][15:39:30] Creating process:
[2020-01-04][15:39:30] "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x264_x64.exe" --version
[2020-01-04][15:39:30]
[2020-01-04][15:39:31] x264 0.159.2991+49 524a90c t_mod_New [0-bit@all X86_64]
[2020-01-04][15:39:31] (libswscale 5.5.100)
[2020-01-04][15:39:31] (libavformat 58.29.100)
[2020-01-04][15:39:31] (ffmpegsource 2.31.0.0)
[2020-01-04][15:39:31] built on Dec 21 2019, gcc: 9.2.1 20191212
[2020-01-04][15:39:31] x264 configuration: --chroma-format=all--disable-opencl
[2020-01-04][15:39:31] libx264 configuration: --chroma-format=all--disable-opencl
[2020-01-04][15:39:31] x264 license: Non-Free
[2020-01-04][15:39:31] libswscale/libavformat/ffmpegsource license: nonfree and unredistributable
[2020-01-04][15:39:31] WARNING: This binary is unredistributable!
[2020-01-04][15:39:31]
[2020-01-04][15:39:31] Detect video source version:
[2020-01-04][15:39:31]
[2020-01-04][15:39:31] Creating process:
[2020-01-04][15:39:31] "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe"
[2020-01-04][15:39:31]
[2020-01-04][15:39:31] Avs2YUV 0.24bm6
[2020-01-04][15:39:31]
[2020-01-04][15:39:31] > x264 revision: 2991 (core #159) - with custom patches!
[2020-01-04][15:39:31] > Avs2YUV version: 0.24.6
[2020-01-04][15:39:31]
[2020-01-04][15:39:31] --- GET SOURCE INFO ---
[2020-01-04][15:39:31]
[2020-01-04][15:39:31] Creating process:
[2020-01-04][15:39:31] "C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x86\avs2yuv_x86.exe" -frames 1 K:\dg.avs NUL
[2020-01-04][15:39:31]
[2020-01-04][15:39:34]
[2020-01-04][15:39:34] FAILED TO DETERMINE CLIP PROPERTIES !!!

[LoRd_MuldeR]

Well, according to your log, Avs2YUV did not produce any text output at all. This means it either ran into some kind of error (but in that case we'd expect to see at least some sort of error message) or it just crashed.

Does that exactly same .avs file open correctly (and seek properly) in the 32-Bit (x86) version of VirtualDub (http://virtualdub.sourceforge.net/)?

Also, please check the following: Does this problem only appear with Avs2YUV 0.24bm6, i.e. is this a new problem in the latest TEST build, or did the same thing already happen with Avs2YUV 0.24bm5?

[deco20]

Does that exactly same .avs file open correctly (and seek properly) in the 32-Bit (x86) version of VirtualDub (http://virtualdub.sourceforge.net/)?
Yes, no problems.


Also, please check the following: Does this problem only appear with Avs2YUV 0.24bm6, i.e. is this a new problem in the latest TEST build, or did the same thing already happen with Avs2YUV 0.24bm5?
It didn't work in the earlier version neither. That's why I updated it to see if it works in the latest one.

[Emulgator]

Maybe some coincidence under changed circumstances ? Win10, nVidia driver, that route ?
A lead, maybe...

https://forum.videohelp.com/threads/378319-DGSource-incompatible-with-KNLMeansCL
http://rationalqm.us/board/viewtopic.php?f=8&t=436

[LoRd_MuldeR]

It didn't work in the earlier version neither. That's why I updated it to see if it works in the latest one.

Maybe some coincidence under changed circumstances ? Win10, nVidia driver, that route ?

Yeah, the problems with bugs, especially memory corruptions, is that they often lead to undefined behavior – which means that things may seem to work 99% of the time, but then, all of a sudden, they stop working.

In this situation, every little (seemingly unrelated) change is like rolling the dice again...

What you can try: Strip down your Avisynth script to the bare minimum (e.g. source filter only) and try again. If the problem still appears with the minimal script, try another source filter.

Also: Which exact version of Avisynth are you using? In my experience, the official "v2.6.0 ST" (32-Bit) build is the most reliably. The "MT" builds may introduce all sorts of random hiccups, so try switching back to "ST" if you are using "MT".

(In addition to that, try removing every plug-in DLL from your Avisynth "plugins" directory that is not actually needed, just to be sure!)

[deco20]

Thanks for suggestions, but none of it worked unfortunately.
I have AviSynth 2.6.0 ST 32-Bit installed. I tried to run it with only source filter in the script, I tried to run with only necessary plugins in AviSynth.
I updated also DGDecNV and NVidia drivers, still the same.

If you work with m2ts files, what source filter do you use?

[LoRd_MuldeR]

If you work with m2ts files, what source filter do you use?

I tend to re-mux M2TS files with MKVToolnix (https://mkvtoolnix.download/downloads.html), and then just load the resulting MKV with FFMS2 ;)

[deco20]

I tend to re-mux M2TS files with MKVToolnix (https://mkvtoolnix.download/downloads.html), and then just load the resulting MKV with FFMS2 ;)

Ok, will try that, thank you very much for your help and of course, for your app, it's great.

[tormento]

Here is a new TEST build that has the latest x264 and Avs2YUV versions included
Working here.

:thanks: