Skip to content
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

Stream port, unexpectedly drops incoming stream from ffmpeg after 120 seconds. #75

Closed
ghost opened this issue Mar 21, 2016 · 2 comments
Closed

Comments

@ghost
Copy link

ghost commented Mar 21, 2016

I'm streaming my usb webcam from ffmpeg, everything works just fine for 120 seconds, then the receiving port (e.g. 8082 or in my case 2900) covertly closes itself (not indicated by stream-server), causing ffmpeg to shut down with an error. I've tried everything I can think of, and my programming skills is rather bad. It seems to me like there is some sort of forced timeout closing the port, but it is beyond me why the port would timeout during excellent streaming. Port 2900 is not occupied by any other process, which netstat -n also confirms. I've tried disabling firewalls and antivirus, to no avail. Is this an isolated occurence or a known problem? Any support would be great. Thanks!

I'm running Windows XP SP3 with Node.js v4.3.0
ffmpeg_log.txt

@ghost ghost changed the title Stream port, unexpectedly drop incomming stream from ffmpeg after 120 seconds. Stream port, unexpectedly drops incoming stream from ffmpeg after 120 seconds. Mar 21, 2016
@phoboslab
Copy link
Owner

I implemented the solution you(?) proposed in my blog comments: http://phoboslab.org/log/2013/09/html5-live-video-streaming-via-websockets#comment112

Thanks!

@ghost
Copy link
Author

ghost commented Mar 24, 2016

Thank you Dominic, for your efforts in providing this superb streaming-invention! If the bracketed question mark above is intended to assign a measure of scrutiny to credits, it's really not about prestige for me, just very happy and very lucky to have the solution at hand. Please, edit my inputs as you see fit, to maybe better reflect due and un-due credits. Google, manuals, other peoples struggles, anlalyzing different angles and approaches, finally brought me close enough to enable me nailing the elusive line of code which solved the timeout issue crucial only to satisfy my personal needs at that moment, and of course it's a joy to forward this individual breakthrough, how ever insignificant or lifesaving it may be to anyone out there. /Magnus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant