Implement support for CODECAPI_AVLowLatencyMode property, which is
useful for live streaming use cases (and cannot be achieved by
selecting any of the low latency "scenario" encoder presets alone).
Co-authored-by: Conn O'Griofa
Signed-off-by: Cameron Gutman
---
libavcodec/mfenc.c | 5 +
1 f
On 8/2/2025 3:33 PM, Michael Niedermayer wrote:
Hi
This breaks:
./ffmpeg -i 'tickets//1666/avc-intra-panasonic-AG-HPX301E.mov' -f null -
after this patch theres a lot of errors:
...
[vist#0:0/h264 @ 0x55837b5fd6c0] [dec:h264 @ 0x55837b62c6c0] Error submitting
packet to decoder: Invalid data
Add check and av_frame_free() for the return value of av_frame_alloc() to avoid
potential NULL pointer dereference and memory leak.
Fixes: 88a8ba5c99 ("avcodec/amfenc: redesign to use hwcontext_amf.")
Signed-off-by: Jiasheng Jiang
---
libavcodec/amfenc.c | 5 +
1 file changed, 5 insertions(
Add av_freep() to free avio_ctx_buffer if avio_alloc_context fails
to avoid potential memory leak.
Fixes: 5fc4dea39c ("examples: add avio_reading.c example")
Signed-off-by: Jiasheng Jiang
---
doc/examples/avio_read_callback.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/examples/avio_
On 2025-08-02 20:08 +0200, Nicolas George wrote:
> Alexander Strasser via ffmpeg-devel (HE12025-08-02):
> > I don't understand what the issue with the commit message is?
>
> Two issues:
OK, now I understand what you mean.
It wasn't clear to me from your original replies in this thread.
> - Form
Hi
This breaks:
./ffmpeg -i 'tickets//1666/avc-intra-panasonic-AG-HPX301E.mov' -f null -
after this patch theres a lot of errors:
...
[vist#0:0/h264 @ 0x55837b5fd6c0] [dec:h264 @ 0x55837b62c6c0] Error submitting
packet to decoder: Invalid data found when processing input
[h264 @ 0x55837c768000
On 2025-07-18 17:42 +0200, Kacper Michajlow wrote:
> On Fri, 11 Jul 2025 at 23:41, Michael Niedermayer
> wrote:
> > On Thu, Jul 10, 2025 at 02:35:10PM +0300, Martin Storsjö wrote:
[...]
> >
> > > I'm unsure if we should allow it everywhere, and just single out loongarch
> > > as a case where it is
Alexander Strasser via ffmpeg-devel (HE12025-08-02):
> I don't understand what the issue with the commit message is?
Two issues:
- Form: “>” is not part of our practice for commit message. Look at the
past year of commit message, the only ones that include “>” lines are
mistakes.
- Substance
Nicolas George (HE12025-08-02):
> - The patch series lacks transverse user documentation.
>
> - The patch series increases the risk of data corruption due to user
> negligence and should include at least some guardrails against that.
Here is the situation before this patch series:
- All alpha
Hi
Please reply with testcases, i just looked and found exactly one testcase
(Ticket11526) which i will post a fix for soon
if you have other cases that fail please provide testcases
its trivial to update the lists in hls.c but i can only do it if i
know the exceptions
thx
--
Michael GnuP
On 2025-07-31 00:02 +0200, Nicolas George wrote:
> Niklas Haas (HE12025-07-30):
> > What you pointed out is pointess nitpicking, and I could point you to
> > plenty of other comments by "experienced" FFmpeg developers who have done
> > the same in the past, presumably without having sat through dia
Romain Beauxis (HE12025-08-02):
> Casual contributors eventually become knowledgeable about the
> framework/code base which eventually leads to some of them becoming
> seasoned developers and reviewers.
>
> If you want to grow the number of people working with the project, you've
> got to be able
Hi.
I write this mail to the technical committee to state that since Niklas
Haas has stated intent to stop discussing on the mailing-list, I am
asking the technical committee to make a decision on the subject.
It will take me a little time, at least several hours, maybe a few days,
to properly ex
Le sam. 2 août 2025 à 04:59, Nicolas George a écrit :
>
> Romain Beauxis (HE12025-08-01):
> > Part of my question is: how should people know what are the area you
> > are responsible for and who to contact when working on specific areas?
>
> I know it and I am perfectly fine with reading the summa
Niklas Haas (HE12025-08-02):
> I don't think you understand the problem here.
… says somebody who has misunderstood what I was suggesting twice in a
row.
> Such a flag would accomplish
> nothing, since there are no filters that would actually set it.
Yes, your job involves setting this flags on
On Sat, 02 Aug 2025 11:40:54 +0200 Nicolas George wrote:
> Niklas Haas (HE12025-07-29):
> > I think this would involve more invasive changes (i.e. adding negotiation to
> > the avfilter code for this and ideally other properties) that you and I both
> > agreed is out of scope of this series.
>
> N
Hi Luca
It would be really cool if you would return.
Theres a real lack of developers / maintainers in some areas
If you want me to update your entry in the MAINTAINER file,
we now have a [0] [1] [2] that can be added to each to indicate
the "status"
[0] No current maintainer [but maybe you could
Kacper Michajlow (HE12025-08-02):
> It's trivial to automatically download/preview patches, similar to how
> attachments can be previewed if a patcheset is sent as an attachment.
Then document it.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpe
On Sat, 2 Aug 2025 at 11:59, Nicolas George wrote:
>
> Romain Beauxis (HE12025-08-01):
> > Part of my question is: how should people know what are the area you
> > are responsible for and who to contact when working on specific areas?
>
> I know it and I am perfectly fine with reading the summary
Kieran Kunhya via ffmpeg-devel (HE12025-07-29):
> Hello,
>
> It seem there is strong evidence that AI wrote TLS code as part of the
> WHIP patch. It goes without saying why this is bad. Further discussion
> here:
> https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20053
>
> This patch was pushed withou
Romain Beauxis (HE12025-08-01):
> Part of my question is: how should people know what are the area you
> are responsible for and who to contact when working on specific areas?
I know it and I am perfectly fine with reading the summary line of every
submitted patch to see if I need to open it. Anyt
Niklas Haas (HE12025-07-29):
> I think this would involve more invasive changes (i.e. adding negotiation to
> the avfilter code for this and ideally other properties) that you and I both
> agreed is out of scope of this series.
No it does not. You just need to add a flag “this filter supports
prem
Niklas Haas (HE12025-08-02):
> I would like to merge the AVFrame.alpha_mode series as well.
Bad idea. This kind of feature affecting the whole code should stay in
the master branch for a while before being enshrined in a release.
Regards,
--
Nicolas George
On Wed, 23 Jul 2025 13:43:43 +0200 Michael Niedermayer
wrote:
> Hi everyone
>
> I intend to create the release/8.0 branch in the next 1-2 weeks
> after that i intend to make teh 8.0 release in the following 1-2 weeks
>
> If theres something you want in it make sure its pushed before the branch
>
24 matches
Mail list logo
