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

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

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

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]

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

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]

Originally Posted by buzzqw

again, not for daily use, but fun for testing

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

[buzzqw]

yea KISS rule!

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

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

Originally Posted by archaeo

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

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

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

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]

Originally Posted by Rodger

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]

Originally Posted by Rodger

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