srt_socket was deprecated after 1.4.1.
---
libavformat/libsrt.c | 4
1 file changed, 4 insertions(+)
diff --git a/libavformat/libsrt.c b/libavformat/libsrt.c
index 19b9cb9895..1610ce8318 100644
--- a/libavformat/libsrt.c
+++ b/libavformat/libsrt.c
@@ -429,7 +429,11 @@ static int libsrt_setup
Signed-off-by: Zhao Zhili
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 931cf4bd2c..5daa6f8e03 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -516,6 +516,7 @@ Protocols:
bluray.c Petri Hintukainen
ftp.c
Hi, ping on this patch? It's quite simple, happy to answer any questions.
On Tue, Mar 22, 2022 at 2:25 PM wrote:
> From: Kevin Wang
>
> 7-bit PictureIDs are not supported by WebRTC:
> https://groups.google.com/g/discuss-webrtc/c/333-L02vuWA
>
> In practice, 15-bit PictureIDs offer better compat
> On Mar 25, 2022, at 5:13 PM, Kevin Wang wrote:
>
> Hi, ping on this patch? It's quite simple, happy to answer any questions.
>
> On Tue, Mar 22, 2022 at 2:25 PM wrote:
>
>> From: Kevin Wang
>>
>> 7-bit PictureIDs are not supported by WebRTC:
>> https://groups.google.com/g/discuss-webrtc
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 4
libavfilter/f_realtime.c | 4 +++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index d70ac3e237..1d56d24819 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -26757,6 +26
From: Niklas Haas
Upstream gained a new tone-mapping API, which we never switched to. We
don't need a version bump for this because it was included as part of
the v4.192 release we currently already depend on.
The "tonemapping" was changed from an enum to a string, owing to the new
(extensible)
25 Mar 2022, 13:27 by ffm...@haasn.xyz:
> From: Niklas Haas
>
> Upstream gained a new tone-mapping API, which we never switched to. We
> don't need a version bump for this because it was included as part of
> the v4.192 release we currently already depend on.
>
> The "tonemapping" was changed fro
This patch series implements a series of features, mostly enhancing the
dshow avdevice, but also adding new functionality to avformat.
This whole patchset enabled users of the FFmpeg API to fully
query and control a dshow device, making FFmpeg a nice backend for any
program that needs access to, e.
a1c4929f accidentally undid part of d9a9b4c8, so the bug in ticket #9420
resurfaced. Fixing again.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 23 ++-
1 file changed, 6 insertions(+), 17 deletions(-)
diff --git a/libavdevice/dshow.c b/libavdevice/dshow.c
in
As per discussion on the list (
https://ffmpeg.org/pipermail/ffmpeg-devel/2021-June/281513.html, see
especially https://ffmpeg.org/pipermail/ffmpeg-devel/2021-June/281586.html),
to resolve the the unholy ABI-relationship between libavdevice and
libavformat and allow easier working on the part of th
Control messages are useful for programmatic control of not only outdevs
but also indevs.
Bumping avformat version.
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 8 +---
libavformat/avformat.h | 6 ++
libavformat/version.h | 2 +-
3 files changed, 12 insertions(+), 4
This allows programmatic users of avdevice to start and stop the
DirectShow Capture graph (i.e. receive frames or not). This is important
because now the buffer fills up and starts dropping samples when
enqueued packets are not read out immediately after the demuxer is
opened.
Bumping avdevice ver
This control message can be used to programmatically ask a device to
show one of its configuration dialogs.
Adding documentation of this message's int argument.
Bumping avdevice version.
Signed-off-by: Diederick Niehorster
---
doc/indevs.texi| 34 ++
lib
DirectShow source will pop up its configuration dialog when
AV_APP_TO_DEV_CONFIG is received. Implementation for several other
possible configuration dialogs is more involved and will be provided in
the next commit.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 29 +++
The "show config dialog" command message can now also trigger dialog
boxes for the crossbar connecting pins filter the analog tuner
audio / analog tuner filters.
Bumping avdevice version.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 51 ++--
libavdevice
This reverts commit 4f49ca7bbc75a9db4cdf93f27f95a668c751f160. The next
few patches clean up the API and implement this capability for
avdevice/dshow.
Bumping avformat and avdevice version.
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 71 ++
Draw implementation in line with that of avdevice_list_devices
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/libavdevice/avdevice.c b/libavdevice/avdevice.c
index 2000e63bb2..24e14b84c9 100644
--- a/libav
Bumping avdevice major version (API removed, even if it cannot have been used
by anyone)
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 2 +-
libavdevice/avdevice.h | 28 +---
libavdevice/internal.h | 33 +
AVOptionRange needs a way to encode that an option is not set. Here i
provide a documentation solution. When a range is invalid (value_min >
value_max), it should be considered unset/value not available.
When querying a range of formats of an avdevice, sometimes for a given
format the queried opti
Signed-off-by: Diederick Niehorster
---
libavdevice/internal.h | 31 +++
libavdevice/utils.c| 48 ++
2 files changed, 79 insertions(+)
diff --git a/libavdevice/internal.h b/libavdevice/internal.h
index bef3a4bd2d..eee493a4c7 100
Changes fps option from AVRational to double. This since any device
capability query results are returned in AVOptionRanges, which hold the
value as doubles, which can't contain AVRationals.
Also updated documentation of other capabilities, some had the wrong
option type listed.
micro version bum
This adds avdevice_capabilities_get_class() to allow examining the
capabilities that can be queried/set through the capabilities API, and
avdevice_capabilities_bprint_num() which allows printing the value
returned when querying a capability. These values (min_value and
max_value of an AVOptionRange
Needs to be moved up in file for upcoming implementation of
avdevice_capabilities_create.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/libavdevice/dshow.c b/libavdevice/d
After the avdevice capabilities API is implemented, the format context
may be reused after querying device capabilities in a later
avformat_open_input call. To enable this reuse, after releasing
resources, make sure to also set the corresponding pointers back to
NULL. This correctly indicates their
This implements avdevice_capabilities_create and
avdevice_capabilities_free for the dshow device.
This enables configuration discovery of DirectShow devices through the
API, which is important for my use case. It enables making proper GUIs
presenting users with options, instead of asking them to d
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/libavdevice/dshow.c b/libavdevice/dshow.c
index 25c7f5a0e8..c426cef905 100644
--- a/libavdevice/dshow.c
+++ b/libavdevice/dshow.c
@@ -933,6
avformat_alloc_input_context function analogous to
avformat_alloc_output_context2, except that it does not take a filename
argument as guessing the format by just the filename does not make sense.
avformat_alloc_input_context can be used e.g. with the avdevice
capabilities API, which needs an alloc
This example also shows use of get_device_list API.
Also improve capability API doc in avdevice.h: now point to this example
instead of rough example code given in the header.
Signed-off-by: Diederick Niehorster
---
configure | 2 +
doc/examples/.gitignore
Signed-off-by: Diederick Niehorster
---
doc/examples/Makefile | 48 +--
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/doc/examples/Makefile b/doc/examples/Makefile
index de707bb3ca..7988ed4226 100644
--- a/doc/examples/Makefile
+++ b/doc/e
While the capabilities API is in principle meant to be used with an
allocated format context belonging to an unopened device, small changes
make it work for an opened dshow device as well. So hereby done.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 110 +
From: Niklas Haas
Upstream gained a new tone-mapping API, which we never switched to. We
don't need a version bump for this because it was included as part of
the v4.192 release we currently already depend on.
Some of the old options can be moderately approximated with the new API,
but specifica
On Fri, Mar 25, 2022 at 03:10:39PM +0100, Diederick Niehorster wrote:
> This example also shows use of get_device_list API.
>
> Also improve capability API doc in avdevice.h: now point to this example
> instead of rough example code given in the header.
>
> Signed-off-by: Diederick Niehorster
>
On Thu, Mar 24, 2022 at 09:20:06PM +0100, Andreas Rheinhardt wrote:
> ff_er_frame_start() initializes ERContext.error_count
> to three times the number of macroblocks to decode.
> Later ff_er_add_slice() reduces this number by the amount
> of macroblocks whose AC resp. DC resp. MV have been finishe
The VC1 decoder was missing lots of important fast paths for Arm, especially
for 64-bit Arm. This submission fills in implementations for all functions
where a fast path already existed and the fallback C implementation was
taking 1% or more of the runtime, and adds a new fast path to permit
vc1_un
Note that the benchmarking results for these functions are highly dependent
upon the input data. Therefore, each function is benchmarked twice,
corresponding to the best and worst case complexity of the reference C
implementation. The performance of a real stream decode will fall somewhere
between
This test deliberately doesn't exercise the full range of inputs described in
the committee draft VC-1 standard. It says:
input coefficients in frequency domain, D, satisfy -2048 <= D < 2047
intermediate coefficients, E, satisfy-4096 <= E < 4095
fully inverse-transformed coeffici
Disable ff_add_pixels_clamped_arm, which was found to fail the test. As this
is normally only used for Arms prior to Armv6 (ARM11) it seems quite unlikely
that anyone is still using this, so I haven't put in the effort to debug it.
Signed-off-by: Ben Avison
---
libavcodec/arm/idctdsp_init_arm.c
Includes a checkasm test.
Signed-off-by: Ben Avison
---
libavcodec/vc1dec.c | 20 +++---
libavcodec/vc1dsp.c | 2 ++
libavcodec/vc1dsp.h | 3 +++
tests/checkasm/vc1dsp.c | 59 +
4 files changed, 74 insertions(+), 10 deletions(-)
diff
checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows. Note that the C
version can still outperform the NEON version in specific cases. The balance
between different code paths is stream-dependent, but in practice the best
case happens about 5% of the time, the worst case happens about 40% of th
checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows.
idctdsp.add_pixels_clamped_c: 323.0
idctdsp.add_pixels_clamped_neon: 41.5
idctdsp.put_pixels_clamped_c: 243.0
idctdsp.put_pixels_clamped_neon: 30.0
idctdsp.put_signed_pixels_clamped_c: 225.7
idctdsp.put_signed_pixels_clamped_neon: 37.7
Sig
checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows. Note that the C
version can still outperform the NEON version in specific cases. The balance
between different code paths is stream-dependent, but in practice the best
case happens about 5% of the time, the worst case happens about 40% of th
checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows.
vc1dsp.vc1_unescape_buffer_c: 655617.7
vc1dsp.vc1_unescape_buffer_neon: 118237.0
Signed-off-by: Ben Avison
---
libavcodec/aarch64/vc1dsp_init_aarch64.c | 61
libavcodec/aarch64/vc1dsp_neon.S | 176 ++
checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows.
vc1dsp.vc1_inv_trans_4x4_c: 158.2
vc1dsp.vc1_inv_trans_4x4_neon: 65.7
vc1dsp.vc1_inv_trans_4x4_dc_c: 86.5
vc1dsp.vc1_inv_trans_4x4_dc_neon: 26.5
vc1dsp.vc1_inv_trans_4x8_c: 335.2
vc1dsp.vc1_inv_trans_4x8_neon: 106.2
vc1dsp.vc1_inv_trans_4x8
checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows.
vc1dsp.vc1_unescape_buffer_c: 918624.7
vc1dsp.vc1_unescape_buffer_neon: 142958.0
Signed-off-by: Ben Avison
---
libavcodec/arm/vc1dsp_init_neon.c | 61 +++
libavcodec/arm/vc1dsp_neon.S | 118 +
25 Mar 2022, 19:52 by bavi...@riscosopen.org:
> checkasm benchmarks on 1.5 GHz Cortex-A72 are as follows. Note that the C
> version can still outperform the NEON version in specific cases. The balance
> between different code paths is stream-dependent, but in practice the best
> case happens about
On Fri, 25 Mar 2022, Lynne wrote:
25 Mar 2022, 19:52 by bavi...@riscosopen.org:
+@ VC-1 in-loop deblocking filter for 4 pixel pairs at boundary of
vertically-neighbouring blocks
+@ On entry:
+@ r0 -> top-left pel of lower block
+@ r1 = row stride, bytes
+@ r2 = PQUANT bitstream paramete
25 Mar 2022, 20:49 by mar...@martin.st:
> On Fri, 25 Mar 2022, Lynne wrote:
>
>> 25 Mar 2022, 19:52 by bavi...@riscosopen.org:
>>
>>> +@ VC-1 in-loop deblocking filter for 4 pixel pairs at boundary of
>>> vertically-neighbouring blocks
>>> +@ On entry:
>>> +@ r0 -> top-left pel of lower block
>
>>Could this infinite loop also happen before switching to the new API?
>>Does it happen because avail_data is zero for all streams?
>>
>>- Andreas
>
>I will take time to double-check this very carefully, but in my experience, if
>I remember correctly, it is nothing easy and was already buggy befo
On Fri, Mar 25, 2022 at 6:26 PM Michael Niedermayer
wrote:
>
> On Fri, Mar 25, 2022 at 03:10:39PM +0100, Diederick Niehorster wrote:
> > This example also shows use of get_device_list API.
> >
> > Also improve capability API doc in avdevice.h: now point to this example
> > instead of rough example
On Tue, 22 Mar 2022, ke...@muxable.com wrote:
From: Kevin Wang
7-bit PictureIDs are not supported by WebRTC:
https://groups.google.com/g/discuss-webrtc/c/333-L02vuWA
In practice, 15-bit PictureIDs offer better compatibility.
Signed-off-by: Kevin Wang
---
libavformat/rtpenc_vp8.c | 3 ++-
1 f
On Fri, 25 Mar 2022, Ben Avison wrote:
Note that the benchmarking results for these functions are highly dependent
upon the input data. Therefore, each function is benchmarked twice,
corresponding to the best and worst case complexity of the reference C
implementation. The performance of a real
The first patch is left unchanged since v4.
The second has been totally reworked after some investigations advised by
Andreas.
Nicolas Gaullier (2):
lavf/mpegenc: fix ever-growing fifo size since the new API
lavf/mpegenc: fix termination on error conditions
libavformat/mpegenc.c | 23 ++
The older av_fifo_realloc2 implemented an auto grow that
should be ported as such in the new API.
This patch introduces a limitation in the fifo buffer size.
The default is set to 128MB and may be overriden by a new user option.
The amount of memory allocated depends on multiple factors, including
Avoid an infinite 'retry' loop in output_packet when flushing.
Signed-off-by: Nicolas Gaullier
---
libavformat/mpegenc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavformat/mpegenc.c b/libavformat/mpegenc.c
index e0955a7d33..e113a42867 100644
--- a/libavformat/mpe
This search takes alot of time especially when compared with small packets
Signed-off-by: Michael Niedermayer
---
libavformat/demux.c| 15 +--
libavformat/internal.h | 5 +
2 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/libavformat/demux.c b/libavformat/demu
Fixes: signed integer overflow: 536870913 * 536870913 cannot be represented in
type 'int'
Fixes:
45862/clusterfuzz-testcase-minimized-ffmpeg_dem_MOV_fuzzer-4730373768085504
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael
On Mon, 21 Mar 2022, Martin Storsjö wrote:
---
I'll apply in a couple days if there's no comments.
---
gas-preprocessor.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Pushed.
// Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.o
Hello.
A re-submit of a re-base of a formerly proposed patch to align with ffmpeg
github
commit 8ae15b565533944d042d3caf25f7262e002e8953
at 2022.03.26 ACST, after changes overlapped the formerly proposed patch.
Add commandline options to v4l2_m2m_enc (h264_v4l2m2m only)
and use those to config
Oops, accidentally submitted with the wrong title so not in the right thread.
Is submitted with the right one now.
A re-submit of a re-base of a formerly proposed patch to align with ffmpeg
github
commit 8ae15b565533944d042d3caf25f7262e002e8953
as at 2022.03.26 ACST, after ffmpeg changes overl
59 matches
Mail list logo
