Stream side data such as display matrix is currently lost when using NUT.
Signed-off-by: Matthias Neugebauer
---
libavformat/nutdec.c | 9 +
libavformat/nutenc.c | 18 ++
2 files changed, 27 insertions(+)
diff --git a/libavformat/nutdec.c b/libavformat/nutdec.c
index 53a05
On Wed, Nov 4, 2020 at 12:52 AM Mark Thompson wrote:
>
> On 03/11/2020 23:17, Bas Nieuwenhuizen wrote:
> > The kernel defaults to initializing the field to 0 when modifiers
> > are not used and this happens to be linear. If we end up actually
> > passing the modifier to a driver, tiling issues hap
On Wed, Nov 4, 2020 at 1:21 AM Bas Nieuwenhuizen
wrote:
>
> On Wed, Nov 4, 2020 at 12:52 AM Mark Thompson wrote:
> >
> > On 03/11/2020 23:17, Bas Nieuwenhuizen wrote:
> > > The kernel defaults to initializing the field to 0 when modifiers
> > > are not used and this happens to be linear. If we en
On Wed, Nov 4, 2020 at 1:09 AM Mark Thompson wrote:
>
> On 03/11/2020 23:17, Bas Nieuwenhuizen wrote:
> > As we get a new set of objects each frame anyway, we
> > do not gain anything by keeping the modifier constant.
> >
> > This helps with capturing when switching your setup a
> > bit, e.g. from
Fixes: assertion failure
Fixes:
26813/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_SMVJPEG_fuzzer-5756269803339776
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/smvjpegdec.c | 6 +++---
Fixes: out of array access
Fixes:
26816/clusterfuzz-testcase-minimized-ffmpeg_dem_MPEGTSRAW_fuzzer-6282861159907328.fuzz
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/mpegts.c | 2 +-
1 fil
Fixes: NULL pointer dereference
Fixes:
26814/clusterfuzz-testcase-minimized-ffmpeg_dem_ICO_fuzzer-5758487797432320
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/icodec.c | 7 +--
1 file
Signed-off-by: Michael Niedermayer
---
libavformat/icodec.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/libavformat/icodec.c b/libavformat/icodec.c
index c061f3ec42..cf1e60815e 100644
--- a/libavformat/icodec.c
+++ b/libavformat/icodec.c
@@ -113,8 +113,7 @@ st
Fixes: signed integer overflow: 131203586 * 28 cannot be represented in type
'int'
Fixes:
26817/clusterfuzz-testcase-minimized-ffmpeg_dem_MSF_fuzzer-6296902548848640
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Nieder
Fixes: left shift of 65536 by 15 places cannot be represented in type 'int'
Fixes:
26801/clusterfuzz-testcase-minimized-ffmpeg_dem_MPC8_fuzzer-5164313092030464
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
Fixes: out of array access
Fixes:
26819/clusterfuzz-testcase-minimized-ffmpeg_dem_FITS_fuzzer-5634559355650048
Fixes:
26820/clusterfuzz-testcase-minimized-ffmpeg_dem_FITS_fuzzer-5760774955597824
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
On 03/11/2020 23:17, Bas Nieuwenhuizen wrote:
As we get a new set of objects each frame anyway, we
do not gain anything by keeping the modifier constant.
This helps with capturing when switching your setup a
bit, e.g. from ingame to desktop or from X11 to wayland.
---
libavdevice/kmsgrab.c | 7
On 03/11/2020 23:17, Bas Nieuwenhuizen wrote:
The kernel defaults to initializing the field to 0 when modifiers
are not used and this happens to be linear. If we end up actually
passing the modifier to a driver, tiling issues happen.
So if the kernel doesn't return a modifier set it explicitly t
This way we can pass explicit modifiers in. Sometimes the
modifier matters for the number of memory planes that
libva accepts, in particular when dealing with
driver-compressed textures. Furthermore the driver might
not actually be able to determine the implicit modifier
if all the buffer-passing h
The kernel defaults to initializing the field to 0 when modifiers
are not used and this happens to be linear. If we end up actually
passing the modifier to a driver, tiling issues happen.
So if the kernel doesn't return a modifier set it explicitly to
INVALID. That way later processing knows there
As we get a new set of objects each frame anyway, we
do not gain anything by keeping the modifier constant.
This helps with capturing when switching your setup a
bit, e.g. from ingame to desktop or from X11 to wayland.
---
libavdevice/kmsgrab.c | 7 ---
1 file changed, 7 deletions(-)
diff --
On Sat, Oct 24, 2020 at 13:32:25 +1300, Michael Keeley wrote:
> -if (memcmp(p->buf, "DHAV", 4))
> +if (memcmp(p->buf, "DHAV", 4) != 0 && memcmp(p->buf, "ZLAV", 4) != 0)
The "!= 0" isn't necessary.
> -if (!memcmp(signature, "DHAV", 4)) {
> +if (memcmp(signature, "DHAV", 4)
On 03/11/2020 16:51, Eoff, Ullysses A wrote:>> -Original Message-
From: ffmpeg-devel On Behalf Of Jan Ekström
Sent: Tuesday, November 03, 2020 3:17 AM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] [PATCH 1/3] vaapi_encode_h264: Fix setting colour
properties
Makes selection of d3d11va device type by default and over DirectX 9,
which might break users with older drivers/systems.
DCH driver with Gen6th support should be still fine.
Decode, encode, transcode have been validated.
child_device_type option is responsible for d3d11va/dxva2 device selection
This enables usage of non-powered/headless GPU, better HDR support.
Pool of resources is allocated as one texture with array of slices.
Signed-off-by: Artem Galin
---
libavutil/hwcontext_qsv.c | 323 +++---
1 file changed, 262 insertions(+), 61 deletions(-)
diff
Microsoft VideoProcessor requires texture with D3DUSAGE_RENDERTARGET flag as
output.
There is no way to allocate array of textures with D3D11_BIND_RENDER_TARGET flag
and .ArraySize > 2 by ID3D11Device_CreateTexture2D due to the Microsoft
limitation.
Adding AVD3D11FrameDescriptors array to store a
Adding DX11 relevant device type checks and adjusting callback with
proper MediaSDK pair type support.
Signed-off-by: Artem Galin
---
libavfilter/vf_deinterlace_qsv.c | 44 ++--
1 file changed, 25 insertions(+), 19 deletions(-)
diff --git a/libavfilter/vf_deinterlace
Adding DX11 relevant device type checks and adjusting callback with
proper MediaSDK pair type support.
Signed-off-by: Artem Galin
---
libavfilter/qsvvpp.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/libavfilter/qsvvpp.c b/libavfilter/qsvv
In case of DX11 device type, Media SDK is sensitive to these flags.
Signed-off-by: Artem Galin
---
libavfilter/vf_scale_qsv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/vf_scale_qsv.c b/libavfilter/vf_scale_qsv.c
index 47701c20d0..9eb59325c3 100644
--- a/liba
Adding DX11 relevant device type checks and adjusting callback with
proper MediaSDK pair type support.
Signed-off-by: Artem Galin
---
libavfilter/vf_scale_qsv.c | 43 +-
1 file changed, 24 insertions(+), 19 deletions(-)
diff --git a/libavfilter/vf_scale_qsv.c
Adding DX11 relevant device type checks and adjusting callbacks with
proper MediaSDK pair type support.
Extending structure for proper MediaSDK pair type support.
Signed-off-by: Artem Galin
---
libavcodec/qsv.c | 53 ++-
libavcodec/qsv_internal.h |
Reduces the number of allocations and frees.
Signed-off-by: Andreas Rheinhardt
---
libavcodec/truemotion2.c | 46 +---
1 file changed, 19 insertions(+), 27 deletions(-)
diff --git a/libavcodec/truemotion2.c b/libavcodec/truemotion2.c
index a90ff8cf01..0f4f345
The codec's private context has already been zeroed generically.
Signed-off-by: Andreas Rheinhardt
---
libavcodec/truemotion2.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/libavcodec/truemotion2.c b/libavcodec/truemotion2.c
index 51266e5744..1ae13bbf06 100644
--- a
Signed-off-by: Andreas Rheinhardt
---
libavcodec/truemotion2.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/libavcodec/truemotion2.c b/libavcodec/truemotion2.c
index 1ae13bbf06..a90ff8cf01 100644
--- a/libavcodec/truemotion2.c
+++ b/libavcodec/truemotion2.c
@
Signed-off-by: Andreas Rheinhardt
---
libavcodec/truemotion2.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/truemotion2.c b/libavcodec/truemotion2.c
index a1d4eea340..51266e5744 100644
--- a/libavcodec/truemotion2.c
+++ b/libavcodec/truemotion2.c
@@ -1016,8 +
Signed-off-by: Andreas Rheinhardt
---
libavcodec/sonic.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/sonic.c b/libavcodec/sonic.c
index db2c4339a3..a285228bbc 100644
--- a/libavcodec/sonic.c
+++ b/libavcodec/sonic.c
@@ -506,7 +506,7 @@ static void modified_l
Instead allocate it together with the buffer that it mirrors.
Signed-off-by: Andreas Rheinhardt
---
libavcodec/sonic.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/libavcodec/sonic.c b/libavcodec/sonic.c
index bca1eca27a..db2c4339a3 100644
--- a/libavcode
It simplifies freeing them and reduces the amount of allocations.
Signed-off-by: Andreas Rheinhardt
---
libavcodec/sonic.c | 48 --
1 file changed, 21 insertions(+), 27 deletions(-)
diff --git a/libavcodec/sonic.c b/libavcodec/sonic.c
index 0d4891ebf4
Nikola Pajkovsky writes:
Ping?
> init.mp4 can be expanded with strftime() the same way as
> hls_segment_filename.
>
> Signed-off-by: Nikola Pajkovsky
> ---
> v2: fix memleak on strftime failure
> v3: use av_free() insted of free()
>
> doc/muxers.texi | 7 ++
> libavformat/hlsenc.c
> -Original Message-
> From: ffmpeg-devel On Behalf Of Jan Ekström
> Sent: Tuesday, November 03, 2020 3:17 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 1/3] vaapi_encode_h264: Fix setting colour
> properties
>
> On Tue, Nov 3, 2020 at 12:59
On 11/3/2020 10:32 AM, Anton Khirnov wrote:
> Quoting James Almer (2020-11-02 16:26:57)
>> On 11/2/2020 10:17 AM, Anton Khirnov wrote:
>>> ---
>>> Makefile | 3 +++
>>> tools/Makefile | 2 +-
>>> tools/enum_options.c | 26 +-
>>> 3 files changed, 17 inse
Joakim Tjernlund:
> On Tue, 2020-11-03 at 14:38 +0100, Andreas Rheinhardt wrote:
>>
>> Timo Rothenpieler:
>>> Given the multitude of recent serious security issues in Chromium-Based
>>> Browsers, is this even still an issue?
>>> Anything not up to date enough to have already been fixed has serious
On Tue, 2020-11-03 at 14:38 +0100, Andreas Rheinhardt wrote:
>
> Timo Rothenpieler:
> > Given the multitude of recent serious security issues in Chromium-Based
> > Browsers, is this even still an issue?
> > Anything not up to date enough to have already been fixed has serious
> > security issues a
Causes a divide-by-zero in the rare case where:
- the file has an audio stream,
- the first audio frame isn't within the first BRP_BASF_LOOKAHEAD frames,
- an audio frame is encountered later, and
- its chunk header (except num_blocks) contains all zeros
(matching the uninitialised structure in
Timo Rothenpieler:
> Given the multitude of recent serious security issues in Chromium-Based
> Browsers, is this even still an issue?
> Anything not up to date enough to have already been fixed has serious
> security issues and should be updated ASAP, which also fixes this issue
> in turn.
>
> I'd
Quoting James Almer (2020-11-02 16:26:57)
> On 11/2/2020 10:17 AM, Anton Khirnov wrote:
> > ---
> > Makefile | 3 +++
> > tools/Makefile | 2 +-
> > tools/enum_options.c | 26 +-
> > 3 files changed, 17 insertions(+), 14 deletions(-)
> >
> > diff --git
On 11/3/2020 10:19 AM, Joakim Tjernlund wrote:
> On Tue, 2020-11-03 at 10:05 -0300, James Almer wrote:
>>
>> On 11/3/2020 9:12 AM, Anton Khirnov wrote:
>>> Quoting Joakim Tjernlund (2020-11-03 12:39:53)
Pretty please ?
>>>
>>> ok, would people who are strongly against this patch please raise t
On Tue, 2020-11-03 at 10:05 -0300, James Almer wrote:
>
> On 11/3/2020 9:12 AM, Anton Khirnov wrote:
> > Quoting Joakim Tjernlund (2020-11-03 12:39:53)
> > > Pretty please ?
> >
> > ok, would people who are strongly against this patch please raise their
> > hands.
>
> Would applying this to mast
On 11/3/2020 9:12 AM, Anton Khirnov wrote:
> Quoting Joakim Tjernlund (2020-11-03 12:39:53)
>> Pretty please ?
>
> ok, would people who are strongly against this patch please raise their
> hands.
Would applying this to master now (backporting it to 4.3 too) and then
reverting it at the time of th
Given the multitude of recent serious security issues in Chromium-Based
Browsers, is this even still an issue?
Anything not up to date enough to have already been fixed has serious
security issues and should be updated ASAP, which also fixes this issue
in turn.
I'd rather see downstream users
Quoting Joakim Tjernlund (2020-11-03 12:39:53)
> Pretty please ?
ok, would people who are strongly against this patch please raise their
hands.
Personally I'm ok with pushing this, even though it's ugly. Then again
the vey existence of av_malloc_max is ugly and it should be deprecated
IMO.
--
A
On Tue, Nov 3, 2020 at 12:59 AM Mark Thompson wrote:
>
> The properties should always be set; only the presence flags want to be
> conditional.
>
> Fixes #8959.
> ---
Thanks for this on such short notice. Patch set LGTM, and simplifies
the logic nicely for these values (always set, only set flags
AMV is a hard-coded (and broken) subset of AVI. It's not worth sullying
the existing AVI muxer with its filth.
Fixes ticket #747.
Signed-off-by: Zane van Iperen
---
MAINTAINERS | 1 +
libavformat/Makefile | 1 +
libavformat/allformats.c | 1 +
libavformat/amvenc.c | 4
Signed-off-by: Zane van Iperen
---
libavcodec/adpcm.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
index d0807cbd98..7f2c958d16 100644
--- a/libavcodec/adpcm.c
+++ b/libavcodec/adpcm.c
@@ -1698,6 +1698,16 @@ static int adpcm_decode_frame(
Fixes ticket #747.
Signed-off-by: Zane van Iperen
---
doc/general_contents.texi | 2 +-
libavcodec/adpcmenc.c | 58 ++-
libavcodec/allcodecs.c| 1 +
libavcodec/utils.c| 1 +
4 files changed, 60 insertions(+), 2 deletions(-)
diff --git a/doc
The format doesn't allow for anything else.
Signed-off-by: Zane van Iperen
---
libavcodec/adpcm.c | 5 -
libavcodec/utils.c | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
index 701b125c47..d34fd6c6e1 100644
--- a/libavcodec/adpc
Signed-off-by: Zane van Iperen
---
libavcodec/adpcm.c | 25 ++-
tests/ref/fate/adpcm-ima-amv | 312 +--
2 files changed, 180 insertions(+), 157 deletions(-)
diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
index d34fd6c6e1..d0807cbd98 100644
--- a/l
Adds support for encoding to adpcm_ima_amv and muxing to AMV.
Things to note:
- AMV is a hard-coded (and broken) subset of AVI. It's not worth sullying the
existing AVI muxer with its filth.
- The muxer is extremely pedantic about its streams, this is to
not break certain software players.
- T
Pretty please ?
Jocke
On Thu, 2020-10-29 at 13:46 +, Joakim Tjernlund wrote:
>
> Ping ..
>
> On Tue, 2020-10-27 at 08:48 +, Joakim Tjernlund wrote:
> >
> > Yet a ping ...
> >
> > This is a simple technical patch, it just needs a policy decision.
> > Can I have one ?
> >
> > Jocke
From: Limin Wang
Signed-off-by: Limin Wang
---
libavformat/rtsp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c
index 49c2d52..4427bd2 100644
--- a/libavformat/rtsp.c
+++ b/libavformat/rtsp.c
@@ -2049,7 +2049,7 @@ static int udp_read
On Mon, Nov 02, 2020 at 11:57:47PM -0500, Andriy Gelman wrote:
> On Thu, 22. Oct 14:21, Limin Wang wrote:
> > ffmpeg | branch: master | Limin Wang | Sat Oct 10
> > 21:30:21 2020 +0800| [92c40ef882be115e72d2aa02f9032b7ce88f8537] |
> > committer: Limin Wang
> >
> > avformat/rtsp: support for list
56 matches
Mail list logo
