Re: [FFmpeg-devel] Quo vadis, code of conduct?

On 5/6/19, Nicolas George wrote: > Nicolas George (12019-05-06): >> Hi. Replying in private to avoid feeding the flame. > > Well, fumbled that. Yet, what I said was true and I made no judgement in > my mail. I singled somebody, but since it was specifically who would > have been in breach of the C

Re: [FFmpeg-devel] [PATCH] lavfi/gblur: doing several columns at the same time

On 5/6/19, Ruiling Song wrote: > Instead of doing each column one by one, doing several columns > together gives about 30% better performance. > > Signed-off-by: Ruiling Song > --- > below is some of performance numbers(fps) on my i7-6770HQ (decode + gblur): > > resolution:480p | 720p

Re: [FFmpeg-devel] [DECISION] scaletempo filter

On 5/6/19, Marton Balint wrote: > > > On Sat, 4 May 2019, John Warburton wrote: > >> On Sat, May 4, 2019 at 3:34 PM Nicolas George wrote: >> >>> John Warburton (12019-05-04): >>> >>> > Is there a patch I can use to test scaletempo to compare it against >>> atempo? >>> > It'll be no trouble to do

Re: [FFmpeg-devel] [PATCH v2 2/2] fftools/ffmpeg: Add stream metadata from first frame's metadata

Jun Li (12019-05-05): > Fix #6945 > Exif extension has 'Orientaion' field for image flip and rotation. > This change is to add the first frame's exif into stream so that > autorotation would use the info to adjust the frames. What happens if not all frames have the same orientation? Regards, --

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On 5/6/19, Lynne wrote: > May 5, 2019, 1:52 PM by d...@lynne.ee: > >> May 4, 2019, 10:00 PM by > d...@lynne.ee > : >> >>> May 4, 2019, 8:10 PM by > >> mich...@niedermayer.cc >>> >> > mich...@niedermayer.cc >>> >>

[FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

Signed-off-by: Paul B Mahol --- Makes ffplay display correct timestamps when seeking. --- libavfilter/af_atempo.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index bfdad7d76b..6a23d59641 100644 --- a/libavfilter/af_a

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On Mon, May 6, 2019, 06:42 Paul B Mahol wrote: > Signed-off-by: Paul B Mahol > --- > Makes ffplay display correct timestamps when seeking. > --- > libavfilter/af_atempo.c | 8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/libavfilter/af_atempo.c b/libavfilter/af_ate

Re: [FFmpeg-devel] [PATCH] avfilter/af_atempo: offset all output timestamps by same amount of first input timestamp

On Mon, May 6, 2019, 07:28 Pavel Koshevoy wrote: > > > On Mon, May 6, 2019, 06:42 Paul B Mahol wrote: > >> Signed-off-by: Paul B Mahol >> --- >> Makes ffplay display correct timestamps when seeking. >> --- >> libavfilter/af_atempo.c | 8 +++- >> 1 file changed, 7 insertions(+), 1 deletion(

Re: [FFmpeg-devel] [DECISION] Project policy on closed source components

On 28/04/2019 21:02, Marton Balint wrote: > 1) Should libNDI support be removed from the ffmpeg codebase? Yes. - Mark ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link abov

Re: [FFmpeg-devel] [PATCH V2 2/2] lavfi/opencl: add nlmeans_opencl filter

On 29/04/2019 03:06, Song, Ruiling wrote:> > In order to verify the patch, I also have more testing on the CPU OpenCL > driver from Intel. > I make it run 100 times, and still not see any reported overflow. So I think > we can say the filter is in good quality to be merged. Any different idea?

[FFmpeg-devel] [PATCH 1/7] ffmpeg_hw: Mark some strings as const

--- fftools/ffmpeg.h| 2 +- fftools/ffmpeg_hw.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fftools/ffmpeg.h b/fftools/ffmpeg.h index eb1eaf6363..7b6f802082 100644 --- a/fftools/ffmpeg.h +++ b/fftools/ffmpeg.h @@ -72,7 +72,7 @@ typedef struct HWAccel { } HWAccel;

[FFmpeg-devel] [PATCH 7/7] hwcontext_qsv: Try to select a matching VAAPI device by default

Tries to find a device backed by the i915 kernel driver and loads the iHD VAAPI driver to use with it. This reduces confusion on machines with multiple DRM devices and removes the surprising requirement to set the LIBVA_DRIVER_NAME environment variable to use libmfx at all. --- libavutil/hwcontex

[FFmpeg-devel] [PATCH 2/7] ffmpeg_hw: Treat empty device string as no device setting

The implementation will use some default in this case. The empty string is not a meaningful device for any existing hardware type, and indeed OpenCL treats it identically to no device already to work around the lack of this setting on the command line. --- fftools/ffmpeg_hw.c | 13 -

[FFmpeg-devel] [PATCH 4/7] hwcontext_vaapi: Make default DRM device selection more helpful

Iterate over available render devices and pick the first one which looks usable. Adds an option to specify the name of the kernel driver associated with the desired device, so that it is possible to select a specific type of device in a multiple-device system without knowing the card numbering. F

[FFmpeg-devel] [PATCH 3/7] hwcontext_vaapi: Add option to specify connection type

Can be set to "drm" or "x11" to force a specific connection type. --- libavutil/hwcontext_vaapi.c | 32 1 file changed, 28 insertions(+), 4 deletions(-) diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c index 8624369bb9..561b82fcce 100644 ---

[FFmpeg-devel] [PATCH 5/7] hwcontext_vaapi: Add option to set driver name

For example: -init_hw_device vaapi:/dev/dri/renderD128,driver=foo This may be more convenient that using the environment variable, and allows loading different drivers for different devices in the same process. --- libavutil/hwcontext_vaapi.c | 19 +++ 1 file changed, 19 insertion

[FFmpeg-devel] [PATCH 6/7] hwcontext_vaapi: Try to create devices via DRM before X11

Opening the device via X11 (DRI2/DRI3) rather than opening a DRM render node directly is only useful if you intend to use the legacy X11 interop functions. That's never true for the ffmpeg utility, and a library user who does want this will likely provide their own display instance rather than mak

Re: [FFmpeg-devel] [PATCH v3 2/4] cbs_mpeg2: Improve checks for invalid values

On 28/04/2019 23:15, Andreas Rheinhardt wrote: > Mark Thompson: >> On 23/04/2019 23:55, Andreas Rheinhardt wrote: >>> horizontal/vertical_size_value (containing the twelve least significant >>> bits of the frame size) mustn't be zero according to the specifications; >>> and the value 0 is forbidden

[FFmpeg-devel] [PATCH] vaapi_encode: Refactor encode misc parameter buffer creation

This removes the use of the nonstandard combined structures, which generated some warnings with clang and will cause alignment problems with some parameter buffer types. --- On 27/03/2019 14:18, Carl Eugen Hoyos wrote: > Attached patch fixes many warnings when compiling vaapi with clang. > Also tes

Re: [FFmpeg-devel] [DECISION] scaletempo filter

On Mon, 6 May 2019, Paul B Mahol wrote: On 5/6/19, Marton Balint wrote: On Sat, 4 May 2019, John Warburton wrote: On Sat, May 4, 2019 at 3:34 PM Nicolas George wrote: John Warburton (12019-05-04): > Is there a patch I can use to test scaletempo to compare it against atempo? > It'll b

Re: [FFmpeg-devel] [DECISION] scaletempo filter

On Mon, 6 May 2019, Marton Balint wrote: On Mon, 6 May 2019, Paul B Mahol wrote: On 5/6/19, Marton Balint wrote: On Sat, 4 May 2019, John Warburton wrote: On Sat, May 4, 2019 at 3:34 PM Nicolas George wrote: John Warburton (12019-05-04): > Is there a patch I can use to test scale

[FFmpeg-devel] [PATCH] fftools/ffprobe.c: Add to ffprobe S12M Timecode (such as SEI TC) as side data of show frame

Add to ffprobe S12M Timecode (such as SEI TC) as side data with -show_frame option. This has been previously implemented in libav but partialy not in ffprobe. Thanks in advance ! ffprobe_S12M_TC_Side_data.patch Description: Binary data ___ ffmpeg-deve

[FFmpeg-devel] [PATCH v4 4/5] lavc/h265_profile_level: Add unit test

Operates in the same way as the h264-levels test. --- libavcodec/Makefile| 1 + libavcodec/tests/h265_levels.c | 297 + tests/fate/libavcodec.mak | 5 + 3 files changed, 303 insertions(+) create mode 100644 libavcodec/tests/h265_levels.c diff

[FFmpeg-devel] [PATCH v4 3/5] h265_metadata: Add option to set the level of the stream

To match the same option in h264_metadata. --- doc/bitstream_filters.texi | 9 +++ libavcodec/Makefile| 2 +- libavcodec/h265_metadata_bsf.c | 136 + 3 files changed, 146 insertions(+), 1 deletion(-) diff --git a/doc/bitstream_filters.texi b/doc

[FFmpeg-devel] [PATCH v4 1/5] lavc/h265_profile_level: Fix DPB size calculation

The maxDpbPicBuf value which is used in the DPB size calculation depends on the profile (it's usually 6, but 7 for screen-extended profiles). --- libavcodec/h265_profile_level.c | 86 - libavcodec/h265_profile_level.h | 1 + 2 files changed, 44 insertions(+), 43 de

[FFmpeg-devel] [PATCH v4 2/5] lavc/h265_profile_level: Do not allow high tier at level < 4

--- libavcodec/h265_profile_level.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/libavcodec/h265_profile_level.c b/libavcodec/h265_profile_level.c index 692252bb4d..126f8dbc2a 100644 --- a/libavcodec/h265_profile_level.c +++ b/libavcodec/h265_profile_leve

[FFmpeg-devel] [PATCH v4 5/5] lavc/h265_profile_level: Add new profiles

Monochrome 10 and Main 10 Still Picture profiles are added by the 2018 version of the standard. --- libavcodec/h265_profile_level.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/libavcodec/h265_profile_level.c b/libavcodec/h265_profile_level.c index 126f8dbc2a..70db1a52f

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On Mon, May 06, 2019 at 02:23:26AM +0200, Lynne wrote: > May 5, 2019, 1:52 PM by d...@lynne.ee: > > > May 4, 2019, 10:00 PM by > d...@lynne.ee > : > > > >> May 4, 2019, 8:10 PM by > >> mich...@niedermayer.cc > >> >> > mich...@niedermayer.cc >

Re: [FFmpeg-devel] [PATCH v2 2/2] fftools/ffmpeg: Add stream metadata from first frame's metadata

On Mon, May 6, 2019 at 1:52 AM Nicolas George wrote: > Jun Li (12019-05-05): > > Fix #6945 > > Exif extension has 'Orientaion' field for image flip and rotation. > > This change is to add the first frame's exif into stream so that > > autorotation would use the info to adjust the frames. > > What

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On 5/6/2019 6:26 PM, Michael Niedermayer wrote: > also i agree with paul, the API looks good > implementation not really reviewed I don't like the avfft_* namespace. It's unlike other modules we have. Since av_fft_* is taken by the lavc implementation and can't be used, maybe this one could be av

Re: [FFmpeg-devel] [PATCH v2 2/2] fftools/ffmpeg: Add stream metadata from first frame's metadata

Am Mo., 6. Mai 2019 um 05:41 Uhr schrieb Jun Li : > +uint8_t* sd = NULL; Wouldn't it simplify the patch if this were a pointer to int32_t? Or is there a aliasing violation that can't be avoided? > +if (entry) { > +orientation = atoi(entry->value); > +sd = av_stream_new_sid

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

Am Di., 7. Mai 2019 um 00:03 Uhr schrieb James Almer : > > On 5/6/2019 6:26 PM, Michael Niedermayer wrote: > > also i agree with paul, the API looks good > > implementation not really reviewed > > I don't like the avfft_* namespace. It's unlike other modules we have. > > Since av_fft_* is taken by

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On Mon, May 06, 2019 at 07:02:54PM -0300, James Almer wrote: > On 5/6/2019 6:26 PM, Michael Niedermayer wrote: > > also i agree with paul, the API looks good > > implementation not really reviewed > > I don't like the avfft_* namespace. It's unlike other modules we have. > > Since av_fft_* is tak

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On 5/6/2019 7:04 PM, Carl Eugen Hoyos wrote: > Am Di., 7. Mai 2019 um 00:03 Uhr schrieb James Almer : >> >> On 5/6/2019 6:26 PM, Michael Niedermayer wrote: >>> also i agree with paul, the API looks good >>> implementation not really reviewed >> >> I don't like the avfft_* namespace. It's unlike oth

Re: [FFmpeg-devel] [PATCH V5 1/2] configure: sort decoder/encoder/filter/... names in alphabet order

On 2019-05-05 21:14 +, avih wrote: > > I guess you were looking at the right patch. I mean this one: > >   http://ffmpeg.org/pipermail/ffmpeg-devel/2019-May/243380.html > > I was referring to this patch indeed. Thanks. > > > > > > Agreed; of course we shouldn't just use awk because we can. > >

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On Tue, May 07, 2019 at 12:15:37AM +0200, Michael Niedermayer wrote: > On Mon, May 06, 2019 at 07:02:54PM -0300, James Almer wrote: > > On 5/6/2019 6:26 PM, Michael Niedermayer wrote: > > > also i agree with paul, the API looks good > > > implementation not really reviewed > > > > I don't like the

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote: > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. > > I don't think it is a good idea to drop frames from CFR input just because > they > are duplicated, that can cause issues for API users expecting CFR input. Also > it

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

On Mon, May 06, 2019 at 02:23:26 +0200, Lynne wrote: > This allowed for the exptabs to be computed just once on startup and > stored in a global array. I have no real understanding of this, but: Would there be a desire for a static implementation as well, for those using "-enable-hardcoded-tables"

Re: [FFmpeg-devel] [PATCH v2 2/2] fftools/ffmpeg: Add stream metadata from first frame's metadata

On Mon, May 6, 2019 at 3:04 PM Carl Eugen Hoyos wrote: > Am Mo., 6. Mai 2019 um 05:41 Uhr schrieb Jun Li : > > +uint8_t* sd = NULL; > > Wouldn't it simplify the patch if this were a pointer to int32_t? > Or is there a aliasing violation that can't be avoided? > Thanks Carl for review. Will a

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

May 6, 2019, 11:41 PM by barsn...@gmx.net: > On Mon, May 06, 2019 at 02:23:26 +0200, Lynne wrote: > >> This allowed for the exptabs to be computed just once on startup and >> stored in a global array. >> > > I have no real understanding of this, but: > Would there be a desire for a static implemen

Re: [FFmpeg-devel] [PATCH] libavutil: add an FFT & MDCT implementation

May 6, 2019, 11:11 PM by jamr...@gmail.com: > On 5/6/2019 7:04 PM, Carl Eugen Hoyos wrote: > >> Am Di., 7. Mai 2019 um 00:03 Uhr schrieb James Almer <>> jamr...@gmail.com >> >> >: >> >>> >>> On 5/6/2019 6:26 PM, Michael Niedermayer wrote: >>> also i agree with pa

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer wrote: > > On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote: > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. > > > > I don't think it is a good idea to drop frames from CFR input just because > > they > > are dupli

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

On Tue, May 7, 2019 at 1:39 AM Hendrik Leppkes wrote: > > On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer > wrote: > > > > On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote: > > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. > > > > > > I don't think it is a good

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

On Tue, 7 May 2019, Michael Niedermayer wrote: On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote: This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. I don't think it is a good idea to drop frames from CFR input just because they are duplicated, that can cause issues fo

Re: [FFmpeg-devel] [PATCH 01/15] avformat/matroskaenc: Fix relative timestamp check

Andreas Rheinhardt: > At this point, ts already includes the ts_offset so that the relative > time written with the cluster is already given by ts - mkv->cluster_pts. > It is this number that needs to fit into an int16_t. > > Signed-off-by: Andreas Rheinhardt > --- > The only difference between t

Re: [FFmpeg-devel] [PATCHv2] lavfi: add gblur_opencl filter

Anyone have any comments/feedback? On Sat, 27 Apr 2019 at 1:05 am, Dylan Fernando wrote: > --- > configure | 1 + > doc/filters.texi | 28 > libavfilter/Makefile | 2 + > libavfilter/allfilters.c | 1 + > libavfilter/opencl/gblur.cl |

Re: [FFmpeg-devel] [PATCH] lavfi/gblur: doing several columns at the same time

> -Original Message- > From: Paul B Mahol [mailto:one...@gmail.com] > Sent: Monday, May 6, 2019 4:02 PM > To: FFmpeg development discussions and patches de...@ffmpeg.org> > Cc: Song, Ruiling > Subject: Re: [FFmpeg-devel] [PATCH] lavfi/gblur: doing several columns at > the same time > >

Re: [FFmpeg-devel] [PATCH V2 2/2] lavfi/opencl: add nlmeans_opencl filter

> -Original Message- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > Of Mark Thompson > Sent: Monday, May 6, 2019 10:20 PM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH V2 2/2] lavfi/opencl: add > nlmeans_opencl filter > > On 29/04/2019 03:0

Re: [FFmpeg-devel] [PATCH 6/7] hwcontext_vaapi: Try to create devices via DRM before X11

On Mon, May 6, 2019 at 10:56 PM Mark Thompson wrote: > > Opening the device via X11 (DRI2/DRI3) rather than opening a DRM render > node directly is only useful if you intend to use the legacy X11 interop > functions. That's never true for the ffmpeg utility, and a library user > who does want thi

Re: [FFmpeg-devel] [PATCH 5/7] hwcontext_vaapi: Add option to set driver name

On Mon, May 6, 2019 at 10:55 PM Mark Thompson wrote: > > For example: -init_hw_device vaapi:/dev/dri/renderD128,driver=foo > > This may be more convenient that using the environment variable, and allows > loading different drivers for different devices in the same process. > --- > libavutil/hwcon

[FFmpeg-devel] [PATCH V3] lavfi/opencl: add nlmeans_opencl filter

Signed-off-by: Ruiling Song --- configure | 1 + doc/filters.texi| 4 + libavfilter/Makefile| 1 + libavfilter/allfilters.c| 1 + libavfilter/opencl/nlmeans.cl | 115 + libavfilter/opencl_source.h | 1 + libavfilter

Re: [FFmpeg-devel] [PATCH V1 0/2] Use avctx->framerate first for frame rate setting

On Sun, May 5, 2019 at 11:23 AM myp...@gmail.com wrote: > > On Sun, May 5, 2019 at 9:31 AM Carl Eugen Hoyos wrote: > > > > Am So., 5. Mai 2019 um 03:23 Uhr schrieb myp...@gmail.com > > : > > > > > > On Sun, Apr 28, 2019 at 7:02 PM myp...@gmail.com wrote: > > > > > > > > On Sun, Apr 28, 2019 at

Re: [FFmpeg-devel] [PATCH V5 1/2] configure: sort decoder/encoder/filter/... names in alphabet order

> -Original Message- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of > Alexander Strasser > Sent: Tuesday, May 07, 2019 6:21 AM > To: FFmpeg development discussions and patches > Subject: Re: [FFmpeg-devel] [PATCH V5 1/2] configure: sort > decoder/encoder/filte

Re: [FFmpeg-devel] [PATCH 0/3] *** VDPAU: HEVC YUV 4:4:4 Support ***

On Mon, 6 May 2019 03:33:58 + Manoj Bonda wrote: > Thanks Philip for pushing the changes, sorry for the churn. > > I am not familiar with the MPV code much, but from a quick check by > enabling the direct mode for 444 surfaces by modifying the condition > > p->direct_mode = mapper->dst

[FFmpeg-devel] [PATCH] avformat/mpegts: index only keyframes to ensure accurate seeks

From: Aman Gupta Signed-off-by: Aman Gupta --- libavformat/mpegts.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavformat/mpegts.c b/libavformat/mpegts.c index 8a84e5cc19..49e282903c 100644 --- a/libavformat/mpegts.c +++ b/libavformat/mpegts.c @@ -3198,9 +3198,9 @@

[FFmpeg-devel] [PATCH] avformat/mpegts: apply -merge_pmt_versions only when versions change

From: Aman Gupta Previously the code assumed that stream_identifier was unique per stream in the PMT, as suggested by the spec. However, I found some samples from Finland MTV3 where this is not the case. PID 0231 ( 561) -> Stream type 04 ( 4) 13818-3 audio (MPEG-2) ES info (17 bytes

[FFmpeg-devel] [PATCH] avutil: Add NV24 and NV42 pixel formats

These are the 4:4:4 variants of the semi-planar NV12/NV21 formats. I'm surprised we've not had a reason to add them until now, but they are the format that VDPAU uses when doing interop for 4:4:4 surfaces. Signed-off-by: Philip Langdale --- libavutil/pixdesc.c | 24 +++

[FFmpeg-devel] [PATCH v3] lavf/h264: add support for h264 video from Arecont camera, fixes ticket #5154

The patch is for ticket #5154. I have improved the patch as suggested. Please review. Thank you, Shivam GoyalFrom 2aa843626f939218179d3ec252f76f9991c33ed6 Mon Sep 17 00:00:00 2001 From: Shivam Goyal Date: Tue, 7 May 2019 10:01:15 +0530 Subject: [PATCH] lavf/h264: Add support for h264 video

[FFmpeg-devel] [PATCH v3 1/2] fftools/ffmpeg_filter, ffplay: Add flip support to rotation

Current implemantion for autoratation does not support flip. That is, if the matrix contains flip info, the API get_rotation only reflects partial information. This change is for adding support for hflip (vflip can be achieved by rotation+hflip). --- fftools/cmdutils.c| 4 ++-- fftools/cm

[FFmpeg-devel] [PATCH v3 2/2] fftools/ffmpeg: Add stream metadata from first frame's metadata

Fix #6945 Exif extension has 'Orientaion' field for image flip and rotation. This change is to add the first frame's exif into stream so that autorotation would use the info to adjust the frames. --- fftools/ffmpeg.c | 57 +++- 1 file changed, 56 inserti

Re: [FFmpeg-devel] [PATCH V5 1/2] configure: sort decoder/encoder/filter/... names in alphabet order

Am 7. Mai 2019 04:07:23 MESZ schrieb "Guo, Yejun" : > >> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf >Of >> Alexander Strasser >> Sent: Tuesday, May 07, 2019 6:21 AM >> To: FFmpeg development discussions and patches > >> Subject: Re: [FFmpeg-devel] [PATCH V5 1/2] configu