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

[LoRd_MuldeR]

Originally Posted by samtroy

@LoRd_MuldeR:

May I ask what exact settings + parameters you personally use for encoding a normal 2h 1080p movie?

Cheers, S.

--crf 20 --preset veryslow

[samtroy]

Originally Posted by LoRd_MuldeR

--crf 20 --preset veryslow

OK.. and no extra parameters at all? Like --level 4.1 for compatability reasons maybe?

[LoRd_MuldeR]

Originally Posted by samtroy

OK.. and no extra parameters at all? Like --level 4.1 for compatability reasons maybe?

Nope.

[egrimisu]

how to use 10bit encode? i select high10 profile but stil x264 x86 8 bit is used.

[LoRd_MuldeR]

8-Bit vs. 10-Bit is a compile-time decision. It's nothing you can change at runtime via option

The "--profile" option of x264 only restricts your other option to (at most) the selected H.264 Profile. It does not enforce the selected Profile, if a lower Profile is sufficient for your file.

In other words: Using 10-Bit H.264 implies the "High 10" Profile, but selecting the "High 10" Profile (alone) does NOT trigger or imply 10-Bit encoding!

You can enable "10-Bit encoding" in the preferences dialog. This will use the 10-Bit x264 binary for subsequent encodes, instead of the 8-Bit x264 binary that is used by default.

[egrimisu]

Originally Posted by LoRd_MuldeR

8-Bit vs. 10-Bit is a compile-time decision. It's nothing you can change at runtime via option

The "--profile" option of x264 only restricts your other option to (at most) the selected H.264 Profile. It does not enforce the selected Profile, if a lower Profile is sufficient for your file.

In other words: Using 10-Bit H.264 implies the "High 10" Profile, but selecting the "High 10" Profile (alone) does NOT trigger or imply 10-Bit encoding!

You can enable "10-Bit encoding" in the preferences dialog. This will use the 10-Bit x264 binary for subsequent encodes, instead of the 8-Bit x264 binary that is used by default.

Fair enough, still what to enter in dialog there nothing in the help related to 10bit?

[LoRd_MuldeR]

Originally Posted by egrimisu

Fair enough, still what to enter in dialog there nothing in the help related to 10bit?

If you ask how to enable 10-Bit encoding in Simple x264 Launcher, just go to "File" -> "Preferences" and enable "Use 10-Bit version of x264".

It will show a warning. Read that warning and, if you have understood the consequences, click "Continue".

[egrimisu]

Originally Posted by LoRd_MuldeR

If you ask how to enable 10-Bit encoding in Simple x264 Launcher, just go to "File" -> "Preferences" and enable "Use 10-Bit version of x264".

It will show a warning. Read that warning and, if you have understood the consequences, click "Continue".

Iddiot me, thanks, nice that you had implemented queue

[darknoob]

Just wanted to say thank you Lord for making the new version with batch process, so much easier now queuing up test encodes. Also now I can see my RF after first pass, good stuff mate!

[nibus]

After upgrading to the newest version I'm getting constant crashes from avs2yuv:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	avs2yuv_x86.exe
  Application Version:	0.0.0.0
  Application Timestamp:	4e78e870
  Fault Module Name:	avisynth.DLL
  Fault Module Version:	2.6.0.3
  Fault Module Timestamp:	4f7b27cf
  Exception Code:	c0000005
  Exception Offset:	00066e34
  OS Version:	6.1.7601.2.1.0.256.4
  Locale ID:	1033
  Additional Information 1:	9bb2
  Additional Information 2:	9bb2af9eb5b5e3c312278cd2f1aa9dbe
  Additional Information 3:	9af5
  Additional Information 4:	9af54169938890e76fe9ec03370a170d

This is on a Sandy Bridge 2600K, 8gb Ram, running at 4.0ghz. I didn't have any problems with the previous version. However it appears to run fine on my non-overclocked i7 930.

Is x264_x64.2012-07-22.exe the previous build? I will try it with that version and make sure it still runs stable.

[LoRd_MuldeR]

All previous versions can be found here:
http://code.google.com/p/mulder/down...+DownloadCount

But Avs2YUV neither is my work nor did I change the included Avs2YUV binaries lately...

I've always been using the latest version from here:
http://komisar.gin.by/tools/avs2yuv/

What you are experiencing is probably a crash in Avisynth or (more likely) in one of the Avisynth plug-in's involved.

Does the very same Avisynth script open in VirtualDub and play through all the way to the end?

[nibus]

Originally Posted by LoRd_MuldeR

What you are experiencing is probably a crash in Avisynth or (more likely) in one of the Avisynth plug-in's involved.

Does the very same Avisynth script open in VirtualDub and play through all the way to the end?

It appears to play fine in VirtualDub, though I haven't had time to run through the entire video.

After reverting to x264_x64.2012-07-22.exe I still have the crash, though without the avs2yuv notice. The application just reports that x264 is not responding. Each time it appears to be in a different portion of the video.

The only other thing that has changed was a small mvtools2.dll update. That is probably the cause of the crash, though it's strange that it only happens on my newer i7 box.

I'm trying the encode again without filters; will report back.

[LoRd_MuldeR]

That's the problem with software testing: The fact that you didn't get a crash, doesn't prove the absence of bugs

Depending on the nature of the bug, it may only be triggered under specific conditions. The conditions may even not be deterministic, which is especially true for "race conditions" errors!

And with memory corruption bugs, like "buffer overruns" or "dangling pointers", it's sheer luck whether you get an instant crash or "only" corrupted output (or no effect at all).

[nibus]

The encode runs fine without filters so it's probably an issue with mvtools2 or MT. Thanks for your help Mulder.

[GZZ]

in preferences I have checked "Automatically save output to log file when job has finished" - Where can I locate this log file, its not among my movie source files and I have tried look in the temp folder where the .ffindex file are saved. Can you give me a hint on where to find it ?

[r0lZ]

C:\Users\<YOU>\AppData\Local\LoRd_MuldeR\Simple x264 Launcher\logs\

[RockTheBass]

Hey!

Thaks for this great x264 encoder software! I love it!
I want to ask something. I downloaded the newest version (v2.06), I installed and I checked the version of x264 encoders:
toolset\x264_8bit_x64.exe

x264 core:128 r2216 198a7ea

I downloaded the newest x64 8bit version EXE from there: http://x264.nl/ and I checked this version also:

x264 core:128 r2216 198a7ea

The versions are same, but I noticed there are difference between the file sizes.
\Simple x264 Launcher v2\toolset\x264_8bit_x64.exe 9,034,240 Bytes

x264.nl_x64_8bit\x264.exe 10,607,616 Bytes.

Can someone explain why is difference these file sizes? I thought, x264 Simple Launcher uses the original x264 files. May I should replace the original files that located in \toolset\ folder with the www.x264.nl files?

Thank you!

[LoRd_MuldeR]

There is no such thing as "original" x264 files. x264 is OpenSource software and released as source code. There are no "official" binaries

Everybody can make his/her own builds. And the resulting file size will depend on many things, like the compiler version that was used, the compiler settings that were used, the libraries included in the build (or not), the versions of the included libraries, the debug symbols being stripped (or not), and so on. The binaries might even have been compressed with an "exe packer" like UPX...

I didn't compile x264 myself this time. The binaries I included in the Simple x264 Launcher download are those provided by Komisar (http://komisar.gin.by/) and the differences to JEEB's binaries (http://x264.nl/) should be negligible.

[RockTheBass]

Ohh, I understand. Thank you very much for quick answer! Please keep up this great software, and continue your work as you always do

Originally Posted by LoRd_MuldeR

There is no such thing as "original" x264 files. x264 is OpenSource software and released as source code. There are no "official" binaries

Everybody can make his/her own builds. And the resulting file size will depend on many things, like the compiler version that was used, the compiler settings that were used, the libraries included in the build (or not), the versions of the included libraries, the debug symbols being stripped (or not), and so on. The binaries might even have been compressed with an "exe packer" like UPX...

I didn't compile x264 myself this time. The binaries I included in the Simple x264 Launcher download are those provided by Komisar (http://komisar.gin.by/) and the differences to JEEB's binaries (http://x264.nl/) should be negligible.

[VideoFanatic]

I've installed the latest version of your program (2.06) on a new Windows 7 64-bit installation. I can't drag and avs files into your program. Even if I open the job window and drag it into the source file box, it doesn't work. The only way I can open a file is to manually select the file in the directory.

On my Vista 32-bit PC I had the 22nd July 2012 version and I could drag and drop an AVS file into main window and it would automatically populate the job source file.