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 v3 3/5] avformat/hls: relay programs to child muxers
Date: Sat, 18 Feb 2023 10:21:16 +0530
Message-ID: <83b929cf-061e-ce62-8764-9a3d78133148@gyani.pro> (raw)
In-Reply-To: <46224f44-2eca-f8d3-2ba8-3a849337d5bb@passwd.hu>



On 2023-02-18 03:31 am, Marton Balint wrote:
>
>
> On Fri, 17 Feb 2023, Gyan Doshi wrote:
>
>> ---
>> libavformat/hlsenc.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
>> index e1f96feda3..cf2b36da01 100644
>> --- a/libavformat/hlsenc.c
>> +++ b/libavformat/hlsenc.c
>> @@ -911,6 +911,14 @@ FF_ENABLE_DEPRECATION_WARNINGS
>>         st->id = vs->streams[i]->id;
>>     }
>>
>> +    for (i = 0; i < s->nb_programs; i++) {
>> +        ret = av_program_copy(oc, (const AVFormatContext *)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);
>
> Aren't these errors supposed to be propagated back as hard failures, 
> instead of simply ignoring them? The next 2 patches also has this 
> problem.


Updated in v4.

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:[~2023-02-18  4:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 17:02 [FFmpeg-devel] [PATCH v3 1/5] avformat: add av_program_add_stream_index2() Gyan Doshi
2023-02-17 17:02 ` [FFmpeg-devel] [PATCH v3 2/5] avformat: add av_program_copy() Gyan Doshi
2023-02-17 17:02 ` [FFmpeg-devel] [PATCH v3 3/5] avformat/hls: relay programs to child muxers Gyan Doshi
2023-02-17 22:01   ` Marton Balint
2023-02-18  4:51     ` Gyan Doshi [this message]
2023-02-17 17:02 ` [FFmpeg-devel] [PATCH v3 4/5] avformat/segment: " Gyan Doshi
2023-02-17 17:02 ` [FFmpeg-devel] [PATCH v3 5/5] avformat/tee: " 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=83b929cf-061e-ce62-8764-9a3d78133148@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