Re: [FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

Hi, Do we have a conclusion on whether this patch can be pushed in? Thanks, Ben On Tue, Jan 30, 2018 at 4:25 PM, Ben Chang wrote: > > > On Fri, Jan 26, 2018 at 3:10 PM, Mark Thompson wrote: > >> On 26/01/18 20:51, Ben Chang wrote: >> > On Fri, Jan 26, 2018 at 3:

Re: [FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

On Fri, Jan 26, 2018 at 3:10 PM, Mark Thompson wrote: > On 26/01/18 20:51, Ben Chang wrote: > > On Fri, Jan 26, 2018 at 3:32 AM, Mark Thompson wrote: > > > >> On 26/01/18 09:06, Ben Chang wrote: > >>> Thanks for the review Mark. > >>> > > T

Re: [FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

On Fri, Jan 26, 2018 at 3:32 AM, Mark Thompson wrote: > On 26/01/18 09:06, Ben Chang wrote: > > Thanks for the review Mark. > > > > There are some cuda kernels in the driver that may be invoked depending > on > > the nvenc operations specified in the commandline. M

Re: [FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

Thanks for the review Mark. On Thu, Jan 25, 2018 at 4:13 PM, Mark Thompson wrote: > > > diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c > > index 4a91d99..2da251b 100644 > > --- a/libavcodec/nvenc.c > > +++ b/libavcodec/nvenc.c > > @@ -420,6 +420,12 @@ static av_cold int nvenc_check_device(A

Re: [FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

>Just use another provider like gmail. Done. Patch-wise, is it approved? Thanks, Ben ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

Thanks for the review Carl. > This looks as if your commit message spans several lines, should be one line > followed by an empty line and as many more lines as you need. Fixed. Reattaching. > Is there a reason why the error messages are different? I am following the current convention of cuda e

[FFmpeg-devel] [PATCH]: Change Stack Frame Limit in Cuda Context

Hi, Please help review this patch to reduce stack frame size per GPU thread. The default allocation size per thread (1024 bytes) is excessive and can be reduced to 128 bytes based on nvidia cuda kernel compilation statistics. This should help with reducing video memory usage per cuda context.

Re: [FFmpeg-devel] [PATCH] NVENC Surface Allocation Reduction

Hi Timo, Thanks for the review. Attaching patch updated with your suggestions and answering some queries from previous email. >Did you test if and how much it affects performance to reduce the default >delay from 32 to 4? >This was originally done because nvenc is extremely slow if you try to

[FFmpeg-devel] [PATCH] NVENC Surface Allocation Reduction

[sorry for re-sending; but still looking for review. Thanks!] Hi, This patch aims to reduce the number of input/output surfaces NVENC allocates per session. Previous default sets allocated surfaces to 32 (unless there is user specified param or lookahead involved). Having large number of sur

[FFmpeg-devel] [Patch] NVENC Surface Allocation Reduction

Hi, This patch aims to reduce the number of input/output surfaces NVENC allocates per session. Previous default sets allocated surfaces to 32 (unless there is user specified param or lookahead involved). Having large number of surfaces consumes extra video memory (esp for higher resolution enco

[FFmpeg-devel] [PATCH] HDR Transcode VUI Info Copy

destroy all copies of the original message. --- HDR_transcode_VUI_copy.patch Description: HDR_transcode_VUI_copy.patch --- Begin Message --- On Fri, Mar 3, 2017 at 4:38 AM, Ben Chang wrote: > > In short, is there any

[FFmpeg-devel] HEVC Video Transcode Transfer VUI, SEI Information

Hi, I posted a query regarding HDR transcode on the user forum a few weeks earlier and did not get a very clear answer; re-posting here in devel to see if I can gain more insight (sorry about duplication). >I was wondering if ffmpeg supports transfer of VUI and SEI info between an >original bi