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

[JoeH]

Just a note to thank you for this tool. The interface is nice and I love being able to use the 64-bit for that extra bit of speed! :thanks:

One feature I'd love to see in future editions is the ability to do a 2-pass encode.

[LoRd_MuldeR]

One feature I'd love to see in future editions is the ability to do a 2-pass encode.

Automated 2-Pass already is implemented. Maybe you want batch processing?

[JoeH]

Automated 2-Pass already is implemented. Maybe you want batch processing?

Oooooooooooops! I actually originally wanted to do the the automated two pass with the benchmark and saw it wasn't yet implemented and just figured I couldn't do a simple encode either. But it works great. Batch processing would always be come in handy occasionaly but isn't as essential for me.

Honestly one thing I was thinking would be nice to see that I've never seen in any X264 GUI is some sort of a checkbox to activate / require the different options necessary to make an encoding compatible with a Blu-ray Standalone. I know for example that the --nad-hd (or whatever it's called) needs to be activated, but then there are a couple other things as well like max bitrate and such that are recommended / required.

I always used the MeGUI options for Standalone, but now that those presets are not working properly it is something I need to look into.

[LoRd_MuldeR]

Updated x264 to r1360 (Komisar's builds) and fixed one typo.

[XadoX]

Oops! (404). Can not download the file.

[LoRd_MuldeR]

Oops! (404). Can not download the file.

DropBox has disabled public downloads for my account. Too much traffic :rolleyes:

Will upload to another mirror, once I get back home...

[EDIT]

Re-uploaded. The download link in the first post has been updated accordingly.

[egrimisu]

avisource work jsut great with megui, i believe there is nothing wrong with it

my script look like this:
DGDecode_mpeg2source("d:\misu\nana22\VTS_01_1.d2v")
source1=DGDecode_mpeg2source("d:\misu\nana22\VTS_01_1.d2v").trim(0,38011)
source2=AviSource("D:\Misu\nana22\hfyu_1.avi")
a=source1.animeivtc(mode=1,aa=0,mt=true).assumefps(30000,1001)
b=source2
a+b

Probaply an issue with Avisynth/AVISource or (more liekly) the result of a borked VFW Codec. Try FFmpegSource2 as a replacement for AVISource.

[LoRd_MuldeR]

avisource work jsut great with megui, i believe there is nothing wrong with it

my script look like this:
DGDecode_mpeg2source("d:\misu\nana22\VTS_01_1.d2v")
source1=DGDecode_mpeg2source("d:\misu\nana22\VTS_01_1.d2v").trim(0,38011)
source2=AviSource("D:\Misu\nana22\hfyu_1.avi")
a=source1.animeivtc(mode=1,aa=0,mt=true).assumefps(30000,1001)
b=source2
a+b

There really is no reason why AVISource should work only in MeGUI, but not in another GUI.

Given that you use the same version of Avisynth and the same source clip...

[Rodger]

I miss the call of the plugin itself in that script....may be the reason

[deets]

and odd situation, when i chose slower, my video stops after a few seconds. no encode error, it just freezes on the first few frame but the time carries on.

if i chose any lower preset, the video encodes just fine.

im using a script created by dgdecnv and a 1080i source from BBC HD.

just wondered if it could be anything obvious?

[LoRd_MuldeR]

What happens if you run x264 from the console with the exactly same command-line and the exactly same avisynth script?

[kool]

Thanks for this thread, I have few questions...

I moved to win 7 64bit for the first time, and i need help to get x264 work with Win 7 64bit. I usually use meGUI and some time RipBot. I still don't know if there is an other way to use x264 64bit work with 64bit OS.

guide me please if I need to use any other softs or avisynth 64bit.

Thanks in advance.

[LoRd_MuldeR]

You can use x264 on 64-Bit Windows just fine. Both, 32-Bit builds and 64-Bit builds of x264, will work perfectly fine. However the 64-Bit builds should give a nice speed boost!

But if you want to use 64-Bit x264, the you need 64-Bit Avisynth. Then all your Avisynth plugins must be 64-Bit too! And, if you use DirectShowSource() or AVISource(), all Codecs must be 64-Bit as well!

With my tool you can avoid this. It uses 64-Bit x264, but pipes the data in from a separate 32-Bit process. Hence you can continue using 32-Bit Avisynth/Plugins/Codecs, as you are used to...

[kool]

:o now I'm geting confuse, which way is recommended and stable to use avisynth 64bit or 32bit under 64bit OS?

if 64bit avisynth is stable under 64bit OS, could you please point me to link, to get avisynth 64bit and 64bit filters.

Thanks.

[LoRd_MuldeR]

:o now I'm geting confuse, which way is recommended and stable to use avisynth 64bit or 32bit under 64bit OS?

if 64bit avisynth is stable under 64bit OS, could you please point me to link, to get avisynth 64bit and 64bit filters.

Thanks.

There are no "official" builds of 64-Bit Avisynth, but you can find squid_80's builds here:
http://www.members.optusnet.com.au/squid_80/

Also you will find some 64-Bit plugins there. However you won't be able to use any 32-Bit Plugins with 64-Bit Avisynth, which is a limitation!

And as said before, you need 64-Bit Codecs, as 32-Bit Codecs won't work...

(BTW: Updated x264 to r1373. Using Komisar's builds)

[deets]

What happens if you run x264 from the console with the exactly same command-line and the exactly same avisynth script?

yeah same thing, weird. wonder why

[LoRd_MuldeR]

yeah same thing

Then it has absolutely nothing to with my GUI and this is the wrong place to complain...

[deets]

Then it has absolutely nothing to with my GUI and this is the wrong place to complain...

i wasn't complaining, just making a comment. and until we did the test, we didn't know if it was or not :)

maybe with your advanced knowledge you could have shed some light as to what options changed between presets to warrant a crash.

but i didnt expect you to devote any time to answering.

[kool]

Thanks alot LoRd_MuldeR for your help, Could you help me out, how to install Avisynth 64BiT, as there is no installer.
* Could you guide me, how to use your tool?
* can we use 32-Bit Plugins and 32bit avisynth under 64bit os? "at lose of some speed" just want to make sure.

[LoRd_MuldeR]

Thanks alot LoRd_MuldeR for your help, Could you help me out, how to install Avisynth 64BiT, as there is no installer.

Unzip.

* Could you guide me, how to use your tool?

Install 32-Bit Avisynth with the official installer - and then use the tool.

* can we use 32-Bit Plugins and 32bit avisynth under 64bit os? "at lose of some speed" just want to make sure.

Yes, of course! And there generally is no loss in speed! What I said is: 64-Bit x264 has some speed-up compared to 32-Bit x264.

It's not related to what Avisynth you use. However, as I said before, 64-Bit x264 requires 64-Bit Avisynth.

Or you use my tool (or a similar one), which allows you to use 64-Bit x264 with 32-Bit Avisynth by piping the data into x264 from a 32-Bit process.

That said, in theory, Avisynth plugins could gain some speed-up from 64-Bit too. But it depends on the individual plugin!

(Keep in mind that many Avisynth plugins don't even have a 64-Bit build available. So if you use 64-Bit Avisynth, the usable plugins are limited)

[LoRd_MuldeR]

i wasn't complaining, just making a comment. and until we did the test, we didn't know if it was or not :)

But now we know that's your problem isn't related to my GUI and therefore it has become clear that you are discussing your problem at the wrong place...

[kool]

(Keep in mind that many Avisynth plugins don't even have a 64-Bit build available. So if you use 64-Bit Avisynth, the usable plugins are limited)

OK...:) in theory I can use avisynth 32bit and it's plugins under 64bit OS with out any problem? but can't use 32bit avisynth and it's plugins under 64bit avisynth, as you mentioned there are few plugins for 64bit avisynth, and the usable plugins are limited for 64bit avisynth? "if yes" than I happyly move to 64bit.

Your suggestion i ask, I have total of 4GB Ram with 32bit OS, I can use about 3.25 GB, so when I move to 64bit OS I will get total of 4 GB Ram, and here...will the extra 0.35 GB make any speed differences when I move to 64 bit OS?

Thank you once again :)

[LoRd_MuldeR]

OK...:) in theory I can use avisynth 32bit and it's plugins under 64bit OS with out any problem?

Yes, you can. There is absolutely no problem.

but can't use 32bit avisynth and it's plugins under 64bit avisynth, as you mentioned there are few plugins for 64bit avisynth, and the usable plugins are limited for 64bit avisynth? "if yes" than I happyly move to 64bit.

32-Bit Avisynth can only use 32-Bit plugins, it cannot use 64-Bit plugins. 64-Bit Avisynth can only use 64-Bit plugins, it cannot use 32-Bit plugins.

Various plugins are already available as 64-Bit version (see squid80's site), but many are not...

Your suggestion i ask, I have total of 4GB Ram with 32bit OS, I can use about 3.25 GB, so when I move to 64bit OS I will get total of 4 GB Ram, and here...will the extra 0.35 GB make any speed differences when I move to 64 bit OS?

Probably there won't be much speed-up regarding the additional RAM. But you will run in "out of RAM" problems less frequently.

Be aware that 32-Bit applications are still limited to 2 GB of memory per process, even when running on a 64-Bit OS. That's often a problem with memory-intensive Avisynth scripts!

Only if you use 64-Bit applications (which of course requires a 64-Bit OS) the per-process 2 GB memory limit is gone!

With my tool Avisynth is still 32-Bit and still has the 2 GB limit. But as Avisynth and x264 are running in separate processes with my tool, the memory issue is eased a bit, at least ;)

