From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v2 2/4] avformat/hls: relay programs to child muxers
Date: Thu, 9 Feb 2023 16:25:17 +0530
Message-ID: <20230209105519.1814-2-ffmpeg@gyani.pro> (raw)
In-Reply-To: <20230209105519.1814-1-ffmpeg@gyani.pro>
---
libavformat/hlsenc.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 39df9becc7..0b66efad3e 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -907,6 +907,12 @@ static int hls_mux_init(AVFormatContext *s, VariantStream *vs)
st->id = vs->streams[i]->id;
}
+ for (i = 0; i < s->nb_programs; i++) {
+ ret = av_program_copy(oc, s, s->programs[i]->id, 0);
+ if (ret < 0)
+ av_log(s, AV_LOG_WARNING, "unable to transfer program %d to child muxer\n", s->programs[i]->id);
+ }
+
vs->start_pos = 0;
vs->new_start = 1;
--
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-09 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 10:55 [FFmpeg-devel] [PATCH v2 1/4] avformat: add av_program_copy() Gyan Doshi
2023-02-09 10:55 ` Gyan Doshi [this message]
2023-02-16 6:57 ` [FFmpeg-devel] [PATCH v2 2/4] avformat/hls: relay programs to child muxers Andreas Rheinhardt
2023-02-16 8:00 ` Gyan Doshi
2023-02-09 10:55 ` [FFmpeg-devel] [PATCH v2 3/4] avformat/segment: " Gyan Doshi
2023-02-09 10:55 ` [FFmpeg-devel] [PATCH v2 4/4] avformat/tee: " Gyan Doshi
2023-02-11 5:56 ` [FFmpeg-devel] [PATCH v2 1/4] avformat: add av_program_copy() Gyan Doshi
2023-02-16 4:02 ` Gyan Doshi
2023-02-16 6:52 ` Andreas Rheinhardt
2023-02-16 7:58 ` 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=20230209105519.1814-2-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