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

[tormento]

Try here
Is it normal that with NVEncC I can't set almost anything from GUI? At least I would need profile (main10) and so. The basic things...

P.S: New version out :)

[LoRd_MuldeR]

Is it normal that with NVEncC I can't set almost anything from GUI? At least I would need profile (main10) and so. The basic things...

What exactly you can't set?

The "Tuning" combobox is disabled for NVEncC, because NVEncC doesn't have anything like that. You can still set "Preset" and "Profile" for NVEncC.

Anything else, as always, needs to be set via "Custom Encoder Parameters" edit box...

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.97
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.97

Version 2.97 [2020-05-15]
* Updated x265 to version 3.3+27
* Updated NVEncC to version 5.01
* Updated cURL to version 7.70.0 (2020-04-29)VapourSynth R49 Warning
There is a bug in VapourSynth R49 that causes vspipe.exe to fail loading the Python DLL. Therefore, Simple x264 Launcher was unable to find a working VapourSynth. Please update to R50 (http://www.vapoursynth.com/2020/05/r50-low-risk-release/), which fixed the issue!

[redbtn]

Big thanks for new release!

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.98
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.98

Version 2.98 [2020-06-25]
* Updated x264 to revision 3009 (API v160)
* Updated x265 to version 3.4+7
* Updated NVEncC to version 5.06
* Added experimental "dark mode" (use option --dark-gui-mode to enable)
* Updated build environment to Visual Studio 2019 with Update-6

[darkio]

how is the quality using nvenc compared to x265?

[tormento]

Simple x264/x265 Launcher v2.98
I love dark mode.

Tell me there is a way to set it in preferences.ini. :p

[LoRd_MuldeR]

Tell me there is a way to set it in preferences.ini. :p

Not at this time. It's just a crude integration of QDarkStylesheet (https://github.com/ColinDuquesnoy/QDarkStyleSheet), which works fairly well, but also produces quite a few glitches.

I will see if further improvements are possible when I have more time...

how is the quality using nvenc compared to x265?

It's exactly 42.3141 percent worse ;)

(Really, this depends on a whole lot of factors, including the kind of material you are encoding, the selected bit rate and the selected quality preset. So you are best off doing you own tests with settings that fit your workflow!)

[darkio]

I had no doubts, why then is it used here?
I tried something but the results are not satisfactory even at the same bitrate. I did a bluray rip of the alien film, even using the preset faster the results are much better with x265 (I have an i7 4790k). Using nvenc CQP 20 or in vbr mode, it does not improve the quality via gpu

[LoRd_MuldeR]

I had no doubts, why then is it used here?
I tried something but the results are not satisfactory even at the same bitrate. I did a bluray rip of the alien film, even using the preset faster the results are much better with x265 (I have an i7 4790k). Using nvenc CQP 20 or in vbr mode, it does not improve the quality via gpu

Just as an example: With x265, I get ~5.5 fps for "4K" material on my Core-i 6700K, using the "medium" (default) preset. This goes up to at most ~15.7 fps, when using the "ultrafast" preset. With NVEncC, I get ~80 fps for the same input, on my RTX 2070 SUPER (HEVC mode, default preset). So, NVEncC typically runs many times faster than x265. This means that a quality comparison which completely disregards encoding speed is not really "fair" here.

Anyway, it's all about giving users options to choose from. If your goal is to get the maximum quality at a medium to low bitrate, and if you are willing the spend a whole lot of encoding time for that, then using one of the software encoders probably still is your best choice. But, if your goal is to finish the encode as quickly as possible while still getting a "reasonable" quality, then probably nothing will beat a hardware encoder, such as NVEncC.

[jlw_4049]

I had no doubts, why then is it used here?

I tried something but the results are not satisfactory even at the same bitrate. I did a bluray rip of the alien film, even using the preset faster the results are much better with x265 (I have an i7 4790k). Using nvenc CQP 20 or in vbr mode, it does not improve the quality via gpuI usually encode 4k via x265 on my 3900x. It takes about 16 hours.

I really wouldn't recommend encoding 4k on a quad core. Although like Lord said, hardware is an option if you dont mind the quality loss.

Sent from my SM-G986U1 using Tapatalk

[darkio]

rigaya's nvenc 5.12 have 2 pass mode now.

[szabi]

Hi

The latest included x264 version is r3009 from june, however official one (https://artifacts.videolan.org/x264/release-win64/) is newer: x264 r3027 from october.
Is it still get update?

Regards
szabi

[LoRd_MuldeR]

The latest included x264 version is r3009 from june, however official one (https://artifacts.videolan.org/x264/release-win64/) is newer: x264 r3027 from october.

Not that there have been a lot of important changes in x264 (for Windows users), but a new release is up now ;)

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.99
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v2.99

Version 2.98 [2020-06-25]
* Updated x264 to revision 3027 (API v161)
* Updated x265 to version 3.4+30
* Updated NVEncC to version 5.20

[szabi]

Not that there have been a lot of important changes in x264 (for Windows users), but a new release is up now ;)

Thanks. :)

EDIT:
Regarding the lots of changes I use x264 with this settings since years.

https://abload.de/img/simplemajou.png

Should I change my preferred settings or I can stay on my oldies one? :)
What do u suggest?

[Emulgator]

It depends what resolution you feed to encoder, how much grain you want to encode,
how much picture deterioration you can stand and which playback device you intend to target.
x264 has not changed much in that regard.

If you aim at 1080p25/29,97 blu-ray for instance and want to have transparency through grain and keep all details,
bufsize and maxrate are too high, while 13Mbps would be too misery.

If you aim at a hardware player or mobile phone and supply denoised, degrained stuff 720p@24/25/29fps,
13Mbps are good to go, while the bufsize and maxrate are still unnecessary high.

[szabi]

Hi
You are right I did not go into details.
I use for 1080p output and all limits are kept due to hardware decoder I have expect nofastpskip which in use to increase quality.
I still use 2 pass encode that is why bitrate is calculated for the size of output however quality is still around 1 pass 17mbps bitrate. At least I hope. :-)
Thanks for your help.
Regards.
szabi

[StainlessS]

JFYI, from long time ago, [2018, I just noticed your reply]

It actually is 0xC0000139, equal to STATUS_ENTRYPOINT_NOT_FOUND, if you interpret it as 32-Bit unsigned integer, which I think is the right thing to do here.

NT_STATUS codes are defined as DWORDs, which are 32-Bit unsigned integer values, but will be typecasted to 32-Bit signed integer values when returned as a process' exit code.

(Hence, if the original unsigned value had its most significant bit set, the signed value will have negative sign)

#include <stdint.h>

int main()
{
const uint32_t code = (uint32_t)(-1073741511);
printf("0x%X\n", code);
return 0;
}
Output:
0xC0000139

I had entered the denary number [1073741511], and then hit the negate key in my calculator, it failed to negate that number before my hex conversion. [10 digit display calculator]

[guest]

Not that there have been a lot of important changes in x264 (for Windows users), but a new release is up now ;)

Hi LoRd MuldeR,

I just happen to find this app today, and I have had a bit of a fiddle with it, and I think it's pretty easy to update x264 & x265, and I notice that it seems to use L Smash as a decoder (is that correct?), anyway, can this be updated by the user ??

Would there be a chance that you could "point" the app to where the sources paths could be chosen, instead of integrated with in the app ? (I'm not really sure what I'm talking about).

I also installed Vapoursynth & Python, but it also ask's for Visual Studio, which looks like it's a fairly large download..is that really required ??

One thing I noticed when I updated x264 from https://artifacts.videolan.org/x264/release-win64/, and renamed it, when I tested a new job, the encoding info window at the bottom of the app, did NOT show all the info that the built in version x264 did (if you know what I'm trying to say) I could send screenshots if you like.

[videoh]

I notice that it seems to use L Smash as a decoder (is that correct?), anyway, can this be updated by the user ?? Just as you discovered with staxrip, you can create your own avisynth or vapoursynth script invoking the source filter and other filters that you like. Then the script can be opened in Simple Launcher.

[guest]

Just as you discovered with staxrip, you can create your own avisynth or vapoursynth script invoking the source filter and other filters that you like. Then the script can be opened in Simple Launcher.

Oh, Hi DG, (are you following me?...lol)...yeah, not really the answer(s) to my question, but nice to know.

I'd just like to know how to update some of the key components, not necessarily "custom" scripts. (unless that's a clue)

For example, where is the L-Smash source, when using this app ??

Cheers

[videoh]

My understanding is that it uses the input capabilities of x264.exe and x265.exe. They are built with understanding of (for example) MKV input. It won't be easy to change those things, which is why Avisynth/Vapoursynth input is the way to go for such flexibility.

Sincerely,
your stalker

[guest]

Sincerely,
your stalker

Nice :)

OK, well, I might have good play around with it the next couple of days, and see if I can make any sense of it.

I was out riding my dirt bike today, so I need a rest.

[kebulek]

Oh no, pop up window with "Your version of Simple x264 Launcher is more than 6 month old!" is back. :rolleyes:

@LoRd_MuldeR: Could you make a new update for us? Thanks.

BTW: "Update web-server" doesn't work.

[dREV]

Hi, I can't seem to get this to work again for some reason. It's telling me this: FAILED TO DETERMINE VERSION INFO !!!

I switched both x264 64 bit with jpsdr's tmod https://github.com/jpsdr/x264/releases and a HEVC 64 bit build ver 3.5.0.20 from DJATOM https://github.com/DJATOM/x265-aMod/releases as I didn't wanna use the one that's included with it. Using the portable version btw.

I didn't change anything else. Simply refuses to encode using 64 bit now. This has been happening for the past 2-3 days. It was just working fine for the last couple of months till then when I stumbled upon this seeking to replace MeGUI with a faster gui that would create and keep the index of lsmash now this. Leaving me going back to my ex, MeGUI, so I can continue to encode with those encoders as of course no issues in MeGUI with those encoders. :scared:

[2021-05-17][08:52:27] Simple x264 Launcher (Build #1210), built 2020-11-19
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] Job started at 2021-05-17, 08:52:27.
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] Source file : Z:\# # DL\Encode\S1\Active 01 (002).avs
[2021-05-17][08:52:27] Output file : Z:\# # DL\Encode\S1\Active 01 (002).264
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] --- SYSTEMINFO ---
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] Binary Path : C:\Users\---\Desktop\! TEST\x264 launcher
[2021-05-17][08:52:27] Avisynth : Yes
[2021-05-17][08:52:27] VapourSynth : No
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] --- SETTINGS ---
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] Encoder : x264 (AVC/H.264), 64-Bit (x64), 8-Bit
[2021-05-17][08:52:27] Source : Avisynth (avs)
[2021-05-17][08:52:27] RC Mode : CRF
[2021-05-17][08:52:27] Preset : placebo
[2021-05-17][08:52:27] Tuning : Animation
[2021-05-17][08:52:27] Profile : High
[2021-05-17][08:52:27] Custom : --level 5.0 --direct auto --partitions all --trellis 2 --b-pyramid normal --b-adapt 2 --threads 0 --deblock 0:0
--bframes 16 --ref 16 --qcomp 0.60 --rc-lookahead 60 --aq-mode 3 --aq-strength 1.00 --lookahead-thread=2 --me tesa --subme 11 --merange 32
--psy-rd 1.00:0 --no-interlaced --transfer iec61966-2-1 --sar 1:1 --fade-compensate 0.3
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] --- CHECK VERSION ---
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] Detect video encoder version:
[2021-05-17][08:52:27]
[2021-05-17][08:52:27] Creating process:
[2021-05-17][08:52:27] "C:\Users\---\Desktop\! TEST\x264 launcher\toolset\x64\x264_x64.exe" --version
[2021-05-17][08:52:27]
[2021-05-17][08:52:28] x264 0.161.3048+53M 0749c36 t_mod_New [(8 & 10)-bit@all X86_64]
[2021-05-17][08:52:28] (libswscale 5.7.100)
[2021-05-17][08:52:28] (libavformat 58.45.100)
[2021-05-17][08:52:28] (ffmpegsource 2.40.0.0)
[2021-05-17][08:52:28] (lsmash 2.16.1)
[2021-05-17][08:52:28] built on Feb 14 2021, gcc: 10.2.1 20200926
[2021-05-17][08:52:28] x264 configuration: --chroma-format=all--disable-opencl
[2021-05-17][08:52:28] libx264 configuration: --chroma-format=all--disable-opencl
[2021-05-17][08:52:28] x264 license: GPL version 2 or later
[2021-05-17][08:52:28] libswscale/libavformat/ffmpegsource license: GPL version 3 or later
[2021-05-17][08:52:28]
[2021-05-17][08:52:28] Detect video source version:
[2021-05-17][08:52:28]
[2021-05-17][08:52:28] Creating process:
[2021-05-17][08:52:28] "C:\Users\---\Desktop\! TEST\x264 launcher\toolset\x86\avs2yuv_x86.exe"
[2021-05-17][08:52:28]
[2021-05-17][08:52:28] Avs2YUV 0.24bm6
[2021-05-17][08:52:28]
[2021-05-17][08:52:28] > x264 revision: 3048 (core #161) - with custom patches!
[2021-05-17][08:52:28] > Avs2YUV version: 0.24.6
[2021-05-17][08:52:28]
[2021-05-17][08:52:28] --- GET SOURCE INFO ---
[2021-05-17][08:52:28]
[2021-05-17][08:52:28] Creating process:
[2021-05-17][08:52:28] "C:\Users\---\Desktop\! TEST\x264 launcher\toolset\x86\avs2yuv_x86.exe" -csp I420 -depth 8 -frames 1
Z:\##DL~1\_B77DA~1\S1VOL1~1\active~1.avs NUL
[2021-05-17][08:52:28]
[2021-05-17][08:52:32] Z:\##DL~1\_B77DA~1\S1VOL1~1\active~1.avs: 852x480, YV12, 8-bits, progressive, 24000/1001 fps, 40054 frames
[2021-05-17][08:52:32]
[2021-05-17][08:52:32] Resolution: 852 x 480
[2021-05-17][08:52:32] Frame Rate: 24000/1001
[2021-05-17][08:52:32] No. Frames: 40054
[2021-05-17][08:52:32]
[2021-05-17][08:52:32] --- ENCODING VIDEO ---
[2021-05-17][08:52:32]
[2021-05-17][08:52:32] Creating input process:
[2021-05-17][08:52:32] "C:\Users\---\Desktop\! TEST\x264 launcher\toolset\x86\avs2yuv_x86.exe" -csp I420 -depth 8 Z:\##DL~1\_B77DA~1\S1VOL1~1\active~1.avs -
[2021-05-17][08:52:32]
[2021-05-17][08:52:32] Creating encoder process:
[2021-05-17][08:52:32] "C:\Users\---\Desktop\! TEST\x264 launcher\toolset\x64\x264_x64.exe" --output-depth 8 --crf 16.0 --preset placebo
--tune animation --profile high --level 5.0 --direct auto --partitions all --trellis 2 --b-pyramid normal --b-adapt 2 --threads 0 --deblock 0:0 --bframes 16
--ref 16 --qcomp 0.60 --rc-lookahead 60 --aq-mode 3 --aq-strength 1.00 --lookahead-thread=2 --me tesa --subme 11 --merange 32 --psy-rd 1.00:0
--no-interlaced --transfer iec61966-2-1 --sar 1:1 --fade-compensate 0.3 --output "Z:\# # DL\Encode\S1\Active 01 (002).264" --frames 40054
--demuxer y4m --stdin y4m -
[2021-05-17][08:52:32]
[2021-05-17][08:52:40] y4m [info]: 852x480p 1:1 @ 24000/1001 fps (cfr)
[2021-05-17][08:52:40] y4m [info]: color matrix: undef
[2021-05-17][08:52:40] x264 [info]: using SAR=1/1
[2021-05-17][08:52:40] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[2021-05-17][08:52:40] x264 [info]: profile High, level 5.0, 4:2:0, 8-bit
[2021-05-17][08:52:40] x264 [info]: cabac=1 ref=16 deblock=1:0:0 analyse=0x3:0x133 me=tesa subme=11 psy=1 fade_compensate=0.30
psy_rd=1.00:0.00 mixed_ref=1 me_range=32 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=0 chroma_qp_offset=-2
threads=15 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 fgo=0 bframes=16
b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=23 scenecut=40 intra_refresh=0
rc_lookahead=60 rc=crf mbtree=1 crf=16.0000 qcomp=0.60 qpmin=0:0:0 qpmax=69:69:69 qpstep=4 ip_ratio=1.40 aq=3:1.00
aq-sensitivity=10.00 aq-factor=1.00:1.00:1.00 aq2=0 aq3=0
[2021-05-17][08:52:40] x264 [info]: started at Mon May 17 08:52:34 2021
[2021-05-17][10:23:06] x264 [info]: frame I:316 Avg QP:11.57 size: 83396
[2021-05-17][10:23:06] x264 [info]: frame P:9325 Avg QP:15.16 size: 15423
[2021-05-17][10:23:06] x264 [info]: frame B:30413 Avg QP:18.68 size: 3160
[2021-05-17][10:23:06] x264 [info]: consecutive B-frames: 3.7% 4.4% 10.2% 27.0% 13.3% 14.5% 6.1% 7.4% 2.1% 2.6% 1.4% 2.7% 1.9% 0.8% 0.7% 0.8% 0.6%
[2021-05-17][10:23:06] x264 [info]: mb I I16..4: 10.2% 37.3% 52.5%
[2021-05-17][10:23:06] x264 [info]: mb P I16..4: 2.1% 5.4% 4.3% P16..4: 27.3% 22.6% 10.5% 3.1% 0.6% skip:24.2%
[2021-05-17][10:23:06] x264 [info]: mb B I16..4: 0.3% 0.6% 0.3% B16..8: 25.3% 9.4% 1.9% direct: 2.1% skip:60.2% L0:48.8% L1:43.9% BI: 7.3%
[2021-05-17][10:23:06] x264 [info]: 8x8 transform intra:45.6% inter:46.1%
[2021-05-17][10:23:06] x264 [info]: direct mvs spatial:99.6% temporal:0.4%
[2021-05-17][10:23:06] x264 [info]: coded y,uvDC,uvAC intra: 69.0% 69.8% 54.4% inter: 9.1% 8.9% 4.3%
[2021-05-17][10:23:06] x264 [info]: i16 v,h,dc,p: 31% 36% 2% 30%
[2021-05-17][10:23:06] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 11% 14% 12% 8% 10% 9% 12% 10% 15%
[2021-05-17][10:23:06] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 22% 8% 8% 10% 9% 10% 8% 10%
[2021-05-17][10:23:06] x264 [info]: i8c dc,h,v,p: 32% 37% 18% 13%
[2021-05-17][10:23:06] x264 [info]: Weighted P-Frames: Y:4.6% UV:3.9%
[2021-05-17][10:23:06] x264 [info]: ref P L0: 49.2% 5.4% 14.2% 7.7% 4.5% 4.3% 2.9% 2.7% 1.5% 1.5% 1.1% 1.3% 0.9% 1.0% 0.8% 0.9%
[2021-05-17][10:23:06] x264 [info]: ref B L0: 61.5% 13.1% 7.7% 4.0% 3.1% 2.1% 1.9% 2.0% 1.2% 0.8% 0.8% 0.7% 0.6% 0.5% 0.2%
[2021-05-17][10:23:06] x264 [info]: ref B L1: 91.1% 8.9%
[2021-05-17][10:23:06] x264 [info]: kb/s:1275.20
[2021-05-17][10:23:06] encoded 40054 frames, 7.374 fps, 1275.20 kb/s, 253.95 MB
[2021-05-17][10:23:06] x264 [info]: ended at Mon May 17 10:23:06 2021
[2021-05-17][10:23:06] x264 [info]: encoding duration 1:30:32
[2021-05-17][10:23:06] av2y [info]: Z:\##DL~1\_B77DA~1\S1VOL1~1\active~1.avs: 852x480, YV12, 8-bits, progressive, 24000/1001 fps, 40054 frames
[2021-05-17][10:23:06] Final file size is 254.0 MB bytes.
[2021-05-17][10:23:06]
[2021-05-17][10:23:06] --- COMPLETED ---
[2021-05-17][10:23:06]
[2021-05-17][10:23:06] Job finished at 2021-05-17, 10:23:06. Process took 90 minutes, 38 seconds.




to this

[2021-05-21][14:59:27] Simple x264 Launcher (Build #1210), built 2020-11-19
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] Job started at 2021-05-21, 14:59:27.
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] Source file : Z:\# # DL\Encode\S1\Active 01 (002).avs
[2021-05-21][14:59:27] Output file : Z:\# # DL\Encode\S1\Active 01 (002).264
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] --- SYSTEMINFO ---
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] Binary Path : C:\Users\--\Desktop\! TEST\x264 launcher
[2021-05-21][14:59:27] Avisynth : Yes
[2021-05-21][14:59:27] VapourSynth : No
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] --- SETTINGS ---
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] Encoder : x264 (AVC/H.264), 64-Bit (x64), 8-Bit
[2021-05-21][14:59:27] Source : Avisynth (avs)
[2021-05-21][14:59:27] RC Mode : CRF
[2021-05-21][14:59:27] Preset : placebo
[2021-05-21][14:59:27] Tuning : Animation
[2021-05-21][14:59:27] Profile : High
[2021-05-21][14:59:27] Custom : --level 5.0 --direct auto --partitions all --trellis 2 --b-pyramid normal --b-adapt 2 --threads 0 --deblock 0:0
--bframes 16 --ref 16 --qcomp 0.60 --rc-lookahead 60 --aq-mode 3 --aq-strength 1.00 --lookahead-thread=2 --me tesa --subme 11
--merange 32 --psy-rd 1.00:0 --no-interlaced --transfer iec61966-2-1 --sar 1:1 --fade-compensate 0.3
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] --- CHECK VERSION ---
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] Detect video encoder version:
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] Creating process:
[2021-05-21][14:59:27] "C:\Users\--\Desktop\! TEST\x264 launcher\toolset\x64\x264_x64.exe" --version
[2021-05-21][14:59:27]
[2021-05-21][14:59:27]
[2021-05-21][14:59:27] FAILED TO DETERMINE VERSION INFO !!!

using the same script!

I tried the skip version from https://github.com/lordmulder/Simple-x264-Launcher#command-line-syntax that didn't seem to work since I did place it in the custom parameter field. Dunno where to place it and according to this https://github.com/lordmulder/Simple-x264-Launcher/issues/14 if I read it right it's not recommended, why? :cool:

Any help on why this is happening? What am I doing wrong?
The program works again when I place the original x264.exe and x265.exe back not surprisingly. :thanks:


And that 6 month update thing is really annoying. Can't turn it off.

Could the author possibly include a feature where when you select the destination I can either type it in or copy and paste my folder location instead of the one it currently is using so it's faster? As I already mention I do tons of trim encodes then append them together and I do see it says something about a batch but I dunno how to do that.

Also, an option to keep jobs on the program as soon as they're on the program as I use tons of scripts with trim like MeGUI and I had a crash with the program adding new jobs while it was encoding and lost everything and had to redo them all... Also an option to not encode right after adding a job. And an option to move more than 1 job on the list up or down and to delete them as well instead of moving them 1 by 1. All could be a on/off toggle in the preference.

I really like this program a lot. Thanks for adding a pause when encoding. Never knew such a thing was possible of all my years encoding with MeGUI. Its neat! Hella lot faster than it too!


[EDIT] Seems downgrading to version 2.98 fixed the issue so far. Strange bug.

[LoRd_MuldeR]

Simple x264/x265 Launcher v3.00
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v3.00

Version 3.00 [2021-05-29]
* Updated x265 to version 3.5+2
* Updated NVEncC to version 5.33
* Updated cURL to version 7.76.1 (2021-04-14)
* Updated build environment to Visual Studio 2019 with Update-10
* Do not close application when hibernating the computer

[kebulek]

Thank you!

[zorrax]

Hi
I would like to encode UHD video in x265 format (2pass).
I saw that two parameters ( --scenecut-aware-qp and --vbv-live-multi-pass) are specific for the 2pass.
is it possible to specify these options for the 2pass in simpleX264 ?
thks

[LoRd_MuldeR]

Hi
I would like to encode UHD video in x265 format (2pass).
I saw that two parameters ( --scenecut-aware-qp and --vbv-live-multi-pass) are specific for the 2pass.
is it possible to specify these options for the 2pass in simpleX264 ?
thks

Currently it is not possible to specify custom encoder options only for the second pass. Generally, except for "--pass", the exactly same options should be set for both passes.

So options that are allowed only in a second pass are something new :D

[LoRd_MuldeR]

Simple x264/x265 Launcher v3.01
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v3.01

Version 3.01 [2021-12-08]
* Updated x265 to version 3.5+20
* Updated NVEncC to version 5.41
* Replaced GnuPG by CodeSign for checking the auto-update signatures
* Updated build environment to Visual Studio 2022

