Open kapulkin opened 3 years ago
The error also occurs on v2.3, installation file: ant-media-server-enterprise-2.3.0-20210302_1432.zip
Hi @kapulkin ,
It's likely a packet lost issue in the network. I think we can enable some SVC parameters in VP8 transcoding if applicable.
@mekya Yes, it looks like a packet loss. I read, that WebRTC could request server to send lost packets again.
I think we can enable some SVC parameters in VP8 transcoding if applicable.
You better understand, which parameters do you mean. Describe them please, and we can discuss.
The same issue has place for h264. If it is more comfortable for you to work with h264, you could do that.
@kapulkin ,
Thank you for your comments. Yes you are right about WebRTC could request server to send lost packets again. I can debug that part.
You better understand, which parameters do you mean. Describe them please, and we can discuss.
VP8 SVC options are better than H264. SVC makes the video playing more robust against the packet loss.
I'm moving it to the backlog to schedule for next release(hopefully next sprint)
Short description
Some frames during the videostreaming come broken. That happens periodically with frequency from 1 time in 10 minutes to several times in a minute. There is a screenshot with a broken frame.
Environment
Steps to reproduce
Expected behavior
I have a conference with three participants without corrupted frames, freezes are acceptable.
Actual behavior
Some times frames in one or two streams become corrupted on period 1-2 seconds. The moment the corrupted frame starts matches the moment in log /usr/local/antmedia/log/ant-media-server.log, when the next message occurs
Logs
I suppose that there is a moment occurs, when the internet speed becomes lower suddenly. Ant-media server switches from one bitrate to another and loses a keyframe or several frames, that precedes the broken frame. In terms of h264 protocol may be you should force to send IDR frame or SI frame as a first frame with a new bitrate.