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.

[INFO] CUDA proc
#4
Quote:"config / input / use gpu for decoding"
the tool-tip states:
Quote:Use gpu decoding:
When enabled Hybrid will add '-hwaccel auto' to ffmpeg decoding calls.

This option has no effect if the selected hwaccel is not available or not supported by the chosen decoder (only mpeg-2, H.264, VC-1 and WMV3 content are supported atm.).
Note that most acceleration methods are intended for playback and will not be faster than software decoding on modern CPUs. Additionally, ffmpeg will usually need to copy the decoded frames from the GPU memory into the system memory, resulting in further performance loss. So this option might not provide any additional speed and thus is mainly useful for testing.

Warning:
Only enable if your ffmpeg version and your Hardware does support DXVA2 (on Windows) or VDPAU/VDA (on Linux/Unix).
the important part is here to ffmpeg decoding calls, so as soon as Avisynth or Vapoursynth is used that option doesn't do anything.

That said, depending on what you do there are multiple ways to use the gpu:
  • "Config->Input->Decoding->Use gpu for decoding" will tell Hybrid to use hardware decoding in case neither Avisynth nor Vapoursynth  (or DVDiInput) is used
  • "x264->Misc->Main->OpenCL" enabled x264s openCL based motion estimation (doesn't help much on most systems)
  • Depending on your drivers and GPU capabilities Hybrid offers you 'NVEnc' and 'NCEnc (ffmpeg)' (<-experimental) as encoders. Depending on you GPU NVEnc will support H.264 and H.265 encoding. When using NVEncC and no Avisynth or Vapoursynth filtering is needed, you can also use the options under NVEnc->Filtering.
  • When using Avisynth (32bit) filters, some filters allow gpu assistance, which is usually enabled through a 'gpu' or 'opencl' option and there are also filters like NLMeansCL2, KNLMeans, fft3dgpu which are gpu based. In case you own DGDecNV from Donald Graft it can also be used through Hybrid as a source filter (you need to copy your DGDecNV files and your license.txt file into the Hybrid/32bit/avisynthPlugins-folder to use it). Additionally there is FRIM which is also a gpu based source filter.
  • When using Vapoursynth (64bit), like for Avisynth there a bunch of filters which are either GPU based or GPU assisted (again 'gpu' or 'opencl' option).

Cu Selur
Reply


Messages In This Thread
CUDA proc - by weyb06 - 11.09.2018, 14:08
RE: CUDA proc - by Selur - 11.09.2018, 15:31
RE: CUDA proc - by weyb06 - 11.09.2018, 16:35
RE: CUDA proc - by Selur - 11.09.2018, 16:47
RE: CUDA proc - by weyb06 - 12.09.2018, 10:51
RE: CUDA proc - by Selur - 12.09.2018, 16:03
RE: CUDA proc - by weyb06 - 12.09.2018, 17:44
RE: CUDA proc - by Selur - 12.09.2018, 17:49
RE: CUDA proc - by weyb06 - 13.09.2018, 09:00
RE: CUDA proc - by Selur - 13.09.2018, 15:54
RE: CUDA proc - by weyb06 - 13.09.2018, 20:52
RE: CUDA proc - by Selur - 13.09.2018, 20:56
RE: CUDA proc - by weyb06 - 13.09.2018, 22:11
RE: CUDA proc - by Selur - 14.09.2018, 05:26
RE: CUDA proc - by weyb06 - 14.09.2018, 08:54
RE: CUDA proc - by weyb06 - 15.09.2018, 09:57
RE: CUDA proc - by Selur - 15.09.2018, 11:16

Forum Jump:


Users browsing this thread: 2 Guest(s)