On Tue, Mar 10, 2020 at 05:36:40PM +0800, Jianhui Dai wrote:
> Avoid constant N frames latency in video streaming.
>
> Signed-off-by: Jianhui Dai
> ---
> libavcodec/pthread_frame.c | 17 ++---
> 1 file changed, 2 insertions(+), 15 deletions(-)
This patch causes segfaults
./ffmpeg_g
Quoting James Almer (2020-02-27 19:02:00)
> This commit follows the same logic as 061a0c14bb, but for the encode API: The
> new public encoding API will no longer be a wrapper around the old deprecated
> one, and the internal API used by the encoders now consists of a single
> receive_packet() call
With the description in frame size with refs semantics (SPEC 7.2.5),
it is a requirement of bitstream conformance that for at least one
reference frame has the valid dimensions.
Modify the check to make sure the decoder works well in the condition
that not all references frames have valid dimensio
Add qmax/qmin support for HEVC software bitrate control(SWBRC).
Limitations:
- RateControlMethod != MFX_RATECONTROL_CQP
- with EXTBRC ON
Signed-off-by: Dmitry Rogozhkin
Signed-off-by: Linjie Fu
---
Relative code in MSDK for the limitation:
https://github.com/Intel-Media-SDK/MediaSDK/bl
Am Mi., 11. März 2020 um 11:44 Uhr schrieb Linjie Fu :
>
> With the description in frame size with refs semantics (SPEC 7.2.5),
> it is a requirement of bitstream conformance that for at least one
> reference frame has the valid dimensions.
>
> Modify the check to make sure the decoder works well i
---
doc/general.texi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/general.texi b/doc/general.texi
index 87eaad7791..e92de9d954 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -58,8 +58,8 @@ For Windows, supported AviSynth variants are
@url{http://avisynt
Since there were no responses to my question about whether
we should use a warning message about AvxSynth's deprecation
before switching over at a later time, or to just do the
switch immediately, I've gone ahead and sent just the
switchover patch.
Stephen Hutchinson (5):
compat/avisynth: update
AviSynth+ can now be used on Linux, which required some changes
to the headers.
---
compat/avisynth/avisynth_c.h | 24
compat/avisynth/avs/capi.h | 16 +
compat/avisynth/avs/config.h | 46 +--
compat/avisynth/avs/posix.h | 111 +++
com
---
libavformat/avisynth.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/avisynth.c b/libavformat/avisynth.c
index 1970553e49..f3e8df933f 100644
--- a/libavformat/avisynth.c
+++ b/libavformat/avisynth.c
@@ -555,7 +555,7 @@ static int avisynth_open_file(AVFormatCon
AviSynth+ now supports non-Windows OSes, making AvxSynth
obsolete. Since we no longer support AviSynth 2.5 (which is
essentially what AvxSynth is), remove AvxSynth support and
replace it with AviSynth+.
As a result, the USING_AVISYNTH defines can be switched back
to generic _WIN32.
---
libavform
---
compat/avisynth/avxsynth_c.h | 728 --
.../windowsPorts/basicDataTypeConversions.h | 85 --
compat/avisynth/windowsPorts/windows2linux.h | 77 --
3 files changed, 890 deletions(-)
delete mode 100644 compat/avisynth/avxsynth_c.h
delete mode 100644 compat/
On Wed, Mar 11, 2020 at 11:44 AM Linjie Fu wrote:
> Add qmax/qmin support for HEVC software bitrate control(SWBRC).
>
> Limitations:
> - RateControlMethod != MFX_RATECONTROL_CQP
> - with EXTBRC ON
>
> Signed-off-by: Dmitry Rogozhkin
> Signed-off-by: Linjie Fu
> ---
>
> Relative code in
On Tue, Mar 10, 2020 at 10:36 PM Soft Works wrote:
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Artem Galin
> > Sent: Tuesday, March 10, 2020 5:10 PM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH v2] lav
Hi!
Attached patch fixes part of ticket #8565 (compilation with
--disable-neon is broken on aarch64).
Please comment, Carl Eugen
From d96c8d26802978077d5d32b7aa2b535eca99cfea Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Wed, 11 Mar 2020 13:01:02 +0100
Subject: [PATCH] lavc/aarch64: Move
Hi!
Attached patch fixes the remaining part of ticket #8565.
Please comment, Carl Eugen
From c6451d3e57eca639e0272609fd817bf22390111e Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Wed, 11 Mar 2020 13:16:47 +0100
Subject: [PATCH] lavc/aarch64: Fix compilation with --disable-neon
Fixes ti
On Wed, 11 Mar 2020, Carl Eugen Hoyos wrote:
Hi!
Attached patch fixes part of ticket #8565 (compilation with
--disable-neon is broken on aarch64).
This looks ok to me.
// Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.
On Wed, 11 Mar 2020, Carl Eugen Hoyos wrote:
Hi!
Attached patch fixes the remaining part of ticket #8565.
This looks correct.
// Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsu
> From: ffmpeg-devel On Behalf Of
> Carl Eugen Hoyos
> Sent: Wednesday, March 11, 2020 18:48
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vp9: fix reference frame
> dimensions check
>
> Am Mi., 11. März 2020 um 11:44 Uhr schrieb Li
> From: ffmpeg-devel On Behalf Of
> Max Dmitrichenko
> Sent: Wednesday, March 11, 2020 19:37
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_hevc: add qmax/qmin
> support for HEVC encoding
>
> On Wed, Mar 11, 2020 at 11:44 AM L
Andreas Rheinhardt:
> Several variables which are only used when the HLS_SINGLE_FILE flag is
> unset have been set even when this flag is set. This has been changed.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> Now not moving variables into a smaller scope.
>
> libavformat/hlsenc.c | 16 ++
On 3/11/2020 7:18 AM, Anton Khirnov wrote:
> Quoting James Almer (2020-02-27 19:02:00)
>> This commit follows the same logic as 061a0c14bb, but for the encode API: The
>> new public encoding API will no longer be a wrapper around the old deprecated
>> one, and the internal API used by the encoders
Am Mi., 11. März 2020 um 13:35 Uhr schrieb Martin Storsjö :
>
> On Wed, 11 Mar 2020, Carl Eugen Hoyos wrote:
>
> > Hi!
> >
> > Attached patch fixes part of ticket #8565 (compilation with
> > --disable-neon is broken on aarch64).
>
> This looks ok to me.
Patch applied (and fixed).
Thank you, Carl
Am Mi., 11. März 2020 um 13:36 Uhr schrieb Martin Storsjö :
>
> On Wed, 11 Mar 2020, Carl Eugen Hoyos wrote:
>
> > Hi!
> >
> > Attached patch fixes the remaining part of ticket #8565.
>
> This looks correct.
Patch applied.
Thank you, Carl Eugen
___
ffmp
Am Mi., 11. März 2020 um 13:44 Uhr schrieb Fu, Linjie :
>
> > From: ffmpeg-devel On Behalf Of
> > Carl Eugen Hoyos
> > Sent: Wednesday, March 11, 2020 18:48
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] lavc/vp9: fix reference frame
On 11/03/2020 03:28, Dai, Jianhui J wrote:
> As reply in another thread, the sequence of output frames still follows
> standard, like display order POC in H264.
> Big enough frame cache can guarantee deterministic delay in some extent, but
> not always (decoding time > caching time).
That was my
On 11/03/2020 05:29, Dai, Jianhui J wrote:
> Like RTSP/RTMP/DASH, the latency is variable according to network bandwidth.
He is not talking about wallclock or een latency in the time domain.
Latency as in 'number of packets passed in before a frame is output'. Which this
patch makes both non-dete
lgtm
On 3/11/20, Thierry Foucu wrote:
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 8b17134944..2d2e4d8817 100755
> --- a/configure
> +++ b/configure
> @@ -2790,7 +2790,7 @@ msmpeg4v3_decoder_select="h263_decoder"
> msmp
On Tue, Mar 10, 2020 at 06:45:58PM +0100, Anton Khirnov wrote:
> It is always 0.
> ---
> libavcodec/mpegvideo.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
LGTM
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The worst form of inequa
On Wed, Mar 11, 2020 at 10:28 AM Derek Buitenhuis
wrote:
> > E.g. in FF_THREAD_FRAME 4320x2160 30fps video streaming, 4 threads, the
> > frame caching is 99ms (33ms x 3frames)
> > If the cpu-decoding-execution-time is 80ms ~ 120ms (dependent on video
> > frame content).
>
> Also aside: It is no
>
> Regardless of the actual proposed patch, I think the author's use of
> wallclock time to describe the problem is very reasonable. I do a
> large amount of work where I'm measuring "glass-to-glass" latency,
> where I am interested in the total pipeline (encode/network/decode),
> and I definitel
On 11/03/2020 14:53, Devin Heitmueller wrote:
> Regardless of the actual proposed patch, I think the author's use of
> wallclock time to describe the problem is very reasonable. I do a
> large amount of work where I'm measuring "glass-to-glass" latency,
> where I am interested in the total pipelin
> From: ffmpeg-devel On Behalf Of
> Carl Eugen Hoyos
> Sent: Wednesday, March 11, 2020 21:42
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vp9: fix reference frame
> dimensions check
>
> Am Mi., 11. März 2020 um 13:44 Uhr schrieb Fu
Thierry Foucu:
> ---
> libavformat/matroskaenc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/matroskaenc.c b/libavformat/matroskaenc.c
> index 42f21eae8b..cf436f9e3e 100644
> --- a/libavformat/matroskaenc.c
> +++ b/libavformat/matroskaenc.c
> @@ -2630,7 +2
On Tue, Mar 10, 2020 at 06:45:56PM +0100, Anton Khirnov wrote:
> Hi,
> sending a proposed new API for exporting QP tables (and possibly other
> things in the future). It is based on a patch from Juan De León
> (cf. <20190819233655.171637-1-jua...@google.com>).
>
> The set is intended for dicussion
On Wed, Mar 11, 2020 at 10:13 AM Andreas Rheinhardt <
andreas.rheinha...@gmail.com> wrote:
> Thierry Foucu:
> > ---
> > libavformat/matroskaenc.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavformat/matroskaenc.c b/libavformat/matroskaenc.c
> > index 42f21eae
On Thu, 05. Mar 00:02, Andriy Gelman wrote:
> From: Andriy Gelman
>
> Signed-off-by: Andriy Gelman
> ---
> libavcodec/avcodec.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
> index 5a0fc3405c5..8cda2422efa 100644
> -
On Wed, 11 Mar 2020, Derek Buitenhuis wrote:
On 11/03/2020 14:53, Devin Heitmueller wrote:
Regardless of the actual proposed patch, I think the author's use of
wallclock time to describe the problem is very reasonable. I do a
large amount of work where I'm measuring "glass-to-glass" latency,
w
Support to generate dash SegmentBase manifests, by adding
"use_segmentbase" option to dash muxer. SegmentBase manifest
is defined in ISO DASH Specification section 5.3.9.2 and has as
prerequisite the option "global_sidx" as players will use this box
to have a reference to all fragments in the media
Am Mi., 11. März 2020 um 22:12 Uhr schrieb David Martin :
>
> Support to generate dash SegmentBase manifests, by adding
> "use_segmentbase" option to dash muxer. SegmentBase manifest
> is defined in ISO DASH Specification section 5.3.9.2 and has as
> prerequisite the option "global_sidx" as players
Support to generate dash SegmentBase manifests, by adding
"use_segmentbase" option to dash muxer. SegmentBase manifest
is defined in ISO DASH Specification section 5.3.9.2 and has as
prerequisite the option "global_sidx" as players will use this box
to have a reference to all fragments in the media
This avoids long delays when converting live streams that have sparse subtitles
---
libavformat/avformat.h | 9 +
libavformat/mux.c | 25 +
libavformat/options_table.h | 1 +
libavformat/version.h | 2 +-
4 files changed, 32 insertions(+), 5
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Max Dmitrichenko
> Sent: Wednesday, March 11, 2020 12:49 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/qsv: adding DX11 support
>
> On Tue, Mar 10, 2020 at 10:
Am Mi., 26. Feb. 2020 um 19:50 Uhr schrieb Carl Eugen Hoyos
:
>
> Am Sa., 15. Feb. 2020 um 20:21 Uhr schrieb Michael Niedermayer
> :
> >
> > On Sat, Feb 15, 2020 at 10:10:45AM +0100, Carl Eugen Hoyos wrote:
> > > Hi!
> > >
> > > Transparency levels are currently changed when reading bgra and
> > >
On Wed, Mar 11, 2020 at 06:50:15AM -0400, Stephen Hutchinson wrote:
> AviSynth+ can now be used on Linux, which required some changes
> to the headers.
> ---
> compat/avisynth/avisynth_c.h | 24
> compat/avisynth/avs/capi.h | 16 +
> compat/avisynth/avs/config.h | 46
On Wed, Mar 11, 2020 at 03:39:23PM +0100, Paul B Mahol wrote:
> lgtm
will apply
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Never trust a computer, one day, it may think you are the virus. -- Compn
signature.asc
Description: PGP signature
On Wed, Mar 11, 2020 at 11:20:48PM +0100, Michael Niedermayer wrote:
> On Wed, Mar 11, 2020 at 03:39:23PM +0100, Paul B Mahol wrote:
> > lgtm
>
> will apply
actually, i wont apply this yet, it looks a bit odd
-mvha_decoder_deps="zlib"
+mvha_decoder_select="llviddsp zlib"
zlib should be a _deps
On 11/03/2020 20:42, Martin Storsjö wrote:
> FWIW, while I agree it shouldn't be the default, I have occasionally
> considered the need for this particular feature.
Arguably slice threading should be used, but that assumes you have sane input,
which is obviously not always the case for some.
> C
On Sun, Mar 01, 2020 at 11:59:34PM +0100, Michael Niedermayer wrote:
> Fixes: left shift of negative value -1
> Fixes:
> 20859/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ADPCM_PSX_fuzzer-5720391507247104
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/ma
On Sat, Mar 07, 2020 at 11:40:42PM +0100, Michael Niedermayer wrote:
> Fixes: out of array access
> Fixes:
> 19734/clusterfuzz-testcase-minimized-ffmpeg_BSF_TRACE_HEADERS_fuzzer-5673507031875584
> Fixes:
> 19353/clusterfuzz-testcase-minimized-ffmpeg_BSF_TRACE_HEADERS_fuzzer-5703944462663680
>
>
On Thu, Mar 12, 2020 at 1:42 AM Jan Ekström wrote:
>
> Utilizes a subpicture sample with one decodable subpicture for the
> test.
>
> Based on a failing test case in reported by Michael in
> https://ffmpeg.org/pipermail/ffmpeg-devel/2019-February/240398.html
> which at the time had no test case fo
---
tests/fate/ffmpeg.mak | 9
tests/ref/fate/sub2video_basic | 95 ++
2 files changed, 104 insertions(+)
create mode 100644 tests/ref/fate/sub2video_basic
diff --git a/tests/fate/ffmpeg.mak b/tests/fate/ffmpeg.mak
index 967150983a..835aab3665 10064
Utilizes a subpicture sample with one decodable subpicture for the
test.
Based on a failing test case in reported by Michael in
https://ffmpeg.org/pipermail/ffmpeg-devel/2019-February/240398.html
which at the time had no test case for it.
Additionally, this is the first test case for the presenta
On Thu, Mar 12, 2020 at 1:42 AM Jan Ekström wrote:
>
> ---
> tests/fate/ffmpeg.mak | 9
> tests/ref/fate/sub2video_basic | 95 ++
> 2 files changed, 104 insertions(+)
> create mode 100644 tests/ref/fate/sub2video_basic
>
Before the logic affecting
Each time the sub2video structure is initialized, the sub2video
subpicture is initialized together with the first received heartbeat.
The heartbeat's PTS is utilized as the subpicture start time.
Additionally, add some documentation on the stages.
---
fftools/ffmpeg.c| 22 +++-
Thierry Foucu:
> On Wed, Mar 11, 2020 at 10:13 AM Andreas Rheinhardt <
> andreas.rheinha...@gmail.com> wrote:
>
>> Thierry Foucu:
>>> ---
>>> libavformat/matroskaenc.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/libavformat/matroskaenc.c b/libavformat/matroskaen
AviSynth+ can now be used on Linux, which required some changes
to the headers.
As part of this, and to not cause issues with adding a new header,
correct the header inclusion guards to make FATE happy.
---
compat/avisynth/avisynth_c.h | 30 ++
compat/avisynth/avs/capi.h | 22 ++-
---
compat/avisynth/avxsynth_c.h | 728 --
.../windowsPorts/basicDataTypeConversions.h | 85 --
compat/avisynth/windowsPorts/windows2linux.h | 77 --
tests/ref/fate/source | 5 -
4 files changed, 895 deletions(-)
delete mode 100644 c
Thanks for clarify the packets-to-frames delay. I will respect that decoder
design principle.
Add a few backgrounds for this issue.
I work on 4K@30fps streaming playback on 16-cores host.
Initially I use FF_THREAD_SLICE, but "avcodec_send_packet" takes ~100ms, only
10fps playback (I want 30fps).
Linjie Fu 于2020年3月11日周三 下午6:44写道：
>
> Add qmax/qmin support for HEVC software bitrate control(SWBRC).
>
> Limitations:
> - RateControlMethod != MFX_RATECONTROL_CQP
> - with EXTBRC ON
>
> Signed-off-by: Dmitry Rogozhkin
> Signed-off-by: Linjie Fu
> ---
>
> Relative code in MSDK for the li
fix ticket: 8566
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 4b28c412fa..75e75ff57a 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -2587,7 +2587,6 @@ static int hls_write_
> 2020年3月12日 上午11:02，Steven Liu 写道：
>
> fix ticket: 8566
>
> Signed-off-by: Steven Liu
> ---
> libavformat/hlsenc.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
> index 4b28c412fa..75e75ff57a 100644
> --- a/libavformat/hlsenc.c
> +++ b/li
> 2020年3月11日 上午7:06，Steven Liu 写道：
>
>>
>> 2020年3月7日 上午11:26，Steven Liu 写道：
>>
>>
>>
>>> 2020年3月6日 上午11:58，Hongcheng Zhong 写道：
>>>
>>> This patch fixes Bug #8469
>>> If x264 baseline profile is used with other profiles,
>>> start_pts will be initialized to audio stream's first pts,
>>> w
62 matches
Mail list logo
