-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
rpiCamera: selected camera is not available #3715
Comments
Got the same issue! |
Hello, thanks for providing logs, in which this line is visible
Digging into libcamera issues, it turns out that that warning is triggered when libcamera is compiled without PISP support (Raspberry Image Signal Processor): raspberrypi/libcamera#145 The libcamera bundled into the server is indeed compiled without PIPS. Therefore, we'll change bundled libcamera in order to enable PISP. |
please test this nightly release and let me know if it fixes the issue (click on "artifacts", "binaries"): https://github.com/bluenviron/mediamtx/actions/runs/10734526077 |
Hello,
I tried creating directories and a symlink with that file:
It works with that modification. Hope this helps. Kind Regards, Daniel |
@dgo19 thanks for the feedback, try again with this different nightly release: https://github.com/bluenviron/mediamtx/actions/runs/10739500678 |
Yes, this build works for me. Thank you! |
Also works for me, thanks! |
This issue is mentioned in release v1.9.1 🚀 |
Which version are you using?
v1.9.0
Which operating system are you using?
Describe the issue
When using the path configuration described in the section below, running mediamtx results in the following error:
ERR [path cam] [RPI Camera source] camera_create(): selected camera is not available
This happens in both regular and docker environments. Device is Raspberry Pi 5 4GB with Camera Module 3,
libcamera-hello
works perfectly fine.Unsure if related to #3714.
Describe how to replicate the issue
Did you attach the server logs?
log.txt
Did you attach a network dump?
No
The text was updated successfully, but these errors were encountered: