You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(a). Adding a GPU-based encoder, specifically NVENC, configurable with presets and the global GPU selection option, and;
(b). Most importantly, a GPU-based filter, such as scale_cuda, scale_npp, and yadif_cuda (targeting NVIDIA-based systems) would greatly eliminate the single largest performance bottleneck. CPU-bound scaling and deinterlacing is expensive, consuming precious CPU cycles that eventually lower transcode density per target host.
A good primer on what's possible with this addition can be found here.
The text was updated successfully, but these errors were encountered:
On Sat, 26 Sep 2020, 02:54 John, ***@***.***> wrote:
Thank you for your interest and forwarding information about NVENC. I will
certainly review it and see if it is something I can get integrated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR7NB6P6GYBIP74EGJEOXLSHUUSPANCNFSM4RSMUUPA>
.
Hello there,
Looking at how transcoding is being called up:
(a). Adding a GPU-based encoder, specifically NVENC, configurable with presets and the global GPU selection option, and;
(b). Most importantly, a GPU-based filter, such as scale_cuda, scale_npp, and yadif_cuda (targeting NVIDIA-based systems) would greatly eliminate the single largest performance bottleneck. CPU-bound scaling and deinterlacing is expensive, consuming precious CPU cycles that eventually lower transcode density per target host.
A good primer on what's possible with this addition can be found here.
The text was updated successfully, but these errors were encountered: