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

[stinman]

Of course I'm not planning to quit updating this tool anytime soon...
http://mewiki.project357.com/wiki/X264_Settings

Good I'm glad you will be here,as far as x264 wiki,I been there and still visit from time to time.I mainly got to learn how to write the commands and use cmd.I can use cmd when I see what other people write for commands.Thanks maybe I will try again,but who needs to when I got this tool :rolleyes:.I was looking at Komisar's link to his x264 builds,seems he is building a x264Gui also.Didn't look like it supports Bluray yet?Keep up the good work!!

Is there a program to help write the necessary avisynth script needed to use a raw h264 file for encoding with simple x264 launcher? I may have ask this before (or something like it).I was looking at your avsproxy gui,it will do this?

[LoRd_MuldeR]

Good I'm glad you will be here,as far as x264 wiki,I been there and still visit from time to time.I mainly got to learn how to write the commands and use cmd.I can use cmd when I see what other people write for commands.Thanks maybe I will try again,but who needs to when I got this tool :rolleyes:.

Well, my tool doesn't expose most x264 options in the GUI. Most non-standard options need to be written into the "custom x264 parameters" box, in CLI syntax!

I was looking at Komisar's link to his x264 builds,seems he is building a x264Gui also.Didn't look like it supports Bluray yet?Keep up the good work!!

You probably are referring to the x264 VFW encoder. That's something different!

You would use the x264 VFW encoder in VirtualDub and friends, but you can not use it as a "stand alone" application.

Is there a program to help write the necessary avisynth script needed to use a raw h264 file for encoding with simple x264 launcher? I may have ask this before (or something like it).I was looking at your avsproxy gui,it will do this?

"AVS Proxy GUI for Avidemux", as the name implies, is a GUI for Avidemux' AVS Proxy. If you don't use Avidemux, then the AVS Proxy GUI is not for you ;)

Nonetheless you should give Avidemux a try, if you didn't do so yet...

About loading H.264 stream in your Avisynth script: If you have a NVidia card and are willing to spend 15$, then DGDecodeNV (http://neuron2.net/dgdecnv/dgdecnv.html) would be the easiest choice.

Otherwise look at FFmpegSource2!

[click2]

Your program works well and is very helpful. : ) One very minor bug report: The tooltip text hasn't been updated since support for media files was added..?


http://i.imgur.com/DtVas.png

[LoRd_MuldeR]

Your program works well and is very helpful. : ) One very minor bug report: The tooltip text hasn't been updated since support for media files was added..?


http://i.imgur.com/DtVas.png

You are right. I will fix that with the next release.

[egrimisu]

Hi,
it seems that if the avs is avisource the encode freezes at the begining, will i lose quality if i use directshowsource (using ffdshow with no postprocesing or other filters), or basicly it's the same thing.
I'm using avisynth 2.58, win7 x64.thanks.

[Tatsukun]

Thanks for this tool, I just found out about it but it's really nice to have. Until now I had been using a bunch of .bat scripts.

I see that the advanced options saves some of your past entries. I was wondering if it would be possible to give these names so it's easier to distinguish and quickly recall them. For example, 480p, 720p, Bluray, Anime, etc.

[Rodger]

Thanks for this tool, I just found out about it but it's really nice to have. Until now I had been using a bunch of .bat scripts.

I see that the advanced options saves some of your past entries. I was wondering if it would be possible to give these names so it's easier to distinguish and quickly recall them. For example, 480p, 720p, Bluray, Anime, etc.

That is an interesting idea. But I don´t think mulder is into it.
My fellow-countryman is not into profiles. He wants to keep it easy as it is named "SIMPLE....."

My idea for you is to create a simple txt-file on the desktop.
Mine looks like this: 1080p Blu-Ray
--level 4.1 --nf --direct auto --subme 5 --no-mbtree --trellis 0 --me umh --vbv-bufsize 28000 --vbv-maxrate 28000 --nal-hrd "vbr" --sar 1:1

1080p AVCHD
--level 4.1 --nf --direct auto --subme 5 --no-mbtree --trellis 0 --me umh --vbv-bufsize 16500 --vbv-maxrate 16500 --nal-hrd "vbr" --sar 1:1

576p 16:9
--level 4.1 --nf --direct auto --subme 5 --no-mbtree --trellis 0 --me umh --vbv-bufsize 6000 --vbv-maxrate 6000 --nal-hrd "vbr" --sar 16:11

It´s the the easiest way to have "profiles" available at hand.

[stinman]

I wonder if we will get a update any time soon to the latest komisars x264.I tried to download the x264x64 from his web page but simple x264 launcher would not recognize it.I don't know how to make it.I hope you haven't quit on us Lord Mulder!

[komisar]

rename it from x264.1804.generic.x86_64.exe to x264_64.exe

[kypec]

rename it from x264.1804.generic.x86_64.exe to x264_64.exe

Small typo there ^^^
The proper filename should be x264_x64.exe
I would recommend to always update both x264 executables to same version (32-bit x264.exe & 64-bit x264_x64.exe) because
launcher uses 32-bit executable for printing help info whereas 64-bit for actual encoding on 64-bit Windows.

[stinman]

Thanks to both of you for your help,I did not update the 32-bit only the 64-bit the first time...Lord Muldor has them separated because the file size makes me think this anyway .So far no matter what it will not work.Tells me x264 is not in the home directory.I put both in the same folder,does the tar folder got to be changed also? I put these snips so you can see what I did.

[kypec]

Thanks to both of you for your help,I did not update the 32-bit only the 64-bit the first time...Lord Muldor has them separated because the file size makes me think this anyway .So far no matter what it will not work.Tells me x264 is not in the home directory.I put both in the same folder,does the tar folder got to be changed also? I put these snips so you can see what I did.
You must have done something wrong. Please follow my step-by-step instructions below and it will work:

I assume you have Simple x264 Launcher installed already. Your installation folder must contain these files:C:\Program Files (x86)\AVTools\Simple x264 Launcher
avs2yuv.exe 52736 4. 3. 2005
launcher.exe 373248 6. 9. 2010
pipebuf.exe 41984 10. 1. 2009
x264.exe 6487552 6. 9. 2010
x264_x64.exe 6798848 6. 9. 2010
sources.tar 395776 6. 9. 2010
GPL.txt 18321 29. 1. 2009

Download the latest x264 executables from Komisar:
32-bit executable r1804 (http://komisar.gin.by/old/1804/x264.1804.generic.x86.exe)
64-bit executable r1804 (http://komisar.gin.by/old/1804/x264.1804.generic.x86_64.exe)
Rename each downloaded file like this:
x264.1804.generic.x86.exe ---> x264.exe
x264.1804.generic.x86_64.exe ---> x264_x64.exe
Copy or move both renamed files to your installation folder so that they will replace the original x264 executables over there.
You can start launcher.exe now and enjoy the latest x264 revision doing its job!

[komisar]

64-bit executable r1804 (http://komisar.gin.by/old/1804/x264.1804.generic.x86_64.exe)

[stinman]

I will do this exactly as you stated and get back.You did see the snips I sent here, I don't know if the pipe buf is this- pipebuf.exe 41984 10. 1. 2009, but it is the one from his last update on 9-6-2010, but this is what I done last time.I will re-do it now and get back.Thanks for your help.

[LoRd_MuldeR]

I'm planning to put up a new package soon. Just busy with other projects and with real life stuff.

In the meantime: Replacing the x264 binaries manually should work just fine...

[stinman]

I'm planning to put up a new package soon. Just busy with other projects and with real life stuff.

In the meantime: Replacing the x264 binaries manually should work just fine...

I understand,your not getting paid or anything and you got things you must do.I always knew that a time would come,as it has.Why for me it will not read them.I just don't know.T really have followed the other guys instructions.

[kypec]

stinman, can you show us the content of your Simple Launcher directory? Start "cmd.exe" command line shell first. Then navigate to your Simple Launcher directory with cd command, for example:cd "C:\Program Files (x86)\AVTools\Simple x264 Launcher" When in that directory type dir command with its output redirected to some text file, like this:dir > mydir.txt Finally please post the contents of that file mydir.txt in this thread, preferrably embedded in the CODE tags.
I just can't believe that such simple process doesn't work for you...:eek:

EDIT:
I think I found the reason why the renamed x264 files fail for you ;)
After closer inspection of your screenshots I can see that you have configured your Windows Explorer to hide extensions of known file types.
This is a default setting and you can change it via Organize | Folder and search options | View tab > uncheck "Hide extensions for known file types".

http://i53.tinypic.com/30acoj4.jpg

You have clearly renamed the executable files to x264.exe.exe and x264_x64.exe.exe, just rename them again and leave out one redundant .exe part this time.:p

[stinman]

The thing you are failing to realize is,this tool does not install, it runs from a folder with all contents involved in that folder just like ripbot264 does,where ever it is.I chose to have mine in the Public documents folder,it works from there .The directory is this C:\Users\Public\Public Documents\Video Encoding tools\Simple x264 launcher. Last night I downloaded the new ripbot264 1.16.3.I copied both sets of x264 from that program's tools to this one and it worked.So now they are updated to r1732,but I don't know who's version Atak uses. I do know that Lord Mulder's, Komisars versions of x264 do not say x264.x86_64.exe they say x264.exe and x264_64.exe.
As far as the CMD,I couldn't do it with what you told me to do,I believe because it is not a installed program,installed to the program files.If I was real sharp with command line,I would just use the command line to encode with x264.:) I have Windows 7 Ultimate 64bit.
You can also get to the directory from the Libraries tab.This is what's in the directory folder,look at screen.
What do you mean by Start CMD.exe "command line shell first",I know about cmd and how to start it and with admin rights,but not command line shell first?

[stinman]

Finally got it to accept Komisars 1820 generic build,I did nothing different than before.It just worked this time.Thanks to you all for help!

[kypec]

What do you mean by Start CMD.exe "command line shell first",I know about cmd and how to start it and with admin rights,but not command line shell first?
Yes, by starting "cmd" I meant just what you did i.e. to run cmd.exe command line prompt where you can type all other operating system commands or launch other programs from (executables like .exe, .cmd, .bat).
No, I'm not failing to understand where or how did you install/unzipped Lord Mulder's Simple Launcher application. It doesn't really matter, the only thing important is that launcher.exe is looking for x264.exe & x264_x64.exe files which must be placed in the same directory as launcher.exe itself.
Did you read my notes below EDIT: in my previous post? I have clearly explained what was your problem -> HIDDEN FILE EXTENSIONS in your Windows Explorer window. When you was originally renaming x264.1804.generic.x86 to x264.exe you typed also the .exe extension explicitly but your Windows have appended also the original .exe there which lead to final filename being x264.exe.exe!
Finally got it to accept Komisars 1820 generic build,I did nothing different than before.It just worked this time.
You must have done something differently! I suppose you turned off HIDING EXTENSIONS FOR KNOWN FILE TYPES as I proposed and since that moment you can see full filenames properly and avoid such mistakes with doubled extensions when renaming or viewing directory contents.

[stinman]

I did do as you said,I just didn't come back and report everything I did.I all ready knew about the turning on and off file extensions.I never did name them with 2 .exe.exe at the end.I can say that the only thing I did different was to go back to the next release of x264,(can't remember which x264 release it was) after Lord Mulders Sept 6th and put it in the simple x264 launcher folder and it worked and then went to 1804 release and it also worked.I mean,not much to it but to take old out and put new in with the proper name.Everything is in the same folder so it should of worked.I'm glad it does now though!!

[LoRd_MuldeR]

Updated x264 binaries to r1834 (Komisar's builds) with FFmpgeSource v2.14.0.1.

[stinman]

Glad to see you back LoRd MuldeR,missed ya.I see a exe at the end of simple x264 launcher now.You changed it to a installed application now?

[kypec]

LM changed installer from ZIP/7Z to EXE back in September 2010 already. Anyway, that installer is actually just an unpacker, no registry or Windows configuration files are modified during the process. It just unpacks the files to (selectable) destination folder, that's all.

[LoRd_MuldeR]

Glad to see you back LoRd MuldeR,missed ya.I see a exe at the end of simple x264 launcher now.You changed it to a installed application now?

1. Didin't know I have been away :p

2. If you don't want to run the SFX (installer), then you can unzip the files manually with 7-Zip.

[me7]

I noticed that the GUI doesn't allow me to specify the --fps parameter myself. It says that it will do so itself if required. How safe is your method of detection and how can I know whether the framerate has been changed by the GUI?

[LoRd_MuldeR]

I noticed that the GUI doesn't allow me to specify the --fps parameter myself. It says that it will do so itself if required. How safe is your method of detection and how can I know whether the framerate has been changed by the GUI?

It will set the frame-rate reported by Avisynth/AVS2YUV. That is required, because when piping in the video as "raw" data, x264 can't know the FPS (and would always assume 25 fps, unless we specify explicitely). You can use AssumeFPS() or ChangeFPS() in your AVS script, if required.

[me7]

Since ffmpegsource is sometimes wrong about the framerate (current example: Watchmen Motion Comic from BluRay) and AssumeFPS() and ChangeFPS() have problems with non-integer values (they turn 24000/1001 into 23 AFAIK) I usually used x264 to correct the framerate. Maybe this warrants the option for the user to specify the framerate by himself?

[LoRd_MuldeR]

Since ffmpegsource is sometimes wrong about the framerate (current example: Watchmen Motion Comic from BluRay) and AssumeFPS() and ChangeFPS() have problems with non-integer values (they turn 24000/1001 into 23 AFAIK) I usually used x264 to correct the framerate. Maybe this warrants the option for the user to specify the framerate by himself?

Maybe the GUI could be changed in a future version to only insert "--fps <fps reported by AVS>" if the user has not specified "--fps" explicitely.

[Didée]

AssumeFPS() and ChangeFPS() have problems with non-integer values (they turn 24000/1001 into 23 AFAIK)
Sorry, but that's your fault, not that of those filters. :)
24000/1001 is [integer]/[integer], so the result is an integer, too. You must write at least one of those numbers as float, then the result will be float, too.

AssumeFPS( 24000/1001.0 ) # integer/float = [float]

or (preferred)

AssumeFPS( 24000, 1001 ) # numerator,denominator (division is handled internally)

[me7]

Sorry, but that's your fault, not that of those filters. :)
24000/1001 is [integer]/[integer], so the result is an integer, too. You must write at least one of those numbers as float, then the result will be float, too.

AssumeFPS( 24000/1001.0 ) # integer/float = [float]

or (preferred)

AssumeFPS( 24000, 1001 ) # numerator,denominator (division is handled internally)

I see, my bad. Thanks for the thorough explanation :)

[djesteban]

Hey LoRd_MuldeR,

Since we now have a 64bit build of Avisynth 2.5.8, are you planning to release a version of your x264 launcher that goes directly through avisynth x64, then to x264 x64??
Would be awesome!! I really like this simple GUI :)

