Attached patch increases the max length of control URI to 2048 characters,
as urls of some RTSP streams do exceed this limit.
0001-Increasing-the-max-length-of-control-URI-to-2048-cha.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-d
Hello everyone,
This is the first time for me to send a patch via email. Is this the
correct format?
I would appreciate it if someone could confirm, and if there is anything
else I need to do to get it into upcoming releases.
Best,
*• **Yiğit (Yeet) Uyan*
*•* Smart Home Intelligence | Google
://patchwork.ffmpeg.org/ at the
moment.
*• **Yiğit (Yeet) Uyan*
*•* Smart Home Intelligence | Google Home
*•* yigitu...@google.com
On Wed, Aug 5, 2020 at 7:58 PM zhilizhao wrote:
>
>
> > On Aug 6, 2020, at 10:46 AM, zhilizhao wrote:
> >
> >
> >
> >> On Aug 6, 2020, at 6
the problems we are experiencing with rtsps streams).
*• **Yiğit (Yeet) Uyan*
*•* Smart Home Intelligence | Google Home
*•* yigitu...@google.com
On Thu, Aug 6, 2020 at 2:15 AM myp...@gmail.com wrote:
> On Thu, Aug 6, 2020 at 11:47 AM Yiğit (Yeet) Uyan
> wrote:
> >
>
Hi, the patch file I have sent via git-email does not seem to be listed in
the patchwork list of patches. Can somebody comment on the file/mimetype,
and if everything looks good?
First time submitting a patch, please let me know if there is any other
thing I need to do.
*• **Yiğit (Yeet) Uyan
-devel@ffmpeg.org,
though it does not show up in patchwork. I am not sure what the following
steps are..
Signed-off-by: Yiğit (Yeet) Uyan
---
libavformat/rtsp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/rtsp.h b/libavformat/rtsp.h
index 54a9a30c16..2b37f5b49f
