-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue] Unexpected behavior with unstable connection #43
Comments
Here's a sample part of the FFMPEG log which shows how FFMPEG is called again and again. in normal scenarios, it is called only once. ffmpeg version N-73031-gd4c9ece Copyright (c) 2000-2015 the FFmpeg developers |
In fact, if the network is timeout, CONNECTION_TIMEOUT will be called. If not, that means the connection is ok.
but the connection shouldn't be broken, that is to say, the stream should be existing. |
I agree, but the only problem is that after it stops and restarts the streaming, the sending speed is always 0 and the frames are not sent to the server. I see this same behaviour when I switch camera in current version also. It stops and restarts streaming, but after restarting, it actually never sends the frames to the server. In the server we see incoming bytes as 0. |
Please test it on v1.3.6. |
Sure, will test and let you know. On Tue, Sep 22, 2015 at 6:29 PM, jpxiong notifications@github.com wrote:
Regards, |
Closing this as looks like issue is solved. Will reopen with more tests reveal the problem |
I distributed a version of our app using PILI to few of our customers. We observe the following
!) One of our customer has a very unstable connection.
2) We use Nginx RTMP and see that the upload speed goes to 0 and when internet restores it goes back again to 364kbps or higher.
3) But when it goes to 0, on the RTMP server, PUBLISH_DONE is called, which basically means the stream is over.
4) But on the client side, no state callback is invoked (like STATE.DISCONNECTED, STATE.SHUTDOWN etc..)and the streaming continues, though no data is sent to the server
If I do a test and I disconnect the internet, STATE.DISCONNECTED is called and the behaviour is expected. But in extremely low and unstable connection speed, it looks like PILI is trying to stop and restart the streaming without calling any of the STATE callbacks. And when the streaming restarts in the same session, the Upload speed is always 0 and no data is actually sent to the server.
in the NGINX RTMP and FFMPEG logs in our backend server, we can see that the streaming is getting started then getting over and then getting started and the cycle continues. But in the client side SHUTDOWN or any other error state is not called.
Unfortunately I would not be able to get the logs from customer's mobile.
The text was updated successfully, but these errors were encountered: