-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
DietPi-Software | Raspimjpeg does not stream mjpeg with Lighttpd #1747
Comments
Many thanks for the report 👍 We'll open for investigations. |
Moved to 6.9 so we can focus on 6.8 wrap up and release. |
Confirmed bug, apologies for the delay @fieldOfView. We'll investigate and resolve. |
Notes:
|
Yes, repetitive jpeg “faux-streaming” works fine. I am using raspimjpeg as an alternative to mjpegstreamer for an OctoPrint instance, and that requires mjpeg streaming. |
https://github.com/jacksonliam/mjpg-streamer/blob/master/mjpg-streamer-experimental/plugins/input_raspicam/README.md 🈯️
|
Moving this out of milestone for the following reasons:
|
@fieldOfView @Fourdee |
@fieldOfView
... ähm otherwise this should have been set already when enabling the Pi cam. Regardless worth to assure that it is enabled, and test with new Buster image, now life as default download for RPi. |
I have no RPi camera to test, but generally it should work with Lighttpd (now), as the web interface and it's own installer is actively developed and has a Lighttpd block. I updated our install code to especially use the dedicated Stretch-compatible raspimjpeg binary on Stretch systems, but otherwise it looks good. Would be awesome if someone with an RPi camera module could test it, but I mark this issue as closed now. Please open a new issue if anything does not work or any feature is missing. |
Creating a bug report/issue:
When installing raspimjpeg (package 59) with Lighttpd as the webserver, streaming mjpeg does not work. Getting jpeg stills in rapid succession (the "default stream" option) does work. Streaming mjpeg does work well when selecting nginx as the webserver preference.
Required Information:
Additional Information (if applicable):
Steps to reproduce:
Open the rpicam webpage in a browser (and see the camera stream working)
Go to System and press "mjpeg stream"
Expected behaviour:
An mjpeg stream should be received by the client one frame at a time from a single http connection
Actual behaviour:
No data is arriving at the client, and after a while the client times out (if it is well-behaved)
Did you submit a
dietpi-bugreport
?No
Extra details:
This is an upstream issue between raspimjpeg and lighttpd, some more information can be had here:
https://www.raspberrypi.org/forums/viewtopic.php?t=63276&start=4250#p1210885
For DietPi, this is mostly a documentation issue. Since selecting the raspimjpeg package in the dietpi-software already pops up a dialog, that dialog could include a warning about the incompatibility and an advisory to use nginx (or apache?) instead.
The text was updated successfully, but these errors were encountered: