On Fri, Oct 15, 2021 at 6:12 AM Gyan Doshi wrote:
>
>
> On 2021-10-15 12:35 am, Paul B Mahol wrote:
> > will revert in next 96 hours.
>
> Devote time to something productive.
>
Great words you do not follow at all.
>
> In any case, not all filters have identical lists. spectrumsynth
> supports
On Thu, Oct 14, 2021 at 9:10 PM wrote:
>
> From: Limin Wang
>
> By <>
>
> Signed-off-by: Limin Wang
> ---
> libavformat/mov.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index 57c67e3..49a8c27 100644
> --- a/libavformat/mov.
applied
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
On 10/11/2021 12:36 PM, Andreas Rheinhardt wrote:
Signed-off-by: Andreas Rheinhardt
---
libavcodec/libdav1d.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavcodec/libdav1d.c b/libavcodec/libdav1d.c
index 2807210e50..2d5fccec71 100644
--- a/libavcodec/libdav1d.c
+++ b/libavcodec/l
On Thu, Oct 14, 2021 at 12:10:36AM +0300, Jan Ekström wrote:
> Looking at 3f75e5116b900f1428aa13041fc7d6301bf1988a, the field
> was supposed to be private, but during merging the field and the
> group that had the comment about it got separated.
>
> Thus, move the actual privately utilized state o
On Thu, Oct 14, 2021 at 12:10:37AM +0300, Jan Ekström wrote:
> Such fields can be seen as generally useful in cases where the
> API user is not implementing custom AVIO callbacks, but still would
> like to know if data is being read or written out, such as in case
> data is being read from input bu
On Thu, Oct 14, 2021 at 07:19:37AM +, Wu, Jianhua wrote:
> Ping.
>
> > -Original Message-
> > From: Wu, Jianhua
> > Sent: Thursday, September 30, 2021 4:44 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Cc: Wu, Jianhua
> > Subject: [PATCH v3 1/4] libswscale/x86/rgb2rgb: add shuffle_bytes avx
Hi,
I've fixed the issues pointed out in the earlier discussion at
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2021-September/285688.html
Are there still any problems that block this patch getting applied? I'm
happy to make any changes if needed.
__
The oneAPI Video Processing Library (oneVPL) is a single interface for
encode, decode and video processing[1]. 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 platforms will be supported in o
Intel's oneVPL is a successor to MediaSDK, but removed some obsolete
features of MediaSDK[1]. Some early versions of oneVPL still uses libmfx
as library name[2], however some of obsolete features, including OPAQUE
memory, multi-frame encode, user plugins and LA_EXT rate control mode
etc, have been
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 use the check in thi
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 -I${includedir}/mfx to
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/appendix/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2]: https://github.com/oneapi-src/oneVPL
---
libavcodec/qsv.c
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/appendix/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2]: https://github.com/oneapi-src/oneVPL
---
libavcodec/qsv.c |
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/appendix/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2]: https://github.com/oneapi-src/oneVPL
---
libavcodec/qsv.
In oneVPL, MFXLoad() and MFXCreateSession() are required to create a
workable mfx session[1]
Add AccelerationMode config filter 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 preparatio
This allows user to build FFmpeg against Intel oneVPL. oneVPL 2.2
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 available
hardwares [1]
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/appendix/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2]: https://github.com/oneapi-src/oneVPL
---
libavcodec
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/appendix/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2]: https://github.com/oneapi-src/oneVPL
---
libavc
Michael wrote:
> > On Thu, Oct 14, 2021 at 07:19:37AM +, Wu, Jianhua wrote:
> > Ping.
> >
> > Hi there,
> >
> > Any update?
> you posted a v4 but "ping" v3 ?
> is that intended
No, it's not intentional. I'm sorry I pinged an incorrect version, and the v4
is for updating the incorre
On Fri, Oct 15, 2021 at 04:40:26PM +0800, myp...@gmail.com wrote:
> On Thu, Oct 14, 2021 at 9:10 PM wrote:
> >
> > From: Limin Wang
> >
> > By < > 2.2>>
> >
> > Signed-off-by: Limin Wang
> > ---
> > libavformat/mov.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git
On Fri, Oct 15, 2021 at 08:52:39AM +0200, Paul B Mahol wrote:
> On Fri, Oct 15, 2021 at 12:20 AM James Almer wrote:
>
> > On 10/14/2021 7:13 PM, Michael Niedermayer wrote:
> > > Fixes: signed integer overflow: 2105344 * 539033345 cannot be
> > represented in type 'int'
> > > Fixes: out of array w
On Fri, Oct 15, 2021 at 7:26 PM Michael Niedermayer
wrote:
> On Fri, Oct 15, 2021 at 08:52:39AM +0200, Paul B Mahol wrote:
> > On Fri, Oct 15, 2021 at 12:20 AM James Almer wrote:
> >
> > > On 10/14/2021 7:13 PM, Michael Niedermayer wrote:
> > > > Fixes: signed integer overflow: 2105344 * 5390333
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Haihao Xiang
> Sent: Friday, October 15, 2021 3:39 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Haihao Xiang
> Subject: [FFmpeg-devel] [PATCH v6 00/10] make QSV works with the
> Intel's oneVPL
>
> The oneAPI Video Processing Library (
On Fri, Oct 15, 2021 at 07:30:20PM +0200, Paul B Mahol wrote:
> On Fri, Oct 15, 2021 at 7:26 PM Michael Niedermayer
> wrote:
>
> > On Fri, Oct 15, 2021 at 08:52:39AM +0200, Paul B Mahol wrote:
> > > On Fri, Oct 15, 2021 at 12:20 AM James Almer wrote:
> > >
> > > > On 10/14/2021 7:13 PM, Michael
The attached patch removes build paths from the resulting binaries,
which makes it easier to verify the reproducibility of a build without
needing to know the path from which it was originally built.
I ran "make fate" with and without the patch applied, and all of the
tests that passed as of commi
26 matches
Mail list logo
