Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] ffmpeg: add display_{rotation, hflip, vflip} options
Date: Sun, 17 Jul 2022 21:56:20 +0530
Message-ID: <64edef9e-5052-d335-5dc3-97aa9e23f989@gyani.pro> (raw)
In-Reply-To: <64c6b7ce-671a-1a03-45e1-cad08a8cf04c@mail.de>



On 2022-07-17 08:49 pm, Thilo Borgmann wrote:
> Hi,
>
> Am 26.05.22 um 13:31 schrieb Jan Ekström:
>> On Thu, May 19, 2022 at 9:27 AM Jan Ekström <jeebjp@gmail.com> wrote:
>>>
>>> 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.
>>
>> In the end I did implement this with a single dict-based thing in a
>> branch but never got to posting it to this thread:
>> https://github.com/jeeb/ffmpeg/commits/ffmpeg_c_display_matrix_with_dicts 
>>
>>
>> So for the positive: Now it's all in a single option so it's clear
>> that it's defining a single structure.
>> And the negative: Needs a struct definition, struct, AVOption list,
>> AVClass and actually if you already made a dict out of the options
>> before, as the functions will free the original after usage and
>> generate a new one, it destroys the life time expectations of the dict
>> and thus it is just simpler to copy the dict when entering the
>> function (I think there is an arguments string based API which might
>> or might not actually be simpler for this case).
>>
>> So yea, not sure if I prefer this version.
>
> Ping.
>
> Did this stall for a reason? How can we iterate on it?

Since the rotation/flip/scale hints are stored in a single data 
structure, I prefer a single user option to set those values.

Regards,
Gyan
_______________________________________________
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".

  reply	other threads:[~2022-07-17 16:26 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
2022-05-26 11:31     ` Jan Ekström
2022-07-17 15:19       ` Thilo Borgmann
2022-07-17 16:26         ` Gyan Doshi [this message]
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=64edef9e-5052-d335-5dc3-97aa9e23f989@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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