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

[LoRd_MuldeR]

Why would you want to delete the history? The x264 launcher will only keep the eight most recent entries. And if you don't want to pick an entry from the history, simply don't do it...

[LoRd_MuldeR]

Updated x264 to r1471 (Komisar's builds). Support for FFMS2 input not yet, but under construction...

[LoRd_MuldeR]

Support for FFMS2 input has been added. Not tested very well yet. Feedback welcome :)

[LoRd_MuldeR]

Support for FFMS2 input has been added. Not tested very well yet. Feedback welcome :)

Minor update. Index files (created by FFMS2) will now be kept, so re-indexing the same source file can be avoided. Especially useful for 2-Pass encodes.

[egrimisu]

Minor update. Index files (created by FFMS2) will now be kept, so re-indexing the same source file can be avoided. Especially useful for 2-Pass encodes.

sorry for the dumb question, what is ffms2 and in what way can it help lets say end user. thanks.

[DarkZell666]

sorry for the dumb question, what is ffms2 and in what way can it help lets say end user. thanks.

Official infos :

http://doom10.org/index.php?topic=25.0
http://code.google.com/p/ffmpegsource

and the x264 commit that added ffms2 input support :

http://git.videolan.org/gitweb.cgi?p=x264.git;a=commit;h=380a201e8e8ba5a13022aeeeaf4b7501e1c79279

[LoRd_MuldeR]

sorry for the dumb question, what is ffms2 and in what way can it help lets say end user. thanks.

FFMS2 refers to "FFmpegSource2". It's a library that builds on top of libavcodec/libavformat from FFmpeg project. And it allows x264 to read all kinds of files (MPEG-PS, MPEG-TS, AVI, MKV, MP4, etc) directly and without Avisynth. Also no additional "Codecs" are needed, because all decoders/splitters are "built-in" already. For example the following is now possible:

x264.exe --crf 22 --output "C:\My Encodes\Output.mkv" "C:\My TV Captures\Some Movie.ts"

[deets]

another dumb question :) it cant resize or anything can it? only outputs the same as the input? so my 1440x1080 clips would still need avisynth to resize down to 720p?

[LoRd_MuldeR]

another dumb question :) it cant resize or anything can it? only outputs the same as the input? so my 1440x1080 clips would still need avisynth to resize down to 720p?

AFAIK you cannot apply any filters with FFMS2 input. At least not yet. It was discussed, but not added until now - or did I miss it?

So if you need to apply filters and if you can live without VFR (variable framerate) support, then Avisynth is still the way to go...

[DarkZell666]

AFAIK you cannot apply any filters with FFMS2 input. At least not yet. It was discussed, but not added until now - or did I miss it?

So if you need to apply filters and if you can live without VFR (variable framerate) support, then Avisynth is still the way to go...

Here's what the devs are up to right now : http://doom10.org/index.php?topic=177.0 ;)

[deets]

fascinating, thanks

[echohead]

this might be a pointless idea, but is there any chance you could add support for 2-pass encoding where the first pass uses crf?

[LoRd_MuldeR]

this might be a pointless idea, but is there any chance you could add support for 2-pass encoding where the first pass uses crf?

What would be the purpose of that ???

[buzzqw]

encode at bitrate given/obtained by a crf encoding
microx264 allow this, could be useful mainly for testing purpose
just do a 1 pass crf , then do a 2nd pass using the average bitrate from first pass

BHH

[LoRd_MuldeR]

encode at bitrate given/obtained by a crf encoding
microx264 allow this, could be useful mainly for testing purpose
just do a 1 pass crf , then do a 2nd pass using the average bitrate from first pass

BHH

Doing a 2-Pass encode at bitrate X and doing a CRF encode at the same bitrate X will give (almost) identical results - the only difference is that with CRF you don't know X in advance. The difference in quality will be so small, that you probably wouldn't be able to spot it. So if you need to hit a specific bitrate, then do a "plain" 2-Pass encode. If you want to preserve a certain level of quality (roughly), then use CRF mode at your favourite CRF value. First doing a CRF pass and then doing a second pass (2-Pass mode) based on the bitrate/stats from the CRF pass won't improve quality over the initial CRF pass. Since this GUI was written for simplicity and since it certainly doesn't try to be a "swiss army knife" for x264, I won't add an automated method for such "placebo" features. There is no real use for it (at least none has been presented to me) and it potentially confused people. Plus it unnecessarily complicates the code...

[buzzqw]

you just got a more bitrate variance with the insurance of "fixed" crf value

again, not for daily use, but fun for testing :)

BHH

[LoRd_MuldeR]

again, not for daily use, but fun for testing :)

And thus nothing we need in a "Keep It Simple Stupid" GUI :p

[buzzqw]

yea KISS rule! :D

BHH

[LoRd_MuldeR]

Updated x264 to r1510 (Komisar's builds). Now with full "BluRay" (NAL-HRD) support.

Please see the commit message for detailed info on how to produce BluRay-compliant streams:
http://git.videolan.org/gitweb.cgi?p=x264.git;a=commit;h=c6de86497cdd7b7f3cce7d8a95d723c7d0c9f505

[archaeo]

x264 [warning]: input appears to be interlaced, enabling interlaced mode.
If you want otherwise, use --no-interlaced
x264 [warning]: interlace + weightp is not implemented

Program indicated that it is enabling interlaced mode, but then warning states that it is not implemented. (It wasn't)
Why did it disable? How do I make sure it is enabled when interlaced is found?

thanks

[LoRd_MuldeR]

Program indicates that it is enabling interlaced mode, but then warning states that it is not implemented. (It wasn't)
Why did it disable? How do I make sure it is enabled when interlaced is found?

thanks

(1) If your source is interlaced, but you don't encode it as interlaced (i.e. "--interlaced" wasn't set), then x264 will switch to interlaced mode for you. And for good reason ;)
(2) If you really want to enforce progressive encoding of interlaced source, then you can specify "--no-interlaced". Probably not a good idea though!
(3) The warning about "interlace + weightp is not implemented" means that x264 cannot use both, weight-p and interlaced mode, at the same time. It is not implemented (yet).
(4) It is 100% safe to ignore the warning. Basically it just informs you that interlaced mode is used, and thus weight-p (weighted p-prediction) is not used.

[archaeo]

OK, thanks for the explanation...
By the way, I really like the program - it's simplicity and light footprint is something that works very well for me
:thanks:

[archaeo]

I had another question:
Is there a way to load two m2ts files and merge during encode?
At this point I'm merging them in tsmuxer and loading that file into x264. Could save a step, but not at the risk of complicating a nice program.

[LoRd_MuldeR]

I had another question:
Is there a way to load two m2ts files and merge during encode?
At this point I'm merging them in tsmuxer and loading that file into x264. Could save a step, but not at the risk of complicating a nice program.

Not directly. But if you write a custom Avisynth script, it's easy to do:

a = FFmpegSource("C:\Some Folder\File1.m2ts")
b = FFmpegSource("C:\Some Folder\File2.m2ts")
c = FFmpegSource("C:\Some Folder\File3.m2ts")
return a + b +c

Save that as "MySource.avs" and throw it on x264 ;)

[Vlarol]

1. Twelve Monkeys 1920x1040
2. Core i7 960@4.0GHz (HT disabled in BIOS)
3. Windows 7 Ultimate x64
4. Encoding with --crf 20.0

Medium preset

Source: D:\_FILM\Twelve Monkeys\Test.avs
Preset: Medium
Tuning: Film
Profile: High
Params: --sar 1:1

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 1000 frames, 11.66 fps, 9178.00 kb/s
encoded 1000 frames, 11.65 fps, 9178.00 kb/s
encoded 1000 frames, 11.66 fps, 9178.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 1000 frames, 12.35 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 1000 frames, 12.20 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 1000 frames, 12.20 fps, 9178.00 kb/s
encoded 1000 frames, 12.20 fps, 9178.00 kb/s
encoded 1000 frames, 12.20 fps, 9178.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 1000 frames, 12.35 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 1000 frames, 12.20 fps, 9178.00 kb/s
encoded 1000 frames, 12.35 fps, 9178.00 kb/s
encoded 1000 frames, 12.20 fps, 9178.00 kb/s


Slower preset

Source: D:\_FILM\Twelve Monkeys\Test.avs
Preset: Slower
Tuning: Film
Profile: High
Params: --sar 1:1

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 1000 frames, 3.62 fps, 9160.56 kb/s
encoded 1000 frames, 3.61 fps, 9160.56 kb/s
encoded 1000 frames, 3.62 fps, 9160.56 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 1000 frames, 4.12 fps, 9160.56 kb/s
encoded 1000 frames, 4.08 fps, 9160.56 kb/s
encoded 1000 frames, 4.10 fps, 9160.56 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 1000 frames, 4.12 fps, 9160.56 kb/s
encoded 1000 frames, 4.15 fps, 9160.56 kb/s
encoded 1000 frames, 4.22 fps, 9160.56 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 1000 frames, 4.22 fps, 9160.56 kb/s
encoded 1000 frames, 4.20 fps, 9160.56 kb/s
encoded 1000 frames, 4.20 fps, 9160.56 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 1000 frames, 4.18 fps, 9160.56 kb/s
encoded 1000 frames, 4.18 fps, 9160.56 kb/s
encoded 1000 frames, 4.17 fps, 9160.56 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 1000 frames, 4.17 fps, 9160.56 kb/s
encoded 1000 frames, 4.20 fps, 9160.56 kb/s
encoded 1000 frames, 4.15 fps, 9160.56 kb/s

[mkv]

thx a bunch

[Rodger]

Hi there....how can I fix this:

When I feed the launcher with this avs-script:

AviSource("a.avi")
Lanczos4Resize(720,576)

It´s stuck at: "Preparing source for encode, please wait"

When I remove the resize-filter from the script...it does work properly.

Any ideas?

[LoRd_MuldeR]

Hi there....how can I fix this:

When I feed the launcher with this avs-script:

It´s stuck at: "Preparing source for encode, please wait"

When I remove the resize-filter from the script...it does work properly.

Any ideas?

Sounds like an Avisynth issue. Maybe an x264 issue. Most-likely not related to my GUI...

[Rodger]

But that script worked with megui, I can remember.

[LoRd_MuldeR]

But that script worked with megui, I can remember.

No matter what GUI front-end you use, your Avisynth script will always be handled by Avisynth, i.e. the GUI doesn't make a difference here.

Well, the only difference between MeGUI and my simple x264 launcher is that my launcher uses avs2yuv.exe instead of passing the script to x264.exe directly.

Try something like avs2yuv.exe "C:\Temp\Your Script.avs" -o "C:\Temp\Output.y4m" with your script and see what happens...

[Rodger]

Well...I guess I have to tell you, that you´re wrong!

I does work INSTANDLY within Megui.
Just updated it to the latest build and works like a charm with that little script.

/EDIT: Oversaw your hint at first.

It seems it is reasoned by avs2yuv. Since I get an error message like: "doesn´t look like an avisynth script". The same unchanged avs-file that CURRENTLY works within megui.

Here is the full script for reference:
#LoadCplugin("C:\Program Files (x86)\megui\tools\yadif\yadif.dll")
#Loadplugin("C:\Program Files (x86)\AviSynth 2.5\plugins\DGDecodeNV.dll")
#DGSource("KNICK.dgi", deinterlace=1)
#DGSource("PLATSCH.dgi", deinterlace=1, resize_w=720, resize_h=576)
#DGSource("BLUBB.dgi", deinterlace=1)
#yadif(mode=0,order=-1,opt=-1)
#LeakKernelDeint(order=0)
#Crop(0,72,-0,-72)
#AddBorders(0,16,0,16)
AviSource("a.avi")
Lanczos4Resize(720,576)

[LoRd_MuldeR]

Well...I guess I have to tell you, that you´re wrong!

What I told you are simple facts.

It seems it is reasoned by avs2yuv. Since I get an error message like: "doesn´t look like an avisynth script". The same unchanged avs-file that CURRENTLY works within megui.

If the identical script is accepted by x264.exe, but rejected by avs2yuv.exe, this would indicate a potential bug in avs2yuv.

However you should try to track down the issue by reducing the script as much as possible. For example: Remove all the unneeded lines that are commented out.

Then try removing LanczosResize. If that doesn't make a difference, try a different source filter (i.e. FFVideoSource instead of AVISource).

(BTW: What version of Avisynth do you have installed ???)

EDIT:

And try replacing "a.avi" with the fully qualified path to your input file (such as "C:\Some Folder\a.avi"), just to be sure.

[Rodger]

AVISynth V2.58

Well....As I already said....it´s not related to the disabled lines.
As soon as I disable the lancos4resize line the script works.

You made a good sugguestion! I´ll try to change it "simple" lancosresize. But of course I wanted to use lanczos4resize because of the better upsizing.

/EDIT: Nah...doesn´t work too. Seems avs2yuv doesn´t like the resize filters of avisynth.

[LoRd_MuldeR]

You made a good sugguestion! I´ll try to change it "simple" lancosresize. But of course I wanted to use lanczos4resize because of the better upsizing.

Same issue with any resizer (e.g. BiCubicResize, Spline36Resize or PointResize), or is it just Lanczos4Resize ???

[Rodger]

I think more simple than "LanczosResize" isn´t neccesary to try.

[Rodger]

For all who can use it.

Here is a new Version of my "Excel-Bitrate-Calc".
Added new Media-Types and optimized the settings for newer revisions of x264 since I experienced x264 builds smaller files.

Still comments or Infos are welcome on this one.

[LoRd_MuldeR]

Updated x264 to r1564 (Komisar's builds).

[kypec]

Another small request LM if I may...
After the encoding process completed there is output window shown with report details which is fine of course.
When CRF was used (1-pass method in general probably) there is only one option presented for right-click: Copy to clipboard.
This is also good and I like it this way because frankly, what other actions could anyone want to do with final report, isn't it?
However, when 2-pass encode completes, the window has different right-click menu:

http://i43.tinypic.com/6htbm0.jpg

IMHO it's rather counter-productive this way because I need to make two clicks now to get the contents copied into clipboard (first Select all, then Copy).
Could this menu be replaced to be identical with CRF style report, please?

[LoRd_MuldeR]

Another small request LM if I may...
After the encoding process completed there is output window shown with report details which is fine of course.
When CRF was used (1-pass method in general probably) there is only one option presented for right-click: Copy to clipboard.
This is also good and I like it this way because frankly, what other actions could anyone want to do with final report, isn't it?
However, when 2-pass encode completes, the window has different right-click menu:

http://i43.tinypic.com/6htbm0.jpg

IMHO it's rather counter-productive this way because I need to make two clicks now to get the contents copied into clipboard (first Select all, then Copy).
Could this menu be replaced to be identical with CRF style report, please?

The context menu in the "report" window (as opposed to the "status" window) simply is the default one. In the "status" window I have implemented a custom one.

I can use the my custom context menu in the "report" window easily, if you like. But probably not before Sunday...

[kypec]

:thanks: and take your time! It's not a critical bug after all :p

[me7]

A great tool. Saves me some stupid grunt work I'd have to endure without it.
Thanks.

[CpT]

Nice tool.

http://vizmu.com/images/264-bench.jpg

Win7 32bit
Intel 980x Hyperthreading = on /12 threads.
Currently clocked at 4.2Ghz.
http://valid.canardpc.com/show_oc.php?id=1178119

I have to rebuild my 64bit raid array, it died on me uggg... When the drives come in stock I'll run it via 64bit win7.

If you toss in a auto resizer and NeroAac audio handling I would use this as my main encoder!

Source: C:\Chosen.mov
Output: C:\Output.mp4
Preset: Veryslow
Tuning: Film
Profile: High
Params: --keyint 750

x264 0.94.1583M 7608d73
built on May 9 2010, gcc: 4.4.4 (x86.core2.Komisar)
Revision: 1583

Commandline for x264:
C:\x264_x64.2010-04-25\x264.exe --preset veryslow --tune film --crf 22.0 --keyint 750 --output C:\Output.mp4 --demuxer ffms --index C:\Users\980\AppData\Local\Temp\~14FC3617328D3588A3CE6235F8E31A5F1AC64986.x264-index C:\Output.mp4

ffms [info]: 720x320p 1:1 @ 24/1 fps (vfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
x264 [info]: profile High, level 3.1
x264 [info]: frame I:11 Avg QP:22.46 size: 18588
x264 [info]: frame P:305 Avg QP:25.17 size: 4697
x264 [info]: frame B:479 Avg QP:26.67 size: 2225
x264 [info]: consecutive B-frames: 15.3% 7.4% 9.2% 64.3% 3.8% 0.0% 0.0% 0.0% 0.0%
x264 [info]: mb I I16..4: 22.7% 58.4% 18.9%
x264 [info]: mb P I16..4: 14.7% 13.6% 4.5% P16..4: 21.9% 8.8% 1.6% 0.1% 0.0% skip:34.7%
x264 [info]: mb B I16..4: 2.3% 2.3% 0.4% B16..8: 31.3% 8.2% 1.6% direct: 6.3% skip:47.6% L0:41.7% L1:46.7% BI:11.6%
x264 [info]: 8x8 transform intra:43.5% inter:81.2%
x264 [info]: direct mvs spatial:97.9% temporal:2.1%
x264 [info]: coded y,uvDC,uvAC intra: 42.6% 50.0% 15.7% inter: 15.0% 16.9% 1.4%
x264 [info]: i16 v,h,dc,p: 42% 33% 7% 18%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 10% 17% 13% 7% 9% 9% 12% 9% 14%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 12% 17% 6% 7% 11% 10% 12% 9% 16%
x264 [info]: i8c dc,h,v,p: 44% 33% 13% 10%
x264 [info]: Weighted P-Frames: Y:23.6%
x264 [info]: ref P L0: 57.5% 13.2% 16.5% 5.5% 2.3% 1.2% 0.9% 0.5% 0.4% 0.3% 0.8% 0.3% 0.2% 0.1% 0.2% 0.1%
x264 [info]: ref B L0: 87.5% 6.8% 2.3% 0.8% 0.5% 0.4% 0.3% 0.2% 0.2% 0.2% 0.1% 0.2% 0.3% 0.1% 0.1%
x264 [info]: ref B L1: 96.7% 3.3%
x264 [info]: kb/s:652.76
encoded 795 frames, 42.76 fps, 652.93 kb/s

[LoRd_MuldeR]

If you toss in a auto resizer and NeroAac audio handling I would use this as my main encoder!

This is a x264 GUI, so can't offer any functionality that isn't supported by x264 ;)

Audio encoding support is on the "to do" list of x264, as far as I know. The same goes for video filters (e.g. resize).

Until then you'll have to use Avisynth input and do the resize in your AVS script...

[sebazvideo]

Lord Mulder, is there a way to set your program to make x264 to run in different priority modes, such as Low if I need to do other stuff while I'm encoding? Is that saved in a preference file or in the registry somewhere?

[livache]

Lord Mulder, is there a way to set your program to make x264 to run in different priority modes, such as Low if I need to do other stuff while I'm encoding? Is that saved in a preference file or in the registry somewhere?

Why would you need that? It currently starts x264 on below normal priority, which is enough to not slow down too much the processes that run on normal priority. You can even play games with no stuttering while x264 runs on below normal. If you really have a fixation with this, you can always use task manager to lower x264 priority to Low, but I find it pointless.

[LoRd_MuldeR]

Why would you need that? It currently starts x264 on below normal priority, which is enough to not slow down too much the processes that run on normal priority. You can even play games with no stuttering while x264 runs on below normal. If you really have a fixation with this, you can always use task manager to lower x264 priority to Low, but I find it pointless.

I agree.

[deets]

I agree.

I like the choice as i often leave the pc unattended for a long time, ie over night and want the confidence if my anti virus starts a search or whatever, x264 will always run at full speed.

ripbot has the option and changing it in the task bar is pain if it can be done simpler in software :)

[sebazvideo]

Why would you need that? It currently starts x264 on below normal priority, which is enough to not slow down too much the processes that run on normal priority. You can even play games with no stuttering while x264 runs on below normal. If you really have a fixation with this, you can always use task manager to lower x264 priority to Low, but I find it pointless.

I notice a difference when encoding between using below normal and low priority. Yes, I can change it from Task Manager, but it would be easier to change it from the program with a drop down list like in MeGUI, and also like with MeGUI, it would be nice to be able to set the default priority.

[LoRd_MuldeR]

I notice a difference when encoding between using below normal and low priority. Yes, I can change it from Task Manager, but it would be easier to change it from the program with a drop down list like in MeGUI, and also like with MeGUI, it would be nice to be able to set the default priority.

I really want to keep the GUI minimalistic.

And I assume 99% of all users will be happy with x264 running at below normal priority, as this way x264 will neither slow down other "foreground" applications nor will "background" tasks slow down x264.

Anyway, you can change the default priority by adjusting one single line of source code, if you really need to ;)

Process.Priority := ppBelowNormal;

(That's in the constructor of TEncode in "Unit_Encode.pas")

[Kuningas]

Thank you for this wonderful tool ) It's really make my life easier )
Just one question. I want to use crf + pass2 mode. But launcher rejects "--pass 1" parameter in crf mode. So no .stats I receive.
Could you fix it or what am I doing wrong?