-
Notifications
You must be signed in to change notification settings - Fork 428
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
pngStream stops returning images after some time #105
Comments
When you get a timeout error it should reconnect to the video stream (see #23). I'm going to close this for now, but if it's not reconnecting for you I'll reopen it. |
I am still facing this trouble despite the patches in #23 . |
So I have made a go at it again. I had node v0.10.33 earlier and now I installed v0.12.7. The client re-connects if it has lost connection and streams in video but the parsing has stopped. I have checked if TcpVideoStream emits data events after re-connecting and it does. However, the parser has stopped emitting data events. Has this issue been addressed where once the client loses connection, it is able to reconnect and stream in video from the drone BUT NOT parse it anymore to a h264 file ?? |
I, too, face this issue. Is there any known way to fix this? Using Node 6.2.2 |
I'm facing this issue too, any solution so far please? |
I've done some investigation into this issue tonight. FFMPEG is still churning out files but something in the png encoder is failing silently, and so no more events are dispatched. It might be the png splitter. I know this is an old library. But I'm noticing some people are still using it. |
@paulhayes interesting. If FFMPEG is still outputting data then the splitter might be indeed the problem. The splitter code is fairly simple, so it shouldn't be too hard to debug. |
I'll take another look. |
Im trying to collect image data sets using node.js api but it gives me this error after some time ...
TcpVideoStream error: TcpVideoStream timeout after 1000 ms.
Attempting to reconnect to TcpVideoStream...
The text was updated successfully, but these errors were encountered: