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 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. > So far, there was no need to add explicit checks for SDK 9.1, but > that > will be required for this. > Also, since SDK 8.0 is effectively dead, it can be dropped. > > I immediately bump the version on ffnvcodec git after every release, > so > the correct versions to check for in configure right now are: > 9.1.23.1, 9.0.18.3, 8.2.15.10 and 8.1.24.11 > > I'm not sure I understand this. As I see - ffmpeg wouldn't compile > without the latest version of ffnvcodec, which would be 9.1.23.2 > after > the change is merged, so this is the only check that needs to be > performed, regardless of the supported Video SDK versions, isn't it? > > ffmpeg will compile with the latest version of each Video SDK Version > track. > _______________________________________________ > 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 "unsubscribe". > > >
_______________________________________________ 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 "unsubscribe".
