Hi James!
On 2024-12-25 20:54 -0300, James Almer wrote:
> Addresses ticket #11372
>
> Signed-off-by: James Almer
> ---
> doc/ffmpeg.texi | 64 -
> 1 file changed, 32 insertions(+), 32 deletions(-)
>
LGTM (mabye one of documentation maintainers als
On Wed, Dec 25, 2024 at 4:27 AM Michael Niedermayer
wrote:
>
> Signed-off-by: Michael Niedermayer
> ---
> doc/community.texi | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/community.texi b/doc/community.texi
> index 97a49f15ede..0bc8893f0e8 100644
> --- a/doc/community.texi
>
On Wed, Dec 25, 2024 at 1:31 PM Michael Niedermayer
wrote:
>
> Hi Community, Community Commitee, Moderators
>
Your removal of this message as of 1504 GMT 26/12/2024 is completely
unacceptable with one days notice posted on a public holiday in most
countries.
Furthermore, you make regular allegati
Hi Leo and Joe!
On 2024-12-27 08:13 -0500, Leo Izen wrote:
> On 12/26/24 6:12 PM, J Shiff wrote:
> > On Wed, Dec 25, 2024 at 5:03 PM Alexander Strasser via ffmpeg-devel
> > wrote:
> > >
> > > On 2024-12-21 19:29 -0500, J Shiff wrote:
> > > > On Sa
On Sat, 28 Dec 2024, 01:20 James Almer, wrote:
> On 12/27/2024 10:15 PM, Vittorio Giovara wrote:
> > On Fri, Dec 27, 2024 at 8:04 PM James Almer wrote:
> >
> >> On 12/27/2024 9:58 PM, Vittorio Giovara wrote:
> >>> On Tue, Dec 24, 2024 at 11:46 AM Michael Niedermayer <
> >> [email protected]
On 2024-12-30 20:25 +0200, Rémi Denis-Courmont wrote:
> Le tiistaina 24. joulukuuta 2024, 15.30.00 EET Nuo Mi a écrit :
> > On Mon, Dec 23, 2024 at 11:18 PM flow gg wrote:
> > > Hi, It looks like you submitted your review comments not long after the
> > > patch was merged.
> > >
> > > Previously,
Hi Michael!
On 2024-12-31 04:36 +0100, Michael Niedermayer wrote:
> Suggested-by: Marton Balint
> Signed-off-by: Michael Niedermayer
> ---
> libavformat/vqf.c | 16 ++--
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/libavformat/vqf.c b/libavformat/vqf.c
> index
>
> You can simply verify that vittorio is himself as you meet him next time
> and drink
> beer with him (which you said you did previously).
> Its just a simple "yeah i met him after this and he is still in control
> of his accounts&keys", theres no kyc here, just a statement from you saying
> you
t; On 2/3/2025 10:58 AM, Ben Lu via ffmpeg-devel wrote:
> > Sorry about that, it looks correct in gmail and sending to myself also
> > looks fine, not sure where the line width corruption is happening. Our
> org
> > doesn't allow programmatic email.
>
> Looks lik
Add a parameter (boolean) r to switch the area from
rectangular (r=0) to circular(r=1) delogo.
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_delogo.c b/libavfilter/vf_delogo.c
index bfbf8e6f4c.
Dear list,
I made a patch for the delogo filter. With this I can create a circular
or elliptic zone to apply the delogo algorithm. The borders are defined with
x,y,w,h parameter just like the rectangular area definition. To become
circular I added an additional parameter 'r'=0/1 defaulting to '0'
Added a description of the elliptic formed delogo algorithm. Placed it
outside the doxygen function comment.
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 24
1 file changed, 24 insertions(+)
diff --git a/libavfilter/vf_delogo.c b/libavfilter/vf_delogo.c
Use the corrected x,y,w,h values with boundaries and clipping to
calculate the points inside the ellipse.
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 28 ++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/libavfilter/vf_delogo.c b/libavfi
ink->w, s->w),
+ FFMAX(inlink->h, s->h));
+}
if (!out) {
av_frame_free(&in);
return AVERROR(ENOMEM);
--
2.35.1.70.gdb80f58b59-twtrsrc
On Sat, Feb 1, 2025 at 12:52 AM Michael Niedermayer
wrote:
> Hi
>
Dear list,
sorry for the previous posting. I noticed the lines got mangled. So here
is a new try to get the patches right.
Old text:
I made a patch for the delogo filter. With this I can create a circular or
elliptic zone to apply the delogo algorithm. The borders are defined with
x,y,w,h parame
Use the corrected x,y,w,h values with boundaries and clipping to
calculate the points inside the ellipse.
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 28 ++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/libavfilter/vf_delogo.c b/libavfil
Added a description of the elliptic formed delogo algorithm. Placed it
outside the doxygen function comment.
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 24
1 file changed, 24 insertions(+)
diff --git a/libavfilter/vf_delogo.c b/libavfilter/vf_delogo.c
i
Add a parameter (boolean) r to switch the area from
rectangular (r=0) to circular(r=1) delogo.
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_delogo.c b/libavfilter/vf_delogo.c
index bfbf8e6f4c..
The `dec_ctx->time_base` was incorrectly default set by avcodec_open2(), while
`enc_ctx->time_base` was derived from `dec_ctx->framerate`. This mismatch could
cause incorrect video duration in the output.
This patch corrects the issue by adjusting the `enc_ctx->time_base` calculation
to accoun
From: Jack Lau
The `dec_ctx->time_base` was incorrectly default set by avcodec_open2(), while
`enc_ctx->time_base` was derived from `dec_ctx->framerate`. This mismatch could
cause incorrect video duration in the output.
This patch corrects the issue by adjusting the `enc_ctx->time_base` calcul
Changed the delogo area to a definition of a superellipse. See here
https://en.wikipedia.org/wiki/Superellipse
Changed the meaning of the parameter 'r'.
'r' = 0.0 resolves to a rectangular area.
0 <'r' < 1 resolves to a star with concave sides.
'r' = 1.0 resolves to a rhombus.
1 < 'r' < 2 resolves
Dear list,
with help from Michael I extended the ellipse area to a superellipse.
The user parameter 'r' has changed to become a float value.
Values 0 < r < 1 the area looks like a four edge star.
Value r = 1 the area get a rhombus.
Values 1 < r < 2 the area is a rhombus with concave sides.
Value
Changed the type of the parameter 'r' from int to float. To be able to
flex the area as superellipse from rounded rectangle ('r' > 2.0) to a
concave shaped star ('r' < 1.0).
Check the input value to be 'r' >= 0.0, else error exit
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 21 +++
Changed the delogo area to a definition of a superellipse. See here
https://en.wikipedia.org/wiki/Superellipse
Changed the meaning of the parameter 'r'.
'r' = 0.0 resolves to a rectangular area.
0 <'r' < 1 resolves to a star with concave sides.
'r' = 1.0 resolves to a rhombus.
1 < 'r' < 2 resolves
Changed the type of the parameter 'r' from int to float. To be able to
flex the area as superellipse from rounded rectangle ('r' > 2.0) to a
concave shaped star ('r' < 1.0).
Check the input value to be 'r' >= 0.0, else error exit
Signed-off-by: Jörg Habenicht
---
libavfilter/vf_delogo.c | 21 +++
Version 2 of the pathset. One test "if (isnan(yf))" was missing.
Corrected in this version
with help from Michael I extended the ellipse area to a superellipse.
The user parameter 'r' has changed to become a float value.
Values 0 < r < 1 the area looks like a four edge star.
Value r = 1 the area
---
libavformat/hls.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/hls.c b/libavformat/hls.c
index 3bdc1bc848..c2130bb883 100644
--- a/libavformat/hls.c
+++ b/libavformat/hls.c
@@ -1993,7 +1993,7 @@ static int hls_read_header(AVFormatContext *s)
return r
This change removes one extra floating point operation and simplifies
load operations at the beginning of the loop by using dedicated register
for each of the 5 pointers and interleaving it with calculations. The
first case seems to be a bit slower, but the performance increase is
substantial in th
The patch contains NEON code that splits the uyvy input array into 3
separate buffers.
The existing test cases are covering scenarios with odd height and odd
stride, but width is even in every instance. Is it safe to make that
assumption about the width?
Just as I'm about to send this patch, I'm
On Mon, Feb 10, 2025 at 12:40 PM Martin Storsjö wrote:
>
> On Sat, 8 Feb 2025, Kieran Kunhya via ffmpeg-devel wrote:
>
> > $subj
>
> > -if (memcmp(y0, y1, BUF_SIZE * sizeof(type))
> > \
> > -|| memcmp
Hi
Am 06.02.25 um 18:12 schrieb Michael Niedermayer:
> Hi Jörg
>
> On Tue, Feb 04, 2025 at 08:53:58PM +0100, Jörg Habenicht via ffmpeg-devel
> wrote:
>> Add a parameter (boolean) r to switch the area from
>> rectangular (r=0) to circular(r=1) delogo.
>>
[...]
>&
On Mon, Feb 10, 2025 at 03:15:35PM +0200, Martin Storsjö wrote:
> > Just as I'm about to send this patch, I'm thinking if non-interleaved
> > read followed by 4 invocations of TBL wouldn't be more performant. One
> > call to generate a contiguous vector of u, second for v and two for y.
> > I'm cur
---
libswscale/aarch64/rgb2rgb.c | 16 ++
libswscale/aarch64/rgb2rgb_neon.S | 262 ++
2 files changed, 278 insertions(+)
diff --git a/libswscale/aarch64/rgb2rgb.c b/libswscale/aarch64/rgb2rgb.c
index 7e1dba572d..f474228298 100644
--- a/libswscale/aarch64/rgb2rgb.
Splitting the previous patch into two.
I noticed that on my x86 box, one of the newly added tests fail:
MMXEXT:
uyvytoyuv420_mmxext (sw_rgb.c:126)
yuyvtoyuv420_mmxext (sw_rgb.c:126)
- sw_rgb.uyvytoyuv [FAILED]
SSE2, AVX and AVX2 are passing, though.
---
tests/checkasm/sw_rgb.c |
On Sat, 1 Feb 2025, 14:46 Michael Niedermayer,
wrote:
> Hi
>
> On Wed, Jan 29, 2025 at 10:21:37PM +0100, Niklas Haas wrote:
> > On Wed, 29 Jan 2025 21:51:27 +0100 Nicolas George
> wrote:
> > > Niklas Haas (12025-01-29):
> [...]
>
> > > *Some members* of
> > > what you call community have express
Hi Michael,
On Sat, 1 Feb 2025, 22:27 Michael Niedermayer,
wrote:
>
> Lets be carefull here with the words. But the awnser is "yes"
> Many developers have been paid to write commits. employees, contractors,
> students
>
As an FFlabs employee (which I believe is the biggest GA cohort) and
shareh
On 2025-01-30 9:09 a.m., Araz Iusubov wrote:
The Reference-Only feature in DirectX 12 is a memory optimization
technique designed for video decoding scenarios.
This feature requires that reference resources must be allocated with
the D3D12_RESOURCE_FLAG_VIDEO_DECODE_REFERENCE_ONLY resource flag.
On Sat, 1 Feb 2025, 15:03 Michael Niedermayer,
wrote:
> Hi
>
> On Sat, Feb 01, 2025 at 02:48:51PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Sat, 1 Feb 2025, 14:46 Michael Niedermayer,
> > wrote:
> >
> > > Hi
> > >
> > > On
The benchmarks (before vs after) were gathered using
./tests/checkasm/checkasm --test=sw_scale --bench --runs=6 | grep yuv2yuv1
A78 before:
yuv2yuv1_0_512_accurate_c:2039.5 ( 1.00x)
yuv2yuv1_0_512_accurate_neon: 385.5 ( 5.29x)
yuv2yuv1_0_512_ap
When using pad with eval=frame with variable frame sizes, we get
significant artifacting. This is due to incorrect frame sizes, resulting in
invalid frames. Made changes to use the output width and height for frame
sizes when using eval=frame, with if statement guards to make sure the
normal usage
Hi,
On Friday, December 6th, 2024 at 12:39 PM, Tristan Matthews via ffmpeg-devel
wrote:
> Hi (also apologies if my client mangles the inline version of the patch, it's
> the first time I've tried to review an attached patch with it)...
>
> On Monday, December 2nd,
Hi,
On Tue, Dec 10, 2024, at 19:29, Anton Khirnov wrote:
> Hi,
> Quoting Thomas Guillem via ffmpeg-devel (2024-11-29 11:44:21)
>> avcodec_get_hw_frames_parameters(), called by the user from get_format,
>> is allocating ctx->internal->hwaccel_priv_data. But the hardware
&g
the
> same packet, have not been tested at all, since no software can write such
> files.
>
> The set can also be found on GitHub, where ignoring whitespaces makes
> specially the last patch a lot more readable:
> https://github.com/BtbN/FFmpeg/tree/enhanced-flv
>
>
&
On Thu, 12 Dec 2024 at 17:31, Timo Rothenpieler wrote:
>
> On 12/12/2024 17:30, Dennis Sädtler wrote:
> > With the spec now being in "beta" and no more (functional) changes
> > being expected, would you be happy to revisit this patch set and merge
> > it or do you want to wait for it to be declare
From: Dennis Sädtler
Added in macOS 15 "Sequoia".
Signed-off-by: Dennis Sädtler
---
Fixed line-endings, otherwise identical to v1.
libavcodec/videotoolboxenc.c | 12
1 file changed, 12 insertions(+)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index d
On Mon, 16 Dec 2024 at 03:17, Michael Niedermayer
wrote:
> This patch is corrupted by line breaks
>
> please make sure your editor and MUA dont break lines of patches
> or use git send-email
Seems Thunderbird broke it, will resubmit in a bit.
___
ffmpeg
Hi Rémi!
On 2024-11-19 19:10 +0200, Rémi Denis-Courmont wrote:
>
> I plan to solicit an FFmpeg booth at SCaLE 22x to be held early next March.
> Booths for open-source communities are free and include 5 full conference
> passes. The exhibition area is open, and needs to be manned, on Friday
> afte
On 2024-12-11 15:05 +0100, Anton Khirnov wrote:
> This can be useful in other places, e.g. it can replace objpool in
> fftools.
>
> The API is modified in the following nontrivial ways:
> * opaque pointers can be passed through to all user callbacks
> * read and write were previously separate callb
Hi,
> I see. I've put the code in an #if block, so you can try if
>
> it makes a difference to anything you may encounter.
>
> The spec says: https://aomediacodec.github.io/av1-spec/#ordering-of-obus
>
> "Sequence header OBUs may appear in any order within a coded video
> sequence. Within a parti
On 2024-12-16 22:02 -0500, Leo Izen wrote:
> On 12/16/24 5:50 PM, Michael Niedermayer wrote:
[...]
>
> > (e): Find a input that encodes to max 2 variants and store 2 checksums
>
> Doesn't fix the problem, which is that need to be aware of all the known
> variants and create hacks to work with them
> 1a. Prior context:
> For a long time FFmpeg booths where organized by various FFmpeg developers
> like Thilo but also others. They where always announced publically, they
> surely had a touch of hobbyists and a "non professional" community
>
> On NAB 2023 theres a booth paid by VideoLabs, with Vi
Hello,
My messages are being blocked on the mailing list. How is this fair that
one person can unilaterally decide this?
Here is my message:
Hi Michael,
If the CC has voted to ban someone, why has it not happened?
You can't complain it the CC fails to act when it has voted for something
to hap
Hello,
This person asked for coverity access:
https://x.com/acentauri92/status/1867186643704099105
I don't know if they should have access.
Kieran
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
T
On Fri, 13 Dec 2024, 00:39 Michael Niedermayer,
wrote:
> Hi
>
> On Thu, Dec 12, 2024 at 12:54:29PM +, Nicolas Gaullier wrote:
> [...]
> > This is a significant work with some weird things like dealing with a
> truncated sample rate
> > and droping one sample from time to time to keep sync. An
On Thu, 12 Dec 2024, 13:07 Nicolas Gaullier,
wrote:
> >De : ffmpeg-devel de la part de Anton
> Khirnov
> >Envoyé : jeudi 12 décembre 2024 09:36
> >
> >I am not intimately familiar with these formats and their mutual
> >relationship, so these problems you refer to are not clear to me.
> >What I
Hi Martin!
On 2024-12-11 10:47 +0200, Martin Storsjö wrote:
> On Wed, 23 Oct 2024, Martin Storsjö wrote:
>
> > This corresponds to commit 9278a14cf406f8edb5052c42b83750112bf5b515
> > in dav1d.
> >
> > Omitting the C-only functions doesn't speed up benchmarking
> > anyway (as those has to be benchm
On 2024-12-14 11:09 +0100, Anton Khirnov wrote:
> Quoting Alexander Strasser via ffmpeg-devel (2024-12-01 21:13:56)
> > This is a fixed up version of the series I sent before.
> >
> > This worked for me on Ubuntu 20.04 but probably will break
> > with older zlib version
On Fri, 13 Dec 2024, 02:46 Michael Niedermayer,
wrote:
> Hi
>
> On Fri, Dec 13, 2024 at 01:40:43AM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Thu, 12 Dec 2024, 13:07 Nicolas Gaullier, >
> > wrote:
> >
> > > >De : ffmpeg-devel de la
On Fri, 13 Dec 2024, 10:00 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Where is the second sample rate stored in wav?
>
> Nowhere, obviously. I am surprised somebody who has been in the project
> for more than 12 years still does not know how it
On Fri, 13 Dec 2024, 10:14 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Then the conclusion in your example is wrong.
>
> No it is not. Either you misunderstood what I explained — I am guessing
> you only read it superficially, you did not actuall
On Fri, 13 Dec 2024, 09:31 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Does FFmpeg even support a new sample rate per AVFrame?
>
> Generate a 48000 Hz MP3.
> Generate a 32000 Hz MP3.
> Concatenate them.
> Convert the result to wave.
>
On Thursday, December 12th, 2024 at 4:18 AM, Chris Hodges
wrote:
> Hi Tristan,
>
> thanks for taking the time reviewing.
>
> On 12/6/24 18:39, Tristan Matthews via ffmpeg-devel wrote:
>
> > Hi (also apologies if my client mangles the inline version of the patch,
>
On Fri, 13 Dec 2024, 13:41 Niklas Haas, wrote:
> On Fri, 13 Dec 2024 01:37:34 + Kieran Kunhya via ffmpeg-devel <
> [email protected]> wrote:
> > On Fri, 13 Dec 2024, 00:39 Michael Niedermayer,
> > wrote:
> >
> > > Hi
> > >
> &g
can discuss the changes and it gives me more time to look into the
> issue below.
>
> On 12/11/24 23:53, Tristan Matthews via ffmpeg-devel wrote:
>
> > Aside from my minor comments on the patch, one thing that came up in terms
> > of testing is that while the packetization seems
From: Dennis Sädtler
Added in macOS 15 "Sequoia".
Signed-off-by: Dennis Sädtler
---
libavcodec/videotoolboxenc.c | 12
1 file changed, 12 insertions(+)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index da7b291b03..fb2de7b960 100644
--- a/libavcodec/v
On Fri, 13 Dec 2024, 16:38 Romain Beauxis, wrote:
> Le ven. 13 déc. 2024 à 16:42, Romain Beauxis
> a écrit :
> >
> > This patch adds parameters to pick specific ports for the two FEC error-
> > correction streams associated with a Pro-MPEG CoP #3-R2 FEC streams.
> >
> > Radio France is currently
On Thu, 19 Dec 2024, 02:22 Michael Niedermayer,
wrote:
>
> Kieran reports this to the CC
> and jb and ronald vote for a third ban of Nicolas,
> ronald states that he would not have voted for a ban if Nicolas apologized.
>
Hi Michael,
If the CC has voted to ban someone, why has it not happened?
On Fri, Dec 20, 2024 at 5:20 AM Lingyi Kong wrote:
>
> fix for https://trac.ffmpeg.org/ticket/11360
>
> Signed-off-by: Lingyi Kong
> ---
> libavcodec/h264_mb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/h264_mb.c b/libavcodec/h264_mb.c
> index 4e94136313.
On Thu, 19 Dec 2024, 20:30 compn, wrote:
> On Thu, 19 Dec 2024 20:15:10 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > Some Animals are More Equal Than Others.
> >
> > Kieran
>
> and now a CC candidate calling devs animals ?
>
This is one of th
On Thu, 19 Dec 2024, 20:38 compn, wrote:
> On Thu, 19 Dec 2024 20:35:43 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > On Thu, 19 Dec 2024, 20:30 compn, wrote:
> >
> > > On Thu, 19 Dec 2024 20:15:10 +0000, Kieran Kunhya via ffmpeg-devel
> > > wro
On Thu, Dec 19, 2024 at 7:25 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> First before replying, id like to say, that i hope we can resolve this and
> in the future work together in a mutually more friendly way.
>
> On Wed, Dec 18, 2024 at 10:18:20PM -0500, Kieran Ku
On 2024-12-19 06:46 -1000, compn wrote:
> On Thu, 19 Dec 2024 13:16:23 -0300, James Almer wrote:
>
> > On 12/19/2024 1:12 PM, compn wrote:
> > > On Thu, 19 Dec 2024 10:04:53 -0300, James Almer wrote:
> > >> I have no idea who added the rule for "upcoming vote", but i just
> > >> removed it.
> > >>
On Thu, Dec 19, 2024 at 7:52 PM Michael Niedermayer
wrote:
>
> Hi compn
>
> On Thu, Dec 19, 2024 at 06:16:03AM -1000, compn wrote:
> > On Thu, 19 Dec 2024 08:58:14 +0000, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > Hello,
> > >
> &g
On 2024-12-20 19:38 +0100, Michael Niedermayer wrote:
> On Fri, Dec 20, 2024 at 02:56:54PM +0100, Niklas Haas wrote:
> > On Fri, 20 Dec 2024 08:37:40 -0500 "Ronald S. Bultje"
> > wrote:
[...]
> > > Assuming you agree with that - which is hard to argue with - don't you
> > > agree that for now,
On Thu, Dec 19, 2024 at 9:11 PM compn wrote:
>
> On Thu, 19 Dec 2024 20:40:55 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > Please can you confirm you will be resigning your moderator status in light
> > of the election censorship you have undertaken while at t
I am experiencing a crash in Niagara Workbench when streaming video with the
H.264 codec. The crash occurs during the first 3-4 attempts to initialize the
stream but then stabilizes afterward. This issue started after upgrading FFmpeg
from 6.0 to 7.0.1. Updating to 7.1 also did not resolve the i
Hi Martin,
still looks good to me.
On 2024-12-04 16:08 +0200, Martin Storsjö wrote:
[...]
> --- a/tests/Makefile
> +++ b/tests/Makefile
> @@ -313,6 +313,12 @@ $(FATE): $(FATE_UTILS:%=tests/%$(HOSTEXESUF)) |
> $(FATE_OUTDIRS)
> fate-list:
> @printf '%s\n' $(sort $(FATE))
>
> +fate-list-fai
Hi (also apologies if my client mangles the inline version of the patch, it's
the first time I've tried to review an attached patch with it)...
On Monday, December 2nd, 2024 at 9:57 AM, Chris Hodges
wrote:
> Hi,
>
> On 11/25/24 18:47, Tristan Matthews via ffmpeg-devel wr
Some drivers are more strict about the size of the reference lists given
(i.e. VAOn12 [1]). The next_prev list is used to handle multiple "L0"
references in AV1 encode. Restrict the size of next_prev based on the
value of ref_l0 when the GOP structure is initialized.
[1] https://github.com/intel/c
Some drivers are more strict about the size of the reference lists given
(i.e. VAOn12 [1]). The next_prev list is used to handle multiple "L0"
references in AV1 encode. Restrict the size of next_prev based on the
value of ref_l0 when the GOP structure is initialized.
[1] https://github.com/intel/c
On 2024-12-16 16:19 -0500, Joe Schiffler wrote:
> Since $pkg_version includes spaces, builds can fail in some MSYS environments.
Could you show what the pkg_version with spaces was in your case?
Alexander
> Build passing with quotes:
> https://github.com/JoeSchiff/pyav-ffmpeg/actions/runs/12
On Sun, 22 Dec 2024, 15:14 Michael Niedermayer,
wrote:
> I think what we need is some friendly smiles, some mutual respect,
> some virtual hugs and mutual tolerance. We can do the opposite, but it
> will make noone happier.
>
translation: everyone must agree with me
This plays out the same way
On 2025-01-08 05:13 +0100, Michael Niedermayer wrote:
> Found-by: Elias Myllymäki
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/mpegvideo_enc.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/libavcodec/mpegvideo_enc.c b/libavcodec/mpegvideo_enc.c
> index c5f20c2d855..09
On 2025-01-10 12:10 +0200, Martin Storsjö wrote:
> On Wed, 8 Jan 2025, [email protected] wrote:
>
> > From: Jonathan Baudanza
> >
> > This was previously adjusted by me in 6b3f9c2e92b.
> > Unfortunately, I traded one integer overflow bug for
> > another.
> >
> > Currently, NTP timestamps that exceed I
On 2025-01-10 10:40 -0300, James Almer wrote:
> On 1/10/2025 10:05 AM, James Almer wrote:
> > On 1/7/2025 6:50 PM, Alexander Strasser via ffmpeg-devel wrote:
> > > On 2025-01-07 10:55 -0300, James Almer wrote:
> > > > Should reduce memory usage as w
Hi Andreas!
On 2025-01-11 20:40 +0100, Andreas Rheinhardt wrote:
> Andreas Rheinhardt:
> > Patch attached
>
> Will apply this patch and my other patches tomorrow unless there are
> objections.
LGTM from my side (not maintaining any of the affected areas)
I just reviewed them and partially tested
On 2025-01-08 19:42 +0800, Jun Zhao wrote:
> From: Jun Zhao
>
> close the input file if open output fail
>
> Signed-off-by: Jun Zhao
> ---
> ffbuild/bin2c.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/ffbuild/bin2c.c b/ffbuild/bin2c.c
> index dfeedd7669..168b0c658
On 2025-01-10 05:06 +0100, Michael Niedermayer wrote:
> This may be needed for floats
>
> Sponsored-by: Sovereign Tech Fund
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/ffv1enc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/ffv1enc.c b/libavcodec/
On 2025-01-12 22:19 +0100, Andreas Rheinhardt wrote:
> Patch attached
> From 1abad60fe2eba199845db35c92e27dbc4d35b93f Mon Sep 17 00:00:00 2001
> From: Andreas Rheinhardt
> Date: Sun, 12 Jan 2025 20:40:31 +0100
> Subject: [PATCH] fftools/ffmpeg_opt: Remove audio_drift_threshold
>
> Forgotten in 5a
---
libavutil/aarch64/float_dsp_neon.S | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/libavutil/aarch64/float_dsp_neon.S
b/libavutil/aarch64/float_dsp_neon.S
index 35e2715b87..b21f34c084 100644
--- a/libavutil/aarch64/float_dsp_neon.S
+++ b/libavutil/aarch64/flo
Removed two redundant pointer arithmetic operations and split load
section into two smaller ones.
Speedup compared to C increased from 4.50 to 5.80.
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 2025-01-13 19:42 +0100, Leandro Santiago wrote:
> Signed-off-by: Leandro Santiago
> ---
> libavfilter/dnn/dnn_backend_openvino.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/dnn/dnn_backend_openvino.c
> b/libavfilter/dnn/dnn_backend_openvino.c
> ind
Removed a branch, unrolled loop. Speed increase bumped from 3.95 to 5.60.
Krzysztof
---
libavutil/aarch64/float_dsp_neon.S | 28 +++-
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git a/libavutil/aarch64/float_dsp_neon.S
b/libavutil/aarch64/float_dsp_neon.S
i
Modified the main loop to handle 8 floats in one go. A special case of
length not being multiple of 8 is handled at the beginning. The speed
increased from 3.90 to 4.50.
Krzysztof
---
libavutil/aarch64/float_dsp_neon.S | 30 ++
1 file changed, 22 insertions(+), 8 dele
On Wed, Jan 22, 2025 at 3:33 PM Michael Niedermayer
wrote:
>
> On Mon, Jan 20, 2025 at 06:46:46AM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > >
> > > > The data arrives on multiple sockets, leading to all sorts
> > > > of opportunities
>
> Ah, I got you now. This would mean that one part of patches will never go
> through the ML and another part will never be seen on "WEB". I hadn't even
> considered that as a possible/acceptable way, but I wouldn't mind.
>
How is this not confusing as hell for new contributors?
Running two sys
On Wed, Jan 22, 2025 at 4:37 PM Michael Niedermayer
wrote:
>
> Hi
>
> On Mon, Jan 20, 2025 at 03:00:17PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
>
> > Error recovery protocols are complicated -
>
> everything is complicated
>
>
> > this
On Wed, Jan 22, 2025 at 4:53 PM Romain Beauxis wrote:
>
> Le mer. 22 janv. 2025 à 10:29, Kieran Kunhya via ffmpeg-devel
> a écrit :
> >
> > On Wed, Jan 22, 2025 at 3:33 PM Michael Niedermayer
> > wrote:
> > >
> > > On Mon, Jan 20, 2025 at 06:
Since av_match_list was added in commit 0d92b0d5f445d4f2 , this
function changed its semantics shortly after, especially with
commit 3c0b98dced394da3 .
Signed-off-by: Alexander Strasser
---
libavutil/avstring.h | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git
On Tue, Jan 21, 2025 at 6:59 PM Vittorio Giovara
wrote:
>
> Greetings FFmpeg community
>
> There will be a community meeting during the conference, dates and times
> TBA!
>
> I believe there will be means to connect remotely, and everybody is invited
> to join, especially those that believe that o
1901 - 2000 of 3424 matches
Mail list logo
