From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/tee: signal EOF if no more output is to be published.
Date: Fri, 3 Feb 2023 09:52:36 +0530
Message-ID: <4039d916-a926-de54-7346-ea20c40c6043@gyani.pro> (raw)
In-Reply-To: <e4adda4b-3e4d-8a8a-c775-a8568bb9b9c@passwd.hu>
On 2023-02-03 04:17 am, Marton Balint wrote:
>
>
> On Thu, 2 Feb 2023, Gyan Doshi wrote:
>
>> Prior to 2d924b3a630, ffmpeg.c would exit if any packet write failed.
>> tee's
>> write_packet seemingly relied on that to enforce its abort failure
>> policy.
>>> From 2d924b3a630, ffmpeg only closes that OutputStream and keeps on
>> sending packets of other streams.
>
> Hmm, are you sure? I glanced at the code and it seems to me that any
> failure of av_interleaved_write_frame() will cause the muxing thread
> to exit. So I don't quite see how other streams can receive packets.
Steps to reproduce:
1) ffmpeg -readrate 1 -stream_loop -1 -i INPUT -map 0:v -map 0:a -c copy
-f tee "[f=flv:onfail=abort]rtmp://url/playpath|[f=null:onfail=ignore]stub"
2) Kill the rtmp endpoint at the server side. The tee muxer logs that
it's aborting, however, ffmpeg keeps running. Contrast with 5.1 or
earlier, which exit.
av_iwf returns EOF which just results in a call to tq_receive_finish()
for that ost without breaking muxer_thread's loop.
Reards,
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-03 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 18:06 Gyan Doshi
2023-02-02 22:47 ` Marton Balint
2023-02-03 4:22 ` Gyan Doshi [this message]
2023-02-03 8:32 ` Marton Balint
2023-02-04 10:04 ` 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=4039d916-a926-de54-7346-ea20c40c6043@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