On Thu, Jul 21, 2022 at 12:46:38AM +0200, Michael Niedermayer wrote:
> On Thu, Jul 21, 2022 at 12:17:22AM +0200, Andreas Rheinhardt wrote:
> > Michael Niedermayer:
> > > On Tue, Jul 19, 2022 at 08:37:38AM -0300, James Almer wrote:
> > >>
> > >>
> > >> On 7/19/2022 8:34 AM, Michael Niedermayer wrote
On Thu, 2022-07-21 at 00:45 +0200, Andreas Rheinhardt wrote:
> Xiang, Haihao:
> > From: Haihao Xiang
> >
> > Multi-frame encode isn't supported for MFX_VERSION >= 2.0[1][2]. This is
> > in preparation for oneVPL support
> >
> > [1]
> > https://spec.oneapi.io/versions/latest/elements/oneVPL/sour
Thanks for calling that out. It looks like I was cross-compiling for 32-bit
incorrectly from my 64-bit host. I've reproduced the failure and submitted
a v2 with the fix. If you're still seeing build failures even after v2, can
you also provide more details on how you are building so I can reproduce
Add a new version of yadif_filter_line performed using packed bytes
instead of the packed words used by the current implementaiton. As
a result this implementation runs almost 2x as fast as the current
fastest SSSE3 implementation.
This implementation is created from scratch based on the C code, w
filter_line is generally vectorized, wheras filter_edge is implemented
in C. Currently we rely on filter_edge to process non-edges in cases
where the width doesn't match the alignment. This causes us to process
non-edge pixels with the slow C implementation vs the faster SSE
implementation.
It is
Reformat some of the code to improve readability and reduce code
duplication. This change is intended to be purely cosmentic and
shouldn't result in any functional changes.
Signed-off-by: Chris Phlipot
---
libavfilter/vf_yadif.c | 11 +--
libavfilter/yadif.h| 3 +--
2 files changed,
Allow the alignment to be determined based on what yadif_filter_line
implementation is used. Currently this is either 1, or 8 depending
on whether the C code or the x86 SSE code is used, but allows for
other future implementations that use a larger alignment.
Adjusting MAX_ALIGN to 32 in the case
If alignment is set to less than 4 filter_edges will produce incorrect
output and not filter the entire edge. To fix this, make sure that
the edge size is at least 3.
Signed-off-by: Chris Phlipot
---
libavfilter/vf_yadif.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/l
On Thu, Jul 21, 2022 at 12:17:22AM +0200, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > On Tue, Jul 19, 2022 at 08:37:38AM -0300, James Almer wrote:
> >>
> >>
> >> On 7/19/2022 8:34 AM, Michael Niedermayer wrote:
> >>> Fixes: Timeout
> >>> Fixes:
> >>> 49160/clusterfuzz-testcase-minimized-f
Xiang, Haihao:
> From: Haihao Xiang
>
> Multi-frame encode isn't supported for MFX_VERSION >= 2.0[1][2]. This is
> in preparation for oneVPL support
>
> [1]
> https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
> [2] https://git
James Almer:
> The amount of padding samples reported by containers take into account the
> extended samplerate in HE-AAC.
>
> Fixes ticket #9671.
>
> Signed-off-by: James Almer
> ---
> libavcodec/aacdec_template.c | 3 ---
> tests/ref/fate/audiomatch-afconvert-16000
Michael Niedermayer:
> On Tue, Jul 19, 2022 at 08:37:38AM -0300, James Almer wrote:
>>
>>
>> On 7/19/2022 8:34 AM, Michael Niedermayer wrote:
>>> Fixes: Timeout
>>> Fixes:
>>> 49160/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_FFV1_fuzzer-5672826144686080
>>>
>>> Found-by: continuous fuzzing
Zane van Iperen:
> Signed-off-by: Zane van Iperen
> ---
> libavformat/argo_cvg.c | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/libavformat/argo_cvg.c b/libavformat/argo_cvg.c
> index 12465dcbcc..3d4abb4758 100644
> --- a/libavformat/argo_cvg.c
> +++ b/libavformat/argo_cvg.c
>
On 20/07/2022 10:21, Mark Himsley wrote:
On Tue, 19 Jul 2022 at 13:20, Timo Rothenpieler wrote:
I added an explicit configure check for that type.
Definitely odd, IDXGIOutput5 and it are both Windows 10 APIs, so I'd
have expected them to always exist in tandem.
Thank you - that fixed the bui
On Tue, 19 Jul 2022 at 19:16, Nicolas George wrote:
>
> Emil Velikov (12022-07-19):
> > As you may know the libva* set of libraries share an internal ABI
> > between them. In a resent libva commit, the va_fool API was removed.
> >
> > Thus if one is to mix different versions of libva.so and libva-
On Wed, 20 Jul 2022 at 11:56, Emil Velikov wrote:
>
> From: Emil Velikov
>
> There is an internal ABI between libva.so the libva-XXX.so libraries.
>
> With a recent change, the internal va_fool API was removed breaking the
> ABI. So if libva.so and libva-x11.so are from different version, the
> w
Thanks, I hand patched that back into a newer ffmpeg and with a few changes it
worked great.
-Original Message-
From: ffmpeg-devel On Behalf Of Devin
Heitmueller
Sent: Tuesday, July 19, 2022 11:40 AM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] Live Transc
On Sun, Jul 17, 2022 at 10:01:19AM +0200, Martijn van Beurden wrote:
> Op zo 17 jul. 2022 om 00:50 schreef Michael Niedermayer <
> mich...@niedermayer.cc>:
>
> > ATM we have to maintain many releases because each is used by some distro
> > the LTS designation might cause distros to coalescence on
Signed-off-by: Zane van Iperen
---
libavformat/argo_cvg.c | 28 +---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/libavformat/argo_cvg.c b/libavformat/argo_cvg.c
index be78091f0c..32247a06be 100644
--- a/libavformat/argo_cvg.c
+++ b/libavformat/argo_cvg.c
Signed-off-by: Zane van Iperen
---
libavformat/argo_cvg.c | 4
1 file changed, 4 deletions(-)
diff --git a/libavformat/argo_cvg.c b/libavformat/argo_cvg.c
index 32247a06be..12465dcbcc 100644
--- a/libavformat/argo_cvg.c
+++ b/libavformat/argo_cvg.c
@@ -159,13 +159,9 @@ static int argo_cvg_r
Signed-off-by: Zane van Iperen
---
libavformat/argo_cvg.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/libavformat/argo_cvg.c b/libavformat/argo_cvg.c
index 12465dcbcc..3d4abb4758 100644
--- a/libavformat/argo_cvg.c
+++ b/libavformat/argo_cvg.c
@@ -162,6 +162,15 @@ static int argo
Signed-off-by: Zane van Iperen
---
libavformat/argo_cvg.c | 31 +++
1 file changed, 15 insertions(+), 16 deletions(-)
diff --git a/libavformat/argo_cvg.c b/libavformat/argo_cvg.c
index f32487023a..be78091f0c 100644
--- a/libavformat/argo_cvg.c
+++ b/libavformat/argo_c
On Wed, Jul 20, 2022 at 06:58:10PM +1000, Peter Ross wrote:
> On Tue, Jul 19, 2022 at 01:34:50PM +0200, Michael Niedermayer wrote:
> > Fixes: Timeout
> > Fixes:
> > 49003/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MMVIDEO_fuzzer-5550368423018496
> >
> > Found-by: continuous fuzzing process
On Tue, Jul 19, 2022 at 08:37:38AM -0300, James Almer wrote:
>
>
> On 7/19/2022 8:34 AM, Michael Niedermayer wrote:
> > Fixes: Timeout
> > Fixes:
> > 49160/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_FFV1_fuzzer-5672826144686080
> >
> > Found-by: continuous fuzzing process
> > https://gi
On Tue, Jul 19, 2022 at 01:34:48PM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/mpeg4videoenc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
will apply
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
On Wed, Jul 20, 2022 at 08:55:45AM +0200, Paul B Mahol wrote:
> lgtm
will apply
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On an
On Tue, Jul 19, 2022 at 09:41:17PM -0700, Chris Phlipot wrote:
> Add a new version of yadif_filter_line performed using packed bytes
> instead of the packed words used by the current implementaiton. As
> a result this implementation runs almost 2x as fast as the current
> fastest SSSE3 implementati
> On Jul 20, 2022, at 8:18 PM, facefunk wrote:
>
> It's commonly the case with forced subtitle tracks that samples are more
> than INT_MAX microseconds (35m47.48s) apart. This being the case, packet
> duration will be deemed out of range by check_pkt and the packet dts set to
> an incorrect val
It's commonly the case with forced subtitle tracks that samples are more
than INT_MAX microseconds (35m47.48s) apart. This being the case, packet
duration will be deemed out of range by check_pkt and the packet dts set to
an incorrect value, even if pkt->duration is actually valid.
I had begun wor
From: Emil Velikov
Similar to the VAAPI_X11 bits, guard all the VAAPI_DRM parts behind a
compiler guard.
Signed-off-by: Emil Velikov
---
libavutil/hwcontext_vaapi.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index 7
From: Emil Velikov
There is an internal ABI between libva.so and libva-drm.so. So having
mismatched versions can cause all sorts of issues.
We had the breakage between libva.so and libva-x11.so addressed with
earlier commit. There's no point in waiting for things to break wrt
libva-drm.so so pre
From: Emil Velikov
There is an internal ABI between libva.so the libva-XXX.so libraries.
With a recent change, the internal va_fool API was removed breaking the
ABI. So if libva.so and libva-x11.so are from different version, the
whole stack will crash.
Instead we can dlopen() the libva-x11 lib
Greetings everyone,
As you may know the libva* set of libraries share an internal ABI
between them. In a resent libva commit, the va_fool API was removed.
Thus if one is to mix different versions of libva.so and libva-x11.so
they will get an error, leading to a crash of the whole stack.
The simp
Amir Mazzarella (12022-07-19):
> I understand that FFmpeg does not contain accommodations, but in my
> opinion it is less of an accommodation and more for readability, avoiding
> an implicit cast. An explicit void pointer cast, like the one presented in
The arguments against useless casts have bee
On Tue, Jul 19, 2022 at 01:34:50PM +0200, Michael Niedermayer wrote:
> Fixes: Timeout
> Fixes:
> 49003/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MMVIDEO_fuzzer-5550368423018496
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Sig
On 18/7/2022 11:45 pm, Andreas Rheinhardt wrote:
av_log(s, AV_LOG_TRACE, "size = %u\n", ctx->header.size);
-av_log(s, AV_LOG_TRACE, "unk= %u, %u\n", ctx->header.unk1,
ctx->header.unk2);
+av_log(s, AV_LOG_TRACE, "loop = %u\n", ctx->header.loop);
+av_log(s
On Tue, 2022-07-19 at 07:18 +, Xiang, Haihao wrote:
> On Mon, 2022-07-18 at 15:02 +0200, Anton Khirnov wrote:
> > Quoting Xiang, Haihao (2022-07-12 08:27:32)
> > > +static int qsv_va_update_config(void *ctx, mfxHDL handle, mfxConfig cfg)
> > > +{
> > > +#if CONFIG_VAAPI
> > > +#if VA_CHECK_VERS
From: Haihao Xiang
This allows user to build FFmpeg against Intel oneVPL. oneVPL 2.6
is the required minimum version when building Intel oneVPL code.
It will fail to run configure script if both libmfx and libvpl are
enabled.
It is recommended to use oneVPL for new work, even for currently avai
From: Haihao Xiang
MFX_RATECONTROL_LA_EXT isn't supported for MFX_VERSION >= 2.0[1][2].
This is in preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
-
From: Haihao Xiang
Use the mfxLoader handle in qsv hwdevice to create mfx session for qsv
filters.
This is in preparation for oneVPL support
---
libavfilter/qsvvpp.c | 109 ---
libavfilter/qsvvpp.h | 5 ++
libavfilter/vf_deinterlace_qsv.c |
From: Haihao Xiang
If qsv hwdevice is available, use the mfxLoader handle in qsv hwdevice
to create mfx session. Otherwise create mfx session with a new mfxLoader
handle.
This is in preparation for oneVPL support
---
libavcodec/qsv.c | 226 +++---
libavc
From: Haihao Xiang
In oneVPL, MFXLoad() and MFXCreateSession() are required to create a
workable mfx session[1]
Add config filters for D3D9/D3D11 session (galinart)
The default device is changed to d3d11va for oneVPL when both d3d11va
and dxva2 are enabled on Microsoft Windows
This is in prepa
From: Haihao Xiang
In oneVPL, a valid mfxLoader handle is needed when creating mfx session
for decoding, encoding and processing[1], so add loader field to
AVQSVDeviceContext. User should fill this field before calling
av_hwdevice_ctx_init() if using oneVPL
This is in preparation for oneVPL supp
From: Haihao Xiang
Multi-frame encode isn't supported for MFX_VERSION >= 2.0[1][2]. This is
in preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
From: Haihao Xiang
OPAQUE memory isn't supported for MFX_VERSION >= 2.0[1][2]. This is in
preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
libav
From: Haihao Xiang
Audio isn't supported for MFX_VERSION >= 2.0[1][2]. This is in
preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
libavcodec/qs
From: Haihao Xiang
User plugin isn't supported for MFX_VERSION >= 2.0[1][2]. This is in
preparation for oneVPL Support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
libavco
From: Haihao Xiang
The following Cflags has been added to libmfx.pc, so mfx/ prefix is no
longer needed when including mfx headers in FFmpeg.
Cflags: -I${includedir} -I${includedir}/mfx
Some old versions of libmfx have the following Cflags in libmfx.pc
Cflags: -I${includedir}
We may add -
From: Haihao Xiang
The data structures for VP9 in mfxvp9.h is wrapped by
MFX_VERSION_NEXT, which means those data structures have never been used
in a public release. Actually MFX_CODEC_VP9 and other VP9 stuffs is
added in mfxstructures.h. In addition, mfxdefs.h is included in
mfxvp9.h, so we may
From: Haihao Xiang
Intel's oneVPL is a successor to MediaSDK, but removed some obsolete
features of MediaSDK[1], some early versions of oneVPL still use libmfx
as library name[2]. However some of obsolete features, including OPAQUE
memory, multi-frame encode, user plugins and LA_EXT rate control
From: Haihao Xiang
The oneAPI Video Processing Library (oneVPL) is a single interface for
encode, decode and video processing[1][2]. oneVPL is a successor to Intel(R)
Media
SDK, but removed obsolete features. Intel(R) Media SDK lifetime comes to an
end now, new features for new Intel Gen platfor
On Tue, 19 Jul 2022 at 13:20, Timo Rothenpieler wrote:
> I added an explicit configure check for that type.
> Definitely odd, IDXGIOutput5 and it are both Windows 10 APIs, so I'd
> have expected them to always exist in tandem.
Thank you - that fixed the build for me.
> You might want to update
52 matches
Mail list logo
