> -Original Message-
> From: Marth64
> Sent: Thursday, January 30, 2025 7:56 AM
> To: Soft Works
> Cc: FFmpeg development discussions and patches de...@ffmpeg.org>; Kieran Kunhya
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection
> and ffprobe fields (cover letter)
>
Le mer. 29 janv. 2025 à 17:40, Marvin Scholz a écrit :
>
>
>
> On 29 Jan 2025, at 15:40, Romain Beauxis wrote:
>
> > This patch makes sure that ogg/flac headers are parsed again when
> > encountering a new logic stream inside a chained ogg bistream[1].
> >
> > This patches makes it possible to ret
Hi,
If extended it will have to be more generic. But for only two fields
present now I did not want to over engineer this in the initial
addition of the option.
It makes sense except for the DVB subs. I thought those were discrete
graphics or text streams. Wouldn't analyzeduration catch them?
On Thu, Jan 30, 2025 at 12:27 AM Soft Works <
softworkz-at-hotmail@ffmpeg.org> wrote:
> >
> > If you have reason to believe otherwise, then indeed the situation is
> > more
> > complicated. And then we may have a third faction consisting of some
> > subset of
> > (Michael, Timo, Fabrice, and p
On Wed, Jan 29, 2025 at 9:33 PM Michael Niedermayer
wrote:
> Hi all
>
> Heres my current "work in progress": (sending that before fosdem, so
> people can discuss if they like)
>
> Goals:
> The proposed changes aim to improve the General Assembly's structure
> to ensure inclusivity, fairness,
> -Original Message-
> From: Marth64
> Sent: Thursday, January 30, 2025 6:41 AM
> To: Soft Works
> Cc: FFmpeg development discussions and patches de...@ffmpeg.org>; Kieran Kunhya
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection
> and ffprobe fields (cover letter)
On Wed, Jan 29, 2025 at 10:49 PM Soft Works <
softworkz-at-hotmail@ffmpeg.org> wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Leo
> > Izen
> > Sent: Wednesday, January 29, 2025 10:39 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] Democratizat
On Wed, Jan 29, 2025 at 9:02 PM Ronald S. Bultje wrote:
> Hi,
>
> On Wed, Jan 29, 2025 at 2:32 PM Kieran Kunhya via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> > It's clear the contribution method is outdated and difficult to
> > manage. We need to move to GitLab ASAP
>
>
> Yes please.
>
On Wed, Jan 29, 2025 at 10:45 PM Nicolas George wrote:
> Marth64 (12025-01-29):
> > Help me understand your version so we can make a table to contrast?
>
> Once again: learn from history.
>
> What we are seeing here is a small group of people with some skills in
> social engineering bullying Mich
On Wed, Jan 29, 2025 at 10:36 PM Nicolas George wrote:
> > Yes, obviously. That is exactly why I think that another fork is a likely
> > outcome at this point in time.
>
> Then the only viable strategy is to make sure the people who fork are
> the harmful ones.
>
So you're leaving? Don't let the
> What do you think about this?
On first glance it sounds promising. I think it's worth exploring.
I've not used coded_side_data before so I'd have to look again with
fresh eyes to make a better opinion.
Thanks
___
ffmpeg-devel mailing list
ffmpeg-devel@
> -Original Message-
> From: Marth64
> Sent: Thursday, January 30, 2025 6:46 AM
> To: Soft Works
> Cc: FFmpeg development discussions and patches de...@ffmpeg.org>; Kieran Kunhya
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection
> and ffprobe fields (cover letter
That said, the concept of exposing the properties was rejected. I
understand why since they are internal.
So the conversation would have to be re-opened, or maybe an
alternative solution devised.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https
> LOL 😊
lol indeed :)
> Another use case is in combination with Subtitle Filtering: If there's
> auto-conversion desired in ffmpeg
Yeah that's reasonable. I would request a manual switch or some other
way to establish the filter unconditionally, for those who do want to
operate on the sparse file
Hello,
Would it be possible to merge this patch?
Thanks,
Vitaly
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subje
> -Original Message-
> From: Marth64
> Sent: Thursday, January 30, 2025 6:25 AM
> To: Soft Works
> Cc: FFmpeg development discussions and patches de...@ffmpeg.org>; Kieran Kunhya
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection
> and ffprobe fields (cover letter)
> So, this has to be worked out in some way. Do you want to submit something or
> shall I?
https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=12356
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-dev
> -Original Message-
> From: Marth64
> Sent: Thursday, January 30, 2025 6:07 AM
> To: Soft Works
> Cc: FFmpeg development discussions and patches de...@ffmpeg.org>; Kieran Kunhya
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection
> and ffprobe fields (cover letter)
>
> Which kind of recurrence pattern are you talking about?
I am talking about really sparse pattern. e.g. nothing for a long
time, then ads inserted or program changes, and embedded bit stream
starts.
It's not that often but it happens with SCTE-20, or sloppy DVD edits
for example.
> Even if it wa
From: Marth64
Sent: Thursday, January 30, 2025 5:44 AM
To: Soft Works
Cc: FFmpeg development discussions and patches ;
Kieran Kunhya
Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and
ffprobe fields (cover letter)
> > For what it's worth, I have seen this and it can
> For what it's worth, I have seen this and it can definitely happen.
Hi, I have seen it too, especially with SCTE-20 samples. Thanks
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, v
LGTM. I had noticed that #ffmpeg channel has +r mode but #ffmpeg-devel
does not which can confuse people. So if user does not have registered nick
they will only be loaded into #ffmpeg-devel.
Maybe this gets changed or explained in a second patch later but this is
good enough.
Will push tomorrow. Thanks
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
kiwiirc appears offline, it shows a CloudFlare gateway timeout.
Replace with the new Libera.Chat web client
---
src/contact | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/contact b/src/contact
index 537ca9d..6943d06 100644
--- a/src/contact
+++ b/src/contact
@@ -104,7 +104
From: softworkz
Signed-off-by: softworkz
---
doc/fftools-common-opts.texi | 4
1 file changed, 4 insertions(+)
diff --git a/doc/fftools-common-opts.texi b/doc/fftools-common-opts.texi
index 8b0931a86d..37bed92864 100644
--- a/doc/fftools-common-opts.texi
+++ b/doc/fftools-common-opts.texi
From: softworkz
This commit adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
Signed-off-by: softworkz
---
fftools/opt_common.c | 12
1 file changed, 12 insertions(+)
diff --git a/fftools/opt_common.c b/fftools/
From: softworkz
Signed-off-by: softworkz
---
doc/APIchanges | 3 +++
libavutil/log.c | 32 +---
libavutil/log.h | 10 ++
libavutil/version.h | 2 +-
4 files changed, 43 insertions(+), 4 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
This pathcset adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
Update V2
* Fix merge conflicts
Update V3
* Rebased
softworkz (3):
avutil/log: support logging of date and timing information
fftools/opt_common: add timin
Hi,
I have a file which I can't down-mix to stereo due to
AV_CHANNEL_ORDER_NATIVE requirement in sane_layout.
```
$ ffmpeg -i COMMUNITY_HERO_2.mov -vn -af
'aformat=sample_rates=48000:channel_layouts=stereo' -y /tmp/out.wav
ffmpeg version N-118381-g4ba9ae7742 Copyright (c) 2000-2025 the FFmpeg
dev
Fixes: out of array access
Fixes: crash-a41ef3db699013f669b076f02f36942925f5a98c
Found-by: Kacper Michajlow
Signed-off-by: Michael Niedermayer
---
libavcodec/h263dec.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/libavcodec/h263dec.c b/libavcodec/h263dec.c
i
If the command array failed to allocate, the current parsed
Command has to be cleared, else memory allocated for it
would be leaked.
Fix CID 1638635
---
libavfilter/f_sendcmd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/f_sendcmd.c b/libavfilter/f_sendcmd.c
index 8a0c368108..
Makes clearing the Command more explicit and
consistent.
---
libavfilter/f_sendcmd.c | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/libavfilter/f_sendcmd.c b/libavfilter/f_sendcmd.c
index d5d72e6410..8a0c368108 100644
--- a/libavfilter/f_sendcmd.c
+++ b/l
On Wed, 29 Jan 2025 21:33:21 +0100 Michael Niedermayer
wrote:
> Hi all
>
> Heres my current "work in progress": (sending that before fosdem, so people
> can discuss if they like)
>
> Goals:
> The proposed changes aim to improve the General Assembly's structure to
> ensure inclusivity, fai
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Niklas Haas
> Sent: Wednesday, January 29, 2025 10:22 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> On Wed, 29 Jan 2025 21:51:27 +0100 Nicolas George
> wrot
> -Original Message-
> From: ffmpeg-devel On Behalf Of Leo
> Izen
> Sent: Wednesday, January 29, 2025 10:39 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2
>
> On 1/29/25 3:33 PM, Michael Niedermayer wrote:
> > Hi all
> >
> > Her
Leo Izen (12025-01-29):
> I have been silent on this for a very long time, but I would like to point
> out at this point that Michael has approximately five times as many commits
> as the next-most prolific contributor (Andreas).
We can add that Michael's commits tend to be more complex.
This is
Marth64 (12025-01-29):
> Help me understand your version so we can make a table to contrast?
Once again: learn from history.
What we are seeing here is a small group of people with some skills in
social engineering bullying Michael and manipulating occasional
contributors in order to take control
Niklas Haas (12025-01-29):
> > if people are going to fork, then fork. ffmpeg has plenty of active and
> > inactive forks. its not the end of the world. just a fork.
> I thought we agreed that it's best to avoid this outcome if possible?
We agree on no such thing. If banning a few people who do no
On 1/29/25 3:33 PM, Michael Niedermayer wrote:
Hi all
Heres my current "work in progress": (sending that before fosdem, so people can
discuss if they like)
Goals:
The proposed changes aim to improve the General Assembly's structure to
ensure inclusivity, fairness, and resilience against
Niklas Haas (12025-01-29):
> As I pointed out in the past, I am implicitly assuming that Timo, Fabrice, and
> other current holders of admin rights would go along with whatever Michael
> decides, so that makes Michael alone the only person who is blocking the will
> of
> the CC (and by extension,
On Wed, 29 Jan 2025 06:12:30 -1000 compn wrote:
> On Wed, 29 Jan 2025 16:16:29 +0100, Niklas Haas wrote:
>
> > I think the most important crux of the problem is a fundamental disagreement
> > between Michael and the "community" (for lack of a better term) about the
> > role
> > of the CC (and by
On Wed, 29 Jan 2025 21:51:27 +0100 Nicolas George wrote:
> Niklas Haas (12025-01-29):
> > I think the most important crux of the problem is a fundamental disagreement
> > between Michael and the "community" (for lack of a better term) about the
> > role
> > of the CC (and by extension, the GA).
>
Hi Nicolas:
> Please do not accept uncritically what a greedy minority limply
> supported by a silent majority wants to pass as the will of the
> community.
Help me understand your version so we can make a table to contrast?
Thanks
___
ffmpeg-devel mail
Marth64 (12025-01-29):
> * The community wants
Please do not accept uncritically what a greedy minority limply
supported by a silent majority wants to pass as the will of the
community.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg
Niklas Haas (12025-01-29):
> I think the most important crux of the problem is a fundamental disagreement
> between Michael and the "community" (for lack of a better term) about the role
> of the CC (and by extension, the GA).
That is a very biassed way of stating it.
For one thing, it is not Mic
Add a new filter 'dnn_clip' that performs zero-shot image classification using
CLIP (Contrastive Language-Image Pre-Training) models. The filter supports:
- Loading and running CLIP models through the LibTorch backend
- Outputting classification confidence scores as frame side data
Requires token
Hi all
Heres my current "work in progress": (sending that before fosdem, so people can
discuss if they like)
Goals:
The proposed changes aim to improve the General Assembly's structure to
ensure inclusivity, fairness, and resilience against attacks. The key goals are
as follows:
Increa
On Wed, Jan 29, 2025 at 10:21 PM Jan Ekström wrote:
>
> On Sun, Jan 26, 2025 at 9:41 PM Kacper Michajłow wrote:
> >
> > Signed-off-by: Kacper Michajłow
> > ---
> > libavformat/vqf.c | 8
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/libavformat/vqf.c b/libavf
On Sun, Jan 26, 2025 at 9:41 PM Kacper Michajłow wrote:
>
> Signed-off-by: Kacper Michajłow
> ---
> libavformat/vqf.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/vqf.c b/libavformat/vqf.c
> index 58b1546f53..fbe54739cd 100644
> --- a/libavformat/v
Hi Kieran:
Trying to distill to a start of discussion points at the high level
(without GPT).
Converting the statements, from (issue)->(Michael) to (issue)->(effect):
* The community wants the GA/TC/CC to be sovereign, but there is a
BDOL model too which is not easily compatible, causing uncertai
Hi Ben,
On Wed, Jan 29, 2025 at 11:12 AM compn wrote:
> we can see how badly something ran by GA vote works right now. with our
> own eyes. ffmpeg just had a vote for the CC and two developers
> immediately quit working in the CC. why did we just waste all that
> time with a vote then?
That's
Hi,
On Wed, Jan 29, 2025 at 2:32 PM Kieran Kunhya via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> It's clear the contribution method is outdated and difficult to
> manage. We need to move to GitLab ASAP
Yes please.
Ronald
___
ffmpeg-devel mailin
If there's a very large ISOBMFF box that needs to be skipped, it can
cause an overflow for ctx->skip. There's already a safeguard to return
quickly if ctx->skip > bufsize, so changing ctx->skip to int64_t will
allow this to happen even if ctx->skip would overflow a signed int.
Several other member
On Wed, Jan 29, 2025 at 6:27 PM Marth64 wrote:
>
> Here is an idea,
> Can we try to lay out the friction points in a table or bullet format
> where we can separate the issue from emotion and direct name calling?
>
> For example,
> " * Community has issue ABC but we can't move forward because senio
On Wed, Jan 29, 2025 at 7:01 PM Michael Niedermayer
wrote:
>
> Hi Yigithan
>
> Its good that you bring these issues up.
> Discussing about them is a step towards solving them
>
> see my coments inline below
>
> On Wed, Jan 29, 2025 at 06:51:40PM +0300, Yigithan Yigit wrote:
> > Hi Michael,
> >
> >
Hi Yigithan
Its good that you bring these issues up.
Discussing about them is a step towards solving them
see my coments inline below
On Wed, Jan 29, 2025 at 06:51:40PM +0300, Yigithan Yigit wrote:
> Hi Michael,
>
> I want to give some feedback before GSoC’25 as GSoC’24 participant. I speak
>
If there are no comments, I will push in a few days.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscr
Here is an idea,
Can we try to lay out the friction points in a table or bullet format
where we can separate the issue from emotion and direct name calling?
For example,
" * Community has issue ABC but we can't move forward because senior
leaders don't agree"
" * Community has issue XYZ but we can
Hi Soft Works,
> So I apologize for the misunderstanding. I didn't intend to be rude or hurt
> anybody's feelings, I just meant to express for what it's commonly used and
> didn't mean to take the conversation some levels downwards.
It's okay. You're entitled to share your opinion too. I was not
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Wednesday, January 29, 2025 6:23 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
>
>
> > -Original Message-
> > From: ffmpeg-deve
Hello all,
The thread is passionate but I'm requesting help from everyone to
please help me make it more productive than negative.
I agree with Zhao Zhili:
> I don’t stay long enough to know the history, but I don’t think delving into
> history
> helps the current situation. Let's talk less abou
Hi SW,
would you mind moving to a different thread or at least changing the email
subject?
This discussion is already hard enough to follow without you throwing a fit.
Thank you
Vittorio
On Wed, Jan 29, 2025 at 6:23 PM Soft Works <
softworkz-at-hotmail@ffmpeg.org> wrote:
>
>
> > -Original
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marth64
> Sent: Wednesday, January 29, 2025 6:15 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> Hi Soft Works,
>
> > What do you mean by "colorful languag
Hi Soft Works,
> What do you mean by "colorful language"?
> And "mockery" - you mean the pseudo code? What's wrong about that? I could
> have said the same in many words as well.
Words are fine and passionate opinions are fine. The pseudocode and
"shit-storming" comment came off the wrong way, th
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marth64
> Sent: Wednesday, January 29, 2025 5:59 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> Hello,
>
> Re: Soft Works
> Let's not mock people please. You
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marth64
> Sent: Wednesday, January 29, 2025 5:59 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> Hello,
>
> Re: Soft Works
> Let's not mock people please.
Le 25/01/2025 à 01:46, Michael Niedermayer a écrit :
[...]
this passes tests.
but if you want, you could instead of testing "extra metadata (not needed for
decoding)"
test more than 1 packet
having a best case score of 1 seems to be something that will
likely fail sooner or later by not detect
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> compn
> Sent: Wednesday, January 29, 2025 5:13 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Democratization
>
> michael is not a supervillain. saying its "michael vs the
> community" ? please stop with these per
Hello,
Re: Soft Works
Let's not mock people please. You are entitled to your opinion but we
can leave the colorful language and mockery out.
Not saying you are the first and only one, I am aware this is a
chronic habit for the community email threads at large, but I ask
yourself and everyone for h
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Vittorio Giovara
> Sent: Wednesday, January 29, 2025 5:24 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> On Wed, Jan 29, 2025 at 4:24 PM Soft Works <
> soft
On 29 Jan 2025, at 15:40, Romain Beauxis wrote:
> This patch makes sure that ogg/flac headers are parsed again when
> encountering a new logic stream inside a chained ogg bistream[1].
>
> This patches makes it possible to retrieve metadata in chained ogg/flac
> bitstreams. It is particularly imp
On Wed, Jan 29, 2025 at 4:24 PM Soft Works <
softworkz-at-hotmail@ffmpeg.org> wrote:
> > You are skewing the discuscussion and attacking me while constructing
> > a
> > conspiracy theory that is not true (I don't want to gain any control
> > at
> > all, I want a community-decided process for m
On Wed, Jan 29, 2025 at 5:12 PM compn wrote:
> we can see how badly something ran by GA vote works right now. with our
> own eyes. ffmpeg just had a vote for the CC and two developers
> immediately quit working in the CC. why did we just waste all that
> time with a vote then?
>
I respect the fa
On Wed, 29 Jan 2025 16:16:29 +0100, Niklas Haas wrote:
> I think the most important crux of the problem is a fundamental disagreement
> between Michael and the "community" (for lack of a better term) about the role
> of the CC (and by extension, the GA). Michael is under the impression that
> the
Le mer. 29 janv. 2025 à 15:43, Romain Beauxis
a écrit :
>
> This patch adds a fate test for ogg/flac chained streams.
>
> First, a new api-dump-stream-meta-test utility is introduced then it is
> used to dump the metadata of a ogg/flac chained sample.
>
> Sample is available here:
https://www.drop
Hi Michael,
I want to give some feedback before GSoC’25 as GSoC’24 participant. I speak for
myself but I know some of other colleagues are sharing similar thoughts with
me.
First of all community has incredible talented people and I am not even single
percent of those people. However I tried
On Wed, 29 Jan 2025 21:13:13 +0800, Steven Liu wrote:
> compn 于2025年1月29日 周三17:26写道：
>
> > hi,
>
> Hi compn
>
>
>
> >
> > as i asked on irc this week, and as many of you may have seen it, the
> > owner of twitter/x did a thing at a political rally last week:
> > https://www.youtube.com/watc
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Vittorio Giovara
> Sent: Wednesday, January 29, 2025 3:39 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> On Wed, Jan 29, 2025 at 12:52 PM Soft Works <
> softw
On Wed, 29 Jan 2025 13:39:36 +0100 Nicolas George wrote:
> Zhao Zhili (12025-01-29):
> > I don’t stay long enough to know the history, but I don’t think delving
> > into history
> > helps the current situation. Let's talk less about history and hatred to
> > avoid creating
> > a self-fulfilling
This patch adds a fate test for ogg/flac chained streams.
First, a new api-dump-stream-meta-test utility is introduced then it is
used to dump the metadata of a ogg/flac chained sample.
Sample is available here:
https://www.dropbox.com/scl/fo/fxt2edwkyj2mjc9qubku5/AICHxJyxMMAK8MIJqWLcvk4?rlkey=m
This patch makes sure that ogg/flac headers are parsed again when
encountering a new logic stream inside a chained ogg bistream[1].
This patches makes it possible to retrieve metadata in chained ogg/flac
bitstreams. It is particularly important because ogg/flac is one of the
only (if not the only
On Wed, Jan 29, 2025 at 12:52 PM Soft Works <
softworkz-at-hotmail@ffmpeg.org> wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Vittorio Giovara
> > Sent: Wednesday, January 29, 2025 11:51 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.o
Le mar. 28 janv. 2025 à 00:25, Michael Niedermayer
a écrit :
>
> On Fri, Jan 24, 2025 at 07:40:40PM -0600, Romain Beauxis wrote:
> > Hi all!
> >
> > Le sam. 18 janv. 2025 à 11:54, Romain Beauxis
> > a écrit :
> > >
> > > This patch makes sure that ogg/flac headers are parsed again when
> > > enco
On 1/29/2025 9:29 AM, Andreas Rheinhardt wrote:
James Almer:
Similar in purpose as the packet side data of the same name, but for encoders.
Signed-off-by: James Almer
---
An example of RefCount used for side data, including a copy and uninit callback
to handle allocations within the entry.
On 29 Jan 2025, at 14:09, Steven Liu wrote:
>
>
>
> Ingo Oppermann 于2025年1月29日 周三17:54写道：
> Hi Ingo,
>
> Great job, thanks for your valuable patch,
> The current implementation of the hls_time might produce segments
> with shorter duration in some cases. With the hls_min_time option
> a minima
compn 于2025年1月29日 周三17:26写道：
> hi,
Hi compn
>
> as i asked on irc this week, and as many of you may have seen it, the
> owner of twitter/x did a thing at a political rally last week:
> https://www.youtube.com/watch?v=wubITdJ_MCw
>
> when asked if he meant the gesture, the man replied with this
Ingo Oppermann 于2025年1月29日 周三17:54写道：
Hi Ingo,
Great job, thanks for your valuable patch,
> The current implementation of the hls_time might produce segments
> with shorter duration in some cases. With the hls_min_time option
> a minimal segment duration will be enforced.
>
> Instead of changing
Hi Andreas,
I am not sure if that is needed. I can add the data observed on my machine
(AMD 7950x Zen 4),
I think this will vary from machine to machine. It is expected to be around
2x
compared to AVX2 and there is no core change apart from processing the
scalar loop with masked instructions.
The
Zhao Zhili (12025-01-29):
> I don’t stay long enough to know the history, but I don’t think delving into
> history
> helps the current situation. Let's talk less about history and hatred to
> avoid creating
> a self-fulfilling prophecy.
“Those who cannot remember the past are condemned to repeat
James Almer:
> Similar in purpose as the packet side data of the same name, but for encoders.
>
> Signed-off-by: James Almer
> ---
> An example of RefCount used for side data, including a copy and uninit
> callback
> to handle allocations within the entry.
>
> libavutil/frame.h | 14 ++
Shreesh Adiga:
> Signed-off-by: Shreesh Adiga <16567adigashre...@gmail.com>
> ---
> v3: Fix build failure on older nasm by replacing "kmovw k, tmpw"
> with "kmov k, tmpd" which matches "kmovw k, r32" syntax.
> v2: Tried to align operands and improve indentation for ASM routine.
> libswscale/x8
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Vittorio Giovara
> Sent: Wednesday, January 29, 2025 11:51 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> On Wed, Jan 29, 2025 at 11:32 AM Soft Works <
> softworkz-at-hotmail@ffmpeg.org> wrote:
>
> >
On Wed, Jan 29, 2025 at 11:32 AM Soft Works <
softworkz-at-hotmail@ffmpeg.org> wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Vittorio Giovara
> > Sent: Wednesday, January 29, 2025 10:45 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.o
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Vittorio Giovara
> Sent: Wednesday, January 29, 2025 10:45 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Democratization
>
> On Tue, Jan 28, 2025 at 7:21 PM Michael Niedermaye
On Wed, Jan 29, 2025 at 4:40 PM Frank Plowman wrote:
> On 26/01/2025 03:10, Nuo Mi wrote:
> > fixes https://github.com/ffvvc/tests/tree/main/fuzz/passed/000323.bit
> >
> > Co-authored-by: Frank Plowman
> > ---
> > libavcodec/vvc/ps.c | 11 +--
> > 1 file changed, 9 insertions(+), 2 dele
On 29/01/2025 18:58, Martin Storsjö wrote:
This table is zero initialized by default, and has to be
explicitly initialized.
Coincidentally, this fixes linking checkasm with Apple's older
linker. (In Xcode 15, Apple switched to a new linker. The one in
older toolchains seems to have a bug where i
This table is zero initialized by default, and has to be
explicitly initialized.
Coincidentally, this fixes linking checkasm with Apple's older
linker. (In Xcode 15, Apple switched to a new linker. The one in
older toolchains seems to have a bug where it won't figure out to
load object files from
The current implementation of the hls_time might produce segments
with shorter duration in some cases. With the hls_min_time option
a minimal segment duration will be enforced.
Instead of changing the current behaviour of hls_time which might
break existing workflows, the new option hls_min_time w
On a Zen 5, on Ubuntu 24.04 (with CLOCKS_PER_SEC 100), the
value of clock() in this loop increments by 0 most of the time,
and when it does increment, it usually increments by 1 compared
to the previous round.
Due to the "last_t + 2*last_td + (CLOCKS_PER_SEC > 1000) >= t"
expression, we only m
On Tue, Jan 28, 2025 at 7:21 PM Michael Niedermayer
wrote:
> About people pointing to me as the cause of something they do.
> Given iam in this project for over 20 years and iam the main author and
> we had a fork long ago. With many people joining back together. There are
> people who have had p
1 - 100 of 102 matches
Mail list logo
