From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 2/2] avformat/flvenc: add option to read metadata from file
Date: Tue, 7 Feb 2023 14:27:25 +0530
Message-ID: <79f78a24-3e67-7349-45f7-232546d4d2ca@gyani.pro> (raw)
In-Reply-To: <bf2a3516-e8e2-54df-c84b-79efb8410bba@gyani.pro>
On 2023-02-05 04:35 pm, Gyan Doshi wrote:
>
>
> On 2023-02-05 04:07 pm, Anton Khirnov wrote:
>> Quoting Gyan Doshi (2023-02-04 11:11:12)
>>> On 2023-02-03 09:04 pm, Andreas Rheinhardt wrote:
>>>> What does this achieve that can't be achieved by other means
>>>> (namely by
>>>> an API-user updating the relevant metadata dictionaries)?
>>> This option together with meta_period is for CLI users.
>> Options for CLI users should be in the CLI, not the libraries.
>
> Do I then add and use a AVFMT flag to avoid recurring metadata updates
> for all other muxers?
To add to this, it's not exactly a 'CLI 'option. It allows CLI users the
same feature that API users can manually undertake,
similar to the existence of the tee muxer itself which API users don't need.
But I'll see how this can fit inside fftools, though lavf/mux might be a
better place.
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".
next prev parent reply other threads:[~2023-02-07 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 16:07 [FFmpeg-devel] [PATCH v2 1/2] avformat/flvenc: add option meta_period Gyan Doshi
2023-02-02 16:07 ` [FFmpeg-devel] [PATCH v2 2/2] avformat/flvenc: add option to read metadata from file Gyan Doshi
2023-02-03 15:34 ` Andreas Rheinhardt
2023-02-04 10:11 ` Gyan Doshi
2023-02-04 10:16 ` Paul B Mahol
2023-02-04 10:24 ` Gyan Doshi
2023-02-04 10:32 ` Paul B Mahol
2023-02-04 10:42 ` Gyan Doshi
2023-02-05 10:01 ` Gyan Doshi
2023-02-05 10:09 ` Paul B Mahol
2023-02-05 10:37 ` Anton Khirnov
2023-02-05 11:05 ` Gyan Doshi
2023-02-07 8:57 ` Gyan Doshi [this message]
2023-02-09 15:45 ` Anton Khirnov
2023-02-09 16:14 ` Gyan Doshi
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=79f78a24-3e67-7349-45f7-232546d4d2ca@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