On Fri, 2021-10-08 at 10:32 -0300, James Almer wrote:
> Some packages may not define custom cflags, in which case a simple
> "pkg-config --cflags" call will return an empty string.
> This change will be useful to get a valid include path that can be
> used in library checks.
>
> Signed-off-by: Jam
From: Daniel Socek
Signed-off-by: Daniel Socek
Signed-off-by: Haihao Xiang
---
libavcodec/qsvenc.c | 3 +++
libavcodec/qsvenc_hevc.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c
index 06f55604b5..e21a9b1207 100644
--- a/libavcodec/qsvenc.
On Fri, Oct 8, 2021 at 5:49 PM Michael Koch
wrote:
> > Invalid reasoning. Absolute rotations give those issues.
>
> These issues can easily be avoided by keeping the pitch angle in the -89
> to +89 range, for example.
>
> Please don't misunderstand me, I'm not against relative rotations. If
> you
On Fri, Oct 08, 2021 at 10:33:52PM +0800, lance.lmw...@gmail.com wrote:
> From: Limin Wang
>
> Signed-off-by: Limin Wang
> ---
> libavcodec/mpeg12dec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
LGTM
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC78704
On 8 Oct 2021, at 10:25, Thilo Borgmann wrote:
>> Hi,
>>
>> I'm writing ARM64 ASM and testing on Apple M1 and Graviton2 N1 devices.
>> This, however, is not a good spread of micro-architectures among commonly
>> used ARM64 devices. Additional micro-architectures which I would like to
>> test a
Dear,
I'm really sorry to disturb you. I sent you two emails on September
23rd, but I haven't received any reply yet. May I ask if you have received my
patch
-- --
??:
Invalid reasoning. Absolute rotations give those issues.
These issues can easily be avoided by keeping the pitch angle in the -89
to +89 range, for example.
Please don't misunderstand me, I'm not against relative rotations. If
you need relative rotations for your application, feel free to us
On 10/8/2021 11:57 AM, Timo Rothenpieler wrote:
On 08.10.2021 15:32, James Almer wrote:
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library ch
On 08.10.2021 15:32, James Almer wrote:
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library checks.
Is that at all a standard thing with pkgc
On Thu, Oct 7, 2021 at 1:24 PM Pierre-Anthony Lemieux wrote:
>
> On Thu, Oct 7, 2021 at 1:03 PM Lynne wrote:
> >
> > 6 Oct 2021, 02:45 by p...@sandflow.com:
> >
> > > On Tue, Oct 5, 2021 at 5:03 PM Lynne wrote:
> > >
> > >>
> > >> 5 Oct 2021, 17:22 by p...@sandflow.com:
> > >>
> > >> > Hi Lynne,
From: Limin Wang
Signed-off-by: Limin Wang
---
libavcodec/videotoolboxenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index 93c3898..bac36fd 100644
--- a/libavcodec/videotoolboxenc.c
+++ b/libavcodec/videotool
From: Limin Wang
Signed-off-by: Limin Wang
---
libavcodec/mpeg12dec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/mpeg12dec.c b/libavcodec/mpeg12dec.c
index e6ada1c..09b2902 100644
--- a/libavcodec/mpeg12dec.c
+++ b/libavcodec/mpeg12dec.c
@@ -2265,7 +2265,7 @@
From: Limin Wang
Signed-off-by: Limin Wang
---
libavcodec/avs3_parser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/avs3_parser.c b/libavcodec/avs3_parser.c
index 1a05ea0..d04d96a 100644
--- a/libavcodec/avs3_parser.c
+++ b/libavcodec/avs3_parser.c
@@ -73,7 +7
From: Limin Wang
Signed-off-by: Limin Wang
---
libavcodec/audiotoolboxdec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/audiotoolboxdec.c b/libavcodec/audiotoolboxdec.c
index a222cde..9939fef 100644
--- a/libavcodec/audiotoolboxdec.c
+++ b/libavcodec/audiotool
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library checks.
Signed-off-by: James Almer
---
configure | 5 -
1 file changed, 4 insertions(+
On Fri, Oct 8, 2021 at 2:11 PM Michael Koch
wrote:
> I'd like to suggest to revert this patch for the v360 filter:
> http://ffmpeg.org/pipermail/ffmpeg-cvslog/2020-October/124887.html
>
> Why should it be reverted?
> -- Because after this patch, the yaw, pitch and roll angles have a
> different m
On 10/8/2021 5:14 AM, Andreas Rheinhardt wrote:
avcodec_receive_packet() already unreferences the packet on its own.
Signed-off-by: Andreas Rheinhardt
---
fftools/ffmpeg.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 0e38d6d185..14611480f1 1
On 10/7/2021 12:47 PM, Andreas Rheinhardt wrote:
Andreas Rheinhardt:
James Almer:
On 10/1/2021 6:08 PM, Andreas Rheinhardt wrote:
Signed-off-by: Andreas Rheinhardt
---
One could also do this more generically in the ffmpeg function.
tests/fate-run.sh | 2 +-
1 file changed, 1 insertion(+
On 10/8/2021 8:49 AM, Andreas Rheinhardt wrote:
Avoids checks lateron in the hot path.
Signed-off-by: Andreas Rheinhardt
---
fftools/ffmpeg.c | 16 +---
fftools/ffmpeg_opt.c | 4 ++--
2 files changed, 3 insertions(+), 17 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools
NAK
___
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".
I'd like to suggest to revert this patch for the v360 filter:
http://ffmpeg.org/pipermail/ffmpeg-cvslog/2020-October/124887.html
Why should it be reverted?
-- Because after this patch, the yaw, pitch and roll angles have a
different meaning. If they are set in the command line, they are
interpr
On Fri, Oct 8, 2021 at 4:25 PM Thilo Borgmann wrote:
>
> Hi,
>
> On 8 Oct 2021, at 1:21, J. Dekker wrote:
>
> > Hi,
> >
> > I'm writing ARM64 ASM and testing on Apple M1 and Graviton2 N1
> > devices. This, however, is not a good spread of micro-architectures
> > among commonly used ARM64 devices.
Avoids checks lateron in the hot path.
Signed-off-by: Andreas Rheinhardt
---
fftools/ffmpeg.c | 16 +---
fftools/ffmpeg_opt.c | 4 ++--
2 files changed, 3 insertions(+), 17 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 14611480f1..9d4f9d7a2b 100644
--- a/f
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 18 ++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_convolve.c | 370 +-
4 files changed, 346 insertions(+), 44 deletions(-)
diff --git a/doc/filters.texi b/do
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 31
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_limitdiff.c | 370 +
4 files changed, 403 insertions(+)
create mode 100644 libavfilter/vf_limitdiff.c
lgtm
___
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".
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".
LGTM
___
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".
Hi,
On 8 Oct 2021, at 1:21, J. Dekker wrote:
Hi,
I'm writing ARM64 ASM and testing on Apple M1 and Graviton2 N1
devices. This, however, is not a good spread of micro-architectures
among commonly used ARM64 devices. Additional micro-architectures
which I would like to test are 'High Efficien
avcodec_receive_packet() already unreferences the packet on its own.
Signed-off-by: Andreas Rheinhardt
---
fftools/ffmpeg.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 0e38d6d185..14611480f1 100644
--- a/fftools/ffmpeg.c
+++ b/fftools/ffmpeg.c
The output stream's packet may not have been allocated
at that point. This happens when quitting in the following command line:
$ ./ffmpeg -lavfi abuffer=sample_fmt=u8:sample_rate=48000:channel_layout=stereo
-f null -
Signed-off-by: Andreas Rheinhardt
---
Is there actually a reason that this pac
Should fix failures in the cover-art-flac-remux test.
Signed-off-by: Andreas Rheinhardt
---
Sorry for this; will apply this soon.
tests/fate-run.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/fate-run.sh b/tests/fate-run.sh
index 87b5539296..fbfc0a925d 100755
When inserting an auto-resampler, it may be that the configuration
of the filters that the auto-resampler is supposed to connect is
already partially merged, i.e. converter->inputs[0].incfg.foo and
converter->outputs[0].outcfg.foo (where foo is one of formats,
samplerates, channel_layouts) can coin
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
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]
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
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
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
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.
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 |
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
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
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
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
44 matches
Mail list logo
