Re: [FFmpeg-devel] [PATCH] ffprobe: Initialize coded_width/height

> > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On > Behalf > > Of Hendrik Leppkes > > Sent: Friday, January 19, 2018 6:10 PM > > To: FFmpeg development discussions and patches > > > > Subject: Re: [FFmpeg-devel] [PATCH] ffprobe: Initialize > >

Re: [FFmpeg-devel] [PATCH] docs/codecs: remove dead codec debug options

Ping. x2. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/hevc_ps: Check log2_sao_offset_scale_*

On Wed, 24 Jan 2018 23:42:44 -0300 James Almer wrote: > On 1/24/2018 11:03 PM, Michael Niedermayer wrote: > > On Wed, Jan 24, 2018 at 12:47:18AM -0300, James Almer wrote: > >> On 1/24/2018 12:34 AM, Michael Niedermayer wrote: > >>> Fixes:

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/hevc_ps: Check log2_sao_offset_scale_*

On 1/24/2018 11:03 PM, Michael Niedermayer wrote: > On Wed, Jan 24, 2018 at 12:47:18AM -0300, James Almer wrote: >> On 1/24/2018 12:34 AM, Michael Niedermayer wrote: >>> Fixes: 4868/clusterfuzz-testcase-minimized-6236542906400768 >>> Fixes: runtime error: shift exponent 126 is too large for 32-bit

Re: [FFmpeg-devel] [PATCH] avformat/opensrt: add Haivision Open SRT protocol

On 16-Jan-18 09:43, Michael Niedermayer wrote: if you will maintain this code then you may want to include a change to the MAINTAINERs file also does anyone have any more comments on this patch ? it seems to have not gotten much attention recently. There where reviews/comments a few months ago

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

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/hevc_ps: Check log2_sao_offset_scale_*

On Thu, 25 Jan 2018 03:26:51 +0100 Michael Niedermayer wrote: > On Wed, Jan 24, 2018 at 04:42:38AM +0100, wm4 wrote: > > On Wed, 24 Jan 2018 04:34:49 +0100 > > Michael Niedermayer wrote: > > > > > Fixes:

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/hevc_ps: Check log2_sao_offset_scale_*

On Wed, Jan 24, 2018 at 04:42:38AM +0100, wm4 wrote: > On Wed, 24 Jan 2018 04:34:49 +0100 > Michael Niedermayer wrote: > > > Fixes: 4868/clusterfuzz-testcase-minimized-6236542906400768 > > Fixes: runtime error: shift exponent 126 is too large for 32-bit type 'int' > > >

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/hevc_ps: Check log2_sao_offset_scale_*

On Wed, Jan 24, 2018 at 12:47:18AM -0300, James Almer wrote: > On 1/24/2018 12:34 AM, Michael Niedermayer wrote: > > Fixes: 4868/clusterfuzz-testcase-minimized-6236542906400768 > > Fixes: runtime error: shift exponent 126 is too large for 32-bit type 'int' > > > > Found-by: continuous fuzzing

Re: [FFmpeg-devel] [PATCH] avdevice/decklink_dec: Extract 1080i and NTSC VANC

On Tue, Jan 23, 2018 at 9:07 AM Devin Heitmueller < dheitmuel...@ltnglobal.com> wrote: > Hi Ray, > > > On Jan 22, 2018, at 11:20 PM, Ray Tiley wrote: > > > > I'm reading 334-1:2017 Sec 4 > > "When the ANC packets defined in this standard are carried in a high > > definition

Re: [FFmpeg-devel] [PATCH 1/3] avformat/mov: Increase support for common encryption.

On Wed, Jan 24, 2018 at 11:43:26AM -0800, Jacob Trimble wrote: > On Mon, Jan 22, 2018 at 7:38 PM, Michael Niedermayer > wrote > > [...] > >> This removes support for saio/saiz atoms, but it was incorrect before. > >> A follow-up change will add correct support for those. >

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

2018-01-25 0:44 GMT+01:00 Ben Chang : > 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

[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.

[FFmpeg-devel] [PATCH] avfilter/vf_transpose: Fix used plane count.

Fixes out of array access Fixes: poc.mp4 Found-by: GwanYeong Kim Signed-off-by: Michael Niedermayer --- libavfilter/vf_transpose.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/libavfilter/vf_transpose.c

Re: [FFmpeg-devel] [PATCH V2 1/3] lavfi/vf_xxx_vaapi: fix typo.

2018-01-24 4:04 GMT+01:00 Jun Zhao : > V2: split the patches as carl's comments Pushed. Thank you, Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/3] avformat/mov: Increase support for common encryption.

On Mon, Jan 22, 2018 at 7:38 PM, Michael Niedermayer wrote > [...] >> This removes support for saio/saiz atoms, but it was incorrect before. >> A follow-up change will add correct support for those. > > This removal should be done by a seperate patch if it is done. > diff

Re: [FFmpeg-devel] [PATCH] fate: add id3v2 tests

On Tue, Jan 23, 2018 at 6:15 PM, James Almer wrote: > > > ffprobe -show_format is probably best for an id3v2 tag. Add a new > probeformat() function to fate-run.sh like > > probeformat(){ > run ffprobe${PROGSUF} -show_format -v 0 "$@" > } > > Then call it with the sample in

Re: [FFmpeg-devel] [PATCH] avcodec/hevc_parser: use ff_hevc_decode_extradata() to parse extradata

On 1/20/2018 3:00 PM, James Almer wrote: > On 1/20/2018 1:12 AM, James Almer wrote: >> Signed-off-by: James Almer >> --- >> libavcodec/hevc_parser.c | 21 + >> 1 file changed, 9 insertions(+), 12 deletions(-) >> >> diff --git a/libavcodec/hevc_parser.c

Re: [FFmpeg-devel] [PATCH V2 2/3] lavfi/procamp_vaapi: fix the green video issue if without arguments.

2018-01-24 4:04 GMT+01:00 Jun Zhao : > -procamp_params[i].type = VAProcFilterColorBalance; > -procamp_params[i].attrib = VAProcColorBalanceBrightness; > -procamp_params[i].value = map(ctx->bright, BRIGHTNESS_MIN, > BRIGHTNESS_MAX, > -