We are running WSE on our AWS EC2 instance, using it to capture / record live RTMP. In our case we are capturing two live streams of the same live content (originating from two separate encoders) with unique stream keys. We have been using this workflow successfully for multiple events for almost two years.
To monitor the inbound streams at the entry point to WSE, we copy the “test stream” URL from the incoming live streams control panel and paste it into a standard JW Player test page. At our last live event, both streams had buffering issues at the WSE entry point, i.e. the inbound test stream link showed classic ‘spinning wheel’ buffering delays in the JW Player. We’ve never seen any buffering previously, capturing streams of exactly the same spec’s.
The two streams also buffered at different rates/amounts. Neither recording actually lost any data but by about twenty minutes after the start of the recordings, one recorded stream was delayed by about six minutes more than it’s (otherwise synchronous) partner. Other streams of the same live content from the same encoding facility were streaming smoothly on other platforms, without any buffering issues. We eventually stopped the recording and the streaming transmission and after restarting, and by the end of the 90 minute program, the buffering had stopped. And FWIW - We had tested both streams for more than an hour the evening before, from exactly the same signal path and had zero buffering issues.
Has anyone else experienced this issue? We would appreciate any guidance on settings or best practices to avoid this serious issue on future events. Thanks!