> Yes, this is a simpler logic. Works for me locally. Can you please apply this
> patch to ffmpeg master. Thanks.
Applied
We also discovered a case where this patch is necessary to successfully
use multiple GPUs at all.
A user asked in #ffmpeg about nvenc getting stuck when one GPU is at
full l
@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/nvenc.c Reduce initialization
time for gpu id > 0
Made this into a patch:
https://github.com/BtbN/FFmpeg/commit/cbd128a67fc4621c953419dddc5cc17612764a57
___
ffmpeg-devel mailing list
ffmpeg-de
Made this into a patch:
https://github.com/BtbN/FFmpeg/commit/cbd128a67fc4621c953419dddc5cc17612764a57
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Seems like a good idea to run the full set of capability checks only on
the device that's actually about to be used.
The only issue I see is that if a system has a bunch of different GPUs,
of which some don't support the required capabilities, one might get
unexpected results with the device indice
Hi,
The attached patch reduces initialization time when using a gpu device > 0 in a
multi-gpu setup. It removes the initialization of cuda context and nvenc
session for gpus which are not requested by the user, thereby increasing
startup performance. This is my first time sending a patch to ff
