> 2022年1月29日 上午4:23，Gustav Grusell 写道：
>
> Before, seeking in hls streams would always seek to the next keyframe
> after the given timestamp. With this fix, if seeking in videostream and
> AVSEEK_FLAG_BACKWARD is set, seeking will be to the first keyframe of
> the segment containing the given t
On 2022-02-02 10:55 am, Gyan Doshi wrote:
Plan to push tomorrow.
Pushed as e1a14479a81f5366b95df543992a7fe637cf2dde
Gyan
On 2022-01-31 11:11 am, Gyan Doshi wrote:
At present, side data printing forces display for all levels i.e.
stream, packets and frames. This can bloat output and also
On Thu, 3 Feb 2022, Kacper Michajlow wrote:
On Wed, 26 Jan 2022 at 15:00, Martin Storsjö wrote:
Hi,
On Sat, 22 Jan 2022, Kacper Michajłow wrote:
LLVM tools print installation path upon execution. If one uses LLVM
tools bundled with Microsoft Visual Studio installation, they would be
incorr
On Fri, 21 Jan 2022, Andreas Rheinhardt wrote:
Interesting: There is indeed a delay at the start (720 samples in a
quick test) compared to the native AAC decoder.
Furthermore, the current code is buggy, as it believes that
avcodec->time_base to be the time_base of the returned AVFrames (it is
in
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö wrote:
>
> On Thu, 3 Feb 2022, Kacper Michajlow wrote:
>
> > On Wed, 26 Jan 2022 at 15:00, Martin Storsjö wrote:
> >>
> >> Hi,
> >>
> >> On Sat, 22 Jan 2022, Kacper Michajłow wrote:
> >>
> >>> LLVM tools print installation path upon execution. If one
On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö
wrote:
On Thu, 3 Feb 2022, Kacper Michajlow wrote:
On Wed, 26 Jan 2022 at 15:00, Martin Storsjö
wrote:
Hi,
On Sat, 22 Jan 2022, Kacper Michajłow wrote:
LLVM tools print installation path up
On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö
wrote:
On Thu, 3 Feb 2022, Kacper Michajlow wrote:
On Wed, 26 Jan 2022 at 15:00, Martin Storsjö
wrote:
Hi,
On Sat, 22 Jan 2022, Kacper Michajłow wrote:
LLVM tools print installation path up
On Thu, 3 Feb 2022, Marvin Scholz wrote:
On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö
wrote:
I remember that there has been some variance throughout the versions
for
exactly what MSVC prints as the identification thoughout the
versions,
On 3 Feb 2022, at 13:33, Martin Storsjö wrote:
On Thu, 3 Feb 2022, Marvin Scholz wrote:
On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö
wrote:
I remember that there has been some variance throughout the
versions for
exactly what MSVC pri
On Thu, 3 Feb 2022, Marvin Scholz wrote:
On 3 Feb 2022, at 13:33, Martin Storsjö wrote:
On Thu, 3 Feb 2022, Marvin Scholz wrote:
On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö
wrote:
I remember that there has been some variance throughou
Thanks: Rafal Dabrowa
---
libavcodec/aarch64/Makefile |1 +
libavcodec/aarch64/hevcdsp_init_aarch64.c | 67 +
libavcodec/aarch64/hevcdsp_qpel_neon.S| 2799 +
3 files changed, 2867 insertions(+)
create mode 100644 libavcodec/aarch64/hevcdsp_qpel_neon.S
Thanks: Rafal Dabrowa
---
libavcodec/aarch64/Makefile |3 +-
libavcodec/aarch64/hevcdsp_epel_neon.S| 2501 +
libavcodec/aarch64/hevcdsp_init_aarch64.c | 52 +
3 files changed, 2555 insertions(+), 1 deletion(-)
create mode 100644 libavcodec/aarch64/hevc
Is this being reviewed?
št 20. 1. 2022 o 12:38 David Lacko napísal(a):
> Adds command 'delays' to the adelay filter.
> This command accepts same values as the option with one difference, to
> apply
> delay to all channels prefix 'all:' to the argument is accepted.
>
> Signed-off-by: David Lacko
On Mon, Jan 10, 2022 at 03:58:33PM +0100, Alan Kelly wrote:
> Make the code more readable, follow the style guide and propagate memory
> allocation errors.
Cosmetics and bugfixes should not be in the same patch
> ---
> libswscale/swscale_internal.h | 2 +-
> libswscale/utils.c| 68
On 2/3/2022 1:26 AM, Aman Karmani wrote:
> The size part of the range header is optional, and can be '*' as well.
>
> See also
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20211005233244.37582-1-ffm...@tmm1.net/
Isn't this an orthogonal problem to what this patch is changing?
- Derek
On Wed, Feb 02, 2022 at 03:23:34PM +0100, Mark Gaiser wrote:
> On Wed, Feb 2, 2022 at 2:29 PM Michael Niedermayer
> wrote:
>
> > On Tue, Feb 01, 2022 at 10:58:30PM +0100, Mark Gaiser wrote:
[...]
> >
> >
> > > +AVClass *class;
> > > +URLContext *inner;
> > > +char *gateway;
> > > +} C
On 3 Feb 2022, at 13:47, Martin Storsjö wrote:
On Thu, 3 Feb 2022, Marvin Scholz wrote:
On 3 Feb 2022, at 13:33, Martin Storsjö wrote:
On Thu, 3 Feb 2022, Marvin Scholz wrote:
On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö
wrote:
I r
Hi,
This patch series adds support for IPFS.
V3:
- A lot of style changes
- Made url checks a lot more strict
- av_asprintf leak fixes
- So many changes that a diff to v2 is again not sensible.
V2:
- Squashed and changed so much that a diff to v1 was not sensible.
The following is a short summary
This patch adds support for:
- ffplay ipfs://
- ffplay ipns://
IPFS data can be played from so called "ipfs gateways".
A gateway is essentially a webserver that gives access to the
distributed IPFS network.
This protocol support (ipfs and ipns) therefore translates
ipfs:// and ipns:// to a http:/
Ignore this one, the title went wrong.
On Thu, Feb 3, 2022 at 6:26 PM Mark Gaiser wrote:
> Hi,
>
> This patch series adds support for IPFS.
> V3:
> - A lot of style changes
> - Made url checks a lot more strict
> - av_asprintf leak fixes
> - So many changes that a diff to v2 is again not sensibl
Ignore this one, the title went wrong.
On Thu, Feb 3, 2022 at 6:26 PM Mark Gaiser wrote:
> This patch adds support for:
> - ffplay ipfs://
> - ffplay ipns://
>
> IPFS data can be played from so called "ipfs gateways".
> A gateway is essentially a webserver that gives access to the
> distributed
Hi,
This patch series adds support for IPFS.
V3 (V4):
- V4: title issue from V3..
- A lot of style changes
- Made url checks a lot more strict
- av_asprintf leak fixes
- So many changes that a diff to v2 is again not sensible.
V2:
- Squashed and changed so much that a diff to v1 was not sensible.
This patch adds support for:
- ffplay ipfs://
- ffplay ipns://
IPFS data can be played from so called "ipfs gateways".
A gateway is essentially a webserver that gives access to the
distributed IPFS network.
This protocol support (ipfs and ipns) therefore translates
ipfs:// and ipns:// to a http:/
start_code is used as an [in,out] parameter only twice, once each in mpeg12.c
and mpegvideo_parser.c. The input part of avpriv_find_start_code() has now
been rewritten to still allow this.
I did manage to run FATE this time and it completes without errors.
Regards,
Scott
_
---
libavcodec/cavsdec.c | 2 +-
libavcodec/cbs_mpeg2.c | 4 ++--
libavcodec/extract_extradata_bsf.c | 2 +-
libavcodec/internal.h | 15 +++
libavcodec/mpeg12.c| 2 +-
libavcodec/mpeg12dec.c | 2 +-
libavcodec/mpeg
No functional change.
---
libavcodec/utils.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index b19befef21..cb4437edc2 100644
--- a/libavcodec/utils.c
+++ b/libavcodec/utils.c
@@ -967,10 +967,14 @@ const uint8_t *avpriv_find
The expected number of iterations may increase by one for an input of
alternating
0 and 1 bytes. Instead of incrementing by 2 everytime, it now alternates
between
incrementing by 1 and by 3.
No functional change, but now much clearer.
For the check p[-2] != 0:
Also reduce the number of iterati
---
libavcodec/utils.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index 8f8cc820bd..1a806b9fa8 100644
--- a/libavcodec/utils.c
+++ b/libavcodec/utils.c
@@ -944,18 +944,20 @@ const uint8_t *avpriv_find_start_code(const
This enhances the clarity of the code.
---
libavcodec/cbs_mpeg2.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/libavcodec/cbs_mpeg2.c b/libavcodec/cbs_mpeg2.c
index d41477620e..afe78eef9a 100644
--- a/libavcodec/cbs_mpeg2.c
+++ b/libavcodec/cbs_mpeg2.c
@@ -148,7 +148
---
libavcodec/internal.h | 26 +-
libavcodec/utils.c| 10 +-
2 files changed, 30 insertions(+), 6 deletions(-)
diff --git a/libavcodec/internal.h b/libavcodec/internal.h
index 005f308b70..94c41aef0b 100644
--- a/libavcodec/internal.h
+++ b/libavcodec/internal.
---
libavcodec/mpeg12dec.c | 2 +-
libavformat/rtpenc_mpv.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/libavcodec/mpeg12dec.c b/libavcodec/mpeg12dec.c
index 65b66d11f8..6b0b84ae64 100644
--- a/libavcodec/mpeg12dec.c
+++ b/libavcodec/mpeg12dec.c
@@ -1770,7 +1770,7 @@
ff_cbs_insert_unit_data() does not modify the data or data_size fields of
the CodedBitstreamFragment. It also does not modify the value pointed to
by start. (We don't need that byte in this function anymore, anyway.)
---
libavcodec/cbs_mpeg2.c | 26 +-
1 file changed, 13
If the last four bytes form a valid start code, the loop would run another time.
Since (start == buf_end), start_code is invalidated so the loop terminates.
However, calling avpriv_find_start_code() with p == end, it will immediately
return due to the zero size buffer. Thus the history is not nee
Have the compiler enforce not changing the addresses these parameters point to.
No functional change.
---
libavcodec/internal.h | 6 +++---
libavcodec/utils.c| 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/libavcodec/internal.h b/libavcodec/internal.h
index 94c41aef0b
Separate from part 2 for a clearer diff.
Now the true loop condition has been revealed: start < buf_end
Clarify loop by moving the detection of sequence_end_codes out of the loop.
See also commit fd93d5efe64206d5f1bce8c702602353444c0c1a regarding
sequence_end_codes
---
libavcodec/cbs_mpeg2.c |
If true, this skips the for loop at the beginning of avpriv_find_start_code().
If the state/start_code input is a local variable and only one buffer is used,
then no history is needed.
In loops and inline functions: if ignoring history, don't initialize start_code,
so it isn't reset twice each ti
Whitespace change only. Separate so the previous diff is clearer.
---
libavcodec/utils.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index da057bad3e..255c133737 100644
--- a/libavcodec/utils.c
+++ b/liba
Instead of making an API breaking change, create a new function instead,
and deprecate the old one.
Then replace all uses in FFmpeg of the old function with the new one.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/l
This deprecates av_get_media_type_string() which does return NULL.
printf %s with a null pointer is undefined behavior
This also matches behavior with avcodec_get_name() which never returns NULL,
instead it returns "unknown_codec".
---
doc/APIchanges | 3 +++
libavutil/avutil.h | 7 +++
printf %s with a null pointer is undefined behavior.
---
doc/examples/demuxing_decoding.c | 10 +-
doc/examples/extract_mvs.c | 4 ++--
fftools/cmdutils.c | 7 +++
fftools/cmdutils.h | 2 --
fftools/ffmpeg.c | 14 +++---
ffto
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Oneric
> Sent: Thursday, February 3, 2022 3:11 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/{ass, webvttdec}: fix
> handling of backslashes
>
> On Wed, Fe
From: softworkz
Signed-off-by: softworkz
---
Update ReadMe.md for PR submission and reference Developer Documentation
.
Published-As:
https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-22%2Fsoftworkz%2Fpatch-2-v1
Fetch-It-Via: git fetch https://github.com/ffstaging/FFmp
> -Original Message-
> From: ffmpeg-devel On Behalf Of Carl
> Eugen Hoyos
> Sent: Sunday, January 23, 2022 12:23 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] libavutil/tests/md5: Avoid
> warnings
>
> Am Fr., 21. Jan. 2022
> -Original Message-
> From: ffmpegagent
> Sent: Monday, January 10, 2022 8:56 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Hendrik Leppkes ; Soft Works
> ; Marton Balint ; softworkz
>
> Subject: [PATCH v2 0/2] avcodec/dvbsubdec,dvdsubdec: don't dump images
> to disk based on DEBUG define
>
> -Original Message-
> From: ffmpegagent
> Sent: Tuesday, January 4, 2022 3:19 AM
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz ; softworkz
>
> Subject: [PATCH] avcodec/dvdsubdec: fix incorrect yellow appearance of
> dvd subtitles
>
> From: softworkz
>
> The guess_palette() implemen
On 2/3/22 17:10, Soft Works wrote:
-Original Message-
From: ffmpegagent
Sent: Tuesday, January 4, 2022 3:19 AM
To: ffmpeg-devel@ffmpeg.org
Cc: softworkz ; softworkz
Subject: [PATCH] avcodec/dvdsubdec: fix incorrect yellow appearance of
dvd subtitles
From: softworkz
The guess_palett
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Scott Theisen
> Sent: Thursday, February 3, 2022 11:17 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/dvdsubdec: fix incorrect
> yellow appearance of dvd subtitles
>
> On 2/3/22 17:10, Soft Works wr
On 2/3/22 17:57, Soft Works wrote:
My suspicion is that 0x00 was written assuming RGBA order instead
of ARGB.
You are missing a byte for either RGBA or ARGB. RGBA would be cyan.
I'm pretty sure that it's a mistake and it hasn't been an intentional
choice, because even when you would consi
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Scott Theisen
> Sent: Friday, February 4, 2022 12:15 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/dvdsubdec: fix incorrect
> yellow appearance of dvd subtitles
>
> On 2/3/22 17:57, Soft Works wrot
Fixes: Infinite loop
Fixes:
43932/clusterfuzz-testcase-minimized-ffmpeg_dem_MATROSKA_fuzzer-6175167573786624
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/matroskadec.c | 2 +-
1 file chang
Fixes: pointer index expression with base 0x overflowed to
0x
Fixes:
44012/clusterfuzz-testcase-minimized-ffmpeg_dem_HLS_fuzzer-5670607746891776
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael
On Thu, Feb 03, 2022 at 20:51:16 +, Soft Works wrote:
> I think when you inject that word-joiner as a workaround for ass
> parsing, you'll also need to make sure that it gets removed
> when encoding to other formats.
There's no way of knowing whether the word-joiner comes from
a conversion per
Oneric:
> On Thu, Feb 03, 2022 at 20:51:16 +, Soft Works wrote:
>> I think when you inject that word-joiner as a workaround for ass
>> parsing, you'll also need to make sure that it gets removed
>> when encoding to other formats.
>
> There's no way of knowing whether the word-joiner comes from
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Oneric
> Sent: Friday, February 4, 2022 2:01 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/{ass, webvttdec}: fix
> handling of backslashes
>
> On Thu, Feb
On Wed, Feb 02, 2022 at 03:45:10PM -0500, Patrick Keroulas wrote:
> In previous state, a new frame was allocated on each timestamp step,
> i.e. each frame/field transition. However, for interlace, a new frame
> should be allocated on 1st field, completed with the 2nd and finally
> freed.
>
> This
Ping?
On Jan 28, 2022, 11:24 AM +0800, Wang Chuan , wrote:
> if we are reading udta in trak box, the data should go to metadata
> of current stream.
>
> Signed-off-by: Wang Chuan
> ---
> libavformat/mov.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/libavformat/mov.c
Michael Niedermayer:
> Fixes: Infinite loop
> Fixes:
> 43932/clusterfuzz-testcase-minimized-ffmpeg_dem_MATROSKA_fuzzer-6175167573786624
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michael Niedermayer
> ---
> libavfo
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Friday, February 4, 2022 2:58 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/{ass, webvttdec}: fix
> handling of backslashes
>
>
>
> >
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Friday, February 4, 2022 6:34 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/{ass, webvttdec}: fix
> handling of backslashes
>
>
>
> >
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Friday, February 4, 2022 6:34 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/{ass, webvttdec}: fix
> handling of backslashes
>
>
>
> >
Never apply this. Very sorry state of project.
___
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".
61 matches
Mail list logo
