I doesn't look like there are any blockers on this patch request - could
someone go ahead and merge it?
On Sat, Sep 28, 2019 at 2:55 AM Reino Wijnsma wrote:
> On 2019-09-27T19:37:40+0200, William Martin
> wrote:
> > On Wed, Sep 25, 2019 at 2:36 PM Reino Wijnsma
> wrote:
> &
Hi Reino - good point. Though, that was an existing log message that I did
not modify. Should the old typo be addressed in a separate patch, or should
I update it here?
On Wed, Sep 25, 2019 at 2:36 PM Reino Wijnsma wrote:
> On 2019-09-25T20:57:08+0200, William Martin
>
might want one off and the other on.
On Wed, Sep 25, 2019 at 3:14 PM Carl Eugen Hoyos wrote:
> Am Mi., 25. Sept. 2019 um 21:04 Uhr schrieb William Martin
> :
> >
> > From: Will Martin
> >
> > Motivation: When running multiple rtmp ingest on the same machine on t
From: Will Martin
Motivation: When running multiple rtmp ingest on the same machine on the same
port, users may want to explicitly forbid mismatched rtmp streams from
successfully completing handshakes. This patch allows for such enforcement
Signed-off-by: Will Martin
---
hello. I didn't see any comments about this patch - does that mean it is
ready to be merged?
On Thu, Aug 29, 2019 at 3:54 PM William Martin
wrote:
> From: Will Martin
>
> Some rtmp streamers (i.e. AWS Elemental Encoder, Wirecast) send C0 and C1
> together and expect S0 and S1 retur
From: Will Martin
Some rtmp streamers (i.e. AWS Elemental Encoder, Wirecast) send C0 and C1
together and expect S0 and S1 returned together. When sent in different
packets, this results in a C2 handshake. This patch fixes that error.
Note that the patch is based off of a fix proposed by
