Jan 1, 2021, 01:35 by andreas.rheinha...@gmail.com:
> Signed-off-by: Andreas Rheinhardt
> ---
> Found a few more, in particular the hw_configs lists.
>
> fftools/ffmpeg_opt.c| 86 ++---
> libavcodec/aacenctab.c | 4 +-
> libavcodec/aa
Signed-off-by: Andreas Rheinhardt
---
Found a few more, in particular the hw_configs lists.
fftools/ffmpeg_opt.c| 86 ++---
libavcodec/aacenctab.c | 4 +-
libavcodec/aacenctab.h | 4 +-
libavcodec/av1dec.c
On 31/12/2020 20:15, Jim DeLaHunt wrote:
> One of the places where FFmpeg's inconsistent encoding caused me a
> problem was when I was operating on a Quicktime video. FFmpeg (or
> perhaps FFprobe) printed a 4-byte Quicktime tag literally to stdout. The
> tag's byte sequence was not valid UTF-8.
On 31/12/2020 13:36, Nicolas George wrote:
> This mail is about a project I have to make FFmpeg's API and
> infrastructure more convenient. For a common introduction, see this thread:
> https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
>
> The way we currently report errors is fi
On Thu Dec 31 15:35:38 EET 2020, Nicolas George wrote:
…For each simple type, including enumerations like AVColorRange and flat
structures like AVReplayGain, have a set of standardized functions for
common operations, including probably:
- printing;
- serializing to string;
- parsing from stri
>
> I want to replace it with an event loop. That means that instead of reading
> on a protocol context, we would register a callback for when data is
> available, and then let the loop run.
>
This would be a good idea in general and bring FFmpeg into the early 21st
century.
As I understand it the
Andreas Rheinhardt:
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/opustab.c | 12 ++--
> libavcodec/opustab.h | 1 -
> 2 files changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/libavcodec/opustab.c b/libavcodec/opustab.c
> index 64070f8299..7276dad793 100644
> --- a/lib
Will apply soon.
___
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".
probably ok
On Thu, Dec 31, 2020 at 12:36 AM Andreas Rheinhardt <
andreas.rheinha...@gmail.com> wrote:
> It already uses ff_thread_once() to initialize its static data.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/qdmc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libav
Signed-off-by: Paul B Mahol
---
TODO: add working >8 depth support
---
doc/filters.texi | 56 ++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_estdif.c | 372 +++
4 files changed, 430 insertions(+)
create mode
Nicolas George (12020-12-31):
> Hi.
>
> I would like to summarize the projects I have had in mind for FFmpeg for
> some time. I have already evoked some of them here in more or less details.
>
> These projects are not directly related to FFmpeg's work of codecs and
> formats, they are about FFmpe
This mail is about a project I have to make FFmpeg's API and
infrastructure more convenient. For a common introduction, see this thread:
https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
The API to access our protocols, in particular network protocols, is copied
from the Unix fil
This mail is about a project I have to make FFmpeg's API and
infrastructure more convenient. For a common introduction, see this thread:
https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
The way we currently report errors is fine for command-line tools running in
a terminal, but
This mail is about a project I have to make FFmpeg's API and
infrastructure more convenient. For a common introduction, see this thread:
https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
For each simple type, including enumerations like AVColorRange and flat
structures like AVRep
This mail is about a project I have to make FFmpeg's API and
infrastructure more convenient. For a common introduction, see this thread:
https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
int av_foo_to_string(char *buf, size_t buf_size, AVFoo *foo);
int av_bar_to_string(char *buf,
This mail is about a project I have to make FFmpeg's API and
infrastructure more convenient. For a common introduction, see this thread:
https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274167.html
Global mutable state has annoyed developers for a long time. Log callbacks
and flags, malloc
Hi.
I would like to summarize the projects I have had in mind for FFmpeg for
some time. I have already evoked some of them here in more or less details.
These projects are not directly related to FFmpeg's work of codecs and
formats, they are about FFmpeg's infrastructure and API, to make the actu
> On Dec 31, 2020, at 6:51 PM, Marton Balint wrote:
>
>
>
> On Thu, 31 Dec 2020, Zhao Zhili wrote:
>
>> Rounding min_ts towards +infinity and max_ts towards -infinity can
>> make ts out of the [min_ts, max_ts] range, and then leads to seek
>> failure. For example,
>
> I think this is intent
On Thu, 31 Dec 2020, Zhao Zhili wrote:
Rounding min_ts towards +infinity and max_ts towards -infinity can
make ts out of the [min_ts, max_ts] range, and then leads to seek
failure. For example,
I think this is intentional to adhere to the docs of the function:
"Seeking will be done so that
Rounding min_ts towards +infinity and max_ts towards -infinity can
make ts out of the [min_ts, max_ts] range, and then leads to seek
failure. For example,
max_ts = ts = -25057
time_base = (num = 1, den = 14112000)
After rescale, ts = -353604, and max_ts = -353605.
---
libavformat/utils.c | 4 ++-
20 matches
Mail list logo