[Forteen88]

Simple x264/x265 Launcher v3.01Thanks!

[coocooc]

After having installed your latest x64 version (downloaded from github) on Monday, our company virus scanner Trend Micro interrupted your program's attempt to check if there is a newer version available.

The IT summary is attached in the three PNGs. 15 out of 67 hits; but the big ones like BitDefender, McAfee and Sophos are also classifying it as malicious.

Might be the "Predictive machine learning" causing havoc, but it could also be that the installer on github is really infected. Can you please double-check, if it contains what you expect to be therein?


You provide a cryptographic signature there, but I do not know how to check the installer integrity with these files. Any hint for this?

* Replaced GnuPG by CodeSign for checking the auto-update signatures
Is this change maybe the evil that triggers the scanners?

On my private computer your latest version does not trigger an alarm with Microsoft Defender, but it was not installed from github, but updated automatically from within your program.

And btw, thanks for your program and the integration of 10bit and x265 long ago. It still covers most of my needs on a regular basis! :thanks:

[jlw_4049]

After having installed your latest x64 version (downloaded from github) on Monday, our company virus scanner Trend Micro interrupted your program's attempt to check if there is a newer version available.



The IT summary is attached in the three PNGs. 15 out of 67 hits; but the big ones like BitDefender, McAfee and Sophos are also classifying it as malicious.



Might be the "Predictive machine learning" causing havoc, but it could also be that the installer on github is really infected. Can you please double-check, if it contains what you expect to be therein?





You provide a cryptographic signature there, but I do not know how to check the installer integrity with these files. Any hint for this?





Is this change maybe the evil that triggers the scanners?



On my private computer your latest version does not trigger an alarm with Microsoft Defender, but it was not installed from github, but updated automatically from within your program.



And btw, thanks for your program and the integration of 10bit and x265 long ago. It still covers most of my needs on a regular basis! :thanks:Itll be a false positive.

Sent from my SM-G986U1 using Tapatalk

[LoRd_MuldeR]

Might be the "Predictive machine learning" causing havoc, but it could also be that the installer on github is really infected. Can you please double-check, if it contains what you expect to be therein?

"Unknown threats, Predicative Machine Learning" says it all :D

