Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
17th December 2019, 11:09 | #341 | Link |
Registered User
Join Date: Oct 2001
Posts: 454
|
I gave myself a christmas present and got a RTX 2060. First tests with NVENC in different GUIs give me good enough quality for my 1080p recodes when speed is important (around 140fps).
So far, I only used default settings. Like pacuro, I was wondering what settings I could use to max out quality (enabling b-frames gave me a bigger filesize than defaults in hybrid). Is there some detailied documentation of the NVENC in RTX Cards I could look into? |
29th December 2019, 07:41 | #342 | Link |
Registered User
Join Date: Oct 2001
Posts: 416
|
I'm using this command line app and it has very nice quality and I also get around 150fps for 1080p, about 50fps for 4k
https://github.com/rigaya/NVEnc Is John still around the forums? I saw his settings somewhere, he was using Staxrip. |
14th March 2020, 10:11 | #343 | Link |
Registered User
Join Date: Sep 2015
Location: Opole, Poland
Posts: 20
|
@ReinerSchweinlin you probably doing something wrong if enabling B-frames makes your encodes bigger. In my case just enabling b-frames + b as ref each makes files lighter - as it should be in theory.
__________________
LIT BRO: i5-9500, Z370, RTX2060 BIG BRO: i5-10500, H570, GTX1660S HTPC: i7-11700K, Z570, Topping D10s • MPC-HC + LAV, foobar2000 Last edited by pacuro; 14th March 2020 at 10:18. |
18th April 2020, 14:30 | #344 | Link |
Registered User
Join Date: Feb 2003
Posts: 68
|
These are the settings I'm using and my 720p encodes are always a few hundred MB larger than similar shows from the scene HEVC encodes. Does anyone have any suggestions for better settings please? Thank you.
--cqp 18:20:22 --codec h265 --preset quality --level 5.1 --output-depth 10 --qp-init 20 --qp-max 22 --qp-min 18 --max-bitrate 5000 --aq --aq-temporal --gop-len 240 --lookahead 16 --slices 2 --multiref-l0 4 --multiref-l1 4 --strict-gop --nonrefp --weightp |
20th April 2020, 02:06 | #345 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
|
|
20th April 2020, 05:38 | #346 | Link | |
Registered User
Join Date: May 2009
Posts: 328
|
Quote:
|
|
22nd April 2020, 19:48 | #347 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
GPU encoding is great for things like Twitch where it is recording screen activity while gaming. It takes minimal CPU away from the game, and is able to use the frames in the GPU as source without having to copy the pixels to main memory. Just writing 4Kp60 RGB frames to the CPU on top of everything else further stresse the memory bandwidth. It's also good for very low power embedded solutions where a Tegra or Atom processor can be used with little CPU but with a HW encoder available. There's been work done on hybrid encoders, which use the GPU for the first pass to be refined in software, which can speed up encoding 20-25%. |
|
29th November 2020, 00:41 | #348 | Link |
Registered User
Join Date: Sep 2011
Posts: 362
|
I'm currently testing Quicksync on Iris Xe LP. Compared to Gen9.5 they have greatly improved the fixed function encoder, both quality and speed. On Gen9.5 graphics the fully fixed function encoder was more or less useless (no b-pyramid, no bframes), means the hybrid was the better choice and for H265 Gen9.5 didn't even support FF. On Iris Xe LP I don't really see a quality difference between hybrid and the fully fixed function (H265) encode, the difference is minor I would say but the speed difference is really huge. So at this point it makes the h265 hybrid somehow obsolete.
|
29th November 2020, 05:32 | #349 | Link | |
Registered User
Join Date: May 2009
Posts: 328
|
Quote:
|
|
29th November 2020, 11:51 | #350 | Link | |
Registered User
Join Date: Sep 2011
Posts: 362
|
Quote:
As for the hardware encoder it doesn't matter, it just needs the graphics driver, it has all the required files. The Media SDK is required for the software encoder. |
|
29th November 2020, 22:46 | #351 | Link |
Registered User
Join Date: Sep 2011
Posts: 362
|
I finished my Tigerlake speed test and also some other results just for reference. QSVEnc/NVEnc (h265) used for the GPUs and Handbrake nightly for the x265 run. Test sample is a 1080p 24fps 25 Mbit video which is converted down to ~2500 Kbit.
Iris Xe LP 1100 Mhz GPU+fixed function CBR slowest= 68 fps CBR balanced= 131 fps CBR fastest= 226 fps Iris Xe LP 1100 Mhz fixed function CBR slowest= 260 FPS CBR balanced= 325 FPS CBR fastest= 507 FPS Iris Xe LP 1100 Mhz GPU+ fixed function CQP slowest= 75 fps CQP balanced= 144 fps CQP fastest= 263 fps Iris Xe LP 1100 Mhz fixed function CQP slowest= 271 fps CQP balanced= 344 fps CQP fastest= 518 fps For reference some other GPUs and x265 ultrafast: HD 630 1150 Mhz GPU + fixed function CBR slowest= 43 fps CBR balanced= 100 fps CBR fastest= 302 fps i7-1165G7 2800 Mhz (Turbo disabled) x265 ultrafast= 58 fps GTX 1080 2000 Mhz CBR quality= 317 fps CBR fastest= 502 fps Last edited by Yups; 29th November 2020 at 23:38. |
3rd December 2020, 13:53 | #353 | Link |
Registered User
Join Date: Sep 2011
Posts: 362
|
In this speed test NVENC quality is worse than Iris Xe but I will use different settings when I go for quality on both, for example I didn't use lookahead on NVENC and keep in mind this isn't Turing. I will do a quality comparison later and also I have to test Turing which I don't have for now. I'm testing on Iris Xe mainly at the moment. As for Iris Xe CQP is the best bitrate control method when it comes to quality, better than ICQ and much better than CBR/VBR. CQP works very good with many bframes+bpyramid on Iris Xe unlike ICQ.
|
3rd December 2020, 21:49 | #354 | Link | |
Registered User
Join Date: May 2009
Posts: 328
|
Quote:
|
|
5th December 2020, 01:06 | #355 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
|
|
5th December 2020, 13:57 | #356 | Link |
Registered User
Join Date: Apr 2018
Posts: 63
|
I am honestly surprised how much praise nvenc gets "around the internet"
The H.264 encoder certainly isn't bad for a hardware encoder, but people comparing it to x264 medium or even slow need to tone it down a notch. In a "non realtime" scenario with aq, slowest preset and full bframes it did not seem competitive to x264 medium preset in quality in some gaming footage I've tested |
6th December 2020, 02:22 | #357 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
It is from comparing it to the previous hardware encoders, Turing was a big upgrade.
It is actually somewhat watchable now! Credit where it is due.
__________________
madVR options explained |
6th December 2020, 16:39 | #359 | Link | |
ангел смерти
Join Date: Nov 2004
Location: Lost
Posts: 9,558
|
Quote:
|
|
6th December 2020, 16:46 | #360 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
No, the encoder is the same. Only the decoder was enhanced to support AV1.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
Thread Tools | Search this Thread |
Display Modes | |
|
|