Re: [FFmpeg-devel] [PATCH] avfilter/vf_idet: Fixes issue with idet not flushing last frame.

On Wed, Oct 22, 2014 at 7:43 AM, Pascal Massimino pascal.massim...@gmail.com wrote: Hi, On Tue, Oct 21, 2014 at 11:40 PM, Neil Birkbeck neil.birkb...@gmail.com wrote: Uses a similar approach as vf_yadif to flush the last frame in idet. Quick test with 50 frames from vsynth1:

Re: [FFmpeg-devel] GSoC and Outreachy

On Mon, Mar 2, 2015 at 1:39 PM, Michael Niedermayer michae...@gmx.at wrote: Hi all FFmpeg has been accepted in GSoC this year. This is a GREAT news.. Congratulation to the people working on it If you want to mentor or are considering to mentor then please subscribe to

[FFmpeg-devel] [PATCH] libavformat/riff.c: Adding support of PCM_S24LE in WAVEFORMATEXTENSIBLE

--- libavformat/riff.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavformat/riff.c b/libavformat/riff.c index a9197e7..7de8936 100644 --- a/libavformat/riff.c +++ b/libavformat/riff.c @@ -487,5 +487,6 @@ const AVCodecGuid ff_codec_wav_guids[] = { { AV_CODEC_ID_ATRAC3P, { 0xBF,

Re: [FFmpeg-devel] [PATCH] libavformat/riff.c: Adding support of PCM_S24LE in WAVEFORMATEXTENSIBLE

On Thu, Oct 22, 2015 at 1:45 PM, Paul B Mahol <one...@gmail.com> wrote: > On 10/22/15, Thierry Foucu <tfo...@gmail.com> wrote: > > --- > > libavformat/riff.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/libavformat/riff.c b/libavfo

Re: [FFmpeg-devel] [PATCH] libavformat/riff.c: Adding support of PCM_S24LE in WAVEFORMATEXTENSIBLE

On Thu, Oct 22, 2015 at 2:08 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Thu, Oct 22, 2015 at 9:19 PM, Thierry Foucu <tfo...@gmail.com> wrote: > > --- > > libavformat/riff.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/liba

Re: [FFmpeg-devel] [PATCH] libavformat/riff.c: Adding support of PCM_S24LE in WAVEFORMATEXTENSIBLE

On Thu, Oct 22, 2015 at 2:29 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Thu, Oct 22, 2015 at 11:15 PM, Thierry Foucu <tfo...@gmail.com> wrote: > > On Thu, Oct 22, 2015 at 2:08 PM, Hendrik Leppkes <h.lepp...@gmail.com> > > wrote: > > > >>

Re: [FFmpeg-devel] [PATCH] libavformat/riff.c: Adding support of PCM_S24LE in WAVEFORMATEXTENSIBLE

On Thu, Oct 22, 2015 at 2:29 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Thu, Oct 22, 2015 at 11:15 PM, Thierry Foucu <tfo...@gmail.com> wrote: > > On Thu, Oct 22, 2015 at 2:08 PM, Hendrik Leppkes <h.lepp...@gmail.com> > > wrote: > > > >>

[FFmpeg-devel] [PATCH] libavformat/utils.c: use correct variable for message.

--- libavformat/utils.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/utils.c b/libavformat/utils.c index db988c0..24eacf3 100644 --- a/libavformat/utils.c +++ b/libavformat/utils.c @@ -3348,7 +3348,7 @@ int avformat_find_stream_info(AVFormatContext *ic,

[FFmpeg-devel] [PATCH] libavformat/riff.c: Add support for RV40 codec in AVI

--- libavformat/riff.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavformat/riff.c b/libavformat/riff.c index 768b406..be76b0a 100644 --- a/libavformat/riff.c +++ b/libavformat/riff.c @@ -373,6 +373,7 @@ const AVCodecTag ff_codec_bmp_tags[] = { { AV_CODEC_ID_HQX,

[FFmpeg-devel] [PATCH] libavformat/flvdec.c: free always the packet after a resync.

In case of resync, always free the packet, but retry only if the resync did not get to the end of the file. Otherwise, there is a memory leak when the last packet in the file is corrupted. --- libavformat/flvdec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[FFmpeg-devel] [PATCH] lavf/mov: Extend extracting XMP in mov files using UUID Box

The UUID is based on http://www.adobe.com/devnet/xmp.html The patch is made according to XMP SPECIFICATION PART 3 - STORAGE IN FILES See Table 8 --- libavformat/mov.c | 28 1 file changed, 28 insertions(+) diff --git a/libavformat/mov.c b/libavformat/mov.c index

[FFmpeg-devel] [PATCH] lavf/mov: Extend extracting XMP in mov files using UUID Box

The UUID is based on http://www.adobe.com/devnet/xmp.html The patch is made according to XMP SPECIFICATION PART 3 - STORAGE IN FILES See Table 8 --- libavformat/mov.c | 25 + 1 file changed, 25 insertions(+) diff --git a/libavformat/mov.c b/libavformat/mov.c index

[FFmpeg-devel] [PATCH] lavf/flvdec: Allow files where the PreviousTagSize is not set according to the spec.

Some muxer use the FLV field PreviousTagSize to be the sum of tag length. Without this change, the flv demuxer think the file is broken and the re-sync will fail. --- libavformat/flvdec.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/libavformat/flvdec.c

Re: [FFmpeg-devel] [PATCH v3 1/2] lavc/ccaption_dec: do not ignore repeated character commands

0character%20set%20test/README.TXT), > but three times. > > Aman > > On Mon, Apr 18, 2016 at 1:01 PM, Aman Gupta <a...@tmm1.net> wrote: > >> Please send me the sample and I will try to fix the issue. >> >> Aman >> >> On Mon, Apr 18, 2016 at 1:22 PM T

Re: [FFmpeg-devel] [FFmpeg-cvslog] Merge commit '2758cdedfb7ac61f8b5e4861f99218b6fd43491d'

On Wed, May 4, 2016 at 3:46 PM, Thierry Foucu <tfo...@gmail.com> wrote: > > > On Wed, May 4, 2016 at 1:58 PM, Derek Buitenhuis < > derek.buitenh...@gmail.com> wrote: > >> On 5/4/2016 9:52 PM, wm4 wrote: >> > This was never allowed and was never public

Re: [FFmpeg-devel] [FFmpeg-cvslog] Merge commit '2758cdedfb7ac61f8b5e4861f99218b6fd43491d'

On Wed, May 4, 2016 at 1:58 PM, Derek Buitenhuis wrote: > On 5/4/2016 9:52 PM, wm4 wrote: > > This was never allowed and was never public API. Use custom I/O instead > > (creating an avio context with your own read/write callbacks). > > Can i ask why it cannot be

Re: [FFmpeg-devel] [FFmpeg-cvslog] Merge commit '2758cdedfb7ac61f8b5e4861f99218b6fd43491d'

Hi Team On Mon, Feb 29, 2016 at 8:51 AM, Derek Buitenhuis wrote: > ffmpeg | branch: master | Derek Buitenhuis | > Mon Feb 29 16:50:39 2016 +| [9c75148e6ebc88a0501e3d0242defb6dbdc3c23d] > | committer: Derek Buitenhuis > > Merge commit

Re: [FFmpeg-devel] [PATCH v3 1/2] lavc/ccaption_dec: do not ignore repeated character commands

Hi all On Sun, Feb 14, 2016 at 6:11 PM, Aman Gupta wrote: > From: Aman Gupta > > control codes in a cc stream can be repeated, and must be ignored. > however, repeated characters must not be ignored. the code attempted to > wipe prev_cmd in handle_char to allow

[FFmpeg-devel] [PATCH 3/3] Fix -Werror=parentheses error

--- libavcodec/internal.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/internal.h b/libavcodec/internal.h index 35b9630..c92dba4 100644 --- a/libavcodec/internal.h +++ b/libavcodec/internal.h @@ -262,7 +262,7 @@ static av_always_inline int64_t

[FFmpeg-devel] Problem with vstats file and frame number

Hi, Before sending you some patches to fix it, I would like to know how you want this issue to be fixed. Let me explain it: When we enable vstats file to be generated, each line of the file contains the frame number of the encoded video frames. The frame number is the one from AVStream.nb_frames

[FFmpeg-devel] [PATCH] libavformat/mov: Fix memory leak, need to free the chapter tracks array

--- libavformat/mov.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavformat/mov.c b/libavformat/mov.c index 90bc2499da..f2296f8917 100644 --- a/libavformat/mov.c +++ b/libavformat/mov.c @@ -5794,6 +5794,7 @@ static int mov_read_close(AVFormatContext *s)

[FFmpeg-devel] [PATCH 2/2] vf_fps: Fix memory leak introduced by eea64ef4

--- libavfilter/vf_fps.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavfilter/vf_fps.c b/libavfilter/vf_fps.c index 09fc66a73c..1e5d07e31c 100644 --- a/libavfilter/vf_fps.c +++ b/libavfilter/vf_fps.c @@ -171,6 +171,7 @@ static int request_frame(AVFilterLink *outlink)

Re: [FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

; > On Fri, Sep 15, 2017 at 02:44:59AM +0200, Michael Niedermayer wrote: > > > >> On Tue, Sep 12, 2017 at 06:45:57PM -0700, Thierry Foucu wrote: > > > >>> Fix ticket #2674 > > > >>> Tested with examples from ticket 2674. > > > >>&g

Re: [FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

On Fri, Sep 15, 2017 at 8:24 AM, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > 2017-09-15 17:13 GMT+02:00 Thierry Foucu <tfo...@gmail.com>: > > >> Too fast to reply again, my bad. It's indeed a GCC bug. > > > > Sorry about it. I'm glad you found the proble

[FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

Fix ticket #2674 Tested with examples from ticket 2674. --- Update the Patch with the correct number of duplicate showing. For exmaple, in case we up-sample one second video at 24fps by 2, we should be getting 24 duplicate frames. ffmpeg -loglevel verbose -i 24fps.avi -vf fps=48 -f null -

Re: [FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

On Tue, Sep 12, 2017 at 6:45 PM, Thierry Foucu <tfo...@gmail.com> wrote: > Fix ticket #2674 > Tested with examples from ticket 2674. > --- > Sorry Michael, I forgot to configure using --enable-gpl. > Please find new patch. > > > ping? > liba

[FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

--- libavfilter/vf_fps.c| 42 +- tests/ref/fate/filter-fps | 6 ++ tests/ref/fate/filter-fps-r | 4 3 files changed, 47 insertions(+), 5 deletions(-) diff --git a/libavfilter/vf_fps.c b/libavfilter/vf_fps.c index 20ccd797d1..e450723173

Re: [FFmpeg-devel] [PATCH] vf_fps: uses the last frame duration to duplicate it if needed

On Thu, Sep 7, 2017 at 11:37 AM, Nicolas George <geo...@nsup.org> wrote: > [ Ccing you, but no need to Cc me. ] > > Le primidi 21 fructidor, an CCXXV, Thierry Foucu a écrit : > > Sorry I did not know and I did not see any documentation in the header > > explaining whi

Re: [FFmpeg-devel] [PATCH] vf_fps: uses the last frame duration to duplicate it if needed

Hi Nicolas, On Wed, Sep 6, 2017 at 2:07 PM, Nicolas George <geo...@nsup.org> wrote: > Le decadi 20 fructidor, an CCXXV, Thierry Foucu a écrit : > > --- > > libavfilter/vf_fps.c| 40 ++ > +- > > tests/ref/fate/filter-fp

[FFmpeg-devel] [PATCH] vf_fps: uses the last frame duration to duplicate it if needed

--- libavfilter/vf_fps.c| 40 +++- tests/ref/fate/filter-fps | 6 ++ tests/ref/fate/filter-fps-r | 4 3 files changed, 45 insertions(+), 5 deletions(-) diff --git a/libavfilter/vf_fps.c b/libavfilter/vf_fps.c index 20ccd797d1..a231da415c

[FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

Fix ticket #2674 Tested with examples from ticket 2674. --- Sorry Michael, I forgot to configure using --enable-gpl. Please find new patch. libavfilter/vf_fps.c | 44 +++- tests/ref/fate/filter-fps| 6 ++ tests/ref/fate/filter-fps-r

Re: [FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

On Tue, Sep 12, 2017 at 1:35 AM, Thomas Mundt <tmund...@gmail.com> wrote: > Hi Thierry, > > 2017-09-12 3:25 GMT+02:00 Thierry Foucu <tfo...@gmail.com>: > >> Fix ticket #2674 >> Tested with examples from ticket 2674. >> --- >> >> Update

[FFmpeg-devel] (no subject)

Please find attached new patch. I tried it against ticket 2674 and it seems to work Here are the output: For the up-sample, getting 48 frames out, instead of 47 -- ./ffmpeg -loglevel verbose -i 24fps.avi -vf fps=48 -y 48fps.avi ffmpeg version N-87234-g9a32769f5e

Re: [FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

> > 2017-09-08 19:03 GMT+02:00 Thierry Foucu <tfo...@gmail.com>: > > > --- > > libavfilter/vf_fps.c| 42 ++ > > +++- > > tests/ref/fate/filter-fps | 6 ++ > > tests/ref/fate/filter-fps-r | 4 &

[FFmpeg-devel] [PATCH] vf_fps: when reading EOF, using current_pts to duplicate the last frame if needed.

Fix ticket #2674 Tested with examples from ticket 2674. --- libavfilter/vf_fps.c| 40 +++- tests/ref/fate/filter-fps | 6 ++ tests/ref/fate/filter-fps-r | 4 tests/ref/fate/m4v-cfr | 1 - 4 files changed, 45 insertions(+), 6

Re: [FFmpeg-devel] [PATCH] lavf/mov.c: Guess video codec delay based on PTS while parsing MOV header.

On Tue, Nov 14, 2017 at 3:23 PM, Derek Buitenhuis < derek.buitenh...@gmail.com> wrote: > On 11/14/2017 10:11 PM, Sasi Inguva wrote: > > I don't know if the patch can be made more generic to work for all > > demuxers, because this patch requires that PTS of all packets be > available > > in the

Re: [FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

On Wed, Oct 25, 2017 at 2:43 PM, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > 2017-10-25 20:38 GMT+02:00 Thierry Foucu <tfo...@gmail.com>: > > > Without the patch, the decoder will return only 29 frames > > Isn't that the correct and expected output? >

Re: [FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

On Wed, Oct 25, 2017 at 4:36 PM, Michael Niedermayer <mich...@niedermayer.cc > wrote: > On Wed, Oct 25, 2017 at 04:21:28PM -0700, Thierry Foucu wrote: > > On Wed, Oct 25, 2017 at 2:43 PM, Carl Eugen Hoyos <ceffm...@gmail.com> > > wrote: > > > > > 201

Re: [FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

Derek, On Wed, Oct 25, 2017 at 9:43 AM, Derek Buitenhuis < derek.buitenh...@gmail.com> wrote: > On 10/25/2017 2:42 AM, Thierry Foucu wrote: > > Changed the return value when no VOD were encoded in Mpeg4 bistream. > > And if we do have already a decoded frames and we a

Re: [FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

On Wed, Oct 25, 2017 at 4:59 AM, Michael Niedermayer <mich...@niedermayer.cc > wrote: > On Tue, Oct 24, 2017 at 06:42:54PM -0700, Thierry Foucu wrote: > > Changed the return value when no VOD were encoded in Mpeg4 bistream. > > And if we do have already a

Re: [FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

Michael, what do you think of this patch? I tried to reflect what the xvid decoder does for those N_VOP frame and in case it is not packed. On Tue, Oct 24, 2017 at 6:42 PM, Thierry Foucu <tfo...@gmail.com> wrote: > Changed the return value when no VOD were encoded in Mpeg4

[FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

Changed the return value when no VOD were encoded in Mpeg4 bistream. And if we do have already a decoded frames and we are not in xvid_packed mode, output the existing decoded frame instead of nothing. --- libavcodec/h263dec.c | 9 - libavcodec/mpeg4videodec.c | 2 +-

[FFmpeg-devel] (no subject)

Michael, the following patch seems to work. I restricted the change to N_VOP (from xvid) frame. I tried to match it with what the xvidcore decoder does for such packets. What do you think? ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

On Thu, Oct 19, 2017 at 3:43 PM, Michael Niedermayer <mich...@niedermayer.cc > wrote: > On Thu, Oct 19, 2017 at 09:51:05AM -0700, Thierry Foucu wrote: > > Instead of returning nothing when we detect the xvid skipped frame, we > > could return the last decoded fra

[FFmpeg-devel] [PATCH] libavcodec/h263dec.c: Duplicate the last decoded frame when xvid marks the packet as skipped.

Instead of returning nothing when we detect the xvid skipped frame, we could return the last decoded frame, if we do have one. --- libavcodec/h263dec.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/libavcodec/h263dec.c b/libavcodec/h263dec.c index

Re: [FFmpeg-devel] [PATCH v3] avcodec: libdav1d AV1 decoder wrapper.

On Wed, Oct 24, 2018 at 4:02 AM Rostislav Pehlivanov wrote: > On Sat, 20 Oct 2018 at 00:50, James Almer wrote: > > > Originally written by Ronald S. Bultje, with fixes, optimizations and > > improvements by James Almer. > > > > Signed-off-by: James Almer > > --- > > Updated to work with

Re: [FFmpeg-devel] [PATCH] libaomenc: Add support for tiles

On Mon, Oct 22, 2018 at 3:45 PM Mark Thompson wrote: > Adds an option to specify the number of tile rows and columns, then uses > a uniform tiling if possible and otherwise a fixed tiling with equal-sized > tiles to fill the frame. > > Also adds -tile-columns and -tile-rows options to make

[FFmpeg-devel] [PATCH] Check if we do have also a filter_complex filter.

Right now, the code check for no filter description, but if we use a filter_complex, the code will use the AVFrame.duration which could be wrong in case of using fps filter. How to reproduce the problem: ffmpeg -f lavfi -i testsrc=duration=1 -vf fps=fps=50 -vsync 1 -f null - output 50 frames

[FFmpeg-devel] [PATCH] [cbs_h2645]: Used av_realloc instead of av_malloc

Follow the description of av_realloc, the memory needs to be allocated by av_realloc. --- libavcodec/cbs_h2645.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/cbs_h2645.c b/libavcodec/cbs_h2645.c index 69ea6dc6bb..8da8421e47 100644 --- a/libavcodec/cbs_h2645.c +++

Re: [FFmpeg-devel] [PATCH] [cbs_h2645]: Used av_realloc instead of av_malloc

On Tue, Aug 27, 2019 at 6:39 AM Paul B Mahol wrote: > Probably OK > Thanks Paul. Any change to have someone to push it? Cheers > > On Mon, Aug 26, 2019 at 10:51 PM Thierry Foucu wrote: > > > Follow the description of av_realloc, the memory needs to be alloca

Re: [FFmpeg-devel] [PATCH] avfilter/vf_fps: Avoid inlink fifo build up.

ping? On Wed, Aug 28, 2019 at 7:14 PM Nikolas Bowe wrote: > When duplicating frames we need to schedule for activation again, > otherwise frames can build up in the inlink fifo. > --- > libavfilter/vf_fps.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [FFmpeg-devel] [PATCH] aformat/movenc: add missing padding to output track extradata

On Wed, Sep 25, 2019 at 10:30 AM James Almer wrote: > Fixes ticket #8183. > > Signed-off-by: James Almer > --- > libavformat/movenc.c | 15 ++- > 1 file changed, 10 insertions(+), 5 deletions(-) > > diff --git a/libavformat/movenc.c b/libavformat/movenc.c > index

[FFmpeg-devel] [PATCH 2/2] [monvenc] Add extra padding when allocating trk->vos_data

trk->vos_data is mostly used to store the extradata from the codec. Most encoder when storing their extradata, are allocating with padding. But the current code was ignoring the padding, which could causes heap-buffer-overflow --- libavformat/movenc.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [FFmpeg-devel] [PATCH 2/2] [monvenc] Add extra padding when allocating trk->vos_data

On Thu, Sep 26, 2019 at 11:00 AM James Almer wrote: > On 9/26/2019 2:58 PM, Thierry Foucu wrote: > > trk->vos_data is mostly used to store the extradata from the codec. > > Most encoder when storing their extradata, are allocating with padding. > > But the current code

Re: [FFmpeg-devel] [PATCH] [libdav1d.c]: Add option to output all the spatial layers.

On Thu, Nov 14, 2019 at 9:20 AM James Almer wrote: > On 11/14/2019 2:15 PM, Thierry Foucu wrote: > > Set the option to false by default, to match libaomdec wrapper. > > --- > > libavcodec/libdav1d.c | 4 > > 1 file changed, 4 insertions(+) > > > &g

[FFmpeg-devel] [PATCH] [libdav1d.c]: Add option to output all the spatial layers.

Set the option to false by default, to match libaomdec wrapper. --- libavcodec/libdav1d.c | 4 1 file changed, 4 insertions(+) diff --git a/libavcodec/libdav1d.c b/libavcodec/libdav1d.c index cf4b178f1d..5efa8eeb48 100644 --- a/libavcodec/libdav1d.c +++ b/libavcodec/libdav1d.c @@ -40,6

[FFmpeg-devel] [PATCH] [libdav1d.c]: Add options for spatial layers.

Disable by default to output all the layers, to match libaomdec wrapper. Add option to select the operating point for the spatial layers. --- libavcodec/libdav1d.c | 8 1 file changed, 8 insertions(+) diff --git a/libavcodec/libdav1d.c b/libavcodec/libdav1d.c index

Re: [FFmpeg-devel] [PATCH] [libdav1d.c]: Add option to output all the spatial layers.

On Thu, Nov 14, 2019 at 11:33 AM Ronald S. Bultje wrote: > Hi, > > On Thu, Nov 14, 2019 at 2:12 PM Andrey Semashev > > wrote: > > > I think there needs to be some consistency across different lavc > > decoders. If we consider that lavc should produce one decoded frame per > > one encoded one,

Re: [FFmpeg-devel] [PATCH] [libdav1d.c]: Add options for spatial layers.

On Thu, Nov 14, 2019 at 9:36 AM Thierry Foucu wrote: > Disable by default to output all the layers, to match libaomdec wrapper. > Add option to select the operating point for the spatial layers. > --- > libavcodec/libdav1d.c | 8 > 1 file changed, 8 insertions(+)

[FFmpeg-devel] [PATCH] [libdav1d.c]: Add options for spatial layers.

Disable by default to output all the layers, to match libaomdec wrapper. Add option to select the operating point for the spatial layers. Update the documentation with the new options. --- doc/decoders.texi | 6 ++ libavcodec/libdav1d.c | 8 2 files changed, 14 insertions(+)

Re: [FFmpeg-devel] [PATCH] [libdav1d.c]: Add options for spatial layers.

On Wed, Nov 20, 2019 at 9:55 AM Thierry Foucu wrote: > > > On Thu, Nov 14, 2019 at 9:36 AM Thierry Foucu wrote: > >> Disable by default to output all the layers, to match libaomdec wrapper. >> Add option to select the operating point for the spatial layers. >> ---

[FFmpeg-devel] [PATCH] [libdav1d.c]: Add options for spatial layers.

Disable by default to output all the layers, to match libaomdec wrapper. Add option to select the operating point for the spatial layers. Update the documentation with the new options. --- doc/decoders.texi | 6 ++ libavcodec/libdav1d.c | 8 2 files changed, 14 insertions(+)

Re: [FFmpeg-devel] [PATCH] [libdav1d.c]: Add options for spatial layers.

On Wed, Nov 27, 2019 at 4:02 PM James Almer wrote: > On 11/27/2019 9:00 PM, Moritz Barsnick wrote: > > On Wed, Nov 27, 2019 at 09:21:28 -0800, Thierry Foucu wrote: > >> +@item oppoint > >> +Select an operating point of a scalable AV1 bitstream (0 - 32) > > [...

Re: [FFmpeg-devel] [PATCH 03/12] lavfi: drop vf_qp

Kempf - President > +33 672 704 734 > ___ > 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

Re: [FFmpeg-devel] [PATCH] Workaround to build ffmpeg on MacOs 10.15

On Fri, Jan 3, 2020 at 1:56 PM Nicolas George wrote: > Thierry Foucu (12020-01-03): > > So, right now, we cannot build ffmpeg with optimization on Mac Os 10.15. > > Can't you pass the option as extra-cflags to configure? It should work, > until a proper fix is proposed. >

Re: [FFmpeg-devel] [PATCH] Workaround to build ffmpeg on MacOs 10.15

To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". -- --- Thierry Foucu ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmp

[FFmpeg-devel] [PATCH] configure: Add llviddsp to mvha deps

--- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index 8b17134944..2d2e4d8817 100755 --- a/configure +++ b/configure @@ -2790,7 +2790,7 @@ msmpeg4v3_decoder_select="h263_decoder" msmpeg4v3_encoder_select="h263_encoder"

Re: [FFmpeg-devel] [PATCH] libavformat/matroskaenc.c: Check if we can seek before writing the end of the ebml of the segment.

Thanks Andreas On Wed, Mar 11, 2020 at 5:35 PM Andreas Rheinhardt < andreas.rheinha...@gmail.com> wrote: > Thierry Foucu: > > On Wed, Mar 11, 2020 at 10:13 AM Andreas Rheinhardt < > > andreas.rheinha...@gmail.com> wrote: > > > >> Thierry Foucu: >

[FFmpeg-devel] [PATCH] configure: Add llviddsp to mvha select

--- configure | 1 + 1 file changed, 1 insertion(+) diff --git a/configure b/configure index 8b17134944..6ceb0c7af4 100755 --- a/configure +++ b/configure @@ -2791,6 +2791,7 @@ msmpeg4v3_encoder_select="h263_encoder" mss2_decoder_select="mpegvideo qpeldsp vc1_decoder"

Re: [FFmpeg-devel] [PATCH] configure: Add llviddsp to mvha deps

___ > 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". -- Thierry Foucu

[FFmpeg-devel] [PATCH] libavformat/matroskaenc.c: Check if we can seek before writing the end of the ebml of the segment.

--- libavformat/matroskaenc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/matroskaenc.c b/libavformat/matroskaenc.c index 42f21eae8b..cf436f9e3e 100644 --- a/libavformat/matroskaenc.c +++ b/libavformat/matroskaenc.c @@ -2630,7 +2630,7 @@ static int

Re: [FFmpeg-devel] [PATCH] libavformat/matroskaenc.c: Check if we can seek before writing the end of the ebml of the segment.

On Wed, Mar 11, 2020 at 10:13 AM Andreas Rheinhardt < andreas.rheinha...@gmail.com> wrote: > Thierry Foucu: > > --- > > libavformat/matroskaenc.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/libavformat/matroskaenc.

Re: [FFmpeg-devel] [PATCH]lavc/sbc: Remove bool usage

; > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". -- Thierry Foucu ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH]lavc/sbc: Remove bool usage

y, I am not familiar with PPC...) > > - Derek > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-de

Re: [FFmpeg-devel] [PATCH]lavc/sbc: Remove bool usage

On Thu, Apr 2, 2020 at 11:18 AM Thierry Foucu wrote: > > > On Thu, Apr 2, 2020 at 11:11 AM Derek Buitenhuis < > derek.buitenh...@gmail.com> wrote: > >> On 02/04/2020 17:47, Moritz Barsnick wrote: >> > I though this was the practical argument?: >> >

Re: [FFmpeg-devel] [PATCH] [libavformat/mov.c] Read the QT Metadata Keys only once

On Mon, May 11, 2020 at 9:35 AM Thierry Foucu wrote: > If you have a file with multiple Metadata Keys, the second time you parse > the keys, you will re-alloc c->meta_keys without freeing the old one. > This change will avoid parsing all the consecutive Metadata keys. > --- >

Re: [FFmpeg-devel] [PATCH] [libavformat/mov.c] Read the QT Metadata Keys only once

On Thu, May 14, 2020 at 12:26 PM Derek Buitenhuis < derek.buitenh...@gmail.com> wrote: > On 14/05/2020 18:19, Thierry Foucu wrote: > > Looking at > > > https://developer.apple.com/library/archive/documentation/QuickTime/QTFF/Metadata/Metadata.html > > The spec

Re: [FFmpeg-devel] [PATCH] [libavformat/mov.c] Read the QT Metadata Keys only once

On Thu, May 14, 2020 at 5:09 AM Derek Buitenhuis wrote: > On 11/05/2020 17:35, Thierry Foucu wrote: > > If you have a file with multiple Metadata Keys, the second time you parse > > the keys, you will re-alloc c->meta_keys without freeing the old one. > > This chang

[FFmpeg-devel] [PATCH] [libavformat/mov.c] Read the QT Metadata Keys only once

If you have a file with multiple Metadata Keys, the second time you parse the keys, you will re-alloc c->meta_keys without freeing the old one. This change will avoid parsing all the consecutive Metadata keys. --- libavformat/mov.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

Re: [FFmpeg-devel] [PATCH 1/9] libavutil: add API for exporting video frame quantizers

n/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". -- Thierry Foucu ___ 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".

[FFmpeg-devel] [PATCH] [libavformat/moc.c] Read the QT Metadata Keys only once

If you have a file with multiple Metadata Keys, the second time you parse the keys, you will re-alloc c->meta_keys without freeing the old one. This change will avoid parsing all the consecutive Metadata keys. --- libavformat/mov.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

[FFmpeg-devel] [PATCH] libavformat/rmdec.c: Fix Use-of-uninitialized-value in ff_codec_get_id

In case the pb does not contain 4 bytes, the buf[256] will not be initialize before we pass it to ff_codec_get_id --- libavformat/rmdec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/rmdec.c b/libavformat/rmdec.c index a36e693ab2..220aa8aee2 100644 ---

[FFmpeg-devel] [PATCH] libavformat/r3d.c: Fix Use-of-uninitialized-value in filename.

While reading the filename tag, it mays return a EOF and we are still copying the file with uninitialized value. --- libavformat/r3d.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/r3d.c b/libavformat/r3d.c index 7aa0c5a2c3..7ba589530d 100644 ---

[FFmpeg-devel] [PATCH] libavformat/r3d.c: Fix Use-of-uninitialized-value in filename.

While reading the filename tag, it mays return a EOF and we are still copying the file with uninitialized value. --- libavformat/r3d.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/libavformat/r3d.c b/libavformat/r3d.c index 7aa0c5a2c3..d013b8c30e 100644 ---

[FFmpeg-devel] [PATCH] libavformat/ffmetadecc.c: Fix Use-of-uninitialized-value

Check the return value of sscanf as it can return -1(EOF), for example when the first char in the line is 0x00 --- libavformat/ffmetadec.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/libavformat/ffmetadec.c b/libavformat/ffmetadec.c index 45c92f1ff6..0ea89fe3f3

Re: [FFmpeg-devel] [PATCH] avformat/mpeg: Check avio_read() return value in get_pts()

On Fri, Aug 14, 2020, 4:08 PM Michael Niedermayer wrote: > Found-by: Thierry Foucu > Fixes: Use-of-uninitialized-value > Signed-off-by: Michael Niedermayer > --- > libavformat/mpeg.c | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/libavfor

Re: [FFmpeg-devel] [PATCH] libavformat/rmdec.c: Fix Use-of-uninitialized-value in ff_codec_get_id

On Mon, Sep 14, 2020 at 10:49 AM Thierry Foucu wrote: > In case the pb does not contain 4 bytes, the buf[256] will not be > initialize before we pass it to ff_codec_get_id > --- > libavformat/rmdec.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/

Re: [FFmpeg-devel] Create and populate AVStream side data packet with contents of ISOBMFF edit list entries

data packet > > + * The structure is repeated for each entry in the edit list > > + * The number of entries can be calculated > > + * by dividing the packet size by the entry size > > + * Each entry is 20 bytes and is laid out as follows: > > + * @code > > + * s64be segment duration > > + * s64be media time > > + * s16be media rate > > + * s16be media rate fraction > > + * @endcode > > + */ > > +AV_PKT_DATA_EDIT_LIST, > > + > > /** > > * The number of side data types. > > * This is not part of the public API/ABI in the sense that it may > > diff --git a/libavformat/mov.c b/libavformat/mov.c > > index d16840f3df..fbfcdddf3f 100644 > > --- a/libavformat/mov.c > > +++ b/libavformat/mov.c > > @@ -4311,6 +4311,21 @@ static int mov_read_trak(MOVContext *c, > > AVIOContext *pb, MOVAtom atom) > > && sc->time_scale == st->codecpar->sample_rate) { > > st->need_parsing = AVSTREAM_PARSE_FULL; > > } > > + > > +if (sc->elst_data) { > > +int i; > > +uint8_t *elst_data; > > +elst_data = av_stream_new_side_data(st, > > AV_PKT_DATA_EDIT_LIST, sc->elst_count * 20); > > +if (elst_data) { > > +for (i = 0; i < sc->elst_count; i++) { > > +uint32_t media_rate = > > (uint32_t)(sc->elst_data[i].rate * 65536.0); > > +AV_WB64((elst_data+(i*20)), sc->elst_data[i].duration); > > +AV_WB64((elst_data+(i*20)+8), sc->elst_data[i].time); > > +AV_WB32((elst_data+(i*20)+16), media_rate); > > +} > > +} > > +} > > + > > /* Do not need those anymore. */ > > av_freep(>chunk_offsets); > > av_freep(>sample_sizes); > > -- > > 2.27.0 > ___ > 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". -- Thierry Foucu ___ 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".

[FFmpeg-devel] [PATCH] libavformat/mpeg.c: Initialize the buffer uses to read the PTS.

Fixed an Use-of-uninitialized-value --- libavformat/mpeg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/mpeg.c b/libavformat/mpeg.c index 265b2bd1ad..15a768e6e8 100644 --- a/libavformat/mpeg.c +++ b/libavformat/mpeg.c @@ -146,7 +146,7 @@ static int

[FFmpeg-devel] [PATCH] libavcodec/png_parser.c: fix a use_of_uninitialized_value in target_dec_fuzzer.

target_dec_fuzzer is checking for the avpkt.data pointer but if the png parser cannot combine the frame, the poutbuf is not set and so, the avpkt.data is not initialized. --- libavcodec/png_parser.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/libavcodec/png_parser.c

Re: [FFmpeg-devel] [PATCH] libavcodec/png_parser.c: fix a use_of_uninitialized_value in target_dec_fuzzer.

On Thu, Jun 4, 2020 at 11:52 AM James Almer wrote: > On 6/4/2020 3:40 PM, Thierry Foucu wrote: > > target_dec_fuzzer is checking for the avpkt.data pointer but if the > > png parser cannot combine the frame, the poutbuf is not set and so, the > > avpkt.da

[FFmpeg-devel] [PATCH 1/3] libavcodec/png_parser.c: fix a use_of_uninitialized_value in target_dec_fuzzer.

the target_dec_fuzzer is checking for the avpkt.data pointer but if the png parser cannot combine the frame, the poutbuf is not set. --- libavcodec/png_parser.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavcodec/png_parser.c b/libavcodec/png_parser.c index 74f2964118..9ec8551a1b

[FFmpeg-devel] [PATCH 2/3] libavcodec/mlp_parser.c: fix a use_of_uninitialized_value in target_dec_fuzzer.

the target_dec_fuzzer is checking for the avpkt.data pointer but if the mlp parser cannot combine the frame, the poutbuf is not set. --- libavcodec/mlp_parser.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavcodec/mlp_parser.c b/libavcodec/mlp_parser.c index 5d2ddc5a70..e7162f4aa8

[FFmpeg-devel] [PATCH 3/3] libavcodec/bmp_parser.c: fix a use_of_uninitialized_value in target_dec_fuzzer.

the target_dec_fuzzer is checking for the avpkt.data pointer but if the bmp parser cannot combine the frame, the poutbuf is not set. --- libavcodec/bmp_parser.c | 1 + 1 file changed, 1 insertion(+) diff --git a/libavcodec/bmp_parser.c b/libavcodec/bmp_parser.c index cd65f02a2e..700bf27af1

Re: [FFmpeg-devel] [PATCH] libavformat/mov.c: export vendor id as metadata

ping? On Wed, Nov 18, 2020 at 12:09 PM Thierry Foucu wrote: > --- > libavformat/mov.c | 8 ++-- > tests/ref/fate/hapqa-extract-nosnappy-to-hapalphaonly-mov | 1 + > tests/ref/fate/hapqa-extract-nosnappy-to-hapq-mov | 1 + > tes

Re: [FFmpeg-devel] [PATCH] libavformat/mov.c: export vendor id as metadata

On Wed, Nov 18, 2020 at 12:09 PM Thierry Foucu wrote: > --- > libavformat/mov.c | 8 ++-- > tests/ref/fate/hapqa-extract-nosnappy-to-hapalphaonly-mov | 1 + > tests/ref/fate/hapqa-extract-nosnappy-to-hapq-mov | 1 + > tests/ref/

Re: [FFmpeg-devel] [PATCH] libavformat/avidec: Extract more metadata from the header

On Wed, Nov 11, 2020 at 7:39 AM Anton Khirnov wrote: > Quoting Thierry Foucu (2020-11-07 00:10:17) > > --- > > libavformat/avidec.c | 17 + > > 1 file changed, 17 insertions(+) > > > > diff --git a/libavformat/avidec.c b/libavformat/avidec.c

[FFmpeg-devel] [PATCH] libavformat/avidec.c: remove duplicated conversion

ff_riff_info_conv deals with riff metadata already, so, not need to add those metadata in avi_metadata_conv --- libavformat/avidec.c | 8 1 file changed, 8 deletions(-) diff --git a/libavformat/avidec.c b/libavformat/avidec.c index 7e527e15ee..75a76b995d 100644 ---

[FFmpeg-devel] [PATCH] libavformat/mov.c: export vendor id as metadata

--- libavformat/mov.c | 24 +-- ...hapqa-extract-nosnappy-to-hapalphaonly-mov | 1 + .../fate/hapqa-extract-nosnappy-to-hapq-mov | 1 + tests/ref/fate/mov-zombie | 2 +- tests/ref/fate/rgb24-mkv | 4 ++-- 5

Re: [FFmpeg-devel] [PATCH] libavformat/mov.c: export vendor id as metadata

On Wed, Nov 18, 2020 at 12:30 AM Gyan Doshi wrote: > > > On 18-11-2020 12:16 pm, Thierry Foucu wrote: > > On Tue, Nov 17, 2020 at 9:54 PM Gyan Doshi wrote: > > > >> > >> On 18-11-2020 02:41 am, Thierry Foucu wrote: > >>> --- > >>>

  1   2   >