-
-
Notifications
You must be signed in to change notification settings - Fork 434
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
Add support for UV4L-MJPEG (IP Camera) Support #310
Comments
Doesn't this just stream WebRTC, and therefor require the html5 |
The stream is certainly WebRTC compliant, there is some pre-reqs such as installing the uv4l-mjpegstream plugin and then setting it up so that it can convert any IP Camera sending http stream to WebRTC. The config creates a dummy device that can then be read as if the camera is connected to Pi. The support requested should check for the presense of the plugin and then allow the uv4l config to done via web interface when adding camera. |
I'll need to spend some time testing this to determine what the actual front-end requirements are to set it up. |
Wouldn't it be simpler to integrate this? |
At this stage, I think the path forward might be just to integrate with crowsnest (which should already work anyway!). |
I didn't know about that. Personally I don't care what the 3D printing community does concerning cameras as long as it involves moving away from the absolutely terrible mjpeg streams and towards h264. |
For all matters and purposes, Fluidd web interface already supports most types of camera, as long as the browser has support for it too... we even support setting an http page for which we use an I don't see what more we can do on this one, so will be considering this complete and closing the ticket. |
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like:
Mainsail recently added support for UV4L-MJPEG i-e IP camera support. This will be great addition to allow webcam for IP Cameras such as Yi/Waze etc.
Describe alternatives you've considered:
None
Affected users and/or setups:
None
Additional Context:
None
The text was updated successfully, but these errors were encountered: