Closed Sectran closed 5 months ago
Make sure your network is well. Normally, the delay of HTTP-FLV is about 1~5s (without GOP cache). It seems that HTTP-FLV halted (maybe caused by server timeout). By the way, there is cumulative delay in HTTP-FLV streaming because of network jitter. In other words, TCP is a reliable delivery protocol, it may delay in network, player must wait for delayed packets, that is out of control of server. Further, HTTP-FLV is not as interactive as RTMP, so delay in HTTP-FLV streaming is often larger than RTMP. Players can discard too delayed packets to catch up the streaming pace.
At the beginning, the time interval between the streaming machine's clock and the playback time for the HTTP-FLV was around 10 seconds. After a while, this time interval increased. I'm not sure if it's due to a discrepancy in clock rates between the HTTP-FLV streaming and the actual clock rates, or if there are other reasons. nginx version:1.22 nginx-http-module version:lasted OS:Linux at the begainning: left is rtmp and right is http-flv
in a while:
You can see he time interval has increased, and what I can confirm is that the clock rate during RTMP streaming is correct.
by the way,I play flv useing flv.min.js,this is a demo: