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

[tona69]

Okay, after thinking about it a bit more, I probably know what your problem was:

If you have only the 32-Bit version VapourSynth installed, but you have selected "prefer 64-Bit" in the preferences, it was going to fail at the start of the encode.

Similarly, if you have only the 64-Bit version VapourSynth installed, but you have not selected "prefer 64-Bit" in the preferences, encode was going to fail as well.

This Test build should improve the "32-Bit vs. 64-Bit" selection logic for the Avisynth/VapourSynth source filters:
http://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2016-01-04.TEST.exe/download

Testing (http://prntscr.com/9noye8)

[movmasty]

To make it simple, if one doesnt have Xsinth installed, what input can give?

Why it is not accepting my Huffy avi?

You need FFmpeg for this?

Why you could even have a patch for audio but not for intermediate uncompressed avi?

Why doesnt let me to delete the 64 binaries in a 32 bit environment?

So, my input was illegal and it stopped, but i put the following string like command

--ctu 32 --cutree --keyint 150 --min-keyint 10 --ipratio 1.9 --nr-inter 390 --sar 16:15 --no-strong-intra-smoothing

Is it legal?

[LoRd_MuldeR]

To make it simple, if one doesnt have Xsinth installed, what input can give?

x264: Pretty much anything that can be decoded with libavcodec/libavformat (FFmpeg libraries). Which is pretty much everything.

x265: "Raw" YUV data in YUV4MPEG2 (http://wiki.multimedia.cx/index.php?title=YUV4MPEG2) format.


Why it is not accepting my Huffy avi?

What is "it"?

If you refer to x265 here: At this time, x265 doesn't support reading (compressed) AVI files. Or anything else, except for YUV4MPEG2.

Just frame-serve the input from Avisynth/VaourSynth. Or pipe from FFmpeg. That's it.


You need FFmpeg for this?

If you want to pipe the input from FFmpeg, then, obviously, you are going to need FFmepg.

Avisynth/VaourSynth doesn't need FFmpeg (as a standalone application), but you probably want to use FFMS2 (https://github.com/FFMS/ffms2/releases/latest) (FFmpegSource).


Why you could even have a patch for audio but not for intermediate uncompressed avi?

Don't know what you mean. Neither x264 nor x265 handles audio.

AFAIK, there is an unofficial "audio support" patch for x264, but that has never been committed (and probably never will).


Why doesnt let me to delete the 64 binaries in a 32 bit environment?

Again, what is "it" ???

So, my input was illegal and it stopped, but i put the following string like command


--ctu 32 --cutree --keyint 150 --min-keyint 10 --ipratio 1.9 --nr-inter 390 --sar 16:15 --no-strong-intra-smoothing

Is it legal?

"legal" in what regard?

[movmasty]

I was a bit imprecise sorry,

I refer to x265, it doesnt accet avi in huffy, as i said i dont have avisinth,
could you put any prog able to feed x265 in the pack?

Since im on win32, i tryed to delete the binaries in 64 bits, it is not possible.

is
--ctu 32 --cutree --keyint 150 --min-keyint 10 --ipratio 1.9 --nr-inter 390 --sar 16:15 --no-strong-intra-smoothing
ok for x265?

[LoRd_MuldeR]

I was a bit imprecise sorry,

I refer to x265, it doesnt accet avi in huffy, as i said i dont have avisinth

That's easy to fix:
http://sourceforge.net/projects/avisynth2/

could you put any prog able to feed x265 in the pack?

In theory support for piping input from FFmpeg could be implemented. But it's currently not on my TODO list.

Just use FFMS2 ;)


Since im on win32, i tryed to delete the binaries in 64 bits, it is not possible.

Just ignore the 64-Bit binaries. They will not be used on your system, but they won't hurt either.

is
--ctu 32 --cutree --keyint 150 --min-keyint 10 --ipratio 1.9 --nr-inter 390 --sar 16:15 --no-strong-intra-smoothing
ok for x265?

I don't see anything "wrong" with this command. But is it a "good" idea to use?

Totally depends on what you are trying to achieve...

[movmasty]

OK thanks

[Minister]

Try with this test version:
http://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher.2015-12-20.TEST-2.exe/download


Sorry to reply so late to this.

What you did is terrific! Solves the issue I was having exactly. Thank you very much for that.

Using the newer test build now.

:)

