From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/4] avformat: add av_program_copy()
Date: Wed, 8 Feb 2023 21:33:53 +0530
Message-ID: <2ae1feb4-9c74-d65a-e0fb-91eba44042e3@gyani.pro> (raw)
In-Reply-To: <167586944903.10789.14250318518260724434@lain.khirnov.net>
On 2023-02-08 08:47 pm, Anton Khirnov wrote:
> Quoting Gyan Doshi (2023-02-07 15:58:47)
>> Needed to transfer programs in parent muxing contexts to child muxers,
>> like in hls, segment, tee muxers.
> If it's only intended for use in muxers, why is it public?
Could have worded the msg better. The intention wasn't to limit this
internally.
The fn is motivated by a CLI HLS user's troubleshhoting but it is useful
to any API user who uses
the public av_new_program and then copies the data manually.
That reminds me, I should update this to check for existing programs.
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".
prev parent reply other threads:[~2023-02-08 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 14:58 Gyan Doshi
2023-02-07 14:58 ` [FFmpeg-devel] [PATCH 2/4] avformat/hls: relay programs to child muxers Gyan Doshi
2023-02-07 14:58 ` [FFmpeg-devel] [PATCH 3/4] avformat/segment: " Gyan Doshi
2023-02-07 14:58 ` [FFmpeg-devel] [PATCH 4/4] avformat/tee: " Gyan Doshi
2023-02-08 15:17 ` [FFmpeg-devel] [PATCH 1/4] avformat: add av_program_copy() Anton Khirnov
2023-02-08 16:03 ` Gyan Doshi [this message]
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=2ae1feb4-9c74-d65a-e0fb-91eba44042e3@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