From: "Jan Ekström" <jeebjp@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] ffmpeg: add display_{rotation, hflip, vflip} options
Date: Thu, 19 May 2022 09:27:39 +0300
Message-ID: <CAEu79Sa-EgzuFN-7cgREqu+YNGqwqydLLeV9faRf3DZCQTa_Bg@mail.gmail.com> (raw)
In-Reply-To: <41dcff20-36db-c4e7-5d7f-36c4dc911a2c@gyani.pro>
On Thu, May 19, 2022, 07:21 Gyan Doshi <ffmpeg@gyani.pro> wrote:
>
>
> On 2022-05-18 11:34 pm, Jan Ekström wrote:
> > This enables overriding the rotation as well as horizontal/vertical
> > flip state of a specific video stream on either the input or output
> > side.
>
> Since rotation, flip and scale are stored in a single data structure,
> how about a single option i.e. -display "rotate=90,flip=hv,scale=2"
>
I did think about that, and I even implemented AVDict based options for
ffmpeg.c in a branch. But then pretty much got tired of lack of AVOption
automation (f.ex. for the flip flagging etc), and decided that since these
are relatively basic and simple, the non-generic option for this could be
just three options in the initial submission.
Jan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-05-19 6:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 18:04 Jan Ekström
2022-05-18 18:04 ` [FFmpeg-devel] [PATCH 2/2] ffmpeg: deprecate display rotation override with a metadata key Jan Ekström
2022-05-19 4:21 ` [FFmpeg-devel] [PATCH 1/2] ffmpeg: add display_{rotation, hflip, vflip} options Gyan Doshi
2022-05-19 6:27 ` Jan Ekström [this message]
2022-05-26 11:31 ` Jan Ekström
2022-07-17 15:19 ` Thilo Borgmann
2022-07-17 16:26 ` Gyan Doshi
2022-08-02 16:48 ` Thilo Borgmann
2022-08-02 16:49 ` Thilo Borgmann
2022-08-02 17:10 ` Andreas Rheinhardt
2022-08-02 17:21 ` Thilo Borgmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEu79Sa-EgzuFN-7cgREqu+YNGqwqydLLeV9faRf3DZCQTa_Bg@mail.gmail.com \
--to=jeebjp@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git