Re: [FFmpeg-devel] [PATCH] ppc: replace vec_ld(0), vec_ld(1) by VEC_LD2() which has fewer loads

On Nov 13, 2014 4:15 PM, Michael Niedermayer michae...@gmx.at wrote: On Fri, Nov 07, 2014 at 03:12:19PM +0100, Michael Niedermayer wrote: This needs to be benchmarked, i do not have ppc hw This is on big endian more similar to how the code was before 79e0255956bc8fcdb143f39b2e45db77144ac017

Re: [FFmpeg-devel] [PATCH] ppc: replace vec_ld(0), vec_ld(1) by VEC_LD2() which has fewer loads

On 11/14/14 07:34, Michael Niedermayer wrote: On Fri, Nov 14, 2014 at 06:45:55AM -0700, Pavel Koshevoy wrote: On Nov 13, 2014 4:15 PM, Michael Niedermayer michae...@gmx.at wrote: On Fri, Nov 07, 2014 at 03:12:19PM +0100, Michael Niedermayer wrote: This needs to be benchmarked, i do not have

Re: [FFmpeg-devel] [PATCH] Add FFMPEG_VERSION into the binary libs

On 12/19/14 10:05, Michael Niedermayer wrote: This simplifies identifying from which revission a binary of a lib came from Signed-off-by: Michael Niedermayer michae...@gmx.at --- libavcodec/utils.c |3 +++ libavformat/utils.c |3 +++ 2 files changed, 6 insertions(+) diff --git

Re: [FFmpeg-devel] [PATCH] swresample: Add swr_get_out_samples()

On 6/2/15 16:22, Michael Niedermayer wrote: Signed-off-by: Michael Niedermayer michae...@gmx.at --- libswresample/resample.c| 17 + libswresample/swresample.c | 30 ++ libswresample/swresample.h | 14

Re: [FFmpeg-devel] [PATCHv3] avcodec: Add support for Closed Caption export in h264

On Thu, Jul 2, 2015 at 12:18 PM, Kieran Kunhya kier...@ob-encoder.com wrote: --- libavcodec/h264.c | 11 +++ libavcodec/h264.h | 2 ++ libavcodec/h264_sei.c | 35 ++- 3 files changed, 47 insertions(+), 1 deletion(-) diff --git

[FFmpeg-devel] vf_coreimage.m build failure on ppc osx 10.5

I tried to get a fresh build of ffmpeg today and ran into this issue: OBJCC libavfilter/vf_coreimage.o src/libavfilter/vf_coreimage.m: In function ‘config_output’: src/libavfilter/vf_coreimage.m:75: warning: ISO C90 forbids mixed declarations and code src/libavfilter/vf_coreimage.m: In function

Re: [FFmpeg-devel] [PATCH] Fix broken osx powerpc build

On Jul 12, 2016 05:14, "Ronald S. Bultje" wrote: > > Hi, > > On Mon, Jul 11, 2016 at 9:56 PM, Jing Yu > wrote: > > > .macro movrel rd, sym, gp > > +#ifdef __APPLE__ > > +ld \rd, \sym@got(r2) > > +#else > > ld \rd,

Re: [FFmpeg-devel] [PATCH] Fix broken osx powerpc build

\suffix\()_altivec >From 97965f39a23835b4ecba6b1ba8cd694452c69168 Mon Sep 17 00:00:00 2001 From: Pavel Koshevoy <pkoshe...@gmail.com> Date: Mon, 11 Jul 2016 22:38:55 -0600 Subject: [PATCH] Restore compatibility with powerpc-apple-darwin9-gcc-4.2.1 ... and attempt to preserve comp

Re: [FFmpeg-devel] [PATCH] Restore compatibility with powerpc-apple-darwin9-gcc-4.2.1

. On Thu, Jul 14, 2016 at 10:06 PM, <pkoshe...@gmail.com> wrote: > From: Pavel Koshevoy <pkoshe...@gmail.com> > > ... and attempt to preserve compatibility with clang that was > introduced in 311a953c76081fca99b872629d248f9d69ebc0c3 (untested) > --- > lib

[FFmpeg-devel] latest ffmpeg git master build is broken on osx powerpc

