Hello, nice to meet you.

>Wouldn't it make sense to transition from compile time version checks to 
>runtime checking?
Video Codec SDK headers are not included into ffmpeg 'as is' but using the 
nvcodec-headers project instead.
This is community-driven project which aims to work around the licensing 
policies.
So we can't influence ffmpeg development too much and only supports it's 
development with patches.
Changing compile-time checks with runtime checks is a big thing to do and in 
order to convince community to accept such changes we need to have very solid 
background.

________________________________
От: Soft Works <[email protected]>
Отправлено: 30 июня 2020 г. 17:35
Кому: FFmpeg development discussions and patches <[email protected]>; 
Roman Arzumanyan <[email protected]>
Копия: Yogender Gupta <[email protected]>
Тема: RE: [FFmpeg-devel] [PATCH] avcodec/nvenc: Video Codec SDK 10 features 
support

External email: Use caution opening links or attachments


> -----Original Message-----
> From: ffmpeg-devel <[email protected]> On Behalf Of
> Roman Arzumanyan
> Sent: Tuesday, June 30, 2020 4:08 PM
> To: [email protected]; timo <[email protected]>
> Cc: Yogender Gupta <[email protected]>
> Subject: [FFmpeg-devel] [PATCH] avcodec/nvenc: Video Codec SDK 10
> features support
>
> Hello,
>
> This patch adds Video Codec SDK 10 features support:
>
>   *   Presets and tuning info
>   *   Multipass encode modes
>   *   Low Delay Key Frame Scale

Hi Roman, Yogender,

great to see somebody from Nvidia here. I think it's been a while.. :-)

I have a rather general question: Wouldn't it make sense to transition
from compile time version checks to runtime checking?
(like Intel does..)

We're currently stuck at SDK 8.1 because otherwise it would break
functionality for customers having devices for which no newer drivers
are available.

Regards
softworkz
_______________________________________________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".

Reply via email to