[BUG] RTMP pushes for Steam fail due to waiting for S0/S1 packets

[SoraBytes]

After streaming to steam via automatic push it begins to buffer quiet often and then cant reconnect steam shows a black screen with loader for buffering because it thinks a client is connecting/disconnecting and no video playback occurs and mistserver logs this at least one as:

[WARN] Lost connection while waiting for S0/S1 packets!

Can try to provide whatever debug logging you need to resolve this, let me know.

[Rokamun]

Hmm, I believe this might be caused by a separate issue we have encountered not too long ago. Some of our E-RTMP handshaking was enforced and this could mess up the RTMP connection if the other side didn't understand the extra information and stopped the connection when receiving it. I don't think we've upstreamed it to development yet, I'll see if we can.

If you could make a wireshark capture of the attempted connection we'd be 100% sure however!

[SoraBytes]

I'll try to get a packet capture. I'm honestly not exactly sure what triggers it. Sometimes starting a stream triggers it for a few minutes or longer, and sometimes mid-stream will trigger it at which point the stream is buffering or dead on steam.

If you are able to upstream the E-RTMP handshake fixes to development I can pull them in and check if it contributes to fixing this.

This is an old example of what steam does see when it occurs. Additionally, it doesn't matter if I stream 1080p or lower, or 1,000Kbps or 20,000Kbps. Steam recommends 7,000 or lower but it doesn't contribute to avoiding this. I have since started streaming at 720p 6,000Kbps and still see this bug.

[Rokamun]

Heya,

Checked with my colleague that did the bugfix for E-RTMP and I was mistaken, it is already included in 3.10. So that shouldn't be an issue. I'll see if I can run some tests on Steam myself, I can't say we have tried it before so it will be interesting either way. Should have the time to do this somewhere on Tuesday if I look at my schedule.