Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/rtmpproto: forward rw_timeout to tcp proto
Date: Thu, 20 Jul 2023 23:29:31 +0200
Message-ID: <c846232c-1949-9aa0-207e-cbdf0fda5e13@rothenpieler.org> (raw)
In-Reply-To: <7ba7a96d-f161-631-536b-9b5ca68be4b7@martin.st>

On 20.07.2023 23:09, Martin Storsjö wrote:
> Hmm, geez we have many similar-looking and randomly named timeout 
> options here...
> 
> The av_opt_copy() call in ffurl_open_whitelist() should only iterate 
> over the options within the URLContext itself, not recurse into the 
> protocol private options (as those probably don't match across protocols 
> anyway). So I wouldn't think that the tcp "timeout" option ends up 
> implicitly set from the rtmpproto "timeout" (listen_timeout) option.

My goal here is to specifically be able to set the i/o timeout on the 
tcp side, since I just had an ffmpeg rtmp process wait for more data 
indefinitely after a network hickup, even though the connection was long 
dead.

I just discovered that the URLContext has global options, and rw_timeout 
is one of them.
So setting -rw_timeout should have already been possible, I'll try if 
that ends up in the right place.

> I didn't try running and observing it right now though.
> 
> // Martin
> _______________________________________________
> 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".
_______________________________________________
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-07-20 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 17:01 Timo Rothenpieler
2023-07-20 20:47 ` Martin Storsjö
2023-07-20 20:57   ` Timo Rothenpieler
2023-07-20 21:09     ` Martin Storsjö
2023-07-20 21:29       ` Timo Rothenpieler [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=c846232c-1949-9aa0-207e-cbdf0fda5e13@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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