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

[tormento]

Originally Posted by LoRd_MuldeR

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]

Originally Posted by tormento

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...ases/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, which fixed the issue!

[redbtn]

Big thanks for new release!

[LoRd_MuldeR]

Simple x264/x265 Launcher v2.98
https://github.com/lordmulder/Simple...ases/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]

Originally Posted by LoRd_MuldeR

Simple x264/x265 Launcher v2.98

I love dark mode.

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

[LoRd_MuldeR]

Originally Posted by tormento

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

Not at this time. It's just a crude integration of 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...

Originally Posted by darkio

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]

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

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]

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

I 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 is newer: x264 r3027 from october.
Is it still get update?

Regards
szabi

[LoRd_MuldeR]

Originally Posted by szabi

The latest included x264 version is r3009 from june, however official one 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...ases/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]

Originally Posted by LoRd_MuldeR

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.



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]

Originally Posted by LoRd_MuldeR

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]

[Pauly Dunne]

Originally Posted by LoRd_MuldeR

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.