Signed-off-by: Andreas Rheinhardt
---
libavformat/webmdashenc.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/libavformat/webmdashenc.c b/libavformat/webmdashenc.c
index 182a361eae..303cdd699b 100644
--- a/libavformat/webmdashenc.c
+++ b/libavformat/webmdashenc.
The WebM DASH Manifest muxer only supports VP8, VP9, Vorbis and Opus,
but there was no check for this. The codec type is used to get a pointer
to a string containing the codec name or NULL if it is not one of those
four codecs. Said pointer has then been used without further checks as
string for th
On 25.03.2020 1:12, Carl Eugen Hoyos wrote:
> Am Di., 24. März 2020 um 14:28 Uhr schrieb Pestov Vyacheslav
> :
>> yuy2ToY_c: 10157
>> yuy2ToY_c_vsx: 2353
>>
>> yuy2ToUV_c: 4907
>> yuy2ToUV_c_vsx: 1357
>>
>> rgb24ToY_c: 21172
>> rgb24ToY_c_vsx: 9191
>>
>> rgb24ToUV_c: 33568
>> rgb24ToUV_c_vsx: 1274
From: Jun Zhao
There have been some reports about FLV timestamp discontinuities present.
e,g, the file recorded from live RTMP FLV streaming, so add
AVFMT_TS_DISCONT flag on FLV demuxer and also update the fate test
fate-filter-aresample for test sample nellymoser-discont.flv.
BTW: live_flv demu
From: qoroliang
Fix an occasional crash for hevc decoder in ARM 64 platform, the
root cause is the memory over read(read cross the memory boundary)
in SAO NENO functions ff_hevc_sao_band_filter_neon_8 and
ff_hevc_sao_edge_filter_neon_8.
After this fix, the crash disapper in the massive Android p
On Mon, Mar 30, 2020 at 4:31 PM Jun Zhao wrote:
>
> From: qoroliang
>
> Fix an occasional crash for hevc decoder in ARM 64 platform, the
typo: it's ARM 32 bits platform, not 64,
fixed in local
> root cause is the memory over read(read cross the memory boundary)
> in SAO
From: vacingfang
support DOVIVideo Stream Descriptor from Dolby Vision Streams
Within the MPEG-2 Transport Stream Format V1.2
From the spec: https://www.dolby.com/us/en/technologies/\
dolby-vision/dolby-vision-bitstreams-in-mpeg-2-transport-\
stream-multiplex-v1.2.pdf.
export the Dolby Vision p
On Mon, Mar 30, 2020 at 4:30 PM Jun Zhao wrote:
>
> From: Jun Zhao
>
> There have been some reports about FLV timestamp discontinuities present.
> e,g, the file recorded from live RTMP FLV streaming, so add
> AVFMT_TS_DISCONT flag on FLV demuxer and also update the fate test
> fate-filter-aresamp
From: vacingfang
support dvcC/dvcC box from spec Dolby Vision Streams Within the
ISO Base MediaFile Format Version 2.1.2
(https://www.dolby.com/in/en/technologies/dolby-vision/dolby-vision\
-bitstreams-within-the-iso-base-media-file-format-v2.1.2.pdf)
And export the Dolby Vision profile/level wi
From: Limin Wang
Signed-off-by: Limin Wang
---
libavfilter/vf_subtitles.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/libavfilter/vf_subtitles.c b/libavfilter/vf_subtitles.c
index a3b4029af4..2f312b0ba8 100644
--- a/libavfilter/vf_subtitles.c
+++ b/libavfilter/vf_s
From: Limin Wang
Signed-off-by: Limin Wang
---
doc/filters.texi | 4
libavfilter/vf_subtitles.c | 23 +++
2 files changed, 27 insertions(+)
diff --git a/doc/filters.texi b/doc/filters.texi
index 328e984e92..d26d90d1bb 100644
--- a/doc/filters.texi
+++ b/doc/
From: Juan De León
This is intended to replace the deprecated the AV_FRAME_DATA_QP_TABLE*
API and extend it to a wider range of codecs.
In the future, it may also be extended to support other encoding
parameters such as motion vectors.
Additional changes by Anton Khirnov with suggestions
by Ly
---
libavcodec/h264_picture.c| 8 +-
libavcodec/h264_slice.c | 9 +++
libavcodec/h264dec.c | 48
libavcodec/h264dec.h | 6 +
libavutil/video_enc_params.h | 1 +
5 files changed, 71 insertions(+), 1 deletion(-)
diff --gi
---
libavcodec/avcodec.h | 5 +
libavcodec/options_table.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
index 78c483c25c..436a21f99c 100644
--- a/libavcodec/avcodec.h
+++ b/libavcodec/avcodec.h
@@ -1120,6 +1120,11 @@ typedef struct RcO
---
libavfilter/vf_showinfo.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_showinfo.c
index 71534d1fa8..0025ee63fc 100644
--- a/libavfilter/vf_showinfo.c
+++ b/libavfilter/vf_showinfo.c
@@ -36,6 +36,7 @@
#include "libavuti
---
libavcodec/vp9.c | 36
1 file changed, 16 insertions(+), 20 deletions(-)
diff --git a/libavcodec/vp9.c b/libavcodec/vp9.c
index 7ee375d4d0..e03891887b 100644
--- a/libavcodec/vp9.c
+++ b/libavcodec/vp9.c
@@ -93,6 +93,12 @@ static void vp9_free_entries(AVCo
---
libavcodec/vp9.c | 74
libavcodec/vp9block.c| 8
libavcodec/vp9dec.h | 8
libavutil/video_enc_params.h | 1 +
4 files changed, 91 insertions(+)
diff --git a/libavcodec/vp9.c b/libavcodec/vp9.c
index e03891887b..8ba
Do it only when requested with the AV_CODEC_EXPORT_DATA_VIDEO_ENC_PARAMS
flag.
Drop previous code using the long-deprecated AV_FRAME_DATA_QP_TABLE*
API.
---
libavcodec/h263dec.c | 6 --
libavcodec/mpeg12dec.c | 5 +++--
libavcodec/mpegpicture.c | 1 +
libavcodec/mpegpictu
On Tue, Feb 18, 2020 at 18:41:08 +0330, Mostafa Namazi fard wrote:
> I found this patch useful for prevent crash in http live stream.
> I'm using ffmpeg in my application for show http live when remote address
> send invalid data ffmpeg crash in this part and after my change it was
> fixed.
Can yo
add option for refresh init file after m3u8 refresh everytime.
Signed-off-by: Steven Liu
---
doc/muxers.texi | 3 +++
libavformat/hlsenc.c | 44 ++--
2 files changed, 41 insertions(+), 6 deletions(-)
diff --git a/doc/muxers.texi b/doc/muxers.texi
in
On Sat, Mar 28, 2020 at 13:32:42 +, Tom Needham wrote:
> + * License along with FFmpeg; if not, write to the Free Software
> + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
> 02110-1301 USA
You've inlined your patch again, and again it's corrupted by newlines.
> +unsigned ch
On Sat, Mar 21, 2020 at 12:46:09 +0800, numberwolf wrote:
> Subject: examples/extract_mvs.c: dont disply motionless vectors
Two typos in the commit message: -> don't display
> Reviewed-by: Paul B Mahol
Please don't do this. (Not speaking for Paul here, but in general, this
doesn't really make s
Am Fr., 27. März 2020 um 19:00 Uhr schrieb phunkyfish :
>
> ffmpeg | branch: master | phunkyfish | Mon Mar 2
> 19:21:09 2020 +| [b71685865fe761925feedda3cd0b288224d9a509] | committer:
> Aman Gupta
>
> avformat/rtp: Pass sources and block filter addresses via sdp file for rtp
>
> Signed-off-
On Mon, Mar 30, 2020 at 10:36:30 +0530, gautamr...@gmail.com wrote:
> -if (bytestream2_get_bytes_left(&s->g) == 0 && s->bit_index == 8) {
> -if (*tp_index < FF_ARRAY_ELEMS(tile->tile_part) - 1) {
> -s->g = tile->tile_part[++(*tp_index)].tpg;
> +// Select appropriate stre
On Mon, Mar 30, 2020 at 10:36:31 +0530, gautamr...@gmail.com wrote:
> +tile->has_ppt = 1; // this tile has a ppt marker
> +/*Zppt = */ bytestream2_get_byte(&s->g);
For readability, please place the explanation of what has been ignored
behind the statement. (This line looks commented out w
On Mon, Mar 30, 2020 at 10:36:32 +0530, gautamr...@gmail.com wrote:
> +av_log(s->avctx, AV_LOG_WARNING, "Mising EOC Marker.\n");
Typo: Missing
Moritz
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/f
On Mon, Mar 30, 2020 at 12:20 PM Jun Zhao wrote:
>
> From: vacingfang
>
> support dvcC/dvcC box from spec Dolby Vision Streams Within the
> ISO Base MediaFile Format Version 2.1.2
> (https://www.dolby.com/in/en/technologies/dolby-vision/dolby-vision\
> -bitstreams-within-the-iso-base-media-file-f
On Mon, Mar 30, 2020 at 11:53 AM Jun Zhao wrote:
>
> From: vacingfang
>
> support DOVIVideo Stream Descriptor from Dolby Vision Streams
> Within the MPEG-2 Transport Stream Format V1.2
>
> From the spec: https://www.dolby.com/us/en/technologies/\
> dolby-vision/dolby-vision-bitstreams-in-mpeg-2-t
On Sun, Mar 22, 2020 at 11:01 PM David Michael wrote:
> On Mon, Mar 16, 2020 at 9:16 AM David Michael wrote:
> > On Sat, Mar 7, 2020 at 10:32 AM David Michael wrote:
> > > Using a compiler with a different host triplet is considered
> > > cross-compiling, even when it is for the same architectur
On Mon, Mar 30, 2020 at 7:44 PM Moritz Barsnick wrote:
>
> On Mon, Mar 30, 2020 at 10:36:32 +0530, gautamr...@gmail.com wrote:
> > +av_log(s->avctx, AV_LOG_WARNING, "Mising EOC Marker.\n");
>
> Typo: Missing
>
> Moritz
> ___
> ffmpeg-devel ma
From: Gautam Ramakrishnan
---
libavcodec/jpeg2000dec.c | 48 ++--
1 file changed, 41 insertions(+), 7 deletions(-)
diff --git a/libavcodec/jpeg2000dec.c b/libavcodec/jpeg2000dec.c
index 7103cd6ceb..9d52969821 100644
--- a/libavcodec/jpeg2000dec.c
+++ b/libavc
From: Gautam Ramakrishnan
This patch allows decoding of j2k streams which do
not have an EOC marker.
---
libavcodec/jpeg2000dec.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/libavcodec/jpeg2000dec.c b/libavcodec/jpeg2000dec.c
index 23e43ff052..d27d753992 100644
--
From: Gautam Ramakrishnan
This patch adds functional changes to support the
PPT marker.
---
libavcodec/jpeg2000dec.c | 209 ++-
1 file changed, 162 insertions(+), 47 deletions(-)
diff --git a/libavcodec/jpeg2000dec.c b/libavcodec/jpeg2000dec.c
index 9d5296982
On 07/03/2020 15:32, David Michael wrote:
> Using a compiler with a different host triplet is considered
> cross-compiling, even when it is for the same architecture as the
> build system. With such a cross-compiler, it is still valid to
> optimize builds with --cpu=host. Drop the condition that
On Mon, Mar 30, 2020 at 1:00 PM Derek Buitenhuis
wrote:
> On 07/03/2020 15:32, David Michael wrote:
> > Using a compiler with a different host triplet is considered
> > cross-compiling, even when it is for the same architecture as the
> > build system. With such a cross-compiler, it is still vali
Andreas Rheinhardt (12020-03-24):
> I reconsidered this and I think I got it exactly wrong: libavdevice is
> linked against libavformat, not the other way around. Therefore one can
> swap the libavformat against a newer one, but one is not allowed to
> update libavdevice without also updating libav
On Fri, Apr 15, 2016 at 4:06 AM wm4 wrote:
> On Wed, 6 Apr 2016 17:09:21 -0600
> Nic Wolfe wrote:
>
> > Thanks for elaborating wm4. Out of curiosity when you say "generic"
> > and "normal" metadata what do you mean? Are you talking about using
> > generic key names or is there another way to sto
See [1]. Apple requests that colr atom values be 2 ("unspecified") for
Dolby Vision.
Please review.
--Michael
[1]:
https://developer.apple.com/av-foundation/High-Dynamic-Range-Metadata-for-Apple-Devices.pdf
0001-avformat-movenc-stop-guessing-colr-atom-values.patch
Description: Binary data
_
On Mon, Mar 30, 2020 at 04:22:51PM +0800, Jun Zhao wrote:
> From: Jun Zhao
>
> There have been some reports about FLV timestamp discontinuities present.
> e,g, the file recorded from live RTMP FLV streaming, so add
> AVFMT_TS_DISCONT flag on FLV demuxer and also update the fate test
> fate-filter
The write_colr flag has been marked as experimental for over 5 years. I
propose we do the following (as implemented by the attached patch):
- Write the colr atom by default for mp4/mov if any of the following:
- The primaries/trc/matrix are all specified, OR
- There is an ICC profil
Michael Bradshaw:
> The write_colr flag has been marked as experimental for over 5 years. I
> propose we do the following (as implemented by the attached patch):
>
>- Write the colr atom by default for mp4/mov if any of the following:
> - The primaries/trc/matrix are all specified, OR
>
On Mon, Mar 30, 2020 at 01:45:23PM +0200, Anton Khirnov wrote:
> Do it only when requested with the AV_CODEC_EXPORT_DATA_VIDEO_ENC_PARAMS
> flag.
>
> Drop previous code using the long-deprecated AV_FRAME_DATA_QP_TABLE*
> API.
> ---
> libavcodec/h263dec.c | 6 --
> libavcodec/mpeg12de
Hi!
Attached patch avoids writing an mp4 file that cannot be read by
FFmpeg (only be vlc) in some use cases.
Please comment, Carl Eugen
From 42b5e30f3bf13620a41ed92181f7b0358873e764 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Tue, 31 Mar 2020 00:17:44 +0200
Subject: [PATCH] lavf/movenc
On Mon, Mar 30, 2020 at 3:46 PM Andreas Rheinhardt <
andreas.rheinha...@gmail.com> wrote:
> Why is all this information not in the commit message? (In commit
> message style of course, i.e. no "I propose".)
For reasons that I'm happy to discuss in a separate thread to avoid
derailing this one. A
Am Mo., 30. März 2020 um 22:28 Uhr schrieb Michael Bradshaw
:
>
> See [1]. Apple requests that colr atom values be 2 ("unspecified") for
> Dolby Vision.
> // e.g., Dolby Vision for Apple devices should be set to
> AVCOL_PRI_UNSPECIFIED.
But not every call of the mov muxer is done for Dolby Visio
Refactoring my previous patch into smaller items. Starting with the one
found by the Chromium fuzzers.
0001-libavformat-oggdec.c-Check-return-value-from-avio_re.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https:/
Another one found by the Chromium fuzzers.
0001-libavformat-mov.c-Free-aes_decrypt-to-avoid-leaking-.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, v
On Mon, Mar 30, 2020 at 4:23 PM Carl Eugen Hoyos wrote:
> But not every call of the mov muxer is done for Dolby Vision
> samples or do I misunderstand?
You're right that most muxing doesn't involve Dolby Vision. However, even
for cases that don't involve Dolby Vision I still think guessing is t
On 3/30/2020 7:19 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch avoids writing an mp4 file that cannot be read by
> FFmpeg (only be vlc) in some use cases.
>
> Please comment, Carl Eugen
This enables writing non compliant files, so no.
We should instead check the return value of mov_write
Am Di., 31. März 2020 um 00:35 Uhr schrieb James Almer :
>
> On 3/30/2020 7:19 PM, Carl Eugen Hoyos wrote:
> > Hi!
> >
> > Attached patch avoids writing an mp4 file that cannot be read by
> > FFmpeg (only be vlc) in some use cases.
> >
> > Please comment, Carl Eugen
>
> This enables writing non com
Am Mi., 15. Jan. 2020 um 16:56 Uhr schrieb Marton Balint :
>
>
>
> On Wed, 15 Jan 2020, Carl Eugen Hoyos wrote:
>
> > Hi!
> >
> > Attached patch fixes hard-to-understand behaviour of ffmpeg for some
> > mp4 input files, a hard exit following a debug message.
>
> I don't think such an mp4 file is st
Am Sa., 28. März 2020 um 13:54 Uhr schrieb Carl Eugen Hoyos
:
> Attached patch allows to work-around ticket #7140, tested on a system
> with a lot of memory.
Ping.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mail
Am Di., 31. März 2020 um 00:33 Uhr schrieb Michael Bradshaw
:
>
> On Mon, Mar 30, 2020 at 4:23 PM Carl Eugen Hoyos wrote:
>
> > But not every call of the mov muxer is done for Dolby Vision
> > samples or do I misunderstand?
>
> You're right that most muxing doesn't involve Dolby Vision. However, e
On 3/30/2020 7:44 PM, Carl Eugen Hoyos wrote:
> Am Di., 31. März 2020 um 00:35 Uhr schrieb James Almer :
>>
>> On 3/30/2020 7:19 PM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch avoids writing an mp4 file that cannot be read by
>>> FFmpeg (only be vlc) in some use cases.
>>>
>>> Please co
On Mon, Mar 30, 2020 at 4:48 PM Carl Eugen Hoyos wrote:
> I believe there is some historical evidence that this guessing is needed
> to get visually correct output in many cases.
I haven't found any evidence of that. This guessing has been part of the
code since the write_colr flag was original
The clli atom isn't in ISO/IEC 14496-12:2015 so the flag is marked as
experimental and the clli atom is not written by default.
The clli atom is referenced by e.g., [1][2] and is already parsed in FFmpeg
in mov.c.
Once ISO/IEC 14496-12 standardizes the clli atom (which I assume it will?)
then we
On Mon, Mar 30, 2020 at 09:51:53PM +0530, gautamr...@gmail.com wrote:
> From: Gautam Ramakrishnan
>
> ---
> libavcodec/jpeg2000dec.c | 48 ++--
> 1 file changed, 41 insertions(+), 7 deletions(-)
>
> diff --git a/libavcodec/jpeg2000dec.c b/libavcodec/jpeg2000d
On Tue, Mar 31, 2020 at 5:29 AM Michael Niedermayer
wrote:
>
> On Mon, Mar 30, 2020 at 04:22:51PM +0800, Jun Zhao wrote:
> > From: Jun Zhao
> >
> > There have been some reports about FLV timestamp discontinuities present.
> > e,g, the file recorded from live RTMP FLV streaming, so add
> > AVFMT_T
On Mon, Mar 30, 2020 at 10:56 PM Jan Ekström wrote:
>
> On Mon, Mar 30, 2020 at 12:20 PM Jun Zhao wrote:
> >
> > From: vacingfang
> >
> > support dvcC/dvcC box from spec Dolby Vision Streams Within the
> > ISO Base MediaFile Format Version 2.1.2
> > (https://www.dolby.com/in/en/technologies/dolb
Steven Liu:
> add option for refresh init file after m3u8 refresh everytime.
>
> Signed-off-by: Steven Liu
> ---
> doc/muxers.texi | 3 +++
> libavformat/hlsenc.c | 44 ++--
> 2 files changed, 41 insertions(+), 6 deletions(-)
>
> diff --git a/doc/mu
> 2020年3月31日 上午10:06，Andreas Rheinhardt 写道：
>
> Steven Liu:
>> add option for refresh init file after m3u8 refresh everytime.
>>
>> Signed-off-by: Steven Liu
>> ---
>> doc/muxers.texi | 3 +++
>> libavformat/hlsenc.c | 44 ++--
>> 2 files changed, 4
On Tue, Mar 31, 2020 at 6:10 AM Michael Niedermayer
wrote:
>
> On Mon, Mar 30, 2020 at 09:51:53PM +0530, gautamr...@gmail.com wrote:
> > From: Gautam Ramakrishnan
> >
> > ---
> > libavcodec/jpeg2000dec.c | 48 ++--
> > 1 file changed, 41 insertions(+), 7 delet
Hit send too soon. Patch attached.
On Mon, Mar 30, 2020 at 9:44 PM John Rummell wrote:
> Another uninitialized memory access detected by the Chromium fuzzers.
>
0001-libavformat-amr.c-Check-return-value-from-avio_read.patch
Description: Binary data
_
On Wed, Feb 26, 2020 at 4:36 AM Carl Eugen Hoyos wrote:
>
> Am Mi., 26. Feb. 2020 um 06:57 Uhr schrieb Roger Pack :
> >
> > Original bigger patch is enough for now. Please merge, thanks!
>
> What happened to your git account?
I never made one. Do we still send in private keys for it? If so to
Another uninitialized memory access detected by the Chromium fuzzers.
___
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 s
65 matches
Mail list logo
