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] ffmpeg: set user-set rotation for encoded streams too
Date: Thu, 12 May 2022 00:45:15 +0530
Message-ID: <b0b35a66-8dd4-5e7d-21f1-fb35ffa7bf5e@gyani.pro> (raw)
In-Reply-To: <165229495558.13099.6133016962596120593@lain>



On 2022-05-12 12:19 am, Anton Khirnov wrote:
> Quoting Gyan Doshi (2022-05-11 14:18:49)
>>
>> On 2022-05-11 05:26 pm, Anton Khirnov wrote:
>>> Quoting Gyan Doshi (2022-05-10 13:40:54)
>>>> So far, -metadata:s:v rotate would only be applied to streamcopied
>>>> video streams.
>>> Using -metadata for this functionality is a hack that should be removed,
>>> not extended.
>> When there's a replacement for CLI users, sure.
>> Till then, there's no need for the disparity to be maintained.
> I disagree. You are adding new behavior, which will need to be
> maintained for backward compatibility and add extra burden on the person
> who would want to implement this properly.
>
> If you want this functionality, just add a new option. It's not that
> hard. There's plenty of hacks in ffmpeg already, we don't need any new
> ones.

All the current state does is force the user to run a 2nd remux command 
to set rotation.
A new option for encoded streams creates a divergent syntax for no 
visible benefit.

If and when a display matrix can be user-specified, it will be easier to 
retire the metadata hack than to change the arg syntax of a newly added 
'rotate' option.

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-05-11 19:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:40 Gyan Doshi
2022-05-11 11:56 ` Anton Khirnov
2022-05-11 12:18   ` Gyan Doshi
2022-05-11 18:49     ` Anton Khirnov
2022-05-11 19:15       ` Gyan Doshi [this message]
2022-05-12  5:25         ` Anton Khirnov
2022-05-12  7:01           ` Gyan Doshi
2022-05-12  8:19             ` Anton Khirnov
2022-05-15 10:59               ` Jan Ekström
2022-05-15 11:58                 ` Gyan Doshi
2022-05-15 12:21                   ` Jan Ekström
2022-05-17 12:16                     ` Jan Ekström
2022-05-11 16:30 ` Gyan Doshi
2022-05-11 18:44   ` Anton Khirnov

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=b0b35a66-8dd4-5e7d-21f1-fb35ffa7bf5e@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