From: Gyan Doshi <ffmpeg@gyani.pro> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH v4 5/5] avformat/tee: relay programs to child muxers Date: Sat, 18 Feb 2023 10:19:49 +0530 Message-ID: <20230218044949.1179-5-ffmpeg@gyani.pro> (raw) In-Reply-To: <20230218044949.1179-1-ffmpeg@gyani.pro> --- libavformat/tee.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/libavformat/tee.c b/libavformat/tee.c index cb555f52fd..e81f9ba706 100644 --- a/libavformat/tee.c +++ b/libavformat/tee.c @@ -295,6 +295,14 @@ FF_ENABLE_DEPRECATION_WARNINGS } } + for (i = 0; i < avf->nb_programs; i++) { + ret = av_program_copy(avf2, (const AVFormatContext *)avf, avf->programs[i]->id, 0); + if (ret < 0) { + av_log(avf, AV_LOG_ERROR, "unable to transfer program %d to child muxer\n", avf->programs[i]->id); + return ret; + } + } + ret = ff_format_output_open(avf2, filename, &options); if (ret < 0) { av_log(avf, AV_LOG_ERROR, "Slave '%s': error opening: %s\n", slave, -- 2.39.1 _______________________________________________ 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-18 4:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-18 4:49 [FFmpeg-devel] [PATCH v4 1/5] avformat: add av_program_add_stream_index2() Gyan Doshi 2023-02-18 4:49 ` [FFmpeg-devel] [PATCH v4 2/5] avformat: add av_program_copy() Gyan Doshi 2023-02-20 16:29 ` Anton Khirnov 2023-02-18 4:49 ` [FFmpeg-devel] [PATCH v4 3/5] avformat/hls: relay programs to child muxers Gyan Doshi 2023-02-20 15:35 ` Anton Khirnov 2023-02-18 4:49 ` [FFmpeg-devel] [PATCH v4 4/5] avformat/segment: " Gyan Doshi 2023-02-18 4:49 ` Gyan Doshi [this message] 2023-02-20 15:06 ` [FFmpeg-devel] [PATCH v4 1/5] avformat: add av_program_add_stream_index2() 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=20230218044949.1179-5-ffmpeg@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