[LoRd_MuldeR]

Simple x264 Launcher v2.65

Version 2.65 [2016-01-24]
* Added menu entry to remove all completed or enqueued jobs at once
* Improved 32-Bit vs. 64-Bit selection for Avisynth/VapourSynth
* Updated x264 to revision 2665
* Updated x265 to version 1.8+212

[LoRd_MuldeR]

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

Version 2.66 [2016-02-06]
* Updated x265 to version 1.9+3

[2-perf]

Hi,

I'm a total newbie to video encoding. A friend at work heard me saying that I was using Handbrake to encode some Quicktime files to Blu-ray and told me I should be using a frame server... WTF? I replied to him!

Anyway he came to my place, set me up with:

- python-3.5.1-amd64.exe
- ffms2-2.22-msvc (I'm using the x64 flavor)
- vapoursynth-r29.exe (x64 flavor I guess)
- x264_launcher.2016-02-06.exe

He wrote me a VapourSynth script whish looks like this:

import vapoursynth as vs

# get the core instance
core = vs.get_core()

# load a native vapoursynth plugin, you can also use the auto-loading
# you should use absolute paths as the working directory may not be what you think it is
core.std.LoadPlugin(r'S:\Dropbox\softwares\portableapps\codec_encoder\ffms2-2.22-msvc\x64\ffms2.dll')

# open a video file; ret is now a clip object

path = r'D:\restauration\projet\tropico\deliveries\master\tropico.mov'

ret = core.ffms2.Source( source = path )

# flip the video a bit
#ret = core.std.Transpose( ret )

# set the clip to be output
ret.set_output()

The things is it fails 9 times out of 10 when trying to start the second pass.

Here's the .log (Well, I hope). Sorry I'm a digital colorist not a computer geek. :p

Simple x264 Launcher (Build #1012), built 2016-02-06

Job started at 2016-02-18, 22:19:28.

Source file : D:\encodage\projet\tropico\script.vpy
Output file : D:\encodage\projet\tropico\output\script.264

--- SYSTEMINFO ---

Binary Path : C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2
Avisynth : No
VapourSynth : Yes

--- SETTINGS ---

Encoder : x264 (H.264/AVC), x64, 8-Bit
Source : VapourSynth (vpy)
RC Mode : 2-Pass
Preset : slower
Tuning : Film
Profile : High
Custom : --level 4.1 --ref 4 --subme 10 --psy-rd 1.00:0.15 --merange 24 --deadzone-inter 21 --deadzone-intra 11 --no-fast-pskip --cqm flat --chroma-qp-offset 3 --threads 12 --lookahead-threads 1 --slices 4 --no-dct-decimate --bluray-compat --vbv-maxrate 38000 --vbv-bufsize 30000 --bframes 3 --b-pyramid 1 --weightb --open-gop --weightp 1 --keyint 24 --min-keyint 1 --rc-lookahead 24 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --qcomp 0.00 --qpmin 0

--- CHECK VERSION ---

Detect video encoder version:

Creating process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x264_8bit_x64.exe" --version

x264 0.148.2665 a01e339
(libswscale 4.0.100)
(libavformat 57.21.101)
(ffmpegsource 2.22.0.1)
built by Komisar on Jan 18 2016, gcc: 4.8.4 (multilib.generic.Komisar)
x264 configuration: --bit-depth=8 --chroma-format=all
libx264 configuration: --bit-depth=8 --chroma-format=all
x264 license: GPL version 2 or later
libswscale/libavformat/ffmpegsource license: GPL version 2 or later

Detect video source version:

Creating process:
"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" --version

VapourSynth Video Processing Library
Copyright (c) 2012-2015 Fredrik Mellbin
Core R29
API R3.2
Options: -

> x264 revision: 2665 (core #148)
>
VapourSynth version: r29 (API r3)

--- GET SOURCE INFO ---

Creating process:
"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" --info D:\encodage\projet\tropico\script.vpy -

Width: 1920
Height: 1080
Frames: 7491
FPS: 24000/1001 (23.976 fps)
Format Name: YUV422P10
Color Family: YUV
Bits: 10
SubSampling W: 1
SubSampling H: 0

Resolution: 1920x1080
Frame Rate: 24000/1001
No. Frames: 7491

--- ENCODING PASS #1 ---

Creating input process:
"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" --y4m D:\encodage\projet\tropico\script.vpy -

Creating encoder process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x264_8bit_x64.exe" --bitrate 35000 --pass 1 --stats D:\encodage\projet\tropico\output\script.stats --preset slower --tune film --profile high --level 4.1 --ref 4 --subme 10 --psy-rd 1.00:0.15 --merange 24 --deadzone-inter 21 --deadzone-intra 11 --no-fast-pskip --cqm flat --chroma-qp-offset 3 --threads 12 --lookahead-threads 1 --slices 4 --no-dct-decimate --bluray-compat --vbv-maxrate 38000 --vbv-bufsize 30000 --bframes 3 --b-pyramid 1 --weightb --open-gop --weightp 1 --keyint 24 --min-keyint 1 --rc-lookahead 24 --colorprim bt709 --transfer bt709 --colormatrix bt709 --qcomp 0.00 --qpmin 0 --output D:\encodage\projet\tropico\output\script.264 --frames 7491 --demuxer y4m --stdin y4m -

y4m [info]: 1920x1080p 0:0 @ 24000/1001 fps (cfr)
resize [warning]: converting from yuv422p16le to yuv420p16le
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x264 [info]: profile Main, level 4.1
x264 [info]: frame I:339 Avg QP:10.89 size:467818
x264 [info]: frame P:2145 Avg QP:13.96 size:277862
x264 [info]: frame B:5007 Avg QP:18.17 size:120544
x264 [info]: consecutive B-frames: 5.1% 5.4% 35.4% 54.0%
x264 [info]: mb I I16..4: 41.5% 0.0% 58.5%
x264 [info]: mb P I16..4: 43.0% 0.0% 0.0% P16..4: 35.5% 0.0% 0.0% 0.0% 0.0% skip:21.5%
x264 [info]: mb B I16..4: 12.5% 0.0% 0.0% B16..8: 26.5% 0.0% 0.0% direct:26.8% skip:34.2% L0:10.4% L1:14.9% BI:74.8%
x264 [info]: direct mvs spatial:99.7% temporal:0.3%
x264 [info]: coded y,uvDC,uvAC intra: 94.9% 39.3% 19.9% inter: 47.8% 11.9% 5.6%
x264 [info]: i16 v,h,dc,p: 14% 9% 65% 12%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 12% 9% 20% 10% 11% 11% 9% 10% 10%
x264 [info]: i8c dc,h,v,p: 65% 16% 16% 4%
x264 [info]: Weighted P-Frames: Y:3.0% UV:0.8%
x264 [info]: kb/s:34776.07
encoded 7491 frames, 25.61 fps, 34776.07 kb/s
vpyp [info]: Output 7491 frames in 292.32 seconds (25.63 fps)
Final file size is 1.26 GB bytes.

--- ENCODING PASS #2 ---

Creating input process:
"C:\Program Files (x86)\VapourSynth\core64\vspipe.exe" --y4m D:\encodage\projet\tropico\script.vpy -

Creating encoder process:
"C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64\x264_8bit_x64.exe" --bitrate 35000 --pass 2 --stats D:\encodage\projet\tropico\output\script.stats --preset slower --tune film --profile high --level 4.1 --ref 4 --subme 10 --psy-rd 1.00:0.15 --merange 24 --deadzone-inter 21 --deadzone-intra 11 --no-fast-pskip --cqm flat --chroma-qp-offset 3 --threads 12 --lookahead-threads 1 --slices 4 --no-dct-decimate --bluray-compat --vbv-maxrate 38000 --vbv-bufsize 30000 --bframes 3 --b-pyramid 1 --weightb --open-gop --weightp 1 --keyint 24 --min-keyint 1 --rc-lookahead 24 --colorprim bt709 --transfer bt709 --colormatrix bt709 --qcomp 0.00 --qpmin 0 --output D:\encodage\projet\tropico\output\script.264 --frames 7491 --demuxer y4m --stdin y4m -

y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

WARNING: Input process exited with error (code: -1073741819), your encode might be *incomplete* !!!

IMPORTANT: The Vapoursynth process terminated abnormally. This means Vapoursynth or one of your Vapoursynth-Plugin's just crashed.

PROCESS EXITED WITH ERROR CODE: -1

Thanks for your patience.

[LoRd_MuldeR]

As the error message says:
The Vapoursynth process terminated abnormally. This means Vapoursynth or one of your Vapoursynth-Plugin's just crashed.

-1073741819 = 0xC0000005 = STATUS_ACCESS_VIOLATION

So this is a problem with Vapoursynth or, more likely, one of the Vapoursynth plug-in's involved. Might as well be a hardware issue though...

[2-perf]

As the error message says:


It's a problem with Vapoursynth or, more likely, one of the Vapoursynth plug-in's involved. Might also be a hardware issue though...

Thanks LoRd_MuldeR. I'll post in the VapourSynth forum.

[djesteban]

As the error message says:


-1073741819 = 0xC0000005 = STATUS_ACCESS_VIOLATION

So this is a problem with Vapoursynth or, more likely, one of the Vapoursynth plug-in's involved. Might as well be a hardware issue though...

I tested this on my side out of curiosity. Tested with two .mov file, one encoded in DNxHD and the other one in ProRes.

I have the same issue than 2-perf where it will crash sometimes on 1-pass startup but mostly on 2nd pass, I would say and easy 8-9 times out of 10.

Seems definitively related to vapoursynth mishandling either .mov containers or the two codecs above... or both. Anyways, there's also ffms2 in the equation here so it could also be part of the issue, but I doubt it.
Encoding a h264 file causes no issue/crash at all.

[SuLyMaN]

Thank you Lord Mulder for this software :)

[LoRd_MuldeR]

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

Version 2.67 [2016-03-17]
* Updated x265 to version 1.9+96
* Fixed detection of 64-Bit VapourSynth in certain cases

[LoRd_MuldeR]

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

Version 2.68 [2016-04-09]
* Updated build environment to Visual Studio 2015 with Update-2
* Updated x265 to version 1.9+106

[RTW47]

vapoursynth input - still gives me troubles with x64 Python 3.5.1 and x64 vapoursynth R31 installed, on Windows 7 SP1;
v2.68.1018 --console as expected shows that 64-bit vapoursynth was successfully detected, unfortunately after selecting add job: I still get "VapourSynth is not/available!" message.
- additionally prefering 64-Bit source in the preferences - not helping;
edit:. trying update to 1024 build via web updater returns SendRequest Error;
edit1:. now noticed that if I just "Ignore&Continue", - everything works without actual problem;

[LoRd_MuldeR]

vapoursynth input - still gives me troubles with x64 Python 3.5.1 and x64 vapoursynth R31 installed, on Windows 7 SP1;
v2.68.1018 --console as expected shows that 64-bit vapoursynth was successfully detected, unfortunately after selecting add job: I still get "VapourSynth is not/available!" message.

Argh, there was a stupid mistake in one of the checks, so it was testing for Avisynth flag where it actually should be testing for VapourSynth flag :mad:

Should be fixed by now:
https://github.com/lordmulder/Simple-x264-Launcher/commit/f6e8d2e113fa26819e6e567482fef73df172f0e2#diff-914a5ac5409e8ddb42c98e1f76e206ff

Please try new TEST version:
https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher-TEST.2016-04-28.exe/download

edit:. trying update to 1024 build via web updater returns SendRequest Error;
edit1:. now noticed that if I just "Ignore&Continue", - everything works without actual problem;

Works for me :confused:

(Probably a short server outage on SF.net)

[RTW47]

Should be fixed by now:
https://github.com/lordmulder/Simple-x264-Launcher/commit/f6e8d2e113fa26819e6e567482fef73df172f0e2#diff-914a5ac5409e8ddb42c98e1f76e206ff

Please try new TEST version:
https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher-TEST.2016-04-28.exe/download

I can confirm that test build works properly.

[szabi]

Hi

Since update to version 2.69 this error occurs:
error: LoadPlugin: unable to load "C:\My Program Files\MeGUI\tools\lsmash\LSMASHSource.dll", Module not found. Install missing library?
I tried it and this avs script works correctly with megui and virtualdub.
What reason makes launcher to fail pluginload?

bye

[LoRd_MuldeR]

Hi

Since update to version 2.69 this error occurs:
error: LoadPlugin: unable to load "C:\My Program Files\MeGUI\tools\lsmash\LSMASHSource.dll", Module not found. Install missing library?

This is an Avisynth error, not Simple x264 Launcher error ;)

Note that Simple x264 Launcher is pretty much just a GUI that launches x264/x265 + Avs2YUV/VSPipe for you. So probably just coincidence that the issue happened to start after the v2.69 update. The real problem must be in Avisynth!


Anyway, one possible reason that comes to my mind:

Maybe your plug-in (LSMASHSource.dll) is 32-Bit and with VirualDub you are using 32-Bit Avisynth, so all is fine, but with Simple x264 Launcher you are trying to use 64-Bit Avisynth? Or the other way around.


[EDIT]

Another possible reason:

Maybe LSMASHSource.dll has a dependency on another DLL. And, when working with VirualDub, that DLL is picked up from VirualDub directory, or from whatever happens to be the "current" directory when you launch VirualDub. But when working with Simple x264 Launcher that other DLL can no longer be loaded, because it's neither in the avs2yuv.exe directory nor in whatever happens to be the "current" directory when you launch Simple x264 Launcher.

It's a very common pitfall with Avisynth plug-in's that have dependencies on other DLL's. Putting those other DLL's into the Avisynth plug-in directory, alongside the plug-in DLL, is not going to work! They must be in one of the directories where the host application (e.g. VirualDub or avs2yuv.exe) will be able to pick them up! One solution is to put the required DLL into "System32" directory. Then it can always be found. But, when doing so, be aware of DLL Hell problem...

[LoRd_MuldeR]

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

Version 2.70 [2016-04-29]
* Fixed potential VapourSynth error, when Avisynth is not installed
* Some installer improvements


I can confirm that test build works properly.

Thanks for confirming.

[szabi]

This is an Avisynth error, not Simple x264 Launcher error ;)

Note that Simple x264 Launcher is pretty much just a GUI that launches x264/x265 + Avs2YUV/VSPipe for you. So probably just coincidence that the issue happened to start after the v2.69 update. The real problem must be in Avisynth!


Anyway, one possible reason that comes to my mind:

Maybe your plug-in (LSMASHSource.dll) is 32-Bit and with VirualDub you are using 32-Bit Avisynth, so all is fine, but with Simple x264 Launcher you are trying to use 64-Bit Avisynth? Or the other way around.


[EDIT]

Another possible reason:

Maybe LSMASHSource.dll has a dependency on another DLL. And, when working with VirualDub, that DLL is picked up from VirualDub directory, or from whatever happens to be the "current" directory when you launch VirualDub. But when working with Simple x264 Launcher that other DLL can no longer be loaded, because it's neither in the avs2yuv.exe directory nor in whatever happens to be the "current" directory when you launch Simple x264 Launcher.

It's a very common pitfall with Avisynth plug-in's that have dependencies on other DLL's. Putting those other DLL's into the Avisynth plug-in directory, alongside the plug-in DLL, is not going to work! They must be in one of the directories where the host application (e.g. VirualDub or avs2yuv.exe) will be able to pick them up! One solution is to put the required DLL into "System32" directory. Then it can always be found. But, when doing so, be aware of DLL Hell problem...

Hi

I try to figure out what cause it, until that megui going to be used instead of your program which i prefer more.
However before update this issue did not exist.
Thanks.

bye

[LoRd_MuldeR]

However before update this issue did not exist.

Please confirm again that the issue still exists with latest version. If so, downgrade to the "old" version (v2.68), but do not touch anything else. Does that resolve the issue?

[szabi]

Hi

You were right the problem comes not from simple launcher.
It comes from megui. It was used to create script.
Megui does something what I do not see.
I reinstall it. Since that script works only with megui nothing else.
Until that I use ffms for indexing which works with simple.
Sorry for that I made a false conclusion.

bye

[LoRd_MuldeR]

It comes from megui. It was used to create script.
Megui does something what I do not see.
I reinstall it. Since that script works only with megui nothing else.
Until that I use ffms for indexing which works with simple.
Sorry for that I made a false conclusion.

Again, I suggest you do this:
Figure out if the plugin DLL that won't load is 32-Bit or 64-Bit. You can use this (https://mzrst.com/) tool, to check the "bitness" (see example here (http://i.imgur.com/C0E7Kqc.png)). If it is 32-Bit, can only work with 32-Bit Avisynth and thus only with 32-Bit programs; if it's 64-Bit, can only work with 64-Bit Avisynth and thus only with 64-Bit programs. The Simple x264 Launcher supports both "variants" of Avisynth – provided they are installed on your system – by using either 32-Bit or 64-Bit version of Avs2YUV. If both "variants" of Avisynth are installed, you can choose the preferred one in the preferences (this clearly has no effect, of only one "variant" is installed). Make sure it uses the version that matches the "bitness" of your plugin-in DLL!
Use this (http://www.dependencywalker.com/) tool to figure out if your plug-in DLL has some additional dependencies. You need the 32-Bit version of the tool for 32-Bit plug-in DLL, and the 64-Bit version for 64-Bit DLL. If it shows any dependencies other than standard Windows DLL's, then these additional DLL's will need to be in a path where they can be found when the plug-in DLL's get loaded into the Avs2YUV process – otherwise loading of the plug-in DLL is going to fail due to missing dependency!

[szabi]

Hi

Many thanks for your help and I apologize for my awkward situation.
Something happened with Microsoft Visual C++ 2015 Redistributable x86 (https://go.microsoft.com/fwlink/?LinkId=615459) which needed by L-SMASH.
It had to be reinstalled.
Somehow megui worked without it but simple did not.
I must say again thanks and sorry for it.

bye

[LoRd_MuldeR]

Here is a new TEST version with experimental NVEncC (http://forum.videohelp.com/threads/370223-NVEncC-by-rigaya-NVIDIA-GPU-encoding) (NVidia GPU encoding) support:
https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher-TEST.2016-05-08.exe/download

This requires a NVIDIA Kepler/Maxwell based GPU with driver 358.xx or higher!

[Zetti]

Why is there no option to select x86 or x64 when i choose to use NVEncC??

[LoRd_MuldeR]

Why is there no option to select x86 or x64 when i choose to use NVEncC??

There is. Isn't it? :confused:
http://i.imgur.com/Atx33Gu.png

[Zetti]

Sorry i mean 8-Bit and 10-Bit option for AVC and HEVC when i choose to use NVEncC.

[LoRd_MuldeR]

Sorry i mean 8-Bit and 10-Bit option for AVC and HEVC when i choose to use NVEncC.

I don't think NVEncC currently offers such an option, or am I missing something?

[Zetti]

I do not know because I am a beginner with NVEnc, so that's why I ask.

[LoRd_MuldeR]

Here is a new TEST version:
https://sourceforge.net/projects/muldersoft/files/Simple%20x264%20Launcher/Testing/x264_launcher-TEST.2016-05-13.exe/download

x265 updated to latest build.

[r0lZ]

I would like to know where you download the x265 binaries distributed with your GUI. There are 3 links in the help menu, but I can't find the 10 and 12-bit x86 versions:
builds.x265.eu (https://builds.x265.eu/) has no x86 versions any more.
x265.ru (http://x265.ru/en/builds/) has only the 8bit color depth in x86.
chromashift.org (http://chromashift.org) is dead.

Also, maybe you should remove or change the chromashift dead link.

[LoRd_MuldeR]

I would like to know where you download the x265 binaries distributed with your GUI.

https://www.mediafire.com/?6lfp2jlygogwa --- by LigH

[r0lZ]

Thanks. (And sorry for replying only now. For whatever reason, I haven't been notified of your reply.)

[tormento]

Big thanks for your neat software. I am moving to complete x64 encoding system and MeGUI was only x86 and full of too much bells and whistles.

I have find yours and it's really useful, giving me full control of everything ;)

[LoRd_MuldeR]

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

Version 2.71 [2016-06-12]
* Updated x265 to version 1.9+200
* Added experimental NVEncC (NVIDIA GPU encoding) support
* Code refactoring
* Fixed various included web-links

[easyfab]

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

What is current NVEnc quality compared to x264 or x265, I didn't find recent review and does newer GTX 1070/1080 have something new ( b-frames, SAO ...) vs GTX 960

[gamebox]

First of all, Mulder, THANK YOU for this wonderful software that is one of the rare tools to encode videos to x265 in Windows XP with all the necessary functionality and very low memory requirements! :)

Just two questions this time - is 64-bit version of x265 encoder compatible with Windows XP 64-bit? I got runtime errors related to kernel32.dll while trying to start encoding task. 32-bit version in 32-bit Windows XP works fine.

Secondly - is there a way to "trick" your software so that existing first pass stats file created by x265 can be reused to start encoding directly from second pass? I had an electricity issue at the beginning of the second pass but stats file is intact.

Thanks in advance :)

[LoRd_MuldeR]

Just two questions this time - is 64-bit version of x265 encoder compatible with Windows XP 64-bit? I got runtime errors related to kernel32.dll while trying to start encoding task. 32-bit version in 32-bit Windows XP works fine.

Not sure. I include plain MinGW builds of x265, as provided by LigH.

It's quite possible though that either the 64-Bit MinGW Runtime or the 64-Bit version x265 itself uses some Win32 API functions there were not available in Windows XP yet.

Note that the first "official" 64-Bit Windows was Vista, so that's probably what most developers regard as a minimum baseline for 64-Bit environments.


JSecondly - is there a way to "trick" your software so that existing first pass stats file created by x265 can be reused to start encoding directly from second pass? I had an electricity issue at the beginning of the second pass but stats file is intact.

No, there is no such function right now, sorry.

[LoRd_MuldeR]

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

Version 2.72 [2016-06-17]
* Now actually contains the "x64" version of NVEncC

[jones1913]

Thanks for this launcher, I like uncomplicated software that does one thing right.

Feature request:
It would be nice if there were an indicator on main window that shows the currently active frameserver mode (32/64 bit).
Because everytime I start the launcher I must open the settings and check whether mode is active.
Ultimately clicking on this indicator instantly could change the mode.

Or alternatively make this setting configurable per job.

Maybe you could consider this, Thanks.

[ProVision]

Hi firstly thanks for the amazing software have been using it since forever. Only one issue. When I put in my custom commands for x265, the program puts in a "-" at the end and ruins the encode. Here's the log:

Simple x264 Launcher (Build #1035), built 2016-06-17

Job started at 2016-06-28, 17:43:48.

Source file : C:\Users\Ali Tawfiq\Desktop\Desktop\Ritual Poster\1.avs
Output file : E:\Temporary\1 (3).hevc

--- SYSTEMINFO ---

Binary Path : E:\Video stuff\x264_launcher.2014-11-02
Avisynth : Yes
VapourSynth : No

--- SETTINGS ---

Encoder : x265 (HEVC/H.265), 64-Bit (x64), 12-Bit
Source : Avisynth (avs)
RC Mode : CRF
Preset : medium
Tuning : <None>
Profile : <Unrestricted>
Custom : --log-level 4 --wpp --ref 6 --rd 6 --cu 64 --min-cu-size 8 --limit-refs 3 --rect --amp --limit-modes --b-intra --cu-lossless --rd-refine --rdoq-level 2 --tu-intra-depth 4 --tu-inter-depth 4 --tskip --rdpenalty 2 --max-tu-size 32 --max-merge 5 --me 3 --subme 7 --merange 200 --temporal-mvp --weightp --weightb --strong-intra-smoothing --psy-rd 3.0 --psy-rdoq 1.0 --open-gop --scenecut 35 --rc-lookahead 225 --lookahead-slices 0 --b-adapt 2 --bframes 7 --bframe-bias 40 --b-pyramid --crf-max 24 --crf-min 16 --aq-mode 3 --aq-strength 2 --qg-size 64 --cutree --qcomp 0.84 --qblur 0.9 --cplxblur 60 --sao --deblock=-1:-3 --info

--- CHECK VERSION ---

Detect video encoder version:

Creating process:
"E:\Video stuff\x264_launcher.2014-11-02\toolset\x64\x265_12bit_x64.exe" --version

x265 [info]: HEVC encoder version 1.9+200-6098ba3e0cf16b11
x265 [info]: build info [Windows][GCC 5.3.0][64 bit] 12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX

Detect video source version:

Creating process:
"E:\Video stuff\x264_launcher.2014-11-02\toolset\x86\avs2yuv_x86.exe"

Avs2YUV 0.24bm3

> x265 version: 1.9+200
> Avs2YUV version: 0.24.3

--- GET SOURCE INFO ---

Creating process:
"E:\Video stuff\x264_launcher.2014-11-02\toolset\x86\avs2yuv_x86.exe" -frames 1 C:\Users\ALITAW~1\Desktop\Desktop\RITUAL~1\1.avs NUL

C:\Users\ALITAW~1\Desktop\Desktop\RITUAL~1\1.avs: 1920x1072, 24000/1001 fps, 35661 frames

Resolution: 1920 x 1072
Frame Rate: 24000/1001
No. Frames: 35661

--- ENCODING VIDEO ---

Creating input process:
"E:\Video stuff\x264_launcher.2014-11-02\toolset\x86\avs2yuv_x86.exe" C:\Users\ALITAW~1\Desktop\Desktop\RITUAL~1\1.avs -

Creating encoder process:
"E:\Video stuff\x264_launcher.2014-11-02\toolset\x64\x265_12bit_x64.exe" --crf 22.7 --preset medium --log-level 4 --wpp --ref 6 --rd 6 --cu 64 --min-cu-size 8 --limit-refs 3 --rect --amp --limit-modes --b-intra --cu-lossless --rd-refine --rdoq-level 2 --tu-intra-depth 4 --tu-inter-depth 4 --tskip --rdpenalty 2 --max-tu-size 32 --max-merge 5 --me 3 --subme 7 --merange 200 --temporal-mvp --weightp --weightb --strong-intra-smoothing --psy-rd 3.0 --psy-rdoq 1.0 --open-gop --scenecut 35 --rc-lookahead 225 --lookahead-slices 0 --b-adapt 2 --bframes 7 --bframe-bias 40 --b-pyramid --crf-max 24 --crf-min 16 --aq-mode 3 --aq-strength 2 --qg-size 64 --cutree --qcomp 0.84 --qblur 0.9 --cplxblur 60 --sao --deblock=-1:-3 --info --output "E:\Temporary\1 (3).hevc" --frames 35661 --y4m -

x265 [warning]: extra unused command arguments given <->
av2y [info]: C:\Users\ALITAW~1\Desktop\Desktop\RITUAL~1\1.avs: 1920x1072, 24000/1001 fps, 35661 frames
av2y [info]: error: wrote only 3062628 of 3087360 bytes

WARNING: Input process exited with error (code: 1), your encode might be *incomplete* !!!

PROCESS EXITED WITH ERROR CODE: 1



Any help? Thanks.

When just using the medium preset with no custom options for x265 the encode works fine.

[Ma]

Custom : --log-level 4 --wpp --ref 6 --rd 6 --cu 64 [...]

It could be a problem with '--cu' options that not exists. Try '--ctu' instead.

[LoRd_MuldeR]

@ProVision:
The "-" at the end of the command-line is the input file. And here the special name "-" means "read input from STDIN, rather than regular file". Since the input is pipe'd from the Avs2YUV process, this is absoloutely required!
But, as Ma said, there is no "--cu" option (see here (http://x265.readthedocs.io/en/default/cli.html) for details!). Seems like this is confusing x265's command-line parser, ultimaterly leading to the error that you are seeing. So please ty using "--ctu" instead.

[LoRd_MuldeR]

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

Version 2.73 [2016-07-03]
* Updated x264 to revision 2705
* Updated x265 to version 1.9+227

[kypec]

Hi Mulder, today I was starting your launcher and warning dialog below appeared. Please note that x264_lancher.exe is referred to as *LameXP* which I had never installed. Probably just a copy+paste typo from your other application? :confused:
http://i67.tinypic.com/10huk55.jpg

[LoRd_MuldeR]

Hi Kypec, actually that warning messages is created by the MUtilities (https://github.com/lordmulder/MUtilities) library, which forms the basis of most of my applications nowadays.

Much of that code originates from the LameXP project and has been generalized for library usage. But it's an ongoing job to generalize all the code. That's why you may still find "LameXP" hardcoded in a few places.

I have now fixed (generalized) the message you are referring to. Thanks for pointing me at that! The fix is not included in v2.74 yet though.