From: softworkz
Signed-off-by: softworkz
---
doc/muxers.texi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/doc/muxers.texi b/doc/muxers.texi
index 6d5c17b4cc..1cca8da1fb 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -3510,6 +3510,13 @@ packet written. Defaults to @code{0
From: softworkz
Signed-off-by: softworkz
---
libavformat/segment.c | 48 +--
1 file changed, 23 insertions(+), 25 deletions(-)
diff --git a/libavformat/segment.c b/libavformat/segment.c
index 3cd9e313f4..8e1e4a9c0c 100644
--- a/libavformat/segment.c
From: softworkz
Signed-off-by: softworkz
---
libavformat/segment.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/segment.c b/libavformat/segment.c
index 15196b6970..70ff01b353 100644
--- a/libavformat/segment.c
+++ b/libavformat/segment.c
@@ -905,6 +905,7 @@ static int
> -Original Message-
> From: softworkz
> Sent: Freitag, 13. Juni 2025 07:54
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz ; softworkz
>
> Subject: [PATCH 06/10] avformat/segment: Fix invalid codecpar
> extradata_size after copying
>
> From: softworkz
From: softworkz
Also moves point of log writing to after rename of temp files
and changes log level to INFO. The completion of a segment is
important enough to justify logging at INFO level.
Signed-off-by: softworkz
---
libavformat/segment.c | 10 --
1 file changed, 8 insertions(+), 2
From: softworkz
Signed-off-by: softworkz
---
libavformat/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/segment.c b/libavformat/segment.c
index c2b09b08aa..3cd9e313f4 100644
--- a/libavformat/segment.c
+++ b/libavformat/segment.c
@@ -20,7 +20,7
From: softworkz
Signed-off-by: softworkz
---
libavformat/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/segment.c b/libavformat/segment.c
index 83b7ff269b..c2b09b08aa 100644
--- a/libavformat/segment.c
+++ b/libavformat/segment.c
@@ -1098,7 +1098,7
From: softworkz
Use case is to keep early content out of the first segment when
not starting from zero.
Signed-off-by: softworkz
---
libavformat/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/segment.c b/libavformat/segment.c
index 70ff01b353
From: softworkz
Example use case:
Existing segments 0-30 and 70-99, 31-69 need to be created.
This option allows to stop precisely after 69. Otherwise it would
start overwriting segment 70 before stopping via 'q' or break signal.
Signed-off-by: softworkz
---
libavformat/segm
From: softworkz
Signed-off-by: softworkz
---
doc/muxers.texi | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/muxers.texi b/doc/muxers.texi
index 30c95c3d34..6d5c17b4cc 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -3505,6 +3505,11 @@ argument must be a time duration
From: softworkz
Allows to write segments as temp files (.tmp) which
are renamed on completion.
Signed-off-by: softworkz
---
libavformat/segment.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/libavformat/segment.c b/libavformat/segment.c
Hi,
I have some questions regarding code style.
1. White space
==
Do we prefer this
(float)(*times)[i] / 100, (float)(*times)[I - 1] / 100);
or this
(float)(*times)[i]/100, (float)(*times)[i-1]/100);
2. Multiline Ternary Expressions
wrapper script in build output
>
> softworkz . (HE12025-06-12):
> > "better" would be worse, so that's not gonna happen.
>
> Then your patch is not going to happen.
>
> > The way how the feature is meant to work is laid out clearly:
>
> If you canno
wrapper script in build output
>
> softworkz . (HE12025-06-11):
> > On important platforms like Windows, there is no "install".
> People are
> > taking/copying the build output. If it's not part of the build
> output,
> > it won't arrive at any user
pes
>
>
>
> On 12 Jun 2025, at 18:10, softworkz . wrote:
>
> >> -Original Message-
> >> From: ffmpeg-devel On Behalf
> Of
> >> Marvin Scholz
> >> Sent: Donnerstag, 12. Juni 2025 13:25
> >> To: FFmpeg development discussions
e in mermaid_print_value
>
>
>
> On 12 Jun 2025, at 4:19, softworkz . wrote:
>
> > Hi Marvin,
> >
> >> -Original Message-
> >> From: ffmpeg-devel On Behalf
> Of
> >> Marvin Scholz
> >> Sent: Mittwoch, 11. Juni 2025 21:57
> >
pes
>
>
>
> On 12 Jun 2025, at 4:26, softworkz . wrote:
>
> > Hi Marvin,
> >
> >> -Original Message-
> >> From: ffmpeg-devel On Behalf
> Of
> >> Marvin Scholz
> >> Sent: Mittwoch, 11. Juni 2025 22:42
> >&
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 21:57
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 4/4] fftools/textformat: remove
> leftover comments in mermaid_print_value
>
> Remove some leftover commented code
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 22:42
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 3/4] fftools/textformat: do not
> return early
>
> This would make the goto dead code and also would not properly
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 22:42
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 2/4] fftools/textformat: remove noop
> free
>
> The tctx->hash was freed already right before.
> ---
> fftools/te
Hi Marvin,
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 22:42
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 1/4] fftools/textformat: narrow
> variable scopes
>
> ---
> fftools/textformat/avtextformat.c | 15 +
Hi Marvin,
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 21:57
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 3/4] fftools/textformat: infer type in
> mermaid_print_value
>
> Instead of the caller having to indicate
Hi Marvin,
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 21:57
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 1/4] fftools/textformat: fix writing
> integers for mermaid
>
> With the previous logic, the integer writ
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 21:57
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 2/4] fftools/textformat: exit early in
> mermaid_print_value
>
> Doesn't change the logic, instead of exiting in e
> On Wed, Jun 11, 2025 at 9:58 PM softworkz .
> wrote:
> >
> >
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Marton Balint
> > > Sent: Mittwoch, 11. Juni 2025 21:18
> > > To: FFmpeg developmen
> On Wed, Jun 11, 2025 at 9:58 PM softworkz .
> wrote:
> >
> >
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Marton Balint
> > > Sent: Mittwoch, 11. Juni 2025 21:18
> > > To: FFmpeg developmen
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Marvin Scholz
> Sent: Mittwoch, 11. Juni 2025 21:57
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 3/4] fftools/textformat: infer type in
> mermaid_print_value
>
> Instead of the caller having to indicate if it is
wrapper script in build output
>
>
>
> On Mon, 9 Jun 2025, softworkz wrote:
>
> > From: softworkz
> >
> > Signed-off-by: softworkz
> > ---
> > .gitignore | 1 +
> > fftools/Makefile | 14 --
> > 2 files changed, 13 ins
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Dienstag, 3. Juni 2025 16:34
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib
> directly instead of gzip
>
Hi Andreas,
thinking about the direction
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> softworkz .
> Sent: Dienstag, 10. Juni 2025 15:32
> To: Kieran Kunhya ; FFmpeg development
> discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 0/3] tools/ffmpeg-sg: Add show-
> graph wra
> -Original Message-
> From: Kieran Kunhya
> Sent: Dienstag, 10. Juni 2025 00:49
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: softworkz
> Subject: Re: [FFmpeg-devel] [PATCH 0/3] tools/ffmpeg-sg: Add show-
> graph wrapper scripts (aka
From: softworkz
Signed-off-by: softworkz
---
tools/ffmpeg-sg | 249
1 file changed, 249 insertions(+)
create mode 100755 tools/ffmpeg-sg
diff --git a/tools/ffmpeg-sg b/tools/ffmpeg-sg
new file mode 100755
index 00..c8c298f8e0
--- /dev
From: softworkz
Signed-off-by: softworkz
---
.gitignore | 1 +
fftools/Makefile | 14 --
2 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/.gitignore b/.gitignore
index 59c89da5e0..989c702b6c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -32,6 +32,7 @@
/.config
From: softworkz
Signed-off-by: softworkz
---
tools/ffmpeg-sg.cmd | 73 +
1 file changed, 73 insertions(+)
create mode 100644 tools/ffmpeg-sg.cmd
diff --git a/tools/ffmpeg-sg.cmd b/tools/ffmpeg-sg.cmd
new file mode 100644
index 00
ring Ramp-Up
>
> On Sat, Jun 7, 2025 at 5:20 PM softworkz .
> wrote:
> >
> >
> > It's MythBusters Day!
> > =
> >
> >
> > Today: Busting the Lies of Nicolas George
>
> Can
_ocr] > textsubs > [overlaytextsubs] > video
What's specific to those examples is that in both cases, (closed
captions and OCR for bitmap subs), the text events DO NOT
come all at once, but continuously, which is the nature of
those cases and contradicts the false claim that NG tried
From: Kieran Kunhya
Sent: Samstag, 7. Juni 2025 01:24
To: FFmpeg development discussions and patches
Cc: softworkz
Subject: Re: [FFmpeg-devel] [PATCH v11 0/3] avutil/log: Add log flag to control
printing of memory addresses
#define LIBAVUTIL_VERSION_MAJOR 60
--#define
From: softworkz
This commit adds the mem log flag.
When specifying this flag at the command line, context prefixes will
be printed with memory addresses like in earlier ffmpeg versions.
Example with mem flag:
[hevc @ 018e72a89cc0] .
without (new behavior):
[hevc] .
Signed-off-by
From: softworkz
Signed-off-by: softworkz
---
doc/fftools-common-opts.texi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/fftools-common-opts.texi b/doc/fftools-common-opts.texi
index f6d452c40e..5d66af6b02 100644
--- a/doc/fftools-common-opts.texi
+++ b/doc/fftools-common-opts.texi
From: softworkz
Memory addresses are no longer printed by default.
With this flag set, memory addresses are included like
in earlier versions.
Signed-off-by: softworkz
---
doc/APIchanges | 3 +++
libavutil/log.c | 6 --
libavutil/log.h | 5 +
libavutil/version.h | 2 +-
4
and avoid a
> never
> > ending disagreement
>
> The never ending disagreement is there because softworkz wants that
> there is a never ending disagreement, the alternative being either
> abandoning this broken patch series or having to work at things that
> are
> obvio
y 27, 2025 at 02:35:06AM +, softworkz wrote:
> > From: softworkz
> >
> > ..and resources
> >
> > Signed-off-by: softworkz
> > ---
> > MAINTAINERS: Add myself for graph printing
> >
> > ..and resources
> >
> > Signed-
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Mittwoch, 4. Juni 2025 20:35
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> Objections Summary
> ==
> -Original Message-
> From: ffmpeg-devel On Behalf Of Michael
> Niedermayer
> Sent: Mittwoch, 4. Juni 2025 22:42
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> Hi Nicolas
>
> On Wed, Jun 04, 2025 at 09:13:44AM +020
ables a
wide range of filtering cases and - what I think should also not be
forgotten: All of its functionality is achieved without touching
any of the existing code paths for video and audio, which means
that there are no regression risks to be afraid of.
I hope this clears up
5, 20.07.18 Itä-Euroopan kesäaika softworkz . a
> écrit :
> > Given the preceding conversations, it is pretty safe to assume
> > that these comments are based on personal sentiments rather than
> > technical expertise.
>
> I won't deny the fact that several people hav
Objections Summary
==
Here's a summary of objections made so far:
Lynne
-
- Not using picture buffers for subtitle data
It's not impossible, just doesn't make much sense
I said there wasn't anybody against it anymore in 2022.
We can dig up previous conversations, or w
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 20:13
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 19:57
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
> &
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 19:45
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 19:26
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 19:35
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
&
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 19:30
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
>
sparse. It just
> feeds everything to libass and takes what comes out of it. It works when
> the subtitles arrive neatly before the video frames. It just does not
> work for such a simple use case as shifting the subtitles a few seconds
> forward.
>
> softworkz has refused
5, 20.07.18 Itä-Euroopan kesäaika softworkz . a
> écrit :
> > Given the preceding conversations, it is pretty safe to assume
> > that these comments are based on personal sentiments rather than
> > technical expertise.
>
> I won't deny the fact that several people hav
W_NORMAL
"close to identical" is not the same as identical. A deeper explanation
for the first case is given here:
https://github.com/softworkz/SubtitleFilteringDemos/issues/1
For the duration: There is quite a range of functionality built around
AVFrame's duration field. Yet, that co
I'm setting up the following challenge:
I will pay $1,000 (one-thousand US dollar)
to the first person who is able to show me a patched implementation of my
Subtitle Filtering Patchset from 2022
(https://github.com/softworkz/FFmpeg/tree/submit_subfiltering) which fulfills
the following
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Dienstag, 3. Juni 2025 16:21
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
How many people do remember that Paul actually wanted to me
> -Original Message-
> From: ffmpeg-devel On Behalf Of Hendrik
> Leppkes
> Sent: Dienstag, 3. Juni 2025 20:02
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> On Tue, Jun 3, 2025 at 4:21
> -Original Message-
> From: ffmpeg-devel On Behalf Of Devlist
> Archive
> Sent: Dienstag, 3. Juni 2025 19:16
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> > Given the preceding conversations, it is pretty safe to a
> -Original Message-
> From: ffmpeg-devel On Behalf Of Lynne
> Sent: Dienstag, 3. Juni 2025 18:00
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> You don't get to say "oh, there were no more objections, so it was fine"
> or "the use is evid
ery hard NAK from me.
>
> Indeed. And not just that. The whole series had many deep logic flaws
> that made it a dead end without a complete rewrite. I explained at the
> time, and “softworkz” was almost as rude then than they are now. My
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Dienstag, 3. Juni 2025 16:21
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
I am sorry in case this message was somewhat too brief f
ing objections in this regard.
> which is a very hard NAK from me.
I do not have the impression that this was a serious review
or response, tbh.
Best regards
sw
> On 03/06/2025 23:20, softworkz . wrote:
> > Hello everybody,
> >
> > [just deleted a whole page of introduct
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Dienstag, 3. Juni 2025 16:34
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib directly
> instead of gzip
>
> softworkz .:
know which way you would deem to be most suitable and
whatever thoughts or questions you might have beyond this.
Subtitle Flow Mode
==
Please see the list and explanation of flow modes here:
https://github.com/softworkz/SubtitleFilteringDemos/issues/4
This is not something conc
; On Tue, Jun 3, 2025 at 1:26 AM softworkz .
> wrote:
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of Ramiro
> Polla
> > > Sent: Dienstag, 3. Juni 2025 01:22
> > > To: FFmpeg development discussions and patches
> > > Subje
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Dienstag, 3. Juni 2025 01:26
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 1/5] configure: remove build-time check for
> gzip support in zlib
>
&g
> -Original Message-
> From: ffmpeg-devel On Behalf Of Ramiro Polla
> Sent: Dienstag, 3. Juni 2025 01:22
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 1/5] configure: remove build-time check for
> gzip support in zlib
>
> Hi Jacob,
>
> On Fri, M
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Montag, 2. Juni 2025 04:39
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib directly
> instead of gzip
>
> This is a WIP patchset to
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Montag, 2. Juni 2025 12:50
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
> softworkz . (HE12025-06-02):
> > The w
at mediating (or what you call it) thats
> marth64
+1
> And the CC needs someone who can recognize defamation and document it
> accurately. Ive not seen anyone except softworkz document things as he did.
Admittedly, the motivation was high, since I've been in focus. Naturally
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Montag, 2. Juni 2025 12:50
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
> softworkz . (HE12025-06-02):
> > The w
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Montag, 2. Juni 2025 11:31
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
>
>
> > -Original Message-
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Montag, 2. Juni 2025 09:58
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
> Michael Niedermayer (HE12025-06-02):
> > Id like you to be in the next community
> -Original Message-
> From: ffmpeg-devel On Behalf Of Marton
> Balint
> Sent: Montag, 2. Juni 2025 09:41
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges
>
>
>
> On Sun, 1 Jun 2025, James Almer wrote:
>
> > On 6/1/2025 4:2
> -Original Message-
> From: ffmpeg-devel On Behalf Of Mark
> Thompson
> Sent: Samstag, 31. Mai 2025 22:26
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
Hi Mark,
Here are my answers to the remaining points:
> >> In reality, ffmpeg is often used on m
> -Original Message-
> From: ffmpeg-devel On Behalf Of Mark
> Thompson
> Sent: Samstag, 31. Mai 2025 22:26
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
Hello Mark,
(I've re-ordered some parts to unclutter the conversation)
> It does not seem unreas
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Montag, 2. Juni 2025 04:39
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib directly
> instead of gzip
>
> This is a WIP patchset to
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Montag, 2. Juni 2025 03:43
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] fftools/resman: remove unused
> includes, fix declaration
>
&g
> -Original Message-
> From: ffmpeg-devel On Behalf Of James Almer
> Sent: Montag, 2. Juni 2025 04:41
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: make
> InputFilterPriv and OutputFilterPriv private again
> I did however forget to send a
gt; On 6/1/2025 11:07 PM, softworkz . wrote:
> >
> >
> >> -Original Message-
> >> From: ffmpeg-devel On Behalf Of softworkz
> .
> >> Sent: Samstag, 31. Mai 2025 03:44
> >> To: FFmpeg development discussions and patches
> >> Subject:
m
>
> On Sat, May 31, 2025 at 12:56 AM softworkz .
> wrote:
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of Ramiro
> Polla
> > > Sent: Freitag, 30. Mai 2025 12:52
> > > To: ffmpeg-devel@ffmpeg.org
> > > Subje
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Samstag, 31. Mai 2025 03:44
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: make
> InputFilterPriv and OutputFilterPriv privat
> -Original Message-
> From: ffmpeg-devel On Behalf Of Michael
> Niedermayer
> Sent: Montag, 2. Juni 2025 03:28
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] fftools/resman: remove unused
> includes, fix declarat
An additional note:
While there are opinionated elements of course, I have tried to keep
everything factually correct in this series of messaged to the best
of my knowledge.
If somebody thinks that I would have told anything that is clearly
untrue, please let me know.
Then I will correct and
> -Original Message-
> From: ffmpeg-devel On Behalf Of Michael
> Niedermayer
> Sent: Montag, 2. Juni 2025 01:22
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
> On Sat, May 31, 2025 at 0
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Montag, 2. Juni 2025 00:08
> >>> - Why do you want to remove the ResourceManager AVClass?
> >>
> >> Because I think callers should provide their own logcontext
> >
> > Do we have any precedent cases fo
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Sonntag, 1. Juni 2025 23:46
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 5/5] fftools/Makefile: clean files from
> fftools/{graph, textformat}/
>
&g
> -Original Message-
> From: ffmpeg-devel On Behalf Of Ramiro Polla
> Sent: Sonntag, 1. Juni 2025 23:31
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 5/5] fftools/Makefile: clean files from
> fftools/{graph, textformat}/
>
> On Tue, May 27, 2025 at 3:33 AM Ramiro Po
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Sonntag, 1. Juni 2025 12:40
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 01/11] fftools/graph/graphprint: Fix races
> when initializing graphprint
Hi Andreas,
thanks for v2.
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Sonntag, 1. Juni 2025 05:27
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 01/11] fftools/graph/graphprint: Fix races when
> initializing graphprint
>
> Patches attac
> -Original Message-
> From: ffmpeg-devel On Behalf Of softworkz .
> Sent: Samstag, 31. Mai 2025 22:09
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
>
>
> > -Original Message-
>
>
> A patchset so bad, people who quit the project like Derek came back to clean
> up your mess.
>
> Kieran
For background and aftermath, please read: The "bad" Patch
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2025-May/344274.html
sw
___
ffmpe
> I really wonder how you can't be embarrassed sending what imo is the
> worst patchset in the history of the project.
> Instead of acknowledging that, it's deflecting and playing the victim
> you want to do.
>
> Kieran
For background and aftermath, please read: The "bad" Patch
https://lists.f
> -Original Message-
> From: ffmpeg-devel On Behalf Of James Almer
> Sent: Freitag, 16. Mai 2025 00:00
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/graphprint: Now, make it a
> Killer-Feature!
> >>
> >> Absolutely not, wtf. Calling an external app
05-22):
> > It's obvious basic testing was not done on this patchset seeing the scale
> > of memory leaks.
> >
> > I would like the TC to decide on reverting and proper resubmission later.
>
> For once, I agree with that assessment. I think giving softworkz
;
> Michael Niedermayer (HE12025-05-16):
> > yes if thats possible, iam not sure everyone will agree though
>
> That is possible and easy.
>
> > I think "your senior developers" is a bit provocative
>
> Maybe it is, but it plugs into a pattern of behavior by s
> -Original Message-
> From: ffmpeg-devel On Behalf Of Leo Izen
> Sent: Samstag, 31. Mai 2025 21:31
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
>
> On 5/28/25 11:24, softworkz . wrote:
> > Hello everybody,
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Mark
> Thompson
> Sent: Samstag, 31. Mai 2025 18:21
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
> On 31/05/2025 12:44, softworkz . wrote:
> >> -Origin
1 - 100 of 1022 matches
Mail list logo
