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

[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]

Originally Posted by 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.

You must have done something wrong. Please follow my step-by-step instructions below and it will work:

1. 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

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

[komisar]

64-bit executable r1804

[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]

Originally Posted by 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...

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...

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".



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.

[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]

Originally Posted by stinman

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!

Originally Posted by stinman

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]

Originally Posted by 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?

1. Didin't know I have been away

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]

Originally Posted by 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?

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]

Originally Posted by 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?

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]

Originally Posted by me7

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)