Cheers

[LoRd_MuldeR]

Updated x264 binaries to r1900 (Komisar's builds) with FFmpgeSource v2.14.2.0.

[laserfan]

LM, I borrowed your command line for my own batchfile usage (I don't use yr GUI :o but thanks) and have been fiddling with W7's resmon.exe (Resource Monitor) which allows for Suspend of running tasks.

I notice that when your app Suspends, it does so for all of avs2yuv, x264_x64, and pipebuf. I've done (very limited) testing that suggests I can use resmon to suspend just the x264 process, and it seems to work.

Do you have experience/knowledge that suspending x264_x64 alone can get me into trouble? If you recommend suspending all 3, is there a sequence I should use to suspend them?

In case it's not clear, I don't know how these work together (only that they do, thanks again!). :)

[dansus]

Trying to force --fps 30000/1001 but the GUI says no..

Without this setting, output is ~ ffms [info]: 1440x1080i 0:1 @ 60030/1001 fps (vfr) ~ which is x2 the deinterlaced fps.

[LoRd_MuldeR]

LM, I borrowed your command line for my own batchfile usage (I don't use yr GUI :o but thanks) and have been fiddling with W7's resmon.exe (Resource Monitor) which allows for Suspend of running tasks.

I notice that when your app Suspends, it does so for all of avs2yuv, x264_x64, and pipebuf. I've done (very limited) testing that suggests I can use resmon to suspend just the x264 process, and it seems to work.

Do you have experience/knowledge that suspending x264_x64 alone can get me into trouble? If you recommend suspending all 3, is there a sequence I should use to suspend them?

In case it's not clear, I don't know how these work together (only that they do, thanks again!). :)

Sure, suspending only x264_x64.exe should work too.

As soon as x264 stops reading data from the pipe, the pipe buffer will run full very soon. Then the next write operation of avs2yuv.exe will block, which effectively suspends avs2yuv.exe too.

Finally when x264_64.exe resumes, it will start reading data from the pipe buffer again, so the OS can unblock/resume avs2yuv.exe at this moment and complete the pending write...


Trying to force --fps 30000/1001 but the GUI says no..

Without this setting, output is ~ ffms [info]: 1440x1080i 0:1 @ 60030/1001 fps (vfr) ~ which is x2 the deinterlaced fps.

This GUI was mainly designed to use 64-Bit x264 with 32-Bit Avisynth.

As this requires passing the input data to x264 through a pipe, the GUI has to set the "--fps" option. x264 can't know the FPS for input from STDIN, so it would always assume 25 fps.

Therefore the GUI will detect the proper frame rate from the input Avisynth script and then pass that frame rate to x264 via "--fps" option. Thus settings "--fps" manually isn't intended.

(However I see that is might be desirable, at least when using x264's "native" FFMS2 input. In Avisynth you could always use 'AssumeFPS()' instead)

[laserfan]

Sure, suspending only x264_x64.exe should work too...
Thank you kindly sir! Once again you've made a thorough explanation, and I appreciate it.
:thanks:

[stinman]

Thanks for the latest release!

[Lighto]

Any chance of adding a shutdown when done and batch/queue function?:p

[LoRd_MuldeR]

Any chance of adding a shutdown when done and batch/queue function?:p

Not currently planned.

[Temuthril]

I was low on free memory and wasn't really expecting the encoding to start, but is the following error message intended? After clicking yes (the left one) there was a malloc failed error message from x264.

http://dl.dropbox.com/u/13680560/launcherbug.jpg

x264 settings were preset veryslow, tune film, crf 21.

Avs file contents, if relevant:
LoadPlugin("C:\Plugins\rawsource_25_dll_20060728\rawsource.dll")
RawSource("G:\Video test\1080i25_stockholm_ter.yuv",1920,1080,"YV12")
Trim(1,250)
TDeint()
Crop(16,0,0,0)
FFT3DGPU(mode=1, precision=2)
Spline36Resize(1270,720)

[LoRd_MuldeR]

First of all: This error message does NOT originate from my GUI, but from Avisynth or the affected Avisynth Plugin.

Also the error message is quite clear: You obviously are out of memory! And therefore it's not surprising at all that the next malloc() in x264 will fail ;)

In contrast to many Avisynth plugins, all malloc's in x264 are checked. So if the malloc() in x264 fails, it will throw an error message...

(BTW: Limiting the memory used for caches by calling SetMemoryMax() in your AVS script might help to avoid 'out of memory' errors with Avsynth)

[Temuthril]

Thanks for the explanation, was just thinking if it could be the first case you mentioned.

[stinman]

will you be updating again to latest version of x264.I have tried like the last time to use komiars latest builds and no luck.I guess maybe ffmpeg or something else has to be updated also.

[LoRd_MuldeR]

will you be updating again to latest version of x264.I have tried like the last time to use komiars latest builds and no luck.I guess maybe ffmpeg or something else has to be updated also.

As explained earlier, you can update the 'x264.exe' or 'x264_x64.exe' file yourself. No change to the GUI will be required!

If you are using a build of x264 with FFMS2 (FFmpegSource) support enabled, then FFmpeg/libavcodec is already "built-in" in the EXE file.

And yes, Komisar's builds do have FFMS2 support enabled. Anyway, it's probably time to make an updated package, so here we go ;)

[dispatcher7007]

Testfile was a 1minute-extract of a BD which had the highest bitrate of the complete film.


Source: G:\Tests\hohe Komplexität\title00 (1)-134 (1) temp files\z nur für avs.avs
Preset: Medium
Tuning: None
Profile: High
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 1459 frames, 12.30 fps, 4124.29 kb/s
encoded 1459 frames, 12.34 fps, 4124.29 kb/s
encoded 1459 frames, 12.30 fps, 4124.29 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 1459 frames, 10.98 fps, 4124.29 kb/s
encoded 1459 frames, 11.32 fps, 4124.29 kb/s
encoded 1459 frames, 11.30 fps, 4124.29 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 1459 frames, 12.93 fps, 4124.29 kb/s
encoded 1459 frames, 11.40 fps, 4124.29 kb/s
encoded 1459 frames, 11.47 fps, 4124.29 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 1459 frames, 11.51 fps, 4124.29 kb/s
encoded 1459 frames, 13.01 fps, 4124.29 kb/s
encoded 1459 frames, 13.01 fps, 4124.29 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 1459 frames, 11.57 fps, 4124.29 kb/s
encoded 1459 frames, 13.09 fps, 4124.29 kb/s
encoded 1459 frames, 13.09 fps, 4124.29 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 1459 frames, 13.08 fps, 4124.29 kb/s
encoded 1459 frames, 13.09 fps, 4124.29 kb/s



The .avs was a script created by staxrip with all filters, but autocrop disabled. I haven't got used to writing avisynth-scripts manually, so this was the easiest way for me. I don't think it should have much of an impact on the results.

The script was:

LoadPlugin("E:\Software\DVD rippen\StaxRip\Applications\AviSynth plugins\ffms2\ffms2.dll")
FFVideoSource("G:\Tests\hohe Komplexität\title00 (1)-134 (1).mkv", cachefile="G:\Tests\hohe Komplexität\title00 (1)-134 (1) temp files\title00 (1)-134 (1).ffindex")
AssumeFPS(23.976)
Crop(0,0, -Width % 8,-Height % 8)
ConvertToYV12()
Crop(0,132,-0,-132)


I'm slightly disappointed about the 64bit performance, because I expected more than the 6,5% improvement.

Is it possible to speed it up further by having the complete process chain set up in 64 bit?

What parts are all needed for this? are ffdshow 64, avisynth 64 and x264 64 all, or did I miss anything?

[LoRd_MuldeR]

I'm slightly disappointed about the 64bit performance, because I expected more than the 6,5% improvement.

Is it possible to speed it up further by having the complete process chain set up in 64 bit?

What parts are all needed for this? are ffdshow 64, avisynth 64 and x264 64 all, or did I miss anything?

Essentially 64-Bit x264 is all you need. With its "built-in" FFMS2 support, x264 handles most input alone.

64-Bit Avisynth is required only, if you want to use Avisynth input with a 64-Bit build of x264 directly (i.e. not via avs2yuv).

64-Bit FFdshow would only be relevant, if you did use DirectShowSource() or DSS2() in your AVS script - under a 64-Bit Avisynth.

And of course with 64-Bit Avisynth all your Avisynth plug-in's must be 64-Bit. You can't use 32-Bit plug-in's with 64-Bit Avisyth.

[stinman]

yeaaa!! Thanks for update!!. It seems after the x264 codec gets a few updates ahead of your last update here, it will not recognize the newest Komisar's files.It always say's "x264_x64.exe not found in the directory". Maybe it's just my windows 7 ultimate, or me, but I can make it work a few updates ahead but not way ahead like the last one I tried r1900 to r2008 all from Komisar's because I figured it had to be this set of x264 because this is what you use.Sorry if I seem dumb to you LoRd_MuldeR,I'm not, I have followed the directions to the exact as laid out to me in this forum to do it.
I want to learn to use the command line for x264.I know basic in's and out of cmd. Could I look at the log files of simple x264 launcher and see the commands, then copy them to cmd? Thanks again for the update!!

[LoRd_MuldeR]

yeaaa!! Thanks for update!!. It seems after the x264 codec gets a few updates ahead of your last update here, it will not recognize the newest Komisar's files.

Definitely not ;)

I have no idea what was wrong, but you certainly can replace an older 'x264_x64.exe' with a newer version without modifying/updating the GUI program.

The GUI program would only need updates, if the x264 CLI syntax was changed in a way that breaks compatibility. But that did not happen...

[dispatcher7007]

what buffersize is it using, when you dont run the benchmark?