[djesteban]

Hi,

I have a odd problem here
I am trying to encode this 1920x1080 h264 stream, but it won't encode if I add any option to my avs script.
For example, if my avs script looks like this:
LoadPlugin("<path>\DGDecodeNV.dll")
DGSource("D:\Hatsukoi\video.dga")
#deinterlace
#crop
#resize
#denoise

The encode starts and seems to continue without any issue (I aborted before the end since it's a fairly long movie)

...but if I change my script with a crop like the following:
LoadPlugin("<path>\DGDecodeNV.dll")
DGSource("D:\Hatsukoi\video.dga")
#deinterlace
crop( 0, 22, 0, -22)

#resize
#denoise

...then the launcher displays Creating encoder processes, please wait... forever and never starts the encode.

What am I doing wrong here?!?! When I test this AVS in MeGUI, it does start and encode. Please help!

Here's my .dga info log:
Stream Type: Elementary
Video Type: AVC
Profile: High
Level: 4.1
Coded Size: 1920x1088
SAR: 1:1
Display Size: 1920x1080
Frame Rate: 23.976024 fps
Colorimetry: BT.709 [1]
Frame Structure: Frame
Frame Type: I
Coded Number: 164219
Playback Number: 164219
Frame Repeats: 0
Field Repeats: 0
Bitrate: 0.888
Bitrate (Avg): 34.297
Bitrate (Max): 40.085
Elapsed: 0:09:54
Remain: 0:00:00
FPS:
Info: Finished!


Thanks in advance

[LoRd_MuldeR]

Is that problem specific to DGSource? Then please report it in the proper thread:
http://forum.doom9.org/showthread.php?t=147945

If that problem is specific to x264 itself, which means DGSource works perfectly fine in any other application, you will have to discuss that with the x264 developers.

The only case where I might be able to do something are problems that are specific to my GUI, which means x264 works 100% fine from console but doesn't inside my GUI.

BTW: When cropping, try to avoid Non-Mod16 resolutions. That means: If your source is Mod16, only crop multiples of 16 in each dimension.

[kool]

is this tool belongs to "C:\Program Files (86)?

[LoRd_MuldeR]

is this tool belongs to "C:\Program Files (86)?

You can put it to whatever place you like :p

However Microsoft's "C:\Program Files (86)" -vs- "C:\Program Files" folder concept doesn't fit here, as this software package incorporates 32-bit and 64-Bit binaries :D

But technically there is absolutely no reason to use the one or the other. Choose whatever you personally like more ;)

[rack04]

Hi,

I have a odd problem here
I am trying to encode this 1920x1080 h264 stream, but it won't encode if I add any option to my avs script.
For example, if my avs script looks like this:
LoadPlugin("<path>\DGDecodeNV.dll")
DGSource("D:\Hatsukoi\video.dga")
#deinterlace
#crop
#resize
#denoise

The encode starts and seems to continue without any issue (I aborted before the end since it's a fairly long movie)

...but if I change my script with a crop like the following:
LoadPlugin("<path>\DGDecodeNV.dll")
DGSource("D:\Hatsukoi\video.dga")
#deinterlace
crop( 0, 22, 0, -22)

#resize
#denoise

...then the launcher displays Creating encoder processes, please wait... forever and never starts the encode.

What am I doing wrong here?!?! When I test this AVS in MeGUI, it does start and encode. Please help!

Here's my .dga info log:
Stream Type: Elementary
Video Type: AVC
Profile: High
Level: 4.1
Coded Size: 1920x1088
SAR: 1:1
Display Size: 1920x1080
Frame Rate: 23.976024 fps
Colorimetry: BT.709 [1]
Frame Structure: Frame
Frame Type: I
Coded Number: 164219
Playback Number: 164219
Frame Repeats: 0
Field Repeats: 0
Bitrate: 0.888
Bitrate (Avg): 34.297
Bitrate (Max): 40.085
Elapsed: 0:09:54
Remain: 0:00:00
FPS:
Info: Finished!


Thanks in advance

Since you have DGDecNV tools you could use the DGIndexNV cropping feature and see if that solves anything.

[djesteban]

Is that problem specific to DGSource? Then please report it in the proper thread:
http://forum.doom9.org/showthread.php?t=147945

If that problem is specific to x264 itself, which means DGSource works perfectly fine in any other application, you will have to discuss that with the x264 developers.

The only case where I might be able to do something are problems that are specific to my GUI, which means x264 works 100% fine from console but doesn't inside my GUI.

BTW: When cropping, try to avoid Non-Mod16 resolutions. That means: If your source is Mod16, only crop multiples of 16 in each dimension.
Ok so I tested the following from the cli...
x264.exe --preset slower --tune film --pass 1 --bitrate 12000 --stats "encode.stats" --output NUL "D:\Hatsukoi\video.avs"
(here's the avs script; notice that I have change the crop size to make sure it is mod16):
LoadPlugin("<path>\DGDecodeNV.dll")
DGSource("D:\Hatsukoi\video.dga")
#deinterlace
crop( 0, 20, 0, -20)

#resize
#denoise

...and it works like a charm, encode starts (thanks to your help in another thread :p )

But now, when I try your tool, I input the same avs in launcher.exe, specify my output path with .264 extension and:
mode: 2-pass
target bitrate: 12000
preset: slower
tuning: film
profile: high
no advanced/custom options specified
...then I start the job, and it still stays at the Creating encoder processes, please wait... message forever and never actually starts the encode.

Now, the only way I am able to make it start, is by completely stripping my avs in the following way (notice there's no crop anymore):
LoadPlugin("<path>\DGDecodeNV.dll")
DGSource("D:\Hatsukoi\video.dga")
#deinterlace

#resize
#denoise
That will start the job and encode.
So mod16 or not, as soon as i add a crop, it just sleeps there without doing anything.

[djesteban]

Since you have DGDecNV tools you could use the DGIndexNV cropping feature and see if that solves anything.

Hmmm... that could be the issue, who knows... I'll try it... but still it doesn't explain why it works from the cli and not from this tool (with the same avs)

Let me try that and I'll tell you what happens :)

*EDIT*
By cropping through DGIndexNV the encode indeed starts! Though my avs script is still the stripped one because the crop info are stored in the .dga file now.
Still, the question remains as why it works through cli and not in this tool when cropping through the .avs script

[kool]

I have did the 1th test with 704x304 Win 7 64-bit.

Source: C:\Users\kool\Desktop\Test\test.avs
Preset: Medium
Tuning: None
Profile: High
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 922 frames, 74.81 fps, 1440.62 kb/s
encoded 922 frames, 75.48 fps, 1440.62 kb/s
encoded 922 frames, 74.25 fps, 1440.62 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 922 frames, 76.83 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 922 frames, 76.83 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s
encoded 922 frames, 76.83 fps, 1440.62 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 922 frames, 70.92 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 922 frames, 70.92 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 922 frames, 76.83 fps, 1440.62 kb/s
encoded 922 frames, 76.83 fps, 1440.62 kb/s
encoded 922 frames, 70.92 fps, 1440.62 kb/s

[LoRd_MuldeR]

Updated x264 to r1376, using Komisar's builds.

Also piping source into x264 as YUV4MPEG from now on, so we don't need to specify the video resolution and framerate in the command-line.

However we still need to detect the number of frames and pass it to x264 via command-line parameter explicitly...

[buzzqw]

However we still need to detect the number of frames and pass it to x264 via command-line parameter explicitly...

why ?

from my short test the encoding has always ended at right frame..

BHH

[LoRd_MuldeR]

why ?

from my short test the encoding has always ended at right frame..

BHH

If you pipe input into x264 from STDIN then it doesn't know the total number of frames!

With the YUV4MPEG format the width/height as well as the framerate are included in the stream (as opposed to "raw" YUV), so we don't need to pass those params explicitly.

However the total number of frames are not included in the YUV4MPEG stream, so we need to pass it manually via "--frames" parameter.

Otherwise x264 doesn't display the progress properly - and the GUI fails to parse the output. Well, how should x264 display progress, if the total number of frames isn't known?

But don't worry, the GUI will detect the number of frames for you and pass the "--frames" parameter to x264 ;)

(It's just that we cannot get rid of the "Analyze" step before the encoding starts. Anyway, the analyze isn't required to detect width/height/framerate anymore)

[buzzqw]

thanks for explanation LM!

BHH

[dstln]

http://img695.imageshack.us/img695/4153/errorwh.png

Been getting a bunch of these recently, at the end of encodes. Launcher keeps running and even working (during benchmark) until you press ok, then it crashes out.

[LoRd_MuldeR]

Unless you give me detailed information on how to reproduce this problem, I cannot help. I finished dozens of encodes and it never crashed for me...

[djesteban]

I am actually using this tool as my main x264 GUI front-end!
I am still having the crop issue when cropping from my .avs file, but since I am now cropping directly in my .dga file (now .dgi it seems), this works like a charm.
Thanks for keeping up the good work on this one LoRd_MuldeR :)

*EDIT*
Only thing that is missing from this tool IMO is a good bitrate calculator like in MeGUI. That would be awesome!

[LoRd_MuldeR]

I am actually using this tool as my main x264 GUI front-end!
I am still having the crop issue when cropping from my .avs file, but since I am now cropping directly in my .dga file (now .dgi it seems), this works like a charm.
Thanks for keeping up the good work on this one LoRd_MuldeR :)

I can't help you with the "cropping" issue, as there is no indication that this related to my GUI.

It's caused by x264, Avisynth or DGSource. Or more likely, a combination of those...

*EDIT*
Only thing that is missing from this tool IMO is a good bitrate calculator like in MeGUI. That would be awesome!

What's wrong with %WINDIR%\System32\calc.exe ??? :D

[yesgrey]

My test results with 1920x816p, Win7 RC1 64bit, E2160@2.7GHz:
Source: D:\Temp\test_jumper_x264.avs
Preset: Slow
Tuning: Grain
Profile: High
Params: CRF 18

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 202 frames, 1.86 fps, 14666.12 kb/s
encoded 202 frames, 1.92 fps, 14666.12 kb/s
encoded 202 frames, 1.93 fps, 14666.12 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 202 frames, 1.92 fps, 14666.12 kb/s
encoded 202 frames, 1.96 fps, 14666.12 kb/s
encoded 202 frames, 1.96 fps, 14666.12 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 202 frames, 1.98 fps, 14666.12 kb/s
encoded 202 frames, 1.94 fps, 14666.12 kb/s
encoded 202 frames, 1.98 fps, 14666.12 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 202 frames, 1.98 fps, 14666.12 kb/s
encoded 202 frames, 1.98 fps, 14666.12 kb/s
encoded 202 frames, 1.96 fps, 14666.12 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 202 frames, 1.98 fps, 14666.12 kb/s
encoded 202 frames, 1.98 fps, 14666.12 kb/s
encoded 202 frames, 1.98 fps, 14666.12 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 202 frames, 1.98 fps, 14666.12 kb/s
encoded 202 frames, 1.94 fps, 14666.12 kb/s
encoded 202 frames, 1.98 fps, 14666.12 kb/s

[aegisofrime]

Lord Mulder: Any chance of adding a queuing system?

[dstln]

Fairly certain that has been asked ~10 times in this topic and it's been more or less said that he doesn't want to. So unless you have a specific reason for doing sequential encodes, I'd just say open a bunch of launcher applications and run them if you'll be afk for a while and wish to do so.

[alwyn]

Ran a benchmark on my i7 920 Rig, 6 GB DDR3 RAM, the procesor chip is overclocked to 3.5 GHZ.
Here's the results:
Encode resolution : 640x272, simply resized a sample of one of my 720p encodes
Source: C:\Users\Alwyn's System\Desktop\touch me.avs
Preset: Fast
Tuning: Grain
Profile: Main
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 7734 frames, 87.53 fps, 5274.00 kb/s
encoded 7734 frames, 89.03 fps, 5274.00 kb/s
encoded 7734 frames, 88.95 fps, 5274.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 7734 frames, 100.44 fps, 5273.99 kb/s
encoded 7734 frames, 100.44 fps, 5274.00 kb/s
encoded 7734 frames, 100.44 fps, 5274.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 7734 frames, 100.44 fps, 5274.00 kb/s
encoded 7734 frames, 99.15 fps, 5274.00 kb/s
encoded 7734 frames, 97.90 fps, 5274.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 7734 frames, 99.15 fps, 5274.00 kb/s
encoded 7734 frames, 99.15 fps, 5274.00 kb/s
encoded 7734 frames, 97.90 fps, 5274.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 7734 frames, 100.44 fps, 5274.00 kb/s
encoded 7734 frames, 100.44 fps, 5274.00 kb/s
encoded 7734 frames, 99.15 fps, 5274.00 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 7734 frames, 97.90 fps, 5274.00 kb/s
encoded 7734 frames, 99.15 fps, 5274.01 kb/s
encoded 7734 frames, 99.15 fps, 5274.00 kb/s

[buzzqw]

Lord Mulder: Any chance of adding a queuing system?

MicroX264 (inspired by this great gui) has a queue system

BHH

[kool]

* The tuning option is set to none by default, can you please tell me in details what other 6 options means and when I can use it?
* I understand the two pass mod, but I'm unaware of other 3 mods, CRF, QP and ABR :confused:
* What is the relation between CRF > Quantizer and QP > Quantizer?
* The slower preset means " better quality" :rolleyes: ?
* Is it like higher profile means "high quality" ? Could you explain the profiles :)
* What are the recommended lower value for quantizer for high quality?