(it's a fancy way of the "antivirus" vendor saying: If we can't find a real threat, then we make up one, 'cause well... somehow we need to justify those license fees you payed for our crapware)


Did you consider verifying the signature that I provide along with all of my release binaries in order to check the integrity and authenticity of the file you downloaded ???

If I do this, then the result looks like: https://i.imgur.com/lXAWtYS.png – which should answer your question ;)



* Replaced GnuPG by CodeSign for checking the auto-update signatures
Is this change maybe the evil that triggers the scanners?

Yes, I'm so evil that I even wrote my own program (https://gitlab.com/lord_mulder/codesign) (based on OpenSSL and released under a Public Domain license) for signing/verifying my release binaries :p

https://i.imgur.com/pcUUBII.png

[coocooc]

Looks like this here, using the .sig2 file:
https://imgur.com/a/qSxbgxo

Do I understand this correctly, that I am missing your public key? I however cannot find it on a key server searching for "mulder2@gmx.de". Is there something I need to do with the .rsa file you also offer in the download section?

[Edit]
Ok, I found your public key on www.muldersoft.com. Maybe you can add a link "Public Key" on the top of your page? I didn't expect the key down there after all the 3rd party tools. :-)

I trusted your key based on the same ID, that I saw on your screenshot above. Is the fingerprint published anywhere?

Is the .rsa file only useful in combination with your CodeSign tool? Kleopatra could not import the RSA key published on muldersoft.com, neither saved as .pem nor as .der file.

Ah, and the downloaded file passed the verification, so it was not hacked for some time. So the virus scanner alarm was a false positive.

[LoRd_MuldeR]

Ok, I found your public key on www.muldersoft.com. Maybe you can add a link "Public Key" on the top of your page? I didn't expect the key down there after all the 3rd party tools. :-)
Also here (https://sourceforge.net/projects/muldersoft/files/lord_mulder.pgp_public_key.v2.asc/download) and here (http://tricksoft.de/lord_mulder.pgp_public_key.v2.asc). Anyway, maybe I will make the public keys more prominent on the website :o

I trusted your key based on the same ID, that I saw on your screenshot above. Is the fingerprint published anywhere?
It's on the website, right above the actual PGP key outline ;)

But be aware that the website shows the full fingerprint, whereas the Kleopatra screenshot only shows a "truncated" fingerprint (last 16 hex digits).

Kleopatra could not import the RSA key published on muldersoft.com, neither saved as .pem nor as .der file.
The RSA public key is provided in the standard OpenSSL/PEM format. This is not a GPG key/certificate though, so GnuPG/Kleopatra cannot import it. The OpenSSL command-line tool can work with such files:
https://www.openssl.org/docs/man1.1.1/man1/rsa.html

Is the .rsa file only useful in combination with your CodeSign tool?
It's a "raw" RSA signature value, encoded in the Base64 format. Probably the easiest way to verify it is by using the CodeSign tool. OpenSSL should work too:
https://pagefault.blog/2019/04/22/how-to-sign-and-verify-using-openssl/

(though OpenSSL's "dgst" command requires the signature value in binary form for verification, not Base64, so you'd have to decode it first, e.g. using OpenSSL's "enc" command)

[coocooc]

It's on the website, right above the actual PGP key outline ;)


This can only be explained with my black&white colour blindness ... :-)

Thanks for your explanations, I will try them when being back at work.

[LoRd_MuldeR]

Simple x264/x265 Launcher v3.02
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v3.02

Version 3.02 [2022-06-16]
* Updated x264 to revision 3094 (API v164)
* Updated x265 to version 3.5+37
* Updated NVEncC to version 6.05
* Updated build environment to Visual Studio 2022 with Update-2

[writemaster]

hi LoRd_MuldeR

When will AV1 encoder be added to Simple x264/x265 Launcher?

[tyler durdan]

Can someone give me a guide on this please?

I normally use Staxrip where I just drop the mkv in and i'm good to go.
It seems you cant do that with this one

I cant figure out how to get a valid file for it to work with

I tried splitting the video out with mkvcleaver but still no luck

Can someone help please?

[Emulgator]

What happens if you use .avs script input and preview that in AvsPmod?
LWLibavVideoSource("C:\myfile.mkv")

[almosely]

https://www.directupload.eu/file/d/8604/lpub6q7o_png.htm

... the forced update message is popping up since a few days but I can't do anything to stop that ...

[almosely]

https://www.directupload.eu/file/d/8611/63q8bceo_png.htm

https://www.directupload.eu/file/d/8611/qsj5klgq_png.htm

Now the web-server responds: There's no update available. This should be fine now, but is not: The update notification is repeating at every start, telling me that my version is more than 12 months old.

[rsotome]

Yeah, constant forced "check for update" message & queue no longer saves jobs when you restart.

Could you please maybe look into removing the update requirement & the queue bug?

Thank you.

[LoRd_MuldeR]

Simple x264/x265 Launcher v3.04
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v3.04

Version 3.04 [2024-07-14]
* Updated x264 to revision 3191 (API v164)
* Updated x265 to version 3.6+13
* Support for latest VapourSynth versions that no longer support the '--y4m' switch
* Updated cURL to version 8.8.0 (2024-05-22)
* Updated build environment to Visual Studio 2022 with Update-10

[TP2222]

Thanks for Simple x264/x265 Launcher! I have been using it for many years and am very happy!

[Forteen88]

Thanks. How do I use it with the newest x265-4.1+54 version though?

[TP2222]

Thanks. How do I use it with the newest x265-4.1+54 version though? Rename x265-4.1+54 to x265_x64.exe Send to MuldeR -> Simple x264 Launcher v2 -> toolset -> x64.

[Forteen88]

@TP2222
Thanks, but I did that and Simple Launcher couldn't start the x265 encoding (had some "error"). Maybe I had some unusual setting. It used to work well before on older versions.