The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once



This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

using cuvid in hwaccell ffmpeg
#1
hi,

i am trying to set the ffmpeg hw accel to use cuvid instead of dxva2.
can you add a configuration for it that i can select cuvid for nvidia card ?
Reply
#2
will look into it
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
(29.06.2018, 04:39)Selur Wrote: will look into it

thx
Reply
#4
I did send you a link to a dev version which allows to set 'cuvid' in ffmpeg hwaccel settings.
-> Did you test it?
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
(29.06.2018, 18:27)Selur Wrote: I did send you a link to a dev version which allows to set 'cuvid' in ffmpeg hwaccel settings.
-> Did you test it?

yes, working fine, but my GPU is not able to decode HEVC even with cuvid (860M feature set E - hybrid decoding) :

FFmpeg : cuvid hwaccel requested for input stream #0:0, but cannot be initialized.


but thanks ...

looks like cuvid is broken in my drivers as even AVC is stopping with same error ...
Reply
#6
Ah okay.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#7
(29.06.2018, 19:31)Selur Wrote: Ah okay.

Cu Selur

I have feature set H. Maybe I can test it better.
Reply
#8
.. I already send you a link to the dev version via PM before you posted this, you just didn't check your PMs,...
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#9
(04.07.2018, 04:54)Selur Wrote: .. I already send you a link to the dev version via PM before you posted this, you just didn't check your PMs,...

Hi!

I tested the new version.

During the installation an nvenc file is missing, which is not problem if you did not uninstall the previous version.

The Cuvid decoder is faster than the DXVA2 in Hybrid (80 fps vs. 40-50 fps in 1080p@24 Blu-ray and 1080p@24 HEVC materials) but it was not so fast like the "NVENC Cuda" and "NVENC native" decoders (over 500 FPS ) in StaxRip.  Staxrip had a GPU usage around 98%-100%  for the NVENC (AVC and HEVC encoding) + GPU decoding while Hybrid used the "VPE engine" only between 15%-25% for NVENC HEVC and AVC decoding and encoding. I monitored it in the "sensor panel of the  "GPU-Z" GPU information software, where you can see the usage of all important components of your VGA card. So Hybrid did not really use the card efficiently, while StaxRip used it to the max (99)

After the PC tests, I will make my "Laptop tests" too.

I think you can implement these faster decoders too in the Hybrid, because they work well with Avisynth V.synth and FFMPEG too.

Maybe, if you examine StaxRip, you can see and figure out how did they implemented them to their software. Can't you?
Reply
#10
Quote:Maybe, if you examine StaxRip, you can see and figure out how did they implemented them to their software. Can't you?
Had a quick look, don't see how StaxRip should be faster when avs or vpy is used.
In case neither Avisynth nor Vapoursynth is used StaxRip seems to use (https://github.com/stax76/staxrip/blob/m...g/NVEnc.vb):
Quote: --avhw [<string>] use libavformat + cuvid for input
this enables full hw transcode and resize.
avhw mode could be set as a option
- native (default)
- cuda
and feeds NVEnc directly with the source, so no surprise.
No clue whether I add support for this, since I don't have the time atm. to try to figure out which inputs NVEncC supports directly.
-> might come but probably not any time soon, since I still have a long list of bug to fix and bugs have priority over new features.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)