v1 -> v2: Refactor using GetByteContext; Fix compile error.
v2 -> v3: Remove debug statement.
v3 -> v4: Squash commits
v4 -> v5: Improve portability; Cosmetic changes.
This patch adds an MPEG Media Transport Protocol (MMTP) parser, as defined in
ISO/IEC 23008-1, and an MMT protocol over TLV
If nobody has further comments, I'm planning to push the set tomorrow.
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
Approved
___
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".
From: Niklas Haas
In some circumstances, libplacebo will clear the background as a result
of cropping/padding. Currently, this uses the hard-coded default fill
color of black. This option makes this behavior configurable.
---
doc/filters.texi| 6 ++
libavfilter/vf_libplacebo.c
From: Niklas Haas
Motivated by a desire to use vf_libplacebo as a GPU-accelerated
cropping/padding/zooming filter. This commit adds support for setting
the `input/target.crop` fields as dynamic expressions.
Re-use the same generic variables available to other scale and crop type
filters, and
From: Niklas Haas
This has not been the case since c0b93c4f8+48c385fb4c.
---
doc/filters.texi | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index 2d49f93b9e2..9ffa9dfe22f 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -15976,8
---
libavfilter/vf_tpad.c | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git a/libavfilter/vf_tpad.c b/libavfilter/vf_tpad.c
index f0c065f0c3..88c3c99de4 100644
--- a/libavfilter/vf_tpad.c
+++ b/libavfilter/vf_tpad.c
@@ -27,6 +27,12 @@
#include
When no drawing is to be performed, tpad can work fine with
hardware frames, so advertise this in the query_formats
callback and ensure the drawing context is never initialised
when just cloning frames.
---
libavfilter/vf_tpad.c | 14 +++---
1 file changed, 11 insertions(+), 3
On Mon, May 01, 2023 at 09:00:35AM +0200, Thilo Borgmann wrote:
> Am 01.05.23 um 02:40 schrieb Michael Niedermayer:
> > There are some problems with the ffis webpage "Unable to connect to SQL
> > server"
> > I tried to report this but it seems my email was not achieving that.
> > It may be safer
Will push the set tomorrow if nobody has further objections.
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
On Mon, 1 May 2023, at 08:57, Leo Izen wrote:
> On 4/29/23 14:33, Nicolas George wrote:
>> Anton Khirnov (12023-04-29):
>>> libavfilter is a C library with a C API. Any structured output from
>>> filters should be in the form of a C object, typically a struct. I do
>>> not see why are you so in
---
doc/examples/qsv_transcode.c | 2 +-
libavcodec/libaomenc.c | 2 +-
libavcodec/libkvazaar.c| 2 +-
libavcodec/libsvtav1.c | 2 +-
libavcodec/libvpxenc.c | 2 +-
libavcodec/libx264.c | 2 +-
libavcodec/libx265.c
This new API allows to remove an entry and obtain ownership of the
key/value that was associated with the removed entry.
---
doc/APIchanges | 4
libavutil/dict.c | 27 +++
libavutil/dict.h | 20
libavutil/tests/dict.c | 34
This is a well-defined way to "steal" the value of the dict entry.
---
libavformat/tee.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/libavformat/tee.c b/libavformat/tee.c
index cb555f52fd..70f3f2eb29 100644
--- a/libavformat/tee.c
+++ b/libavformat/tee.c
@@ -157,6
On Sat, Apr 29, 2023 at 8:29 PM Kieran Kunhya wrote:
> On Sat, 29 Apr 2023 at 05:07, Derek Buitenhuis >
> wrote:
>
> > On 4/29/2023 10:41 AM, Anton Khirnov wrote:
> > > ffprobe:
> > > * is not one of the libraries, but rather their caller
> > > * we are not in business of providing random
Am 01.05.23 um 02:40 schrieb Michael Niedermayer:
There are some problems with the ffis webpage "Unable to connect to SQL server"
I tried to report this but it seems my email was not achieving that.
It may be safer to remove the link to ffis until we understand what exactly
is going on on the
Quoting SuperFashi (2023-05-01 03:10:36)
> Thanks for the feedback. I thought across libraries meant across different
> muxers/demuxers. In which case, is there any naming scheme for functions
> that are only used within lavf? Can i just remove the avpriv_ prefix?
tl;dr: use ff_ for non-static
Hi.
Three years ago, I shared some brief thoughts about embedding the
documentation in the libraries. For example, that would allow GUI
applications to open help dialogs about specific options.
To see what it would need, I wrote the following header. I did not work
any further, because
Attached patch.
From 391216f55c8e226974fb2e8a0e725b254811c2b7 Mon Sep 17 00:00:00 2001
From: Paul B Mahol
Date: Sun, 30 Apr 2023 17:06:00 +0200
Subject: [PATCH] avfilter: add Affine Projection adaptive audio filter
Signed-off-by: Paul B Mahol
---
libavfilter/Makefile | 1 +
On 4/29/23 14:33, Nicolas George wrote:
Anton Khirnov (12023-04-29):
libavfilter is a C library with a C API. Any structured output from
filters should be in the form of a C object, typically a struct. I do
not see why are you so in love with strings, they make for terrible
APIs.
Yes,
Leo Izen (12023-05-01):
> > Yes, strings are a terrible API, but our project is not only a set of
> > libraries, it is also a set of command-line tools, and command-line
> > tools work with strings and nothing else.
> This is a good argument for putting the code in fftools/ and not libavutil,
>
On Mon, May 1, 2023 at 12:13 PM Nicolas George wrote:
> Hi.
>
> Three years ago, I shared some brief thoughts about embedding the
> documentation in the libraries. For example, that would allow GUI
> applications to open help dialogs about specific options.
>
> To see what it would need, I wrote
On 01.05.2023 12:13, Nicolas George wrote:
Hi.
Three years ago, I shared some brief thoughts about embedding the
documentation in the libraries. For example, that would allow GUI
applications to open help dialogs about specific options.
To see what it would need, I wrote the following header.
Michael Niedermayer (12023-04-30):
> There are many projects which use libavcodec, format, filter
> Human users use these projects
>
> If the standarization is at a C struct level only then the human interface
> for each application can be different.
> Thats fine if the 2 cases use fundamentally
I'm using setpts to generate timelapses with slowdowns in the middle.
Using setpts filter requires complicated expr to handle intervals. This
patch allows commands to change expr and also adds a constant that
provides time of last command applications to allow specifying gradual
changes using
25 matches
Mail list logo
