On Tue, Feb 13, 2024 at 6:39 PM Frank Plowman wrote:
> On 13/02/2024 02:30, Nuo Mi wrote:
> > fc->ref points to an old VVCFrame, which cannot be used after
> frame_context_setup.
> > This prevents crashes in decode_nal_units-->ff_vvc_report_frame_finished.
> >
> > Signed-off-by: Frank Plowman
>
On Mon, Feb 12, 2024 at 10:34 PM Dariusz Marcinkiewicz via
ffmpeg-devel wrote:
>
> This exposes VP8E_SET_SCREEN_CONTENT_MODE option from libvpx.
>
> Co-authored-by: Erik Språng
> Signed-off-by: Dariusz Marcinkiewicz
> ---
> doc/encoders.texi | 6 ++
> libavcodec/libvpxenc.c | 13 +
>
>
>>>
>>> If there are no objections, I'll push it tomorrow.
> thank you, Kieran and Paul.
>
Hi Kieran,
Patchwork didn't get your patch.
I've checked the fate status locally, and it indicates that "make fate-vvc"
will fail.
Could you please send a new one to the patchwork?
Thank you.
___
On 2/13/2024 10:55 PM, Dmitrii Ovchinnikov wrote:
+const FormatMap format_map[] =
+{
+{ AV_PIX_FMT_NONE, AMF_SURFACE_UNKNOWN },
+{ AV_PIX_FMT_NV12, AMF_SURFACE_NV12 },
+{ AV_PIX_FMT_BGR0, AMF_SURFACE_BGRA },
+{ AV_PIX_FMT_RGB0, AMF_SURFACE_RGBA
Hello.
On Tue, Feb 13, 2024 at 12:12 AM James Zern wrote:
>
[...]
> > +@item screen-content-mode
> > +Screen content mode, one of: off (0), screen (1), screen with more
> > aggressive rate control (2).
> > +
>
> Move this above 'VP9-specific options' and add a section for VP8. Also
> reword this
From: Evgeny Pavlov
Signed-off-by: Evgeny Pavlov
---
doc/filters.texi | 238 +++
1 file changed, 238 insertions(+)
diff --git a/doc/filters.texi b/doc/filters.texi
index e0436a5755..4c5b9c1f63 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -
From: Evgeny Pavlov
This commit adds two AMF filters: scale_amf & scale_amf_hq.
Both filters are using AMF hardware acceleration.
scale_amf supports simple scaling algorithms & color conversion.
scale_amf_hq supports advanced scaling algorithms & might be used
for upscaling only.
Signed-off-by:
Co-authored-by: Evgeny Pavlov
---
libavcodec/amfenc.c | 560
libavcodec/amfenc.h | 23 +-
2 files changed, 158 insertions(+), 425 deletions(-)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
index f1b76bd6aa..e6e5302cca 100644
--- a/libavcodec
From: Evgeny Pavlov
This commit adds option for enabling SmartAccess Video (SAV)
in AMF encoders. SAV is an AMD hardware-specific feature which
enables the parallelization of encode and decode streams across
multiple Video Codec Engine (VCN) hardware instances.
Signed-off-by: Evgeny Pavlov
---
From: Evgeny Pavlov
v2: refactored after review
Signed-off-by: Evgeny Pavlov
Co-authored-by: Dmitrii Ovchinnikov
---
libavcodec/amfenc.c | 2 ++
libavcodec/amfenc_av1.c | 22 ++
2 files changed, 24 insertions(+)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
From: nyanmisaka
v2: fixes for indentation
---
libavcodec/amfenc.c | 83 +
1 file changed, 83 insertions(+)
diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c
index 0bd15dd812..068bb53002 100644
--- a/libavcodec/amfenc.c
+++ b/libavcodec/amfenc.c
From: Michael Fabian 'Xaymar' Dirks
added 10 bit support for amf hevc.
before:
command - ffmpeg.exe -hide_banner -y -hwaccel d3d11va -hwaccel_output_format
d3d11 -i test_10bit_file.mkv -an -c:v h264_amf res.dx11_hw_h264.mkv
output - Format of input frames context (p010le) is not supported by
From: Evgeny Pavlov
Added AMF based h264, hevc, av1 decoders.
Co-authored-by: Dmitrii Ovchinnikov
---
libavcodec/Makefile | 4 +-
libavcodec/allcodecs.c | 3 +
libavcodec/amfdec.c | 667
libavcodec/amfdec.h | 75 +
libavcodec/h264_s
Adds hwcontext_amf, which allows to use shared AMF
context for the encoder, decoder and AMF-based filters,
without copy to the host memory.
It will also allow you to use some optimizations in
the interaction of components (for example, SAV) and make a more
manageable and optimal setup for using GPU
On 2/12/2024 11:54 PM, Nuo Mi wrote:
On Sun, Feb 11, 2024 at 4:21 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
Besides simplifying address computations (it saves 432B of .text
in hevcdsp.o alone here) it also fixes undefined behaviour that
occurs if mx or my are 0 (happens whe
Delete{Global,Local}Ref already handle NULL.
---
libavcodec/mediacodec_wrapper.c | 189
1 file changed, 47 insertions(+), 142 deletions(-)
diff --git a/libavcodec/mediacodec_wrapper.c b/libavcodec/mediacodec_wrapper.c
index 536b5b8e81..19d63e2ba0 100644
--- a/liba
Delete{Global,Local}Ref() already handle NULL.
---
libavutil/jniutils.c | 14 +++---
1 file changed, 3 insertions(+), 11 deletions(-)
diff --git a/libavutil/jniutils.c b/libavutil/jniutils.c
index 89623af3f8..beedf24c0d 100644
--- a/libavutil/jniutils.c
+++ b/libavutil/jniutils.c
@@ -236,
Reduces a bit the horizontal spacing.
---
libavcodec/mediacodec_wrapper.c | 138 +---
1 file changed, 72 insertions(+), 66 deletions(-)
diff --git a/libavcodec/mediacodec_wrapper.c b/libavcodec/mediacodec_wrapper.c
index bc3eb0a80d..536b5b8e81 100644
--- a/libavcodec/m
---
libavutil/jniutils.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavutil/jniutils.h b/libavutil/jniutils.h
index 2be401c974..01f3acb88d 100644
--- a/libavutil/jniutils.h
+++ b/libavutil/jniutils.h
@@ -24,6 +24,7 @@
#define AVUTIL_JNIUTILS_H
#include
+#include
Handles Android content-uri starting with content://.
---
configure | 2 +
doc/APIchanges | 3 +
libavformat/Makefile| 1 +
libavformat/file.c | 157
libavformat/protocols.c | 1 +
5 files changed, 164 insertions(+)
This will allow users to pass the Android ApplicationContext which is mandatory
to retrieve the ContentResolver responsible to resolve/open Android content-uri.
---
libavutil/jni.c | 28
libavutil/jni.h | 17 +
2 files changed, 45 insertions(+)
diff --
This will allow to use the jni utils in libavformat. This will be mostly useful
to add Android content-uri support.
This deprecates avcodec/jni.h functions in favor of the ones from avutil/jni.h.
---
doc/APIchanges | 6 +
libavcodec/Makefile|
Hi,
On Android, content providers are used for accessing files through shared
mechanisms. One typical case would be an app willing to open a video from
Google Photos, gallery apps, TikTok, Instagram or some other providers.
A content URI looks something like "content://authority/path/id", see:
htt
Hello,
On Fri, 2 Feb 2024, at 08:26, wenbin.chen-at-intel@ffmpeg.org wrote:
> +static void infer_completion_callback(void *args) {
> +THRequestItem *request = (THRequestItem*)args;
> +LastLevelTaskItem *lltask = request->lltask;
> +TaskItem *task = lltask->task;
> +DNNData outp
Write EXIF metadata exposed AV_FRAME_DATA_EXIF as an eXIf chunk
to PNG files, if present.
Signed-off-by: Leo Izen
---
libavcodec/pngenc.c | 4
1 file changed, 4 insertions(+)
diff --git a/libavcodec/pngenc.c b/libavcodec/pngenc.c
index 50689cb50c..a302c879da 100644
--- a/libavcodec/pngenc.
Add support to parse eXIf chunks using the new EXIF framework.
Signed-off-by: Leo Izen
---
libavcodec/pngdec.c | 35 +++
1 file changed, 35 insertions(+)
diff --git a/libavcodec/pngdec.c b/libavcodec/pngdec.c
index 026da30c25..e7951d1802 100644
--- a/libavcodec/p
This patch centralizes much of the EXIF parsing and handling code for
libavcodec, and delegates its own AVFrameSideData type to containing
the buffer that holds EXIF metadata. This patch also adds exposes the
exif parsing routing so it can be called by ffprobe, and updates the
corresponding FATE te
A few notes:
- This includes an avpriv_ removal, so it won't be able to be merged
until the ABI is bumped. Alternatively, I could add that avipriv_
back in as a wrapper around the actual API so it's not a blocker,
and then we can remove it when the time comes to bump the ABI.
- MakerNote insi
On Tue, 13 Feb 2024, James Almer wrote:
On 2/12/2024 6:15 PM, Marton Balint wrote:
Signed-off-by: Marton Balint
---
libavutil/channel_layout.h | 4
1 file changed, 4 insertions(+)
diff --git a/libavutil/channel_layout.h b/libavutil/channel_layout.h
index b8bff6f365..db0c005e8
Rémi Denis-Courmont (12024-02-13):
> Speaking as an elected member of another OSS project's TC, I believe
> that the experienced adult developers on the FFmpeg TC are perfectly
> capable of reading mailing archives and Trac comments as necessary. In
> fact, I think it is preferable that they stick
Hi,
Le 13 février 2024 18:22:46 GMT+02:00, Nicolas George a écrit
:
>Martin Storsjo (12024-02-13):
>> The main arguments raised were about API consistency, prevention of
>> accidental inclusions, as well as explicitness in marking a field as
>> public or private.
>
>Too bad the committee negle
If a custom layout is equivalent to a native one, check if it matches one of the
known layout names and print that instead.
Signed-off-by: James Almer
---
Should be applied after the patch this one is a reply to.
libavutil/channel_layout.c| 68 +--
tests/ref/
Andreas Rheinhardt:
> avfilter_insert_filter() already reports (also with AV_LOG_VERBOSE)
> when a filter is auto-inserted.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> Can be applied at any time.
>
> libavfilter/af_hdcd.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/libavfilter
On 2/12/2024 6:15 PM, Marton Balint wrote:
Signed-off-by: Marton Balint
---
libavutil/channel_layout.h | 4
1 file changed, 4 insertions(+)
diff --git a/libavutil/channel_layout.h b/libavutil/channel_layout.h
index b8bff6f365..db0c005e87 100644
--- a/libavutil/channel_layout.h
+++ b/lib
On 2024-01-27 04:08 pm, Gyan Doshi wrote:
Set up framework for non-PCM decoding in-place and
add support for Dolby-E decoding.
Useful for direct transcoding of non-PCM audio in live inputs.
Plan to push in 3 days, barring objections.
Regards,
Gyan
---
configure | 1 +
doc/
Martin Storsjo (12024-02-13):
> The main arguments raised were about API consistency, prevention of
> accidental inclusions, as well as explicitness in marking a field as
> public or private.
Too bad the committee neglected to ask for the arguments of the people
who opposed this. Like having a tri
Hi,
Last year, Anton raised the conflict on his patch "lavfi: get rid of
FF_INTERNAL_FIELDS",
https://lists.ffmpeg.org//pipermail/ffmpeg-devel/2023-January/306102.html, to
the TC to decide on.
At the time, the TC did not come to any conclusion on the matter. Recently,
Anton raised the questio
On Tue, 13 Feb 2024, Ridley Combs wrote:
It looks like checkout has different behavior from reset, and fate uses a
hard reset.
To test, I committed the change adding tests/ref/** -text,
unix2dos'd tests/ref/fate/sub-scc, then ran git -c core.autocrlf=true reset
--quiet --hard; this dos2unix'd th
On Tue, 13 Feb 2024, Andreas Rheinhardt wrote:
Since 7bf1b9b35769b37684dd2f18a54f01d852a540c8,
the test produces ordinary \n, yet this is not what the reference
file used for the most time, leading to test failures.
Signed-off-by: Andreas Rheinhardt
---
tests/fate/subtitles.mak | 1 +
1 file ch
asivery via ffmpeg-devel:
> I've attached the updated patch. Both new entries are now placed in an
> alphabetically correct way in their appropriate lists.
>
Applied.
- Andreas
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/
On 2/10/2024 2:39 PM, James Almer wrote:
The avctx passed to avcodec_string() may have unset coded dimensions, as is
the case when called by av_dump_format() where the streams had all the needed
information at the container level, and as such no frames were decoded
internally.
Signed-off-by: Ja
On Tue, 13 Feb 2024, Ridley Combs wrote:
It looks like checkout has different behavior from reset, and fate uses a
hard reset.
To test, I committed the change adding tests/ref/** -text,
unix2dos'd tests/ref/fate/sub-scc, then ran git -c core.autocrlf=true reset
--quiet --hard; this dos2unix'd th
Since 7bf1b9b35769b37684dd2f18a54f01d852a540c8,
the test produces ordinary \n, yet this is not what the reference
file used for the most time, leading to test failures.
Signed-off-by: Andreas Rheinhardt
---
tests/fate/subtitles.mak | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/fate/s
Broken in ec2036454bcdc6c12382961d4ab539c2f9b70ec8.
Signed-off-by: Andreas Rheinhardt
---
libavformat/dump.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/dump.c b/libavformat/dump.c
index 9bf1695d96..42b1909bd7 100644
--- a/libavformat/dump.c
+++ b/libavfor
> On Feb 13, 2024, at 04:33, Martin Storsjö wrote:
>
> On Tue, 13 Feb 2024, Ridley Combs via ffmpeg-devel wrote:
>
>>> On Feb 13, 2024, at 01:28, Anton Khirnov wrote:
>>> Quoting Martin Storsjö (2024-02-12 12:31:29)
On Mon, 12 Feb 2024, Hendrik Leppkes wrote:
> On Mon, Feb 12, 2024 a
On Tue, 13 Feb 2024, Ridley Combs via ffmpeg-devel wrote:
On Feb 13, 2024, at 01:28, Anton Khirnov wrote:
Quoting Martin Storsjö (2024-02-12 12:31:29)
On Mon, 12 Feb 2024, Hendrik Leppkes wrote:
On Mon, Feb 12, 2024 at 11:22 AM Martin Storsjö wrote:
diff --git a/.gitattributes b/.gitattr
We currently mostly do not empty the MMX state in our MMX
DSP functions; instead we only do so before code that might
be using x87 code. This is a violation of the System V i386 ABI
(and maybe of other ABIs, too):
"The CPU shall be in x87 mode upon entry to a function. Therefore,
every function tha
Andreas Rheinhardt:
> Removed in 704017d91ec8fbade0de072d222018c1a6013b70.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavformat/avformat.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
> index 5d0fe82250..1e98970b89
Andreas Rheinhardt:
> It is unused for decoders.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/cri.c | 1 -
> libavcodec/tdsc.c | 1 -
> libavcodec/tiff.c | 1 -
> 3 files changed, 3 deletions(-)
>
> diff --git a/libavcodec/cri.c b/libavcodec/cri.c
> index 0380a0c665..c4eb468610 100
Andreas Rheinhardt:
> Forgotten in 268062fa15e1c05310f9c3977e0b95ac07eca274.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavfilter/vf_bwdif_cuda.c | 1 -
> libavfilter/vf_yadif_cuda.c | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/libavfilter/vf_bwdif_cuda.c b/libavfilter/vf_bwdi
Signed-off-by: Andreas Rheinhardt
---
libavutil/hwcontext_cuda.c | 43 +++---
1 file changed, 22 insertions(+), 21 deletions(-)
diff --git a/libavutil/hwcontext_cuda.c b/libavutil/hwcontext_cuda.c
index b430b42f62..3de3847399 100644
--- a/libavutil/hwcontext_cuda.
On 2/13/2024 9:10 AM, Lynne wrote:
Feb 13, 2024, 01:59 by ffmpeg-devel@ffmpeg.org:
On Sun Feb 11, 2024 at 10:15 AM EST, Lynne wrote:
From: Lynne
Date: Fri, 19 Jan 2024 10:49:02 +1000
Subject: [PATCH v4 2/2] lavc/vulkan_av1: port to the new stable API
Most of this patch was written by Dave A
Feb 13, 2024, 01:59 by ffmpeg-devel@ffmpeg.org:
> On Sun Feb 11, 2024 at 10:15 AM EST, Lynne wrote:
>
>> From: Lynne
>> Date: Fri, 19 Jan 2024 10:49:02 +1000
>> Subject: [PATCH v4 2/2] lavc/vulkan_av1: port to the new stable API
>>
>> Most of this patch was written by Dave Airlie ,
>> with some a
> On Feb 13, 2024, at 01:28, Anton Khirnov wrote:
>
> Quoting Martin Storsjö (2024-02-12 12:31:29)
>> On Mon, 12 Feb 2024, Hendrik Leppkes wrote:
>>
>>> On Mon, Feb 12, 2024 at 11:22 AM Martin Storsjö wrote:
>
> diff --git a/.gitattributes b/.gitattributes
> index 5a19b963b6..a90
On 13/02/2024 02:30, Nuo Mi wrote:
> fc->ref points to an old VVCFrame, which cannot be used after
> frame_context_setup.
> This prevents crashes in decode_nal_units-->ff_vvc_report_frame_finished.
>
> Signed-off-by: Frank Plowman
> ---
> libavcodec/vvc/vvcdec.c | 2 ++
> 1 file changed, 2 inse
According to ITU-T H.265 7.4.2.1 this byte sequence should not appear in a
NAL unit but in practice in rare cases it seems it does, possibly due to buggy
encoders. Other players like VLC and Quicktime seem to be fine with it.
Currently when this sequence is found it is treated as if the next start
On Tue, 13 Feb 2024, J. Dekker wrote:
Signed-off-by: J. Dekker
---
These devices are fundamentally broken and usecases should be switched
away from output devices in general. Discussion in the thread tended towards
deprecation rather than immediate removal to give time for users to figure o
it was due to a testing , not MMX. fixed it in this reply.
flow gg 于2024年2月13日周二 10:37写道：
> I sended "[FFmpeg-devel] [PATCH] x86: Remove MMX assembly
> rv34_inv_transform_dc in rv34dsp"
>
> Rémi Denis-Courmont 于2024年2月13日周二 03:37写道：
>
>> Le perjantaina 2. helmikuuta 2024, 2.47.16 EET flow gg
I made a mistake. It can be fixed your way. Please ignore this reply.
flow gg 于2024年2月13日周二 17:47写道：
> Thank you for your guidance. Do you mean that it should be modified test
> like this?
>
> - declare_func(void, uint8_t *dst, ptrdiff_t stride, int dc);
> + declare_func_emms(AV_CPU_FLAG_MMX, vo
Thank you for your guidance. Do you mean that it should be modified test
like this?
- declare_func(void, uint8_t *dst, ptrdiff_t stride, int dc);
+ declare_func_emms(AV_CPU_FLAG_MMX, void, uint8_t *, ptrdiff_t, int);
I tried to do it this way, but the test still failed. not sure why ...
_
Quoting Martin Storsjö (2024-02-12 12:31:29)
> On Mon, 12 Feb 2024, Hendrik Leppkes wrote:
>
> > On Mon, Feb 12, 2024 at 11:22 AM Martin Storsjö wrote:
> >> >
> >> > diff --git a/.gitattributes b/.gitattributes
> >> > index 5a19b963b6..a900528e47 100644
> >> > --- a/.gitattributes
> >> > +++ b/.g
flow gg:
> Subject: [PATCH] x86: Remove MMX assembly rv34_inv_transform_dc in rv34dsp
>
> This asm will cause checkasm to fail.
> ---
> libavcodec/x86/rv34dsp.asm| 12
> libavcodec/x86/rv34dsp_init.c | 2 --
Of course your checkasm test will fail: You used declare_func and not
d
62 matches
Mail list logo
