If depth is 0, then the component is invalid/unset.
Signed-off-by: James Almer
---
libavutil/pixdesc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavutil/pixdesc.c b/libavutil/pixdesc.c
index d73c3f0d58..4d61e32a1e 100644
--- a/libavutil/pixdesc.c
+++ b/libavutil/pixdesc.c
@@ -4
On 10/17/2024 7:47 PM, Sean McGovern wrote:
Hi,
On Mon, Oct 14, 2024 at 9:54 AM James Almer wrote:
Signed-off-by: James Almer
---
tests/fate/vcodec.mak | 6 ++
tests/ref/vsynth/vsynth1-v410 | 4
tests/ref/vsynth/vsynth2-v410 | 4
tests/ref/vsynth/vsynth
Hi,
On Mon, Oct 14, 2024 at 9:54 AM James Almer wrote:
>
> Signed-off-by: James Almer
> ---
> tests/fate/vcodec.mak | 6 ++
> tests/ref/vsynth/vsynth1-v410 | 4
> tests/ref/vsynth/vsynth2-v410 | 4
> tests/ref/vsynth/vsynth3-v410 | 4
> tests/ref/vsynt
On 17 Oct 2024, at 21:58, Soma Lucz wrote:
> I’d like to reject the v1 version of this patch on Patchwork. What to do if
> the Patchwork registration confirmation email didn’t arrive for more than 2
> days, so I cannot log in? (Password reset emails also don’t arrive.) I
> checked the spam an
No, I strongly disagree.
Marking a vital encoder as libx265 that thousands of people rely on as
"experimental" after more than 10 years since its inclusion doesn't make any
sense and would make more harm than good.
Besides, the experimental flag is supposed to be used to indicate that the
imple
On Thu, Oct 17, 2024 at 11:05:31AM +0200, Anton Khirnov wrote:
> Quoting Niklas Haas (2024-10-16 14:30:47)
> > On Tue, 15 Oct 2024 18:12:21 +0200 Michael Niedermayer
> > wrote:
> > > Hi all
> > >
> > > This is a quick RFC about peoples oppinions on AVFilter
> > >
> > > The question: Should anyone
This can be useful to simplify certain processes that need to know how many
reserved bits there are and where they are placed, even if they are ultimately
unused, as will be shown in the next commit.
For any other case where the user simply looks at nb_components components, it
will make no differe
I’d like to reject the v1 version of this patch on Patchwork. What to do if the
Patchwork registration confirmation email didn’t arrive for more than 2 days,
so I cannot log in? (Password reset emails also don’t arrive.) I checked the
spam and junk folders, etc. I tried to re-register, but I was
This can be useful to simplify certain processes that need to know how many
reserved bits there are and where they are placed, even if they are ultimately
unused, as will be shown in the next commit.
For any other case where the user simply looks at nb_components components, it
will make no differe
-disposition:
Clarify the meaning of the default value, and how the '+' and '-'
prefixes work. Add more examples.
-stats:
Clarify that it appears as an "info"-level log.
-progress:
Add info about the "progress" key's value being "continue" or "end".
Add an example of logging to stdout.
Signed-of
The way the linked list of images was freed caused a
use after free, by accessing pic->next after pic was
already freed.
Regression from 48a1a12968345bf673db1e1cbb5c64bd3529c50c
Fix CID1633236
---
libavcodec/hw_base_encode.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Le torstaina 17. lokakuuta 2024, 14.38.19 EEST Nicolas George a écrit :
> Anton Khirnov (12024-10-17):
> > Is that really any better than just adding your filter into your private
> > fork of avfilter?
> Are you asking if there is a benefit in the ability to ship a tiny
> binary package with just
Signed-off-by: James Almer
---
libavfilter/vsrc_testsrc.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/libavfilter/vsrc_testsrc.c b/libavfilter/vsrc_testsrc.c
index 6fd8c73757..ce7ca90ae8 100644
--- a/libavfilter/vsrc_testsrc.c
+++ b/libavfilter/vsrc_testsrc.c
@@ -11
This can be useful to simplify certain processes that need to know how many
reserved bits there are and where they are placed, even if they are ultimately
unused, as will be shown in the next commit.
For any other case where the user simply looks at nb_components components, it
will make no differe
> 在 2024年10月17日，下午10:01，James Almer 写道：
>
> On 10/17/2024 10:49 AM, Timo Rothenpieler wrote:
>>> On 17/10/2024 11:22, Anton Khirnov wrote:
>>> Quoting Anton Khirnov (2023-03-15 15:45:25)
This encoder leaks and overreads, as can be seen e.g. by running an
encode under valgrind with def
On 10/17/2024 10:49 AM, Timo Rothenpieler wrote:
On 17/10/2024 11:22, Anton Khirnov wrote:
Quoting Anton Khirnov (2023-03-15 15:45:25)
This encoder leaks and overreads, as can be seen e.g. by running an
encode under valgrind with default encoder parameters. This was known
upstream since at leas
On 17/10/2024 11:22, Anton Khirnov wrote:
Quoting Anton Khirnov (2023-03-15 15:45:25)
This encoder leaks and overreads, as can be seen e.g. by running an
encode under valgrind with default encoder parameters. This was known
upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed
On Mon, 14 Oct 2024 20:58:31 +0200 Michael Niedermayer
wrote:
> On Mon, Oct 14, 2024 at 08:33:50PM +0200, Niklas Haas wrote:
> > On Mon, 14 Oct 2024 19:49:21 +0200 Michael Niedermayer
> > wrote:
> > > On Mon, Oct 14, 2024 at 06:39:21PM +0200, Michael Niedermayer wrote:
> > > > On Mon, Oct 14, 2
On 10/16/2024 8:17 PM, Michael Niedermayer wrote:
On Wed, Oct 09, 2024 at 02:03:28PM -0300, James Almer wrote:
On 10/8/2024 4:56 PM, Michael Niedermayer wrote:
On Mon, Oct 07, 2024 at 09:29:45AM -0300, James Almer wrote:
Signed-off-by: James Almer
---
libswscale/output.c
Hi Anton,
Thank you for your feedback. Could you please clarify which specific
development rules are being broken in this patch? I'm aiming to ensure that
the implementation is aligned with best practices and any guidelines I may
have missed.
In this patch, I’ve added support for the VBV-End feat
On Fri, Sep 27, 2024 at 2:52 PM Ramiro Polla wrote:
[...]
> Ramiro Polla (16):
> swscale/range_convert: call arch-specific init functions from main
> init function
> swscale/range_convert: drop redundant conditionals from arch-specific
> init functions
> swscale/range_convert: indent
Anton Khirnov (12024-10-17):
> Is that really any better than just adding your filter into your private
> fork of avfilter?
Are you asking if there is a benefit in the ability to ship a tiny
binary package with just “Depends: libavfilter (= 7:5.1.6-0+deb12u1)
instead of a package of several megaoc
On Sun, Sep 29, 2024 at 1:32 PM asivery via ffmpeg-devel
wrote:
> Pinging the patch.
> I've merged the fate test case patch into the functionality one, and rebased
> onto the current master.
> Here are the two sample files required by the FATE test:
> https://0x0.st/Xaw2.aea/boxboy333_house_music
On Sun, Sep 29, 2024 at 5:38 PM Ramiro Polla wrote:
>
> ---
> The new owdenoise-scenwin-jpeg.raw reference file is available at
> https://0x0.st/XguT.raw
>
> tests/fate/filter-video.mak | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/fate/filter-video.mak b/tes
On Mon, Sep 9, 2024 at 12:58 PM Ramiro Polla wrote:
>
> The acaps variable was used outside of the #if DSHOWDEBUG block with
> a1c4929f, but it is no longer used outside of the block since f125c504.
> ---
> libavdevice/dshow.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Consider APPx fields that are too short to contain an id field (32-bit)
as stubs, and silently ignore them.
This has been seen in the MJPEG output from some webcams (such as the
Logitech C270 and C920) and the JPEG images embedded in DNG images
from the Pentax K-1 camera.
---
libavcodec/mjpegdec.
The loop to skip the remaining bytes was off by one for all markers
except for Adob.
This patch uses post-decrement instead of pre-decrement in the while
loop to make the len value easier to understand, and updates the len
value to reflect this change for the Adob marker.
---
libavcodec/mjpegdec.
Hi,
On Thu, Oct 17, 2024 at 8:38 AM Cynthia via ffmpeg-devel
wrote:
> From d7863bab8e1028b6cfb3ce848e216e86ff00eca0 Mon Sep 17 00:00:00 2001
> From: cynthia2006
> Date: Tue, 28 May 2024 22:03:50 +0530
> Subject: [PATCH] lavc/mjpegdec: add option for ignorning malformed APPx
> segments
> X-Unsen
Quoting Anton Khirnov (2023-03-15 15:45:25)
> This encoder leaks and overreads, as can be seen e.g. by running an
> encode under valgrind with default encoder parameters. This was known
> upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed
> until now.
>
> Since upstream does
This breaks more development rules than there are lines changed, which
is an impressive achievement.
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link abov
Quoting Niklas Haas (2024-10-16 14:30:47)
> On Tue, 15 Oct 2024 18:12:21 +0200 Michael Niedermayer
> wrote:
> > Hi all
> >
> > This is a quick RFC about peoples oppinions on AVFilter
> >
> > The question: Should anyone be able to write a filter (which
> > other people can use) ?
> > Or should onl
Hi Michael,
Here is the updated patch to support Vbv-end Feature,the API in the patch
is expected to work with X265_BUILD >= 213 only.
>From 64ce51509c74d7a4f9d86dd73662e561ab9c8845 Mon Sep 17 00:00:00 2001
From: yaswanthsastry
Date: Thu, 17 Oct 2024 14:24:47 +0530
Subject: [PATCH] Added support
32 matches
Mail list logo
