On 22.01.25 03:00, Soft Works wrote:
It's a bit difficult to judge those repo providers without appropriate data, so
I made copies of the ffstaging GitHub site (for creating PRs being sent to the
ML), so the all have current ffmpeg data:
Gitea
https://gitea.com/ffstaging/FFmpeg
forgejo
On 22/01/2025 11:53, James Almer wrote:
Equivalent to the one from packet side data using AVSideDataParamChangeFlags,
and will be used for the same purpose with encoders.
Signed-off-by: James Almer
---
libavutil/frame.c | 1 +
libavutil/frame.h | 13 +
2 files changed, 14 ins
Signed-off-by: James Almer
---
libavcodec/libx264.c | 98 ++--
1 file changed, 59 insertions(+), 39 deletions(-)
diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
index 409f45fc7d..c64c2a28b0 100644
--- a/libavcodec/libx264.c
+++ b/libavcodec/libx26
Signed-off-by: James Almer
---
libavcodec/libaomenc.c | 266 -
1 file changed, 159 insertions(+), 107 deletions(-)
diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
index 0f7571ee7a..45d3fe862a 100644
--- a/libavcodec/libaomenc.c
+++ b/libavcode
With this, callers can signal supported encoders to reinitialize using certain
parameters, which should allow for more graceful (but potentially more limited
in scope) reinitialization than closing and reopening the encoder, or even
simply on-the-fly changes of trivial values that would not require
Allow the caller to pass a dictionary with key/value pairs to set encoder
private options for reinitialization.
AVCodecContext global options are not affected. For that, specific
AVSideDataParamChangeFlags should be used, as is currently the case for
dimensions and sample rate.
Signed-off-by: Jame
Equivalent to the one from packet side data using AVSideDataParamChangeFlags,
and will be used for the same purpose with encoders.
Signed-off-by: James Almer
---
libavutil/frame.c | 1 +
libavutil/frame.h | 13 +
2 files changed, 14 insertions(+)
diff --git a/libavutil/frame.c b/li
Its namespace is not packet specific, and will be useful in a follow commit.
Signed-off-by: James Almer
---
libavcodec/packet.h | 5 -
libavutil/defs.h| 5 +
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/libavcodec/packet.h b/libavcodec/packet.h
index c1f1ad7b43..7cc
They don't belong anywhere in particular, so move them to a new generic header
called defs.h, following the same idea as the one from lavc.
Signed-off-by: James Almer
---
libavutil/avutil.h | 94 +++-
libavutil/defs.h | 149 +
On 1/21/2025 11:26 PM, Michael Niedermayer wrote:
Hi all
I see no mention of 7.0 on https://trac.ffmpeg.org/wiki/Downstreams
does that mean it has no users and can be dropped or is tha page
just outdated?
It seems Ubuntu 24.10 uses ffmpeg 7.0 according to
https://packages.ubuntu.com/oracular/
Hi all
I see no mention of 7.0 on https://trac.ffmpeg.org/wiki/Downstreams
does that mean it has no users and can be dropped or is tha page
just outdated?
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
What is money laundering? Its paying someone and not tellin
Hi all
I intend to make releases from the maintained branches soon because of all the
accumulated bugfixes
will start with 7.1.1
like always if you want something backported, please do backport
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is dangerous to
You will need to add "c1p1_04-0.j2c" [1] to
"fate-suite\jpeg2000\itu-iso\codestreams_profile1".
[1] https://github.com/user-attachments/files/18033833/c1p1_04-0.zip
On Tue, Jan 21, 2025 at 6:04 PM wrote:
>
> From: Pierre-Anthony Lemieux
>
> ---
> tests/fate/jpeg2000.mak | 126
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Koushik Dutta
> Sent: Wednesday, January 22, 2025 3:07 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 3/3] scale_qsv frame crop support
>
> Is anyone reviewing patches for qsv? I have two pending patches for
>
Is anyone reviewing patches for qsv? I have two pending patches for
the qsv scale/crop filters. I submitted similar patches for cuda,
videotoolbox, and vulkan already, which were committed.
Koush
On Tue, Sep 10, 2024 at 11:11 AM Koushik Dutta wrote:
>
> The crop filter has no effect on scale_qsv
This is what my pkgconfig file looks like. The issue is that not using
pkgconfig will assume it is a MSVC build. I think using a pkgconfig
file is preferable in this instance. Let the person doing the build
tailor one to their environment.
prefix=/c/VulkanSDK/1.3.280.0
includedir=${prefix}/Include
From: Pierre-Anthony Lemieux
---
tests/fate/jpeg2000.mak | 126 ++-
tests/ref/fate/jpeg2000dec-ds0_hm_15_b8 | 6 ++
tests/ref/fate/jpeg2000dec-ds0_ht_02_b11 | 6 ++
tests/ref/fate/jpeg2000dec-ds0_ht_02_b12 | 6 ++
tests/ref/fate/jpeg2000dec-ds0_ht_03_b
From: Pierre-Anthony Lemieux
As discussed at [1], this draft patch adds the ability to create FATE tests that
compare FFMPEG processing results with a reference image, using peak error and
mse
error metrics.
[1] https://ffmpeg.org/pipermail/ffmpeg-devel/2024-November/335778.html
This is useful
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marth64
> Sent: Wednesday, January 22, 2025 2:08 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Regarding Git Tooling
>
> Hi Soft Works,
>
> > I come to wonder whether this is r
Hi Soft Works,
> I come to wonder whether this is really just about tooling
My post and intent is only about tooling.
Thank you
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Tuesday, January 21, 2025 5:14 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Regarding Git Tooling
>
>
>
> > -Original Message-
> > From: ffmpeg-
On 1/21/2025 6:10 PM, Michael Niedermayer wrote:
Hi
On Tue, Jan 21, 2025 at 02:53:36PM -0300, James Almer wrote:
On 1/21/2025 2:41 PM, Michael Niedermayer wrote:
Hi
As people likely know i belive it is not but i got a 2nd opinion:
I asked chat gpt this:
You can't possibly be serious.
Is
This patch implements the decoding logic for the FEC error-
correction method described in the Pro-MPEG CoP #3-R2 FEC[1]
This implementation was previously discussed here: [2]
Some preliminary testing results are available: [3]
Summary:
1% packet loss: 100% recovery ratio
5% packet loss: 98% rec
Hi all,
Le lun. 20 janv. 2025 à 10:23, Marth64 a écrit :
>
> James Almer:
>
> > I'd really like if we can stop with the "Everything's fucked, nothing
> > can be done" mails every other week and instead make use of the
> > framework we came up with, or if needed, change it and improve it.
>
> +1
>
Hi
On Tue, Jan 21, 2025 at 02:53:36PM -0300, James Almer wrote:
> On 1/21/2025 2:41 PM, Michael Niedermayer wrote:
> > Hi
> >
> > As people likely know i belive it is not but i got a 2nd opinion:
> >
> >
> > I asked chat gpt this:
>
> You can't possibly be serious.
>
> > Is it a democracy, if
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
Hi
On Tue, Jan 21, 2025 at 07:04:53PM +, Soft Works wrote:
[...]
> > > Removing all disgruntled community members and consolidating sole
> > control
> > > under an authoritarian leader may appear to streamline governance
> > in the
> > > short term, but it is rarely a sustainable or beneficial
On 1/21/2025 9:04 AM, Niklas Haas wrote:
On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
Hello, in the context of a GA member,
I think there is general interest in modernizing technical tooling
specifically regarding ML/patch workflow vs. integrated git solution.
Both have their merits. I th
On Tue, 21 Jan 2025, 18:57 James Almer, wrote:
> On 1/21/2025 3:13 PM, Kieran Kunhya via ffmpeg-devel wrote:
> > On Tue, Jan 21, 2025 at 5:42 PM Michael Niedermayer
> > wrote:
> >>
> >> Hi
> >>
> >> As people likely know i belive it is not but i got a 2nd opinion:
> >
> > Hi Michael,
> >
> > Can
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Niklas Haas
> Sent: Tuesday, January 21, 2025 7:49 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Is the GA democratic ?
>
> On Tue, 21 Jan 2025 18:41:49 +0100 Michael Niederma
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 only 1-2 people are
representing the community's desires.
Be the change
On 1/21/2025 3:13 PM, Kieran Kunhya via ffmpeg-devel wrote:
On Tue, Jan 21, 2025 at 5:42 PM Michael Niedermayer
wrote:
Hi
As people likely know i belive it is not but i got a 2nd opinion:
Hi Michael,
Can you ask ChatGPT the following:
Is it ok for one person to be in control of a major op
On Tue, 21 Jan 2025 18:41:49 +0100 Michael Niedermayer
wrote:
> Hi
>
> As people likely know i belive it is not but i got a 2nd opinion:
>
>
> I asked chat gpt this:
> [...]
The validity and relevance of AI tools notwithstanding, I suggest to take a
look at this ChatGPT session:
https://chat
On Tue, 21 Jan 2025 18:48:01 +0100 Michael Niedermayer
wrote:
> Hi James
>
> On Tue, Jan 21, 2025 at 01:22:52PM -0300, James Almer wrote:
> > On 1/21/2025 12:54 PM, Michael Niedermayer wrote:
> > > Hi
> > >
> > > On Tue, Jan 21, 2025 at 01:04:45PM +0100, Niklas Haas wrote:
> > > > On Mon, 20 Jan
On Tue, 21 Jan 2025 18:55:05 +0100 Frank Plowman wrote:
> On 21/01/2025 11:51, Niklas Haas wrote:
> > On Tue, 21 Jan 2025 03:41:06 +0100 Michael Niedermayer
> > wrote:
> >> On Tue, Jan 21, 2025 at 02:26:24AM +0100, Michael Niedermayer wrote:
> >>> Hi
> >>>
> >>> On Mon, Jan 20, 2025 at 02:39:29P
On Tue, Sep 24, 2024 at 06:58:31PM +0200, Tomas Härdin wrote:
> mån 2024-09-23 klockan 23:32 +0200 skrev Michael Niedermayer:
> > Fixes: Use of uninitialized memory
> > Fixes: 71444/clusterfuzz-testcase-minimized-ffmpeg_dem_MXF_fuzzer-
> > 5448597561212928
> >
> > Found-by: continuous fuzzing proc
On Tue, Jan 21, 2025 at 5:42 PM Michael Niedermayer
wrote:
>
> Hi
>
> As people likely know i belive it is not but i got a 2nd opinion:
Hi Michael,
Can you ask ChatGPT the following:
Is it ok for one person to be in control of a major open source
project when they promised to step down?
Can you
On Sat, Nov 30, 2024 at 03:20:57AM +0100, Michael Niedermayer wrote:
> Fixes: use of uninitialized memory
> Fixes:
> 375286238/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_HYMT_fuzzer-6352546854141952
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/
On Thu, Dec 26, 2024 at 04:01:47AM +0100, Michael Niedermayer wrote:
> Fixes: use of uninitialized data
> Fixes:
> 383825642/clusterfuzz-testcase-minimized-ffmpeg_DEMUXER_fuzzer-5380168801124352
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ff
On Wed, Jan 01, 2025 at 06:14:27AM +0100, Michael Niedermayer wrote:
> Fixes: use-of-uninitialized-value
> Fixes:
> 70907/clusterfuzz-testcase-minimized-ffmpeg_BSF_VP9_METADATA_fuzzer-6339363208757248
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/proje
On Wed, Jan 01, 2025 at 07:53:27PM +0100, Alexander Strasser via ffmpeg-devel
wrote:
> On 2025-01-01 06:15 +0100, Michael Niedermayer wrote:
> > Suggested-by: Marton Balint
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavformat/vqf.c | 21 ++---
> > 1 file changed, 14 in
On 1/21/2025 2:41 PM, Michael Niedermayer wrote:
Hi
As people likely know i belive it is not but i got a 2nd opinion:
I asked chat gpt this:
You can't possibly be serious.
Is it a democracy, if only people can vote who have performed a specific action
at least 20 times in the last 3 years
On 1/21/2025 2:48 PM, Michael Niedermayer wrote:
Hi James
On Tue, Jan 21, 2025 at 01:22:52PM -0300, James Almer wrote:
On 1/21/2025 12:54 PM, Michael Niedermayer wrote:
Hi
On Tue, Jan 21, 2025 at 01:04:45PM +0100, Niklas Haas wrote:
On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
Hello,
On 21/01/2025 11:51, Niklas Haas wrote:
> On Tue, 21 Jan 2025 03:41:06 +0100 Michael Niedermayer
> wrote:
>> On Tue, Jan 21, 2025 at 02:26:24AM +0100, Michael Niedermayer wrote:
>>> Hi
>>>
>>> On Mon, Jan 20, 2025 at 02:39:29PM -0600, Marth64 wrote:
Hello, in the context of a GA member,
Hi James
On Tue, Jan 21, 2025 at 01:22:52PM -0300, James Almer wrote:
> On 1/21/2025 12:54 PM, Michael Niedermayer wrote:
> > Hi
> >
> > On Tue, Jan 21, 2025 at 01:04:45PM +0100, Niklas Haas wrote:
> > > On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
> > > > Hello, in the context of a GA memb
Hi
As people likely know i belive it is not but i got a 2nd opinion:
I asked chat gpt this:
Is it a democracy, if only people can vote who have performed a specific action
at least 20 times in the last 3 years? This way 49 of over 2000 people can only
vote
Heres the first reply i got:
A demo
On Thu, Jan 16, 2025 at 04:39:50AM +0100, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavformat/mpegts.c | 1 +
> 1 file changed, 1 insertion(+)
will apply
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The real ebay dictionary,
On Thu, Jan 16, 2025 at 02:37:39PM +0100, Michael Niedermayer wrote:
> Hi all
>
> On Thu, Jan 16, 2025 at 02:23:07PM +0100, Michael Niedermayer wrote:
> > This blocks disallowed extensions from probing
> > It also requires all available segments to have matching extensions to the
> > format
> >
Fixes: ticket/11418
This needs to be reviewed by someone knowing aac
Found-by: 丁zhengzheng
Signed-off-by: Michael Niedermayer
---
libavcodec/aacenc_pred.c | 11 +++
libavcodec/aacenc_tns.c | 9 ++---
2 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/libavcodec/aacen
On Sat, Jan 11, 2025 at 03:02:47AM +0100, Michael Niedermayer wrote:
> On Fri, Jan 10, 2025 at 05:06:13AM +0100, Michael Niedermayer wrote:
> > Sponsored-by: Sovereign Tech Fund
> > Signed-off-by: Michael Niedermayer
> > ---
> > libswscale/input.c| 97 +
Ping?
Manuel Lauss schrieb am Mo., 13. Jan. 2025, 22:00:
> codec37 operates on 2 buffers, which must be considered private to
> the codec and must therefore not be changed by subsequent FOBJs.
>
> Let codec37 therefore operate on frm1/2 instead of frm0/2, but copy
> the decoded image to frm0 whe
On 1/21/2025 12:54 PM, Michael Niedermayer wrote:
Hi
On Tue, Jan 21, 2025 at 01:04:45PM +0100, Niklas Haas wrote:
On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
Hello, in the context of a GA member,
I think there is general interest in modernizing technical tooling
specifically regarding
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: Tuesday, January 21, 2025 4:54 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Regarding Git Tooling
>
> Hi
>
> On Tue, Jan 21, 2025 at 01:04:45PM
Hi
On Tue, Jan 21, 2025 at 01:04:45PM +0100, Niklas Haas wrote:
> On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
> > Hello, in the context of a GA member,
> >
> > I think there is general interest in modernizing technical tooling
> > specifically regarding ML/patch workflow vs. integrated git
On 21/01/2025 21:04, Niklas Haas wrote:
On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
Hello, in the context of a GA member,
I think there is general interest in modernizing technical tooling
specifically regarding ML/patch workflow vs. integrated git solution.
Both have their merits. I t
Hi James
On Mon, Jan 20, 2025 at 12:07:27PM -0300, James Almer wrote:
> On 1/20/2025 11:30 AM, Nicolas George wrote:
[...]
> I'd really like if we can stop with the "Everything's fucked, nothing can be
> done" mails every other week and instead make use of the framework we came
> up with, or if ne
---
libavutil/hwcontext_vulkan.c | 1 +
libavutil/vulkan.c | 7 ---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/libavutil/hwcontext_vulkan.c b/libavutil/hwcontext_vulkan.c
index f728163529..5d08e662bd 100644
--- a/libavutil/hwcontext_vulkan.c
+++ b/libavutil/hwcont
This is a useful format for high-precision intermediates.
---
libavutil/pixdesc.c | 21 +
libavutil/pixfmt.h | 4
2 files changed, 25 insertions(+)
diff --git a/libavutil/pixdesc.c b/libavutil/pixdesc.c
index e595c76232..857cc013ca 100644
--- a/libavutil/pixdesc.c
+++ b
This function can return AVERROR_BUG in theory if something
went wrong, but so can the caller, so we should propagate that
error message upward in that case.
Signed-off-by: Leo Izen
---
libavutil/frame.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/libavutil/frame
On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 wrote:
> Hello, in the context of a GA member,
>
> I think there is general interest in modernizing technical tooling
> specifically regarding ML/patch workflow vs. integrated git solution.
> Both have their merits. I think what we have today is optimized
Sample rates up to 2^31 - 1 are considered valid, while greater values
are invalid. Removing the check potentially allows the sample rate
to be decoded in all cases instead of halting demux for values
greater than 2^31 - 1.
Fixes Trac ticket #11361.
---
libavformat/riffdec.c | 5 -
1 file ch
On Tue, 21 Jan 2025 03:41:06 +0100 Michael Niedermayer
wrote:
> On Tue, Jan 21, 2025 at 02:26:24AM +0100, Michael Niedermayer wrote:
> > Hi
> >
> > On Mon, Jan 20, 2025 at 02:39:29PM -0600, Marth64 wrote:
> > > Hello, in the context of a GA member,
> > >
> > > I think there is general interest in
62 matches
Mail list logo