Thank you.

[LoRd_MuldeR]

* The tuning option is set to none by default, can you please tell me in details what other 6 options means and when I can use it?
* I understand the two pass mod, but I'm unaware of other 3 mods, CRF, QP and ABR :confused:
* What is the relation between CRF > Quantizer and QP > Quantizer?
* The slower preset means " better quality" :rolleyes: ?
* Is it like higher profile means "high quality" ? Could you explain the profiles :)
* What are the recommended lower value for quantizer for high quality?

Thank you very much.

These are very basic question about x264, not specific to this GUI. All the info can be found in this forum or in a basic x264 guide! So I won't answer it in this thread.

Please :search: and, if any questions remain, ask in the Newbies (http://forum.doom9.org/forumdisplay.php?f=6) forum. Also there is the "Show Help Screen" button in my GUI for a complete list of all options ;)

[MuLTiTaSK]

@kool

a little searching and reading can help take you a long ways here are some links to help:)
x264 settings (http://tinyurl.com/67y67w)
x264-encoding-options (http://tinyurl.com/y8coljh)
x264_options_page1 (http://tinyurl.com/2bmh56)
x264Options (http://tinyurl.com/ydr9lbk)
h264-profiles-and-levels (http://tinyurl.com/ybysezt)
x264 explained (http://tinyurl.com/3cp7bq) - LoRd_MuldeR's Sig can help

[kool]

Thank you very much MuLTiTaSK & LoRd_MuldeR for pointing me to right direction :p

[kypec]

Hi LoRd_MuldeR,

could you possibly enhance the information displayed in minimized state in taskbar?
I mean, currently it looks like this:
http://i48.tinypic.com/2uetohz.jpg
When using 2-pass mode I have to maximize window occasionally just to check which pass is really running at the moment. :(
It would be nice if that info was included in minimized window title and tooltip dialog as well.
Thank you very much for your superb tool and for hearing me out! ;)

[Rodger]

Totally different problem here:

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

SIZ 1920 x 1088
FPS 30000 / 1001
CODED 6246
PLAYBACK 7451
99.98% FILM


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