Closed b3ddy closed 1 year ago
Hello, what is the output of command libcamera-still
?
Hey @aler9 ,
https://i.imgur.com/6HS9k6M.png
https://i.imgur.com/5DnC0ck.png
https://i.imgur.com/MacvIkq.png
ran the libcamera-still with and without the docker container running to show both outputs.
Other steps I've tried:
If libcamera-still
or libcamera-vid
don't work with your specific camera, there's nothing that can be done in the server, since the server uses the same backend (libcamera). When adding support for the camera into the server, we chose to use the libcamera backend since the legacy one is deprecated.
Contact the maintainers of libcamera and describe your issue.
This issue is being locked automatically because it has been closed for more than 6 months. Please open a new issue in case you encounter a similar problem.
Which version are you using?
v i.d.k aler9/rtsp-simple-server:latest-rpi pulled 04/04/23
Which operating system are you using?
Describe the issue
When I'm running the latest-rpi docker image I get a warning about a mismatch between Unicam and CamHelper, and when I go to view the stream in my browser I get a 404 page not found. I also noticed when I go back to the log after requesting stream in the browser it's saying [muxer cam] destroyed (no one is publishing to path 'cam'). I turned on the legacy interface for the RPiCam and ran vcgencmd get_camera and the pi shows the cam supported and detected. Went back and turned off the legacy interface restarted the Pi and reran the docker image to only still got the same error.
Describe how to replicate the issue
start the RPi
run the container image "docker run --rm -it \ --network=host \ --privileged \ --tmpfs /dev/shm:exec \ -v /run/udev:/run/udev:ro \ -e MTX_PATHS_CAM_SOURCE=rpiCamera \ aler9/rtsp-simple-server:latest-rpi"
Did you attach the server logs?
yes
Did you attach a network dump?
no