- Posts: 1
- Joined: Wed Jun 23, 2021 11:39 am
- Real Name: Rick Wolthuis
Wed Jun 23, 2021 11:48 am
Hey,
Recently I've purchased a BMD ATEM Mini Extreme and started testing with it using my own streaming platform. However, I noticed the device reconnecting about every 30 seconds.
After some digging, I found that the ATEM device sends a PING request as a control message (0x04) with type 6. This is something I haven't implemented to reply on when a client sends me such message. I decided to reply to such request with a PONG response (control message 0x04, type 7). Now the device seems to stay connected to the RTMP server.
Now the thing is, I thought control message type 6 was designed for the server to ping the client, and not the otherway around like my ATEM device is currently doing. Am I wrong, or could this feature be implemented wrong in the ATEM device it's RTMP client?
Some more info about control message's can be found here:
https://github.com/melpon/rfc/blob/mast ... age-events
https://en.wikipedia.org/wiki/Real-Time ... ture_(0x04)
Thanks in advance!
Recently I've purchased a BMD ATEM Mini Extreme and started testing with it using my own streaming platform. However, I noticed the device reconnecting about every 30 seconds.
After some digging, I found that the ATEM device sends a PING request as a control message (0x04) with type 6. This is something I haven't implemented to reply on when a client sends me such message. I decided to reply to such request with a PONG response (control message 0x04, type 7). Now the device seems to stay connected to the RTMP server.
Now the thing is, I thought control message type 6 was designed for the server to ping the client, and not the otherway around like my ATEM device is currently doing. Am I wrong, or could this feature be implemented wrong in the ATEM device it's RTMP client?
Some more info about control message's can be found here:
https://github.com/melpon/rfc/blob/mast ... age-events
https://en.wikipedia.org/wiki/Real-Time ... ture_(0x04)
Thanks in advance!