bluenviron / mediamtx

Ready-to-use SRT / WebRTC / RTSP / RTMP / LL-HLS media server and media proxy that allows to read, publish, proxy, record and playback video and audio streams.
MIT License
11.41k stars 1.45k forks source link

Setting rpiCameraROI "exits unexpectedly" #1715

Closed parttimer777 closed 1 year ago

parttimer777 commented 1 year ago

Which version are you using?

0.22.2

Which operating system are you using?

Describe the issue

Using this config:

  cam:
    source: rpiCamera
    rpiCameraWidth: 1920
    rpiCameraHeight: 1080
    rpiCameraFPS: 5
    rpiCameraBitrate: 1600000
    # Region of interest, in format x,y,width,height
    rpiCameraROI: 10,10,1024,768
Apr 16 13:24:49 pi-cam mediamtx[886]: 2023/04/16 13:24:44 INF MediaMTX / rtsp-simple-server v0.22.2
Apr 16 13:24:49 pi-cam mediamtx[886]: 2023/04/16 13:24:44 DEB [path cam] created
Apr 16 13:24:49 pi-cam mediamtx[886]: 2023/04/16 13:24:44 DEB path manager created
Apr 16 13:24:49 pi-cam mediamtx[886]: 2023/04/16 13:24:44 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
Apr 16 13:24:49 pi-cam mediamtx[886]: 2023/04/16 13:24:44 INF [path cam] [rpicamera source] started
Apr 16 13:24:49 pi-cam mediamtx[886]: 2023/04/16 13:24:44 INF [path cam] [rpicamera source] ERR: process exited unexpectedly
$ libcamera-hello  --list-cameras
Available cameras
-----------------
0 : ov5647 [2592x1944] (/base/soc/i2c0mux/i2c@1/ov5647@36)
    Modes: 'SGBRG10_CSI2P' : 640x480 [30.00 fps - (0, 0)/0x0 crop]
                             1296x972 [30.00 fps - (0, 0)/0x0 crop]
                             1920x1080 [30.00 fps - (0, 0)/0x0 crop]
                             2592x1944 [30.00 fps - (0, 0)/0x0 crop]

Describe how to replicate the issue

N/A

Did you attach the server logs?

yes

Did you attach a network dump?

N/A

parttimer777 commented 1 year ago

Oops, was using wrong format. It's working now.

libcamera-vid --help|grep roi --roi arg (=0,0,0,0) Set region of interest (digital zoom) e.g. 0.25,0.25,0.5,0.5

github-actions[bot] commented 10 months ago

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.