Hi, PowerPC build on OSX 10.5 (Leopard) is broken: $ gcc --version powerpc-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5577) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On Sun, Jan 22, 2017 at 9:37 AM, Pavel Koshevoy <pkoshe...@gmail.com> wrote: > On 01/22/2017 07:05 AM, Timo Rothenpieler wrote: >>> >>> Despite wm4 objections I am resubmitting this patch, because I can >>> find no other reasonable method for rejecting ffmpeg cu

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On 1/22/17 11:13 AM, Philip Langdale wrote: On Sat, 21 Jan 2017 10:27:30 -0700 pkoshe...@gmail.com wrote: From: Pavel Koshevoy <pkoshe...@gmail.com> Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a limited set of resolutions per codec are sup

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On 01/22/2017 04:58 AM, wm4 wrote: On Sat, 21 Jan 2017 10:35:50 -0700 Pavel Koshevoy <pkoshe...@gmail.com> wrote: On Sat, Jan 21, 2017 at 10:27 AM, <pkoshe...@gmail.com> wrote: From: Pavel Koshevoy <pkoshe...@gmail.com> -ret = cuvid_test_dummy_decoder(avctx, >c

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On 01/22/2017 05:28 AM, Mark Thompson wrote: On 21/01/17 17:35, Pavel Koshevoy wrote: On Sat, Jan 21, 2017 at 10:27 AM, <pkoshe...@gmail.com> wrote: From: Pavel Koshevoy <pkoshe...@gmail.com> Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On Sat, Jan 21, 2017 at 10:27 AM, <pkoshe...@gmail.com> wrote: > From: Pavel Koshevoy <pkoshe...@gmail.com> > > Evidently CUVID doesn't support decoding 422 or 444 chroma formats, > and only a limited set of resolutions per codec are supported. > > Unfortunatel

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On Sat, Jan 21, 2017 at 10:35 AM, Pavel Koshevoy <pkoshe...@gmail.com> wrote: > Despite wm4 objections I am resubmitting this patch, because I can > find no other reasonable method for rejecting ffmpeg cuvid decoder > when it can't handle a given video stream. An unreasonabl

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On Thu, Jan 12, 2017 at 10:32 AM, Timo Rothenpieler <t...@rothenpieler.org> wrote: > On 1/9/2017 7:22 PM, pkoshe...@gmail.com wrote: >> From: Pavel Koshevoy <pkoshe...@gmail.com> >> enum AVPixelFormat pix_

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: fix drift calculation, ticket #6157

On 02/18/2017 07:04 PM, Steven Liu wrote: 2017-02-19 6:46 GMT+08:00 <pkoshe...@gmail.com <mailto:pkoshe...@gmail.com>>: From: Pavel Koshevoy <pkoshe...@gmail.com <mailto:pkoshe...@gmail.com>> --- libavfilter/af_atempo.c | 6 +++--- 1 file cha

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: fix sound shake when change speed

On Feb 17, 2017 01:56, "Steven Liu" wrote: commandline: ./ffmpeg -i ~/Downloads/test.wav -af atempo=1.5 -acodec aac -y output.aac play the output.aac, the sound is very shake, terrible. after this patch， play the sound is smooth Signed-off-by: Steven Liu

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: fix sound shake when change speed

On Fri, Feb 17, 2017 at 1:55 AM, Steven Liu wrote: > commandline: > ./ffmpeg -i ~/Downloads/test.wav -af atempo=1.5 -acodec aac -y > output.aac > > play the output.aac, the sound is very shake, terrible. > after this patch， > play the sound is smooth > > Signed-off-by:

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: Make independent of the channel layout

On Sep 5, 2016 4:41 PM, "Michael Niedermayer" wrote: > > Signed-off-by: Michael Niedermayer > --- > libavfilter/af_atempo.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/libavfilter/af_atempo.c

Re: [FFmpeg-devel] [PATCH] lavc: Fix ticket 6024, truncated mode decoding

passes fate, but I don't do that often so someone might want to double-check Pavel. On Thu, Dec 15, 2016 at 10:19 AM, <pkoshe...@gmail.com> wrote: > From: Pavel Koshevoy <pkoshe...@gmail.com> > > The assumption that avcodec_send_packet makes regarding decoders > con

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: fix assertion failure on empty input

On Wed, Dec 14, 2016 at 7:27 PM, Marton Balint wrote: > Signed-off-by: Marton Balint > --- > libavfilter/af_atempo.c | 10 +++--- > 1 file changed, 7 insertions(+), 3 deletions(-) > > diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c > index

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: fix assertion failure on empty input

On Thu, Dec 15, 2016 at 3:31 AM, Marton Balint <c...@passwd.hu> wrote: > > > On Wed, 14 Dec 2016, Pavel Koshevoy wrote: > >> On Wed, Dec 14, 2016 at 7:27 PM, Marton Balint <c...@passwd.hu> wrote: >>> >>> Signed-off-by: Marton Balint <c...@p

Re: [FFmpeg-devel] [PATCH] Add fate test for ticket 6024, truncated decoding mode

On Sat, Dec 17, 2016 at 6:13 PM, Michael Niedermayer <mich...@niedermayer.cc> wrote: > On Sat, Dec 17, 2016 at 04:02:12PM -0700, pkoshe...@gmail.com wrote: >> From: Pavel Koshevoy <pkoshe...@gmail.com> >> >> --- >> tests/fate/video.mak| 3 +++ &

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

On 01/12/2017 10:32 AM, Timo Rothenpieler wrote: On 1/9/2017 7:22 PM, pkoshe...@gmail.com wrote: From: Pavel Koshevoy <pkoshe...@gmail.com> Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a limited set of resolutions per codec are supported. Given that

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video resolution

On Sun, Jan 1, 2017 at 6:00 PM, <pkoshe...@gmail.com> wrote: > From: Pavel Koshevoy <pkoshe...@gmail.com> > > NVDEC (CUVID) does not support unlimited video resolutions, so if the > resolution of the source is known it can be used during avcodec_open2 > call to fail

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video parameters

On Mon, Jan 2, 2017 at 2:26 PM, <pkoshe...@gmail.com> wrote: > From: Pavel Koshevoy <pkoshe...@gmail.com> > > Evidently CUVID doesn't support decoding 422 or 444 chroma formats, > and only a limited set of resolutions per codec are supported. > > Given that stre

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video parameters

On Sun, Jan 8, 2017 at 2:53 PM, Hendrik Leppkes wrote: > On Tue, Jan 3, 2017 at 8:26 AM, wrote: >> +ret = convert_to_cuda_video_chroma_format(avctx->pix_fmt, >> _chroma_format); >> +if (ret < 0) { >> +// pixel format is not supported:

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video resolution

On Mon, Jan 2, 2017 at 2:00 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Jan 3, 2017 07:52, "Pavel Koshevoy" <pkoshe...@gmail.com> wrote: > > On Mon, Jan 2, 2017 at 9:37 AM, Philip Langdale <phil...@overt.org> wrote: >> It is documented as

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video resolution

On Mon, Jan 2, 2017 at 3:08 PM, Pavel Koshevoy <pkoshe...@gmail.com> wrote: > On Mon, Jan 2, 2017 at 2:00 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: >> On Jan 3, 2017 07:52, "Pavel Koshevoy" <pkoshe...@gmail.com> wrote: >> >> On Mon, Jan 2, 20

Re: [FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video parameters

On Mon, Jan 9, 2017 at 3:12 AM, wm4 <nfx...@googlemail.com> wrote: > On Mon, 2 Jan 2017 14:26:45 -0700 > pkoshe...@gmail.com wrote: > >> From: Pavel Koshevoy <pkoshe...@gmail.com> >> +ret = convert_to_cuda_video_chroma_format(avctx->pix_fmt, >

Re: [FFmpeg-devel] [PATCH] Add fate test for ticket 6024, truncated decoding mode (v2)

On Dec 17, 2016 10:49 PM, <pkoshe...@gmail.com> wrote: From: Pavel Koshevoy <pkoshe...@gmail.com> --- tests/fate/video.mak| 3 +++ tests/ref/fate/mpeg2-ticket6024 | 27 +++ 2 files changed, 30 insertions(+) create mode 100644 tests/ref/fate/mpeg

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: Avoid false triggering an assertion failure

On Wed, Aug 30, 2017 at 2:00 PM, Marton Balint <c...@passwd.hu> wrote: > > On Mon, 19 Dec 2016, Marton Balint wrote: > >> >> On Sat, 17 Dec 2016, pkoshe...@gmail.com wrote: >> >>> From: Pavel Koshevoy <pkoshe...@gmail.com> >>> >>> S

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: Avoid false triggering an assertion failure

On 08/30/2017 03:01 PM, Pavel Koshevoy wrote: On Wed, Aug 30, 2017 at 2:00 PM, Marton Balint <c...@passwd.hu> wrote: On Mon, 19 Dec 2016, Marton Balint wrote: On Sat, 17 Dec 2016, pkoshe...@gmail.com wrote: From: Pavel Koshevoy <pkoshe...@gmail.com> Steps to reproduce: ./ffmpe

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: Avoid false triggering an assertion failure

On Sun, Sep 3, 2017 at 9:26 AM, Marton Balint <c...@passwd.hu> wrote: > > On Sun, 3 Sep 2017, Pavel Koshevoy wrote: > >> On 08/30/2017 03:01 PM, Pavel Koshevoy wrote: >> You can probably revert 4240e5b047379b29c33dd3f4438bc4e610527b83 -- I >> tried it loca

Re: [FFmpeg-devel] AMD external header

On Mon, Nov 27, 2017 at 8:25 AM, Nicolas George wrote: > Mironov, Mikhail (2017-11-27): >> #1 >>policy: do not include external headers >>goal: minimize maintenance efforts and increase stability of the project >>action: remove NVidia headers > > Add to the goal:

Re: [FFmpeg-devel] AMD external header

On Tue, Nov 28, 2017 at 12:47 AM, Tobias Rapp <t.r...@noa-archive.com> wrote: > On 27.11.2017 17:14, Pavel Koshevoy wrote: >> Personally, I would prefer if the bundled external headers were >> installed together with ffmpeg public headers (so nvenc/cuda/etc... >> wer

Re: [FFmpeg-devel] order T-shirts

On 10/24/2017 11:04 AM, Kyle Swanson wrote: Hi, On Sun, Sep 4, 2016 at 2:34 PM, Thomas Volkert wrote: Hi, Some guys at the VDD asked for FFmpeg T-shirts. I'd like to do a new T-shirt order. The shirts could be given to multimedia devs who stop at one of our next booths. My

Re: [FFmpeg-devel] [PATCH] lavc/nvenc: enable nvenc encoder instance reuse after draining

On Thu, Jun 7, 2018, 03:08 Timo Rothenpieler wrote: > On 07.06.2018 06:38, Pavel Koshevoy wrote: > > --- > > libavcodec/nvenc.c | 6 ++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c > &

[FFmpeg-devel] [PATCH] lavc/nvenc: enable nvenc encoder instance reuse (v2)

--- libavcodec/nvenc.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c index b4186c0bec..cfa7268a5e 100644 --- a/libavcodec/nvenc.c +++ b/libavcodec/nvenc.c @@ -2051,8 +2051,16 @@ int ff_nvenc_send_frame(AVCodecContext

Re: [FFmpeg-devel] [PATCH] lavc/nvenc: enable nvenc encoder instance reuse (v2)

On Thu, Jun 7, 2018 at 9:08 AM Pavel Koshevoy wrote: > > --- > libavcodec/nvenc.c | 12 ++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c > index b4186c0bec..cfa7268a5e 100644 > --- a/libavcodec/nv

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: raise max tempo limit (v2)

On Thu, Jun 7, 2018 at 8:16 PM Pavel Koshevoy wrote: > > --- > doc/filters.texi| 17 ++--- > libavfilter/af_atempo.c | 6 +++--- > 2 files changed, 17 insertions(+), 6 deletions(-) > > diff --git a/doc/filters.texi b/doc/filters.texi > index 256ab

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: raise max tempo limit (v2)

On 06/13/2018 07:39 AM, Pavel Koshevoy wrote: On Thu, Jun 7, 2018 at 8:16 PM Pavel Koshevoy wrote: --- doc/filters.texi| 17 ++--- libavfilter/af_atempo.c | 6 +++--- 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/doc/filters.texi b/doc/filters.texi

[FFmpeg-devel] [PATCH] lavfi/atempo: raise max tempo limit (v2)

--- doc/filters.texi| 17 ++--- libavfilter/af_atempo.c | 6 +++--- 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/doc/filters.texi b/doc/filters.texi index 256ab42b00..6b98b04774 100644 --- a/doc/filters.texi +++ b/doc/filters.texi @@ -1986,7 +1986,12 @@

Re: [FFmpeg-devel] Atempo limits

On 06/04/2018 12:09 PM, Ronak wrote: Hello, How are you all? We are looking to use the atempo filter for our audio files. However, the limit between 0.5 - 2x is too restrictive for us. We would like to expand the limit to 0.5x - 3x. I tried changing the range in atempo.c and the rest of the

Re: [FFmpeg-devel] Atempo limits

On 06/04/2018 08:35 PM, Ronak Patel wrote: Thanks. Is it okay if I push a patch for this? How high of a limit does the algorithm support today? I don't think there is an upper limit...  Post a patch here for review.  See http://www.ffmpeg.org/developer.html#Submitting-patches-1 Pavel.

Re: [FFmpeg-devel] Atempo limits

On Mon, Jun 4, 2018 at 8:54 PM, Pavel Koshevoy wrote: > On 06/04/2018 08:35 PM, Ronak Patel wrote: >> >> Thanks. Is it okay if I push a patch for this? How high of a limit does >> the algorithm support today? >> > > I don't think there is an upper limit... P

[FFmpeg-devel] [PATCH] lavfi/atempo: raise max tempo limit

--- libavfilter/af_atempo.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index 8b214bccd7..daf4693321 100644 --- a/libavfilter/af_atempo.c +++ b/libavfilter/af_atempo.c @@ -153,7 +153,7 @@ typedef struct ATempoContext {

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: raise max tempo limit

On Tue, Jun 5, 2018 at 8:59 PM, Pavel Koshevoy wrote: > --- > libavfilter/af_atempo.c | 5 + > 1 file changed, 1 insertion(+), 4 deletions(-) > > diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c > index 8b214bccd7..daf4693321 100644 > --- a/libavfilte

[FFmpeg-devel] [PATCH] lavc/nvenc: enable nvenc encoder instance reuse after draining

--- libavcodec/nvenc.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c index b4186c0bec..8928eacc70 100644 --- a/libavcodec/nvenc.c +++ b/libavcodec/nvenc.c @@ -2181,6 +2181,12 @@ int ff_nvenc_receive_packet(AVCodecContext *avctx, AVPacket *pkt)

Re: [FFmpeg-devel] [PATCH] lavfi/atempo: fix tempo range limit inconsistency

On Thu, Oct 4, 2018 at 2:11 AM Nicolas George wrote: > > Pavel Koshevoy (2018-10-03): > > yae_set_tempo was overlooked when max tempo limit was raised to 100. > > > > tested with: > > ./ffmpeg_g -i Delerium/SemanticSpaces/Gateway.mp3 \ > > -af asendcmd=f=asen

[FFmpeg-devel] [PATCH] lavfi/atempo: fix tempo range limit inconsistency

yae_set_tempo was overlooked when max tempo limit was raised to 100. tested with: ./ffmpeg_g -i Delerium/SemanticSpaces/Gateway.mp3 \ -af asendcmd=f=asendcmd.cfg,atempo=1.0 -y /tmp/asendcmd-atempo.wav where asendcmd.cfg was: 15.0-45.0 [enter] atempo tempo 2.0, [leave] atempo tempo 0.5;

Re: [FFmpeg-devel] [PATCH] libavfilter/af_atempo: offset output frames' pts by first_frame_pts / tempo

On Thu, Jan 24, 2019 at 5:49 AM Paweł Wegner wrote: > > Signed-off-by: Paweł Wegner > --- > libavfilter/af_atempo.c | 9 + > 1 file changed, 9 insertions(+) > > diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c > index bfdad7d76b..1245eae8c1 100644 > ---

Re: [FFmpeg-devel] [PATCH] libavfilter/af_atempo: offset output frames' pts by first_frame_pts / tempo

On Thu, Jan 24, 2019 at 8:01 AM Gyan wrote: > > > > On 24-01-2019 08:18 PM, Paweł Wegner wrote: > > > > This fixes seeking when I have video playback sped up in ffplay like this: > > ffplay -vf "setpts=0.5 * PTS" -af "atempo=2" input > > The better way to run this is > > ffplay -vf

Re: [FFmpeg-devel] [PATCH 1/2] avfilter/vf_zscale: add slice threading

On Fri, May 31, 2019 at 1:44 PM Pavel Koshevoy wrote: > > > > > On Fri, May 31, 2019 at 4:46 AM Paul B Mahol wrote: > > > > Signed-off-by: Paul B Mahol > > --- > > libavfilter/vf_zscale.c | 335 +--- > > 1 f

Re: [FFmpeg-devel] [PATCH 1/2] avfilter/vf_zscale: add slice threading

On Fri, May 31, 2019 at 2:03 PM Paul B Mahol wrote: > > On 5/31/19, Pavel Koshevoy wrote: > > On Fri, May 31, 2019 at 1:44 PM Pavel Koshevoy wrote: > >> > >> > >> > >> > >> On Fri, May 31, 2019 at 4:46 AM Paul

Re: [FFmpeg-devel] [PATCH 1/2] avfilter/vf_zscale: add slice threading

On Fri, May 31, 2019 at 4:46 AM Paul B Mahol wrote: > > Signed-off-by: Paul B Mahol > --- > libavfilter/vf_zscale.c | 335 +--- > 1 file changed, 214 insertions(+), 121 deletions(-) > > diff --git a/libavfilter/vf_zscale.c b/libavfilter/vf_zscale.c > index

Re: [FFmpeg-devel] [PATCH 1/2] avfilter/vf_zscale: add slice threading

On Fri, May 31, 2019 at 2:17 PM Paul B Mahol wrote: > > On 5/31/19, Pavel Koshevoy wrote: > > On Fri, May 31, 2019 at 2:03 PM Paul B Mahol wrote: > >> > >> On 5/31/19, Pavel Koshevoy wrote: > >> > On Fri, May 31, 2019 at 1:44 PM Pavel Koshevoy > &

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: Make ffplay display correct timestamps when seeking

On 5/8/19 1:13 AM, Paul B Mahol wrote: On 5/8/19, Pavel Koshevoy wrote: NOTE: this is a refinement of the patch from Paul B Mahol offset all output timestamps by same amount of first input timestamp --- libavfilter/af_atempo.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On 5/7/19 9:02 PM, Pavel Koshevoy wrote: On 5/7/19 8:41 PM, Pavel Koshevoy wrote: On 5/6/19 6:41 AM, Paul B Mahol wrote: Signed-off-by: Paul B Mahol --- Makes ffplay display correct timestamps when seeking. ---   libavfilter/af_atempo.c | 8 +++-   1 file changed, 7 insertions(+), 1

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On 5/6/19 6:41 AM, Paul B Mahol wrote: Signed-off-by: Paul B Mahol --- Makes ffplay display correct timestamps when seeking. --- libavfilter/af_atempo.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On 5/7/19 8:41 PM, Pavel Koshevoy wrote: On 5/6/19 6:41 AM, Paul B Mahol wrote: Signed-off-by: Paul B Mahol --- Makes ffplay display correct timestamps when seeking. ---   libavfilter/af_atempo.c | 8 +++-   1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/libavfilter

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

btw, I don't know if there is already a way to do this with an existing utility function... there probably is and I just don't know about it. I wrote this debugging helper to help me verify input/output PTS in atempo, I can send a patch if it's useful.  Alternatively, I'd like to know what the

[FFmpeg-devel] [PATCH] avfilter/af_atempo: Make ffplay display correct timestamps when seeking

NOTE: this is a refinement of the patch from Paul B Mahol offset all output timestamps by same amount of first input timestamp --- libavfilter/af_atempo.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On Mon, May 6, 2019, 06:42 Paul B Mahol wrote: > Signed-off-by: Paul B Mahol > --- > Makes ffplay display correct timestamps when seeking. > --- > libavfilter/af_atempo.c | 8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/libavfilter/af_atempo.c

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On Mon, May 6, 2019, 07:28 Pavel Koshevoy wrote: > > > On Mon, May 6, 2019, 06:42 Paul B Mahol wrote: > >> Signed-off-by: Paul B Mahol >> --- >> Makes ffplay display correct timestamps when seeking. >> --- >> libavfilter/af_atempo.c | 8 +++- >&

Re: [FFmpeg-devel] [PATCH] avcodec/videotoolbox_hevc: avoid leaking cached_hw_frames_ctx

On Tue, Aug 6, 2019 at 8:50 PM Pavel Koshevoy wrote: > > vtctx->cached_hw_frames_ctx is unref'd in videotoolbox_uninit, > but videotoolbox_hevc used ff_videotoolbox_uninit which > doesn't unref cache_hw_frames_ctx. > --- > libavcodec/videotoolbox.c | 2 +- > 1 file ch

Re: [FFmpeg-devel] [PATCH] avcodec/videotoolbox_hevc: avoid leaking cached_hw_frames_ctx

On Tue, Aug 6, 2019 at 8:50 PM Pavel Koshevoy wrote: > > vtctx->cached_hw_frames_ctx is unref'd in videotoolbox_uninit, > but videotoolbox_hevc used ff_videotoolbox_uninit which > doesn't unref cache_hw_frames_ctx. > --- > libavcodec/videotoolbox.c | 2 +- > 1 file ch

Re: [FFmpeg-devel] [PATCH] avcodec/videotoolbox_hevc: avoid leaking cached_hw_frames_ctx

On Fri, Aug 23, 2019 at 8:12 AM Pavel Koshevoy wrote: > > On Tue, Aug 6, 2019 at 8:50 PM Pavel Koshevoy wrote: > > > > vtctx->cached_hw_frames_ctx is unref'd in videotoolbox_uninit, > > but videotoolbox_hevc used ff_videotoolbox_uninit which > >

[FFmpeg-devel] [PATCH] lavc/v4l2_m2m: don't close the file descriptor we don't own

ff_v4l2_m2m_create_context initialized V4L2m2mContext.fd to 0 which is a valid file descriptor value. Next ff_v4l2_m2m_codec_init failed and v4l2_m2m_destroy_context closed file descriptor 0 even though it didn't belong to V4L2m2mContext. --- libavcodec/v4l2_m2m.c | 1 + 1 file changed, 1

Re: [FFmpeg-devel] [PATCH] lavc/v4l2_m2m: don't close the file descriptor we don't own

On Mon, Sep 2, 2019 at 10:40 AM Aman Gupta wrote: > > > > On Mon, Sep 2, 2019 at 12:27 AM Pavel Koshevoy wrote: >> >> ff_v4l2_m2m_create_context initialized V4L2m2mContext.fd to 0 >> which is a valid file descriptor value. Next ff_v4l2_m2m_codec_init >> failed

Re: [FFmpeg-devel] [PATCH] avcodec/videotoolbox_hevc: avoid leaking cached_hw_frames_ctx

On 8/23/19 3:46 PM, Aman Gupta wrote: On Wed, Aug 14, 2019 at 3:53 AM Pavel Koshevoy wrote: On Tue, Aug 6, 2019 at 8:50 PM Pavel Koshevoy wrote: vtctx->cached_hw_frames_ctx is unref'd in videotoolbox_uninit, but videotoolbox_hevc used ff_videotoolbox_uninit which doesn't un

[FFmpeg-devel] [PATCH] avcodec/videotoolbox_hevc: avoid leaking cached_hw_frames_ctx

vtctx->cached_hw_frames_ctx is unref'd in videotoolbox_uninit, but videotoolbox_hevc used ff_videotoolbox_uninit which doesn't unref cache_hw_frames_ctx. --- libavcodec/videotoolbox.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/videotoolbox.c

Re: [FFmpeg-devel] [PATCH 14/14] avfilter/af_atempo: use ff_filter_process_command()

On Thu, Oct 10, 2019 at 5:41 AM Paul B Mahol wrote: > > Signed-off-by: Paul B Mahol > --- > libavfilter/af_atempo.c | 25 - > 1 file changed, 8 insertions(+), 17 deletions(-) > > diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c > index

Re: [FFmpeg-devel] [PATCH 14/14] avfilter/af_atempo: use ff_filter_process_command()

On Wed, Oct 9, 2019 at 4:19 AM Paul B Mahol wrote: > > Signed-off-by: Paul B Mahol > --- > libavfilter/af_atempo.c | 25 - > 1 file changed, 8 insertions(+), 17 deletions(-) > > diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c > index 688dac5464..39b500ba95

[FFmpeg-devel] AVFrame.color_trc wrong since f2ad6238e4c0e99e2fc131ee14c586e87b045680

set_side_data used to do out->color_trc = s->sei.alternative_transfer.preferred_transfer_characteristics; In commit f2ad6238e4c0e99e2fc131ee14c586e87b045680 this was removed. Now ffprobe of an HLG stream reports wrong transfer characteristics for each frame: ``` $ ffprobe -show_frames

Re: [FFmpeg-devel] AVFrame.color_trc wrong since f2ad6238e4c0e99e2fc131ee14c586e87b045680

On Tue, Sep 15, 2020, 21:25 James Almer wrote: > On 9/15/2020 10:57 PM, Pavel Koshevoy wrote: > > set_side_data used to do out->color_trc = > > s->sei.alternative_transfer.preferred_transfer_characteristics; > > > > In commit f2ad6238e4c0e99e2fc131ee14c586e87

Re: [FFmpeg-devel] [PATCH] avfilter/setparams: add FF_FILTER_FLAG_HWFRAME_AWARE

On Wed, Sep 23, 2020 at 1:32 PM Paul B Mahol wrote: > On Mon, Sep 21, 2020 at 09:47:40PM -0600, Pavel Koshevoy wrote: > > Allow setparams to be used with hw backed frames and > > avoid an assertion failure in avfilter_config_links. > > --- > > libavfilter/vf_setp

Re: [FFmpeg-devel] [PATCH] avfilter/setparams: add FF_FILTER_FLAG_HWFRAME_AWARE

On Tue, Sep 29, 2020 at 12:14 PM Mark Thompson wrote: > On 29/09/2020 18:14, Pavel Koshevoy wrote: > > On Tue, Sep 29, 2020 at 10:09 AM Mark Thompson wrote: > > > > > > >> - Mark > >> > >> > > It's pretty much this use case, except I'm n

Re: [FFmpeg-devel] [PATCH] avfilter/setparams: add FF_FILTER_FLAG_HWFRAME_AWARE

On Tue, Sep 29, 2020 at 10:09 AM Mark Thompson wrote: > On 28/09/2020 02:17, Pavel Koshevoy wrote: > > On Wed, Sep 23, 2020 at 1:32 PM Paul B Mahol wrote: > > > >> On Mon, Sep 21, 2020 at 09:47:40PM -0600, Pavel Koshevoy wrote: > >>> Allow setpar

[FFmpeg-devel] [PATCH] avfilter/setparams: add FF_FILTER_FLAG_HWFRAME_AWARE

Allow setparams to be used with hw backed frames and avoid an assertion failure in avfilter_config_links. --- libavfilter/vf_setparams.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libavfilter/vf_setparams.c b/libavfilter/vf_setparams.c index 689097fac0..72a69e3fc2 100644 ---

[FFmpeg-devel] suspicious unconditional `goto fail` in decode.c:1892

Hi, I've run into a regression that I've tracked down to this snippet of code in libavcodec/decode.c ``` if (hwaccel) { if (hwaccel->alloc_frame) { ret = hwaccel->alloc_frame(avctx, frame); goto fail; } } else avctx->sw_pix_fmt =

[FFmpeg-devel] [PATCH] lavc/nvenc: disable FMO unconditionally...

because ff_h264_decode_picture_parameter_set doesn't support FMO --- libavcodec/nvenc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c index cb33f9..c21c6dc567 100644 --- a/libavcodec/nvenc.c +++ b/libavcodec/nvenc.c @@ -997,12

Re: [FFmpeg-devel] AVFrame.color_trc wrong since f2ad6238e4c0e99e2fc131ee14c586e87b045680

On 9/15/20 9:24 PM, James Almer wrote: On 9/15/2020 10:57 PM, Pavel Koshevoy wrote: that should be color_transfer=arib-std-b67 Would anyone object if I restored previous behavior? I'd prefer avoid reimplementing SEI parsing outside of libav just to get the correct per-frame color_trc

[FFmpeg-devel] [PATCH] avcodec/hevcdec: fix per-frame signaling of color_trc

This is a partial revert of f2ad6238e4c0e99e2fc131ee14c586e87b045680 It fixes per-frame color_trc signaling of arib-std-b67 frames. Reproducible with: ffprobe -show_frames lg_4k_hlg.ts | grep color_transfer= --- libavcodec/hevcdec.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [FFmpeg-devel] [PATCH v2] avcodec/ccaption_dec: Make real-time latency configurable

On Mon, Jun 14, 2021 at 10:04 AM Paul B Mahol wrote: > On Sun, Jun 13, 2021 at 11:50 PM Pavel Koshevoy > wrote: > > > On Sat, Jun 5, 2021 at 11:40 AM Pavel Koshevoy > > wrote: > > > > > Un-hardcode the 200ms minimum latency between emitting subtitle

Re: [FFmpeg-devel] [PATCH v2] avcodec/ccaption_dec: Make real-time latency configurable

On Sat, Jun 5, 2021 at 11:40 AM Pavel Koshevoy wrote: > Un-hardcode the 200ms minimum latency between emitting subtitle events > so that those that wish to receive a subtitle event for every screen > change could do so. > > The problem with delaying realtime outpu

Re: [FFmpeg-devel] [PATCH v2] avcodec/ccaption_dec: Make real-time latency configurable

On Thu, Jun 17, 2021 at 7:07 PM Pavel Koshevoy wrote: > > > On Sun, Jun 13, 2021 at 3:49 PM Pavel Koshevoy > wrote: > >> >> >> On Sat, Jun 5, 2021 at 11:40 AM Pavel Koshevoy >> wrote: >> >>> Un-hardcode the 200ms minimum latency betwee

Re: [FFmpeg-devel] [PATCH v2] avcodec/ccaption_dec: Make real-time latency configurable

On Sun, Jun 13, 2021 at 3:49 PM Pavel Koshevoy wrote: > > > On Sat, Jun 5, 2021 at 11:40 AM Pavel Koshevoy > wrote: > >> Un-hardcode the 200ms minimum latency between emitting subtitle events >> so that those that wish to receive a subtitle event for every s

Re: [FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable

On Wed, May 26, 2021, 00:18 Moritz Barsnick wrote: > On Tue, May 25, 2021 at 20:16:29 -0600, Pavel Koshevoy wrote: > > -sub->pts > ctx->last_real_time + av_rescale_q(200, ms_tb, > AV_TIME_BASE_Q)) { > > +sub->pts >= ctx->last_real_time + > a

[FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable

Un-hardcode the 200ms minimum latency between emitting subtitle events so that those that wish to receive a subtitle event for every screen change could do so. --- libavcodec/ccaption_dec.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/libavcodec/ccaption_dec.c

Re: [FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable

On Tue, May 25, 2021 at 8:16 PM Pavel Koshevoy wrote: > Un-hardcode the 200ms minimum latency between emitting subtitle events > so that those that wish to receive a subtitle event for every screen > change could do so. > --- > libavcodec/ccaption_dec.c | 4 +++- > 1 file cha

[FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable v2

Un-hardcode the 200ms minimum latency between emitting subtitle events so that those that wish to receive a subtitle event for every screen change could do so. The problem with delaying realtime output by any amount is that it is unknown when the next byte pair that would trigger output will

Re: [FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable v2

On Fri, Jun 4, 2021 at 4:56 PM Valerii Zapodovnikov wrote: > v2 is done by "git send-email -v2 -1" not what you did here. > Thanks, I didn't know that. I am unclear -- do you want me to resubmit the patch? I can just apply and push it myself if there are no objections, although I am not the

[FFmpeg-devel] [PATCH v2] avcodec/ccaption_dec: Make real-time latency configurable

Un-hardcode the 200ms minimum latency between emitting subtitle events so that those that wish to receive a subtitle event for every screen change could do so. The problem with delaying realtime output by any amount is that it is unknown when the next byte pair that would trigger output will

[FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable

Un-hardcode the 200ms minimum latency between emitting subtitle events so that those that wish to receive a subtitle event for every screen change could do so. The problem with delaying realtime output by any amount is that it is unknown when the next byte pair that would trigger output will

Re: [FFmpeg-devel] [PATCH] avcodec/ccaption_dec: Make real-time latency configurable v2

On Sat, May 29, 2021, 08:51 Pavel Koshevoy wrote: > Un-hardcode the 200ms minimum latency between emitting subtitle events > so that those that wish to receive a subtitle event for every screen > change could do so. > > The problem with delaying realtime outpu

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/tiff: Avoid forward declarations

On Tue, Mar 30, 2021 at 2:11 AM Andreas Rheinhardt < andreas.rheinha...@outlook.com> wrote: > In this case it also fixes a potential for compilation failures: > Not all compilers can handle the case in which a function with > a forward declaration declared with an attribute to always inline it >

Re: [FFmpeg-devel] [PATCH] lavc/tiff: Fix build failure due to always_inline

On Tue, Mar 30, 2021 at 2:26 AM Andreas Rheinhardt < andreas.rheinha...@outlook.com> wrote: > Pavel Koshevoy: > > Fixes: > > src/libavcodec/tiff.c: In function ‘tiff_unpack_strip’: > > src/libavcodec/tiff.c:280: error: ‘always_inline’ function could not be >

  1   2   >