You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I play one flv live stream with mpegts.
the 0 ~10 seconds, it play well.
but when I suspend the websocket connection for 10 seconds in websocket.
and resume the transport from server to client.
the client keep playing, but the video in the screen is delayed about for 10 seconds.
and the play bar has been at the newest time line.
I am sure the video frames delayed has been flushed to the client.
the browser debug console show that the number of message received during 21 ~ 22 seconds
is ten more than average in normal.
ther mpegts.version is 1.7.3
var player = mpegts.createPlayer({
type: 'flv', // could also be mpegts, m2ts, flv
isLive: true,
url: url.value
});
is there any configuration resolved it, thanks.
The text was updated successfully, but these errors were encountered:
I have applied play option as follows:
var player = mpegts.createPlayer({
type: 'flv', // could also be mpegts, m2ts, flv
isLive: true,
liveSync: true,
liveBufferLatencyChasing: true,
liveBufferLatencyChasingOnPaused: true,
enableStashBuffer: false,
url: url.value
});
but the video in the screen is still delayed about for 6 seconds.
I play one flv live stream with mpegts.
the 0 ~10 seconds, it play well.
but when I suspend the websocket connection for 10 seconds in websocket.
and resume the transport from server to client.
the client keep playing, but the video in the screen is delayed about for 10 seconds.
and the play bar has been at the newest time line.
I am sure the video frames delayed has been flushed to the client.
the browser debug console show that the number of message received during 21 ~ 22 seconds
is ten more than average in normal.
ther mpegts.version is 1.7.3
var player = mpegts.createPlayer({
type: 'flv', // could also be mpegts, m2ts, flv
isLive: true,
url: url.value
});
is there any configuration resolved it, thanks.
The text was updated successfully, but these errors were encountered: