Fixes a regression introduced in dbfd042983eed8586d4048795c00af820f5b6b1f.
Signed-off-by: Marton Balint
---
doc/fftools-common-opts.texi | 5 -
libavformat/utils.c | 16 +++-
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/doc/fftools-common-opts.texi b/
---
Add the index of the timecode in case of multiple timecodes values
Limit to 3 the number of timecodes
remove break
Thanks you !
---
fftools/ffprobe.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index dea489d02e..b43349f746 100644
--
On Sat, 18 May 2019, Carl Eugen Hoyos wrote:
Am 18.05.2019 um 16:48 schrieb Marton Balint :
On Tue, 14 May 2019, Hendrik Leppkes wrote:
On Tue, May 14, 2019 at 10:34 PM Marton Balint wrote:
On Sun, 5 May 2019, Carl Eugen Hoyos wrote:
Am So., 5. Mai 2019 um 20:51 Uhr schrieb Mart
On 2019-05-18 11:57 -0300, James Almer wrote:
> On 5/18/2019 9:24 AM, Paul B Mahol wrote:
> > On 5/18/19, Reimar Döffinger wrote:
> >> Voting is not yet another mobbing tool for when you get tired of other
> >> ways.
> >> If you wish for an end to that feud, you can ask other developers to try
>
On Sat, 18 May 2019, Antonin Gouzer wrote:
Thank you for your response,
I don't have any example of such a file.
I was thinking that GOP timecode was reserved to MPEG2 files and S12M
to H265/H264 files ?
In every writer the type of timecode is already an attribute: side_data_type.
With the ac
> Am 18.05.2019 um 16:48 schrieb Marton Balint :
>
>
>
>>> On Tue, 14 May 2019, Hendrik Leppkes wrote:
>>>
>>> On Tue, May 14, 2019 at 10:34 PM Marton Balint wrote:
>>>
>>>
>>>
On Sun, 5 May 2019, Carl Eugen Hoyos wrote:
> Am So., 5. Mai 2019 um 20:51 Uhr schrieb Marton Bal
On Sat, May 18, 2019 at 01:05:01PM +0200, Reimar Döffinger wrote:
> On 18.05.2019, at 12:15, Michael Niedermayer wrote:
>
> > On Sat, May 18, 2019 at 12:02:55PM +0200, James Darnley wrote:
> >> On 2019-05-18 09:39, Michael Niedermayer wrote:
> >>> Fixes: "null pointer dereference"
> >>> Fixes:
>
---
I just correct the indentation in the for loop
Thanks
---
fftools/ffprobe.c | 8
1 file changed, 8 insertions(+)
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index dea489d02e..da92c1592f 100644
--- a/fftools/ffprobe.c
+++ b/fftools/ffprobe.c
@@ -2199,6 +2199,14 @@ static void s
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index dea489d02e..da92c1592f 100644
--- a/fftools/ffprobe.c
+++ b/fftools/ffprobe.c
@@ -2199,6 +2199,14 @@ static void show_frame(WriterContext *w, AVFrame *frame,
AVStream *stream,
char tcbuf[AV_TIMECODE_STR_SIZE];
Thank you for your response,
I don't have any example of such a file.
I was thinking that GOP timecode was reserved to MPEG2 files and S12M
to H265/H264 files ?
In every writer the type of timecode is already an attribute: side_data_type.
With the actual xsd the result should be, with the XML writ
On Fri, 17 May 2019, Antonin Gouzer wrote:
Thanks in advance.
---
fftools/ffprobe.c | 8
1 file changed, 8 insertions(+)
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index dea489d02e..4763ce6d98 100644
--- a/fftools/ffprobe.c
+++ b/fftools/ffprobe.c
@@ -2199,6 +2199,14 @@ static
On 5/18/2019 9:24 AM, Paul B Mahol wrote:
> On 5/18/19, Reimar Döffinger wrote:
>> Voting is not yet another mobbing tool for when you get tired of other ways.
>> If you wish for an end to that feud, you can ask other developers to try and
>> help, but you've kept this going for years and usually
On Tue, 14 May 2019, Hendrik Leppkes wrote:
On Tue, May 14, 2019 at 10:34 PM Marton Balint wrote:
On Sun, 5 May 2019, Carl Eugen Hoyos wrote:
> Am So., 5. Mai 2019 um 20:51 Uhr schrieb Marton Balint :
>>
>> This reverts commit dd06f022b07438d650c82255dff16908ba04244a.
>>
>> Fixes ticket
On 5/18/19, Reimar Döffinger wrote:
> Voting is not yet another mobbing tool for when you get tired of other ways.
> If you wish for an end to that feud, you can ask other developers to try and
> help, but you've kept this going for years and usually responded somewhere
> between dismissive and in
On 2019-05-18 12:15, Michael Niedermayer wrote:
> On Sat, May 18, 2019 at 12:02:55PM +0200, James Darnley wrote:
>> I object to the commit message though because it isn't a "null pointer
>> dereference" but if that is the error as reported by the tool then keep
>> it as is.
>
> yes, the tool(s) sa
On 18.05.2019, at 12:15, Michael Niedermayer wrote:
> On Sat, May 18, 2019 at 12:02:55PM +0200, James Darnley wrote:
>> On 2019-05-18 09:39, Michael Niedermayer wrote:
>>> Fixes: "null pointer dereference"
>>> Fixes:
>>> 14551/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_V210_fuzzer-5088609
On 5/18/19, Michael Niedermayer wrote:
> On Wed, May 15, 2019 at 07:19:43PM +0200, Paul B Mahol wrote:
>> On 5/12/19, Paul B Mahol wrote:
>> > On 5/12/19, Michael Niedermayer wrote:
>> >> On Sun, May 12, 2019 at 11:00:51PM +0200, Nicolas George wrote:
>> >>> Marton Balint (12019-05-12):
>> >>> >
On Sat, May 18, 2019 at 12:02:55PM +0200, James Darnley wrote:
> On 2019-05-18 09:39, Michael Niedermayer wrote:
> > Fixes: "null pointer dereference"
> > Fixes:
> > 14551/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_V210_fuzzer-5088609952071680
> >
> > Found-by: continuous fuzzing process
On Wed, May 15, 2019 at 07:19:43PM +0200, Paul B Mahol wrote:
> On 5/12/19, Paul B Mahol wrote:
> > On 5/12/19, Michael Niedermayer wrote:
> >> On Sun, May 12, 2019 at 11:00:51PM +0200, Nicolas George wrote:
> >>> Marton Balint (12019-05-12):
> >>> > Yeah, you are right, what I had in mind was th
On 2019-05-18 09:39, Michael Niedermayer wrote:
> Fixes: "null pointer dereference"
> Fixes:
> 14551/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_V210_fuzzer-5088609952071680
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-o
Fixes: NULL pointer dereference
Fixes:
14723/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_AAC_LATM_fuzzer-5654612436058112
Fixes:
14724/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_AAC_LATM_fuzzer-5712607111020544
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz
Fixes: "null pointer dereference"
Fixes:
14551/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_V210_fuzzer-5088609952071680
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/v210dec.c | 2 +-
Add another two padding methods "VALID" and "SAME" as tensorflow, and keep the
existing "SAME_CLAMP_TO_EDGE" method suggested by sr filter.
As "SAME_CLAMP_TO_EDGE"can keep the output with the same size as original
input, and gives a slight better result as mentioned by sr filter.
Signed-off-by:
23 matches
Mail list logo
