applied with some changes regarding flags and device flags
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "un
On Wed, Nov 20, 2019 at 12:48 PM Timo Rothenpieler
wrote:
>
> On 20/11/2019 11:29, Oleg Dobkin wrote:
> > On Tue, 2019-11-19 at 23:58 +0100, Timo Rothenpieler wrote:
> >> Only thing I'm still wondering is if it would make sense to use the
> >> primary context by default.
> >> I can't think of any
On 20/11/2019 11:29, Oleg Dobkin wrote:
On Tue, 2019-11-19 at 23:58 +0100, Timo Rothenpieler wrote:
Only thing I'm still wondering is if it would make sense to use the
primary context by default.
I can't think of any obvious downsides, other than weakened
isolation,
which really shouldn't be a h
On Tue, 2019-11-19 at 23:58 +0100, Timo Rothenpieler wrote:
> Only thing I'm still wondering is if it would make sense to use the
> primary context by default.
> I can't think of any obvious downsides, other than weakened
> isolation,
> which really shouldn't be a huge concern.
> And there appare
On 19.11.2019 17:42, Oleg Dobkin wrote:
Any more comments?
Only thing I'm still wondering is if it would make sense to use the
primary context by default.
I can't think of any obvious downsides, other than weakened isolation,
which really shouldn't be a huge concern.
And there apparently ar
Any more comments?
On Mon, 2019-11-18 at 15:39 +0200, Oleg Dobkin wrote:
> Updated
>
> On Mon, 2019-11-18 at 13:51 +0100, Timo Rothenpieler wrote:
>
> On 18/11/2019 12:25, Oleg Dobkin wrote:
>
> FFmpeg supports multiple tracks of the Video Codec SDK, to support
> older
> drivers and legacy GPUs
Updated
On Mon, 2019-11-18 at 13:51 +0100, Timo Rothenpieler wrote:
> On 18/11/2019 12:25, Oleg Dobkin wrote:
>
> FFmpeg supports multiple tracks of the Video Codec SDK, to support
> older
> drivers and legacy GPUs that way.
> Since the version number only tracks the Video SDK Version, and not
>
Add AVCUDADeviceContextFlags to control the creation of CUDA device
context for the hardware CUDA decoder.
The current values are 0 (default behavior) - new context will be
created for each decoder, and 1 - primary CUDA context will be used.
There are several reasons for using primary device cont
On 18/11/2019 12:25, Oleg Dobkin wrote:
FFmpeg supports multiple tracks of the Video Codec SDK, to support
older
drivers and legacy GPUs that way.
Since the version number only tracks the Video SDK Version, and not
the
CUDA loader version, what needs to be done is to set the new minimum
version f
> FFmpeg supports multiple tracks of the Video Codec SDK, to support
> older
> drivers and legacy GPUs that way.
> Since the version number only tracks the Video SDK Version, and not
> the
> CUDA loader version, what needs to be done is to set the new minimum
> version for each supported track.
On 18/11/2019 11:51, Oleg Dobkin wrote:
I've changed enum into a flag and moved it into
AVCUDADeviceContextInternal.
Can't one just call cuCtxGetDevice on the context to get the device?
Not sure the cuCtxGetDevice can be used for the primary context; also,
according to documentation it return
On Sun, 2019-11-17 at 23:31 +0100, Timo Rothenpieler wrote:
> On 17.11.2019 15:58, Oleg Dobkin wrote:
>
> Add AVCUDADeviceContextFlags to control the creation of CUDA device
> context for the hardware CUDA decoder.
>
> The current values are 0 (default behavior) - new context will be
> created fo
On Mon, 2019-11-18 at 12:51 +0200, Oleg Dobkin wrote:
> I've changed enum into a flag and moved it into
> AVCUDADeviceContextInternal.
>
>
> Can't one just call cuCtxGetDevice on the context to get the device?
>
> Not sure the cuCtxGetDevice can be used for the primary context;
> also,
> accordi
I've changed enum into a flag and moved it into
AVCUDADeviceContextInternal.
> Can't one just call cuCtxGetDevice on the context to get the device?
Not sure the cuCtxGetDevice can be used for the primary context; also,
according to documentation it returns device id not handle. Anyway, is
it that
Add AVCUDADeviceContextFlags to control the creation of CUDA device
context for the hardware CUDA decoder.
The current values are 0 (default behavior) - new context will be
created for each decoder, and 1 - primary CUDA context will be used.
There are several reasons for using primary device cont
On 17.11.2019 15:58, Oleg Dobkin wrote:
Add AVCUDADeviceContextFlags to control the creation of CUDA device
context for the hardware CUDA decoder.
The current values are 0 (default behavior) - new context will be
created for each decoder, and 1 - primary CUDA context will be used.
There are sev
Add AVCUDADeviceContextFlags to control the creation of CUDA device
context for the hardware CUDA decoder.
The current values are 0 (default behavior) - new context will be
created for each decoder, and 1 - primary CUDA context will be used.
There are several reasons for using primary device cont
17 matches
Mail list logo
