-
Notifications
You must be signed in to change notification settings - Fork 75
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
Streamer with H264 encoded cam support #262
Comments
Klipper has nothing to do with your cam.
Even if we would not skip it, it doesn't support x264 encoding from a cam. So this FR would suit better in the camera-streamer repo.
You say you want advice, but call it a feature request. So what is the feature request? That Crowsnest provides an option to use x264 of a cam? Crowsnest doesn't support any encoding. It only supports streamer, that support specific encoding of cameras. So if you want something like that, you would have to suggest a streamer that supports it and is working in Mainsail/Fluidd. Overall I don't see a benefit atm to support another streamer just for x264 encoding, as I don't think there is a high user base for it currently. Also we would need some sponsoring, that we can get a cam for a few crew members, to test such a streamer, before adding it. I let this open for now, as I'm open for discussion about a new streamer, but there won't be something coming with Crowsnest in the near future. |
Is your feature request related to a problem? Please describe
It's not so much of a problem but asking on how to optimize a crowsnest setup with C920/930e running on rpi with klipper installed via kiauh.
C920/930e have an option which support providing x264 compressed stream from the camera. This would save additional processing overhead on rpi5.
Currently it seems crowsnest installer skips camera-streamer install on a rpi5, and ustreamer only does MJPEG severely limiting framerate
Describe the solution you'd like
Some advice on how to optimize setting for C920/930e with klipper/crowsnest on rpi-5
Describe alternatives you've considered
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: