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

[rack04]

Totally different problem here:

how do I properly transcode a video-file that has this speciality:



Whatever I do...the result is a out of sync file.

Force film.

[Rodger]

care to elaborate?

[HaraldBluetooth]

When I try to download the latest update, it gives me:

"Oops! (404)
We can't find the page you're looking for. Check out our FAQ or forums for help. Or maybe you should try heading home. "

[twazerty]

When I try to download the latest update, it gives me:

"Oops! (404)
We can't find the page you're looking for. Check out our FAQ or forums for help. Or maybe you should try heading home. "

Can somebody give us a working link?

[rack04]

care to elaborate?

Your file appears to be film with 3:2 pulldown. Using DGDecNV you would need to use fieldop=1.

[LoRd_MuldeR]

When I try to download the latest update, it gives me:

"Oops! (404)
We can't find the page you're looking for. Check out our FAQ or forums for help. Or maybe you should try heading home. "

My Dropbox links have been disabled. Too much traffic they say. I don't know when they'll be back.

Will re-upload to another mirror soon...

[EDIT]

Here we go: http://www.mediafire.com/file/tqjoekjwmhm/x264_x64.2010-01-21.7z

[Rush_iam]

Here we go: http://www.mediafire.com/file/tqjoekjwmhm/x264_x64.2010-01-21.7z

I can't run 64-bit encoding on my Athlon II X2 CPU:
This program was not built to run on the processor in your system.
The allowed processors are: Intel(R) Core(TM) Duo processors and compatible Intel processors with supplemental Streaming SIMD Extensions 3 (SSSE3) instruction support

can you post Simple x264 Launcher that will not require SSSE3?

Thanks!

[LoRd_MuldeR]

I can't run 64-bit encoding on my Athlon II X2 CPU:


can you post Simple x264 Launcher that will not require SSSE3?

Thanks!

It's not an issue with my launcher, but with your build of x264 ;)

You must replace "x264_x64.exe" with a build that wasn't compiled with the Intel compiler and Intel-specific optimizations!

I'm including Komisar's "Core2" builds, but you can replace the build with whatever build you like...

You can try that one:
http://komisar.gin.by/old/1400/x264.1400kGIT.generic.x86_64.exe

[kypec]

LM, would you be so kind and post your comments on my small request (http://forum.doom9.org/showpost.php?p=1363584&postcount=299)?
TIA

[LoRd_MuldeR]

Done!

[kypec]

Done!
Much appreciated! :thanks:

[Motenai Yoda]

x264.nl/s build 1414 i7 920

script
MPEG2Source("C:\VTS_01_VOBID_001_CELLID_003_1.d2v", cpu=0,idct=3)
spline16resize(656,480)
removegrain(1,2,2)

Source: C:\Users\Casa\Desktop\VTS_01_VOBID_001_CELLID_003_1.avs
Preset: Fast
Tuning: Animation
Profile: High
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 17800 frames, 123.19 fps, 962.72 kb/s
encoded 17800 frames, 123.45 fps, 962.72 kb/s
encoded 17800 frames, 115.89 fps, 962.72 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 17800 frames, 129.93 fps, 962.72 kb/s
encoded 17800 frames, 130.88 fps, 962.72 kb/s
encoded 17800 frames, 131.85 fps, 962.72 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 17800 frames, 133.83 fps, 962.72 kb/s
encoded 17800 frames, 134.85 fps, 962.72 kb/s
encoded 17800 frames, 133.83 fps, 962.72 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 17800 frames, 134.85 fps, 962.72 kb/s
encoded 17800 frames, 135.88 fps, 962.72 kb/s
encoded 17800 frames, 134.85 fps, 962.72 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 17800 frames, 130.88 fps, 962.72 kb/s
encoded 17800 frames, 131.85 fps, 962.72 kb/s
encoded 17800 frames, 135.88 fps, 962.72 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 17800 frames, 134.85 fps, 962.72 kb/s
encoded 17800 frames, 133.83 fps, 962.72 kb/s
encoded 17800 frames, 134.85 fps, 962.72 kb/s

[LoRd_MuldeR]

Updated x264 to r1416 (Komisar's builds).

[egrimisu]

why are the executalbe that large? 6mb? any queue soon :) ?
Updated x264 to r1416 (Komisar's builds).

[XhmikosR]

They include ffms2+lavf input.

[Keiyakusha]

Is it possible to make sx264 GUI to run x264 without avs2yuv when input file is not avs script?

[rack04]

How does Simple x264 Launcher determine the number of frames from a avisynth script?

[MuLTiTaSK]

@rack04

--frames is used for x264 (http://forum.doom9.org/showpost.php?p=1354661&postcount=284)

[rack04]

@rack04

--frames is used for x264 (http://forum.doom9.org/showpost.php?p=1354661&postcount=284)

I understand that. What I was asking is how does the GUI determine the number of frames from the source, i.e. mediainfo, avisynth writefile, etc?

[MuLTiTaSK]

@rack04

thats actually something that i would like to know as-well;)

[LoRd_MuldeR]

I understand that. What I was asking is how does the GUI determine the number of frames from the source, i.e. mediainfo, avisynth writefile, etc?

avs2yuv does reveal that info. You just need to parse its STDOUT and capture the desired info :)

Is it possible to make sx264 GUI to run x264 without avs2yuv when input file is not avs script?

Possible indeed. And now that we have native FFMS2 input, it certainly would be a nice feature. However I'm too busy at the moment...

[buzzqw]

@Keiyakusha

(sorry for spam)

microx264 allow this
(using lavf/ffms2)

BHH

[kritip]

Windows 7 Home Premium
Dell XPS M1530 Laptop
Intel Mobile Core 2 T9300 @2.5GHz

Source: PAL DVD of Interview with a Vampire, black bars cropped mod16, no resize.

Crop(8,12,-8,-4)
trim(7000,7400)



Source: C:\RIPS\int vamp\MainMovie\INTERVIEW_WITH_A_VAMPIRE_PAL1\VIDEO_TS\tmp\k.avs
Preset: Veryslow
Tuning: Film
Profile: High
Params: --level 4 --ref 3 --bframes 3 --vbv-bufsize 25000 --vbv-maxrate 25000 --sar 16:11 --aud

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 401 frames, 4.69 fps, 1694.85 kb/s
encoded 401 frames, 4.75 fps, 1694.85 kb/s
encoded 401 frames, 4.82 fps, 1694.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 401 frames, 5.73 fps, 1694.85 kb/s
encoded 401 frames, 5.73 fps, 1694.85 kb/s
encoded 401 frames, 5.73 fps, 1694.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 401 frames, 5.65 fps, 1694.85 kb/s
encoded 401 frames, 5.73 fps, 1694.85 kb/s
encoded 401 frames, 5.73 fps, 1694.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 401 frames, 5.73 fps, 1694.85 kb/s
encoded 401 frames, 5.73 fps, 1694.85 kb/s
encoded 401 frames, 5.73 fps, 1694.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 401 frames, 5.65 fps, 1694.85 kb/s
encoded 401 frames, 5.65 fps, 1694.85 kb/s
encoded 401 frames, 5.65 fps, 1694.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 401 frames, 5.65 fps, 1694.85 kb/s
encoded 401 frames, 4.09 fps, 1694.85 kb/s
encoded 401 frames, 4.61 fps, 1694.85 kb/s


Nice improvment over 32bit x264. Could really do with a fater computer though :D


//EDIT

Just got x264 64 bit setup on the command line.

x264.exe r1416 from x264.nl
avisynth 2.5.8 64bit dll
dgdecode.dll 1.4.6 (couldn't find newer 64 bit version)

same clip and settings gave the following output. Note it's not bit identical though, so I may have messed up?


c:\RIPS\int vamp\MainMovie\INTERVIEW_WITH_A_VAMPIRE_PAL1\VIDEO_TS\tmp2>x26464.exe --preset veryslow --tune film --crf 18
--level 4 --ref 3 --bframes 3 --vbv-bufsize 25000 --vbv-maxrate 25000 --sar 16:11 --aud --output k.h264 k.av

avs [info]: 704x560p 16:11 @ 25/1 fps (cfr)
x264 [info]: using SAR=16/11
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
x264 [info]: profile High, level 4.0
x264 [info]: frame I:3 Avg QP:16.00 size: 32207
x264 [info]: frame P:122 Avg QP:17.60 size: 13658
x264 [info]: frame B:276 Avg QP:18.39 size: 5949
x264 [info]: consecutive B-frames: 0.3% 1.5% 61.1% 37.2%
x264 [info]: mb I I16..4: 9.7% 81.8% 8.5%
x264 [info]: mb P I16..4: 1.3% 10.1% 0.5% P16..4: 59.3% 21.5% 4.3% 0.1% 0.1% skip: 2.6%
x264 [info]: mb B I16..4: 0.1% 0.9% 0.0% B16..8: 40.3% 0.7% 1.5% direct:19.4% skip:37.1% L0:41.2% L1:45.6% BI:13.2%
x264 [info]: 8x8 transform intra:84.6% inter:53.7%
x264 [info]: direct mvs spatial:98.9% temporal:1.1%
x264 [info]: coded y,uvDC,uvAC intra: 87.6% 77.5% 47.1% inter: 36.3% 38.5% 2.1%
x264 [info]: i16 v,h,dc,p: 23% 8% 12% 58%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 7% 15% 9% 10% 12% 8% 13% 11%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18% 7% 5% 9% 13% 16% 10% 12% 10%
x264 [info]: Weighted P-Frames: Y:10.7%
x264 [info]: ref P L0: 54.8% 22.1% 8.4% 14.2% 0.5%
x264 [info]: ref B L0: 72.8% 27.2%
x264 [info]: kb/s:1698.15

encoded 401 frames, 5.81 fps, 1698.15 kb/s

[LoRd_MuldeR]

Updated x264 to r1442 (Komisar's builds).

[dstln]

Possible indeed. And now that we have native FFMS2 input, it certainly would be a nice feature. However I'm too busy at the moment...

Yes, I was thinking of this earlier. Would be great when you have the time.

[rack04]

Is it possible to make sx264 GUI to run x264 without avs2yuv when input file is not avs script?

These notes are probably a given:

If you're referring to 64-bit then the build will have to include 64-bit versions of ffmpeg and ffms2 and currently these input methods do not accept --nal-hrd <string> which may impact those who wish to encode to Blu-ray.

[Keiyakusha]

If you're referring to 64-bit then the build will have to include 64-bit versions of ffmpeg and ffms2 and currently these input methods do not accept --nal-hrd <string> which may impact those who wish to encode to Blu-ray.
x264 already contains ffms2 and/or lavc. There should be no problems with x64. Don't know anything about --nal-hrd but if currently it is possible to use it, then it should be also possible with proposed update.

[rack04]

x264 already contains ffms2 and/or lavc. There should be no problems with x64. Don't know anything about --nal-hrd but if currently it is possible to use it, then it should be also possible with proposed update.

What I was referring to is that x264 64-bit has to be compiled with 64-bit ffms and ffmpeg. AFAIK ffmpeg does not compile correctly in 64-bit due to fmpeg not properly following the win64 calling convention in its asm. nal-hrd does not currently work with x264 LAVF/FFMS input.

[Keiyakusha]

What I was referring to is that x264 64-bit has to be compiled with 64-bit ffms and ffmpeg. AFAIK ffmpeg does not compile correctly in 64-bit due to fmpeg not properly following the win64 calling convention in its asm. nal-hrd does not currently work with x264 LAVF/FFMS input.

Well, I don't know anything about this but current avs input should not be affected. If it works now, why it should not work after adding this new feature? Those who wants nal-hrd maybe will need to use another x264 build, but not a big problem I think.
Anyway thats up to LoRd_MuldeR.

[LoRd_MuldeR]

What I was referring to is that x264 64-bit has to be compiled with 64-bit ffms and ffmpeg. AFAIK ffmpeg does not compile correctly in 64-bit due to fmpeg not properly following the win64 calling convention in its asm. nal-hrd does not currently work with x264 LAVF/FFMS input.

We do have working 64-Bit builds of x264 with LAVF/FFMS enabled. This applies to the Komisar builds I have included ;)

There also are working 64-Bit Builds of MPlayer for Windows available. Conclusion: It definitely is possible to compile libavcodec/libavformat for Win64. But don't ask me how ^^

NAL-HRD will be working correctly again in latest x264 as soon as the patch has been updated or NAL-HRD is committed officially, I guess...

[rack04]

We do have working 64-Bit builds of x264 with LAVF/FFMS enabled. This applies to the Komisar builds I have included ;)

There also are working 64-Bit Builds of MPlayer for Windows available. Conclusion: It definitely is possible to compile libavcodec/libavformat for Win64. But don't ask me how ^^

NAL-HRD will be working correctly again in latest x264 as soon as the patch has been updated or NAL-HRD is committed officially, I guess...

Understood. I was just passing along information I received from Dark Shikari when I inquired about building 64-bit ffmpeg.

[Rodger]

A missing NAL-HRD Patch should be clearly stated with a realease since it has this huge impact on stand alone playability.

So I would sugguest to always keep a compatible release up, as long as the latest is the compatible one.

So I´m definitely waiting for a fitting release.

[LoRd_MuldeR]

A missing NAL-HRD Patch should be clearly stated with a realease since it has this huge impact on stand alone playability.

IMHO the presence (not the absence) of unofficial patches should be indicated. Also NAL-HRD is relevant for BluRay only.

Last but not least you can easily replace the x264.exe/x264_x64.exe with a different build...

[Rodger]

Just a different point of view, which I acknowledge but don´t accept.
I think since the playability outside of a computer is a MUST HAVE there is no way I would EVER give that up.
Times like the beginning of DivX when you only were able to play those files on a computer should definitely be over.
NAL-HRD should´nt be a patch. It´s something I still don´t get why it´s not implemented into the core of x264.

Of course I can replace it with a differenz build. But where is the need for me to update my files of "simple X264 launcher"?
Any striking improvement with the gui?
But I´ve already read that Rev.1442 is a huge step forward...sadly without SA compatibility.

[rack04]

But I´ve already read that Rev.1442 is a huge step forward...sadly without SA compatibility.

NAL HRD still works with avs input. So your argument about SA compatibility is incorrect.

[LoRd_MuldeR]

NAL-HRD should´nt be a patch. It´s something I still don´t get why it´s not implemented into the core of x264.

So did you do anything to help the development of x264 or NAL-HRD in particular ??? :sly:

NAL-HRD is still under development and the patch will be committed to the official x264 git repository once the developers are satisfied with it.

Until then you should be happy that there are people who actively work on NAL-HRD support, instead of complaining :rolleyes:

Of course I can replace it with a differenz build. But where is the need for me to update my files of "simple X264 launcher"?
Any striking improvement with the gui?
But I´ve already read that Rev.1442 is a huge step forward...sadly without SA compatibility.

You really should show a more positive attitude. So far I only see you complaining about software that was provided to you for free :mad:

But to answer your question: Nope, there were no changes to the GUI lately. Only the x264 builds have been updated to the latest revision.

[Rodger]

I´ve read that is currently broken?!
....And I just found out that you found out that there has been a change in the use of the string....

/EDIT:
No I didn´t?! But that shouldn´t prevent me on having a right to have my own opinion.
It´s proven to work properly. So I see no reason not to implement it.

[rack04]

I´ve read that is currently broken?!

Have YOU tested it? Does it work for YOU?

....And I just found out that you found out that there has been a change in the use of the string....

....And?

[Rodger]

If I got it right...instead of
--level 4.1 --nf --direct auto --vbv-bufsize 28000 --vbv-maxrate 28000 --subme 5 --no-mbtree --trellis 0 --me umh --nal-hrd --sar 1:1
with that new string I´ll have to say
--level 4.1 --nf --direct auto --subme 5 --no-mbtree --trellis 0 --me umh --nal-hrd 16000,16000 --sar 1:1

right?

[Rodger]

Have YOU tested it? Does it work for YOU?



....And?

IT WORKS!
Used the following build by komisar: http://komisar.gin.by/old/1442/x264.1442kGIT.core2.x86_64.exe

Played on...
...Samsung BD-P2500 Software V2.5
...Pioneer BDP-LX52 Software V3.41

/EDIT:
Damn they did a fantastic job. Faster, sharper and very keen on saving bitrate ;)

[rack04]

--nal-hrd 16000,16000

What is 16000,16000 for? According to full help:

--nal-hrd <string> Signal HRD information (needed e.g. for Blu-Ray compliance)
- vbr, cbr. (requires vbv-bufsize; cbr-hrd not allowed in .mp4)

So for Blu-ray compliance you would set --nal-hrd vbr. You would need to set --vbv-bufsize and --vbv-maxrate separately.

[Rodger]

I understood the new string as a replacement for the other two options.

Hmmh....I´m a bit confused....read the help myself now.

I now would have guessed to repeat the vbv-buffersize.
But when I read your hint....I now would set the used bitrate.

[anubhavrocker]

Is it not possible to make it completely use the command line function only, i mean a way in which it will not use the predefined settings values from mode, quant, b/w etc.

[Rodger]

That would´nt make it the "Simple" x264 Launcher.

[kool]

Hi, My goal is to achieve the highest quality, I don't know that there is something I don't know about or there is problem with GUI, I have been testing 1080p from Blu-Ray source the GUI is hanging I get text that
Analyzing source file:
Preparing for encode please wait... and this been toke me 6 hrs :)

I'm using very simple script
Resize
Tweak
Sharp

GUI setting
-- [Detailed Report] --

Source: C:\Users\kool\Desktop\test\test.avs
Output: C:\Users\kool\Desktop\test\test.mkv
Preset: Placebo
Tuning: Film
Profile: High
Params: (Empty)

Analyzing source file:

Aborted: Process was terminated prematurely!

[LoRd_MuldeR]

Hi, My goal is to achieve the highest quality, I don't know that there is something I don't know about or there is problem with GUI, I have been testing 1080p from Blu-Ray source the GUI is hanging I get text that
Analyzing source file:
Preparing for encode please wait... and this been toke me 6 hrs :)

I'm using very simple script
Resize
Tweak
Sharp

GUI setting
-- [Detailed Report] --

Source: C:\Users\kool\Desktop\test\test.avs
Output: C:\Users\kool\Desktop\test\test.mkv
Preset: Placebo
Tuning: Film
Profile: High
Params: (Empty)

Analyzing source file:

Aborted: Process was terminated prematurely!

There's probably something wrong with your input chain :rolleyes:

[LoRd_MuldeR]

Updated x264 to r1462 (Komisar's builds).

[Magix_995]

How to remove custom x264 lines from GUI ?

[LoRd_MuldeR]

How to remove custom x264 lines from GUI ?

:confused:

[Keiyakusha]

C:\Users\username\AppData\Roaming\x264_x64.ini -> history_1, history_2, history_3... this maybe?