This commit adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
Signed-off-by: softworkz
(cherry picked from commit 960c82cede25c21bcea478b26309691fdc7fcec7)
(cherry picked from commit 0851f36f5ecead61317a1ce631facdacae76d886)
---
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 7643dd8396..483a50d8e9 100644
--- a/doc/fftools-common-opts.texi
+++ b/doc/fftools-common-opts.texi
@@ -198,6 +198,10
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Monday, 9 August 2021 03:11
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v3 1/2] Add option to log timing
>
> Soft Works:
> > This commit adds t
Signed-off-by: softworkz
---
v2: split commits differently, fix AVBPrint finalization
doc/APIchanges | 3 +++
libavutil/log.c | 33 ++---
libavutil/log.h | 10 ++
libavutil/version.h | 2 +-
4 files changed, 44 insertions(+), 4 deletions(-)
diff
This commit adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
Signed-off-by: softworkz
---
doc/fftools-common-opts.texi | 4
fftools/cmdutils.c | 14 ++
fftools/ffmpeg.c | 6 +-
3 fi
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Xiang, Haihao
> Sent: Monday, 9 August 2021 05:00
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/qsvence: Use QSV encoder
> defaults as ffmpeg defaults
>
> On Sat, 2021
Signed-off-by: softworkz
---
libavcodec/qsvenc.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/qsvenc.h b/libavcodec/qsvenc.h
index fc8a14143e..58984f996f 100644
--- a/libavcodec/qsvenc.h
+++ b/libavcodec/qsvenc.h
@@ -76,8 +76,8 @@
#define QSV_COMMON_OPTS \
glines with current time or current date+time
>
> Soft Works (12021-08-09):
> > Signed-off-by: softworkz
> > ---
> > v2: split commits differently, fix AVBPrint finalization
> > doc/APIchanges | 3 +++
> > libavutil/log.c | 33 +++
ons
>
> On Sat, 2021-08-07 at 01:46 +, Soft Works wrote:
[...]
> > if (ret == 0) {
> > dst_ctx->internal->source_device =
> > av_buffer_ref(src_ref);
> > +tmp_ctx->internal->derived_device =
> >
ix loglines with current time or current date+time
>
> Soft Works (12021-08-10):
> > I'm not sure whether it's OK to strip all content when there's nothing
> > new inside..?
>
> I do not understand what you are talking abou
to prefix loglines with current time or current date+time)
>
> Soft Works (12021-08-10):
> > I meant the e-mail body of the previous conversation.
>
> Well, it is my mail, I put what I want in it, and you do what you want with
> yours.
>
> But ask yourself: which one
The test /libavutil/tests/hwdevice checks that when deriving a device
from a source device and then deriving back to the type of the source
device, the result is matching the original source device, i.e. the
derivation mechanism doesn't create a new device in this case.
Previously, this test was u
Signed-off-by: softworkz
---
doc/APIchanges | 3 +++
libavutil/log.c | 35 ++-
libavutil/log.h | 10 ++
libavutil/version.h | 2 +-
4 files changed, 44 insertions(+), 6 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index 6eefc7fc
This commit adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
Signed-off-by: softworkz
---
doc/fftools-common-opts.texi | 4
fftools/cmdutils.c | 21 +
fftools/ffmpeg.c | 6 +
loglines with current time or current date+time)
>
> On Tue, Aug 10, 2021 at 09:47:31AM +, Soft Works wrote:
> >
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Nicolas George
> > > Sent: Tuesday, 10 Aug
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Tuesday, 10 August 2021 16:28
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] Mail quoting (was: libavutil/log: Add
> capability to prefix loglines with current time or curren
Hi,
A while ago there was a discussion about moving forward and
migrating the ffmpeg development process from the mailing list to
another platform (like GitLab).
That discussion had died without further results and an important
takeaway for me was that there are just too many that love this way
or current date+time
>
> Soft Works:
> > Signed-off-by: softworkz
> > ---
> > doc/APIchanges | 3 +++
> > libavutil/log.c | 35 ++-
> > libavutil/log.h | 10 ++
> > libavutil/version.h | 2 +-
> > 4 f
Signed-off-by: softworkz
---
doc/APIchanges | 3 +++
libavutil/log.c | 33 +
libavutil/log.h | 10 ++
libavutil/version.h | 2 +-
4 files changed, 43 insertions(+), 5 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index 6eefc7fc33
This commit adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
Signed-off-by: softworkz
---
doc/fftools-common-opts.texi | 4
fftools/cmdutils.c | 21 +
fftools/ffmpeg.c | 6 +
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Lynne
> Sent: Tuesday, 10 August 2021 19:07
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v6 2/2] fftools: Add option to log
> timing
>
> 10 Aug 2021, 18:12 by softwo...@
Signed-off-by: softworkz
---
doc/APIchanges | 3 +++
libavutil/log.c | 33 +
libavutil/log.h | 10 ++
libavutil/version.h | 2 +-
4 files changed, 43 insertions(+), 5 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index 6eefc7fc33
This commit adds two logging flags: 'time' and 'datetime'.
Usage:
ffmpeg -loglevel +time
or
ffmpeg -loglevel +datetime
Signed-off-by: softworkz
---
doc/fftools-common-opts.texi | 4
fftools/cmdutils.c | 21 +
fftools/ffmpeg.c | 6 +-
3 fil
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Tuesday, 10 August 2021 20:49
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v7 2/2] fftools: Add option to log
> timing
>
> Soft Works:
> > T
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Tuesday, 10 August 2021 21:09
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v7 2/2] fftools: Add option to log
> timing
>
> Soft Works:
> &g
gration
> with GitHub
>
> August 10, 2021 10:37 AM, "Soft Works" wrote:
>
[..]
> > Just recently, I discovered a very interesting project:
> > https://gitgitgadget.github.io
> >
> > This is all about the development of Git itself, which is done via
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Haihao Xiang
> Sent: Wednesday, 11 August 2021 08:02
> To: ffmpeg-devel@ffmpeg.org
> Cc: Haihao Xiang
> Subject: [FFmpeg-devel] [PATCH v3 1/2] qsvdec: add support for
> HW_DEVICE_CTX method
>
> This allows user set hw_device_ctx
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Tuesday, 10 August 2021 11:53
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v2] avutils/hwcontext: When deriving a
> hwdevice, search for existing device in both directio
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Haihao Xiang
> Sent: Wednesday, 11 August 2021 08:44
> To: ffmpeg-devel@ffmpeg.org
> Cc: Haihao Xiang
> Subject: [FFmpeg-devel] [PATCH] ffmpeg_hw: Don't ignore key
> parameters when initializing a hw device
>
> Currently user ma
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Haihao Xiang
> Sent: Thursday, 12 August 2021 04:34
> To: ffmpeg-devel@ffmpeg.org
> Cc: Haihao Xiang
> Subject: [FFmpeg-devel] [PATCH v2] lavc/qsvenc: allows the SDK
> runtime to choose LowPower/non-LowPower modes
>
> The SDK su
t; On Thu, 2021-08-12 at 03:22 +, Soft Works wrote:
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Haihao Xiang
> > > Sent: Thursday, 12 August 2021 04:34
> > > To: ffmpeg-devel@ffmpeg.org
> > > Cc: H
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 12 August 2021 10:51
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHub
> TL;DR: Do not make
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Kieran Kunhya
> Sent: Thursday, 12 August 2021 12:19
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHub
[..]
> It is practicall
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 12 August 2021 14:18
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHu
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 12 August 2021 14:18
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHub
> If you want to inte
Hi,
I have a question: Is there a specific reason why AVFrame does not have
a property indicating the AVMediaType?
Instead, the type is mostly tried to be inferred from other properties, e.g.
AVMEDIA_TYPE_VIDEO when width and height are specified or channel format
in case of audio.
Though I don
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Steven Liu
> Sent: Friday, 13 August 2021 05:01
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Steven Liu
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHub
>
>
> Hi
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Friday, 13 August 2021 11:54
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHub
>
Hi Nicholas,
Thanks
tHub
>
> On Fri, Aug 13, 2021 at 03:14:36PM +, Soft Works wrote:
> [...]
> > > You do not need anybody's permission either to set up a gateway
> that
> > > will re-post GitHub's PR and comments to the mailing-list and
> > > reciprocally
> >
> -Original Message-
> From: ffmpeg-devel On Behalf Of Ronald S.
> Bultje
> Sent: Saturday, 14 August 2021 02:43
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
> GitHub
>
> Hi,
>
> On Thu, Aug 12, 2021 at 4:51
> -Original Message-
> From: ffmpeg-devel On Behalf Of Lynne
> Sent: Saturday, 14 August 2021 03:08
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
> GitHub
>
> The situation is far from perfect. In my opini
> -Original Message-
> From: ffmpeg-devel On Behalf Of Ronald S.
> Bultje
> Sent: Saturday, 14 August 2021 19:32
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
> GitHub
>
> I'm not sure I support it, I'd h
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Saturday, 14 August 2021 08:31
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
> GitHub
>
> Soft W
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft Works
> Sent: Sunday, 15 August 2021 04:12
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
> GitHub
>
>
> Speaking of
> rhetoric.
> >> I agree.
> >
> > Good thing it is not what I wrote, then. I am a little disappointed that
> > you would make a judgement like that without reading carefully and
> > realizing that Soft Works has turned my position on its head.
>
> The rea
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andriy
> Gelman
> Sent: Saturday, 14 August 2021 14:48
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
> GitHub
>
> On Fri
Hi,
some of you might remember that I had warmed-up the discusion about
improving support for subtitle handling in ffmpeg sometime last year.
A lot of different voices were heard and the unfinished work from
Matthieau Buron has been in focus. My takeaway was that it's a pretty
difficult subjec
Signed-off-by: softworkz
---
libavutil/frame.c | 74 -
libavutil/frame.h | 39 ++--
libavutil/version.h | 2 +-
3 files changed, 97 insertions(+), 18 deletions(-)
diff --git a/libavutil/frame.c b/libavutil/frame.c
index b0ceaf7
Signed-off-by: softworkz
---
libavfilter/Makefile| 1 +
libavfilter/internal.h | 8 ++
libavfilter/subtitles.c | 61 +
libavfilter/subtitles.h | 42
4 files changed, 112 insertions(+)
create mode 100644 libavfilter/s
Signed-off-by: softworkz
---
libavfilter/avfilter.c | 8 +---
libavfilter/avfiltergraph.c | 5 +
libavfilter/formats.c | 11 +++
3 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/libavfilter/avfilter.c b/libavfilter/avfilter.c
index ea22b247de..5505c3467
Signed-off-by: softworkz
---
libavfilter/Makefile |1 +
libavfilter/allfilters.c |1 +
libavfilter/vf_overlay_subs.c | 1173 +
libavfilter/vf_overlay_subs.h | 88 +++
4 files changed, 1263 insertions(+)
create mode 100644 libavfilter/vf_ove
Signed-off-by: softworkz
---
libavfilter/Makefile| 1 +
libavfilter/allfilters.c| 1 +
libavfilter/svf_sub2video.c | 260
3 files changed, 262 insertions(+)
create mode 100644 libavfilter/svf_sub2video.c
diff --git a/libavfilter/Makefile b/li
Signed-off-by: softworkz
---
configure| 2 +-
libavfilter/allfilters.c | 10 ---
libavfilter/buffersink.c | 65
libavfilter/buffersink.h | 15 ++
libavfilter/buffersrc.c | 65
libavfilt
Signed-off-by: softworkz
---
libavfilter/Makefile | 3 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_sleet.c | 209 +++
3 files changed, 213 insertions(+)
create mode 100644 libavfilter/sf_sleet.c
diff --git a/libavfilter/Makefile b/libavfilter/M
Signed-off-by: softworkz
---
fftools/ffmpeg.c| 324 +++-
fftools/ffmpeg.h| 7 +-
fftools/ffmpeg_filter.c | 198 +---
fftools/ffmpeg_hw.c | 2 +-
fftools/ffmpeg_opt.c| 3 +-
5 files changed, 330 insertions(+), 20
Signed-off-by: softworkz
---
tests/ref/fate/filter-overlay-dvdsub-2397 | 179 +++---
tests/ref/fate/sub-dvb| 162 +++-
tests/ref/fate/sub2video | 49 +++---
tests/ref/fate/sub2video_basic| 178 +++--
irections
>
> On Fri, 2021-08-13 at 06:29 +, Xiang, Haihao wrote:
> > On Tue, 2021-08-10 at 09:52 +, Soft Works wrote:
> > > The test /libavutil/tests/hwdevice checks that when deriving a device
> > > from a source device and then deriving back to the type of
> -Original Message-
> From: ffmpeg-devel On Behalf Of Paul B
> Mahol
> Sent: Thursday, 19 August 2021 09:52
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 4/9] avfilter/overlay_subs: Add
> overlay_subs filter
>
> Copy pasted code, so big NACK.
> -Original Message-
> From: ffmpeg-devel On Behalf Of Paul B
> Mahol
> Sent: Thursday, 19 August 2021 09:58
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 4/9] avfilter/overlay_subs: Add
> overlay_subs filter
>
> Reuse old code and just put new/
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft Works
> Sent: Thursday, 19 August 2021 09:43
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 1/9] lavu/frame: avframe add type property
>
> Signed-off-by: softworkz
> ---
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 10:28
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 4/9] avfilter/overlay_subs: Add
> overlay_subs filter
>
&
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 10:30
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/9] avfilter/subtitles: Add subtitles.c
>
> Soft Works (1202
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 11:03
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 4/9] avfilter/overlay_subs: Add
> overlay_subs filter
>
&
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 11:08
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/9] avfilter/subtitles: Add subtitles.c
>
> Soft Works (12
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 11:32
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/9] avfilter/subtitles: Add subtitles.c
>
> Soft Works (1
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 11:35
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/9] avfilter/subtitles: Add subtitles.c
>
> Soft Work
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 15:05
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/9] avfilter/subtitles: Add subtitles.c
>
> Soft Works (12
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Thursday, 19 August 2021 15:24
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 4/9] avfilter/overlay_subs: Add
> overlay_subs filter
>
&
> -Original Message-
> From: ffmpeg-devel On Behalf Of Xiang,
> Haihao
> Sent: Monday, 23 August 2021 06:29
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/10] make QSV works with Intel's
> oneVPL
>
> On Mon, 2021-08-16 at 15:33 +0800, Haihao Xiang wrote:
> > T
> -Original Message-
> From: ffmpeg-devel On Behalf Of Nicolas
> George
> Sent: Monday, 23 August 2021 11:45
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 2/2] fftools: add -lavfi_dump option
>
> Signed-off-by: Nicolas George
> ---
> doc/ffmpeg.texi | 4
The current message "Your platform doesn't suppport
hardware accelerated AV1 decoding." is inaccurate and
misleading. When a user doesn't specify a hwcaccel,
this doesn't tell anything about what is actually
supported on that platform.
Signed-off-by: softworkz
---
libavcodec/av1dec.c | 4 ++--
1
put
>
> Hi,
>
> On Mon, Aug 23, 2021 at 9:39 PM Soft Works
> wrote:
>
> > The current message "Your platform doesn't suppport
> > hardware accelerated AV1 decoding." is inaccurate and
> > misleading. When a user doesn't specify a hwcac
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Wang, Fei W
> Sent: Tuesday, 24 August 2021 07:32
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec: Adjust incorrect
> error output
>
> On Tue, 2021-08-24 at 02
This is a more complete and more flexible alternative to the recently submitted
patch "fftools: add -lavfi_dump option"
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
I'm tagging this patch as 'RFC'. There's no need to tell that this is
duplicating
co
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Moritz Barsnick
> Sent: Thursday, 26 August 2021 09:25
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/truemotion1: Cleanup
> prediction code in truemotion1_decode_
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > This is a more complete and more flexible alternative to the
> recently submitted
> > patch "fftools: add -lavfi_dump option"
> >
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/2021
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > The purpose is to get a precise and detailed view of the
> filtergraphs
> > at runtime including all connections with their negotiated formats
> and
> > media types.
>
> I asked the purpose,
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > Does that answer your question?
>
> Yes. It is almost exactly what I had guessed. And therefore my answer
> is
> what I expected it do be: that does not justify thousands, or even
> hundreds, of li
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > Does that answer your question?
>
> Yes. It is almost exactly what I had guessed. And therefore my answer
> is
> what I expected it do be: that does not justify thousands, or even
> hundreds, of
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > To be clear: I didn't submit this to end up in a LOC count
> discussion.
>
> Good.
>
> > My point is that there's much more relevant and important
> information
> > that a fil
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Monday, 23 August 2021 11:45
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 1/2] lavfi/graphdump: add plain
> listing output
>
> Signed-off-by: Nicolas George
> ---
> libavfilter/avfilter.
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > Does that answer your question?
>
> Yes. It is almost exactly what I had guessed. And therefore my answer
> is
> what I expected it do be: that does not justify thousands, or even
> hundreds, of lines
ltergraph information to file or stdout
>
> Soft Works (12021-08-26):
> > - Instead you criticized my patch for its LOC count, even though
> that is
> > just made up from the output writers code duplication...
>
> You are mistaken here too. Unlike what you seem to thi
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Saturday, 7 August 2021 07:02
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v2] DXVA2: Add ARGB format
>
> Required for uploading frames with alpha for qsv_overlay
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Paul B Mahol
> Sent: Thursday, 26 August 2021 09:36
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to file
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 19 August 2021 17:31
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 3/3] lavfi/formats: document the
> negotiation process
>
> Signed-off-by: Nicolas George
> ---
> libavfilter/f
This is a more complete and more flexible alternative to the recently submitted
patch "fftools: add -lavfi_dump option"
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
I'm tagging this patch as 'RFC'. There's no need to tell that this is
duplicating
code
This is a more complete and more flexible alternative to the recently submitted
patch "fftools: add -lavfi_dump option"
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
I'm tagging this patch as 'RFC'. There's no need to tell that this is
duplicating
code
put
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> Soft
> > Works
> > Sent: Thursday, August 26, 2021 5:12 AM
> > To: FFmpeg development discussions and patches de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Friday, 27 August 2021 05:14
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v3] fftools: Add option for writing
> detailed filtergraph information to file or stdout
>
&
t;
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> Soft
> > Works
> > Sent: Friday, August 27, 2021 12:18 PM
> > To: FFmpeg development discussions and patches de...@ffmpeg.org>
> > Subject: Re:
> -Original Message-
> From: ffmpeg-devel On Behalf Of Fei
> Wang
> Sent: Friday, 27 August 2021 13:54
> To: ffmpeg-devel@ffmpeg.org
> Cc: Fei Wang
> Subject: [FFmpeg-devel] [PATCH v1] avcodec/av1dec: check if hwaccel
> is specificed
>
> Since av1 decoder is only available for hw acce
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Friday, 27 August 2021 09:27
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 3/3] lavfi/formats: document the
> negotiation
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Xiang, Haihao
> Sent: Monday, 30 August 2021 06:20
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v5 00/20] clean-up QSV filters
>
> On Thu, 2021-08-05 at 16:21 +, Soft Works wr
v2 Update:
- Implemented Andreas' suggestions
- overlay_subs filter:
- removed duplicated code
- implemented direct (no pre-conversion) blending of graphical
subtitle rects
- Supported input formats:
- all packed RGB formats (with and without alpha)
- yuv420p, yuv422p, yuv444
Signed-off-by: softworkz
---
v2 Update:
- Implemented Andreas' suggestions
- overlay_subs filter:
- removed duplicated code
- implemented direct (no pre-conversion) blending of graphical
subtitle rects
- Supported input formats:
- all packed RGB formats (with and without alpha)
Signed-off-by: softworkz
---
v2 Update:
- Implemented Andreas' suggestions
- overlay_subs filter:
- removed duplicated code
- implemented direct (no pre-conversion) blending of graphical
subtitle rects
- Supported input formats:
- all packed RGB formats (with and without alpha)
Signed-off-by: softworkz
---
v2 Update:
- Implemented Andreas' suggestions
- overlay_subs filter:
- removed duplicated code
- implemented direct (no pre-conversion) blending of graphical
subtitle rects
- Supported input formats:
- all packed RGB formats (with and without alpha)
Signed-off-by: softworkz
---
v2 Update:
- Implemented Andreas' suggestions
- overlay_subs filter:
- removed duplicated code
- implemented direct (no pre-conversion) blending of graphical
subtitle rects
- Supported input formats:
- all packed RGB formats (with and without alpha)
Signed-off-by: softworkz
---
v2 Update:
- Implemented Andreas' suggestions
- overlay_subs filter:
- removed duplicated code
- implemented direct (no pre-conversion) blending of graphical
subtitle rects
- Supported input formats:
- all packed RGB formats (with and without alpha)
901 - 1000 of 1691 matches
Mail list logo