According to official documentation the correct parameters, if octoprint uses raspistill/raspivid (likely) are -h and -w
Did you ever find a solution to the fov issue when using the raspicam and 1080p? i have exactly the same issue.
Could be that you have image stabilization enabled. Here are all of the settings that the camera supports (I think), at least when using the official driver:
When I enable image stabilization, it definitely zooms in. Here is an image of the stream with stabilization enabled (it's clearly zoomed in):
It looks like a TON of the raspi camera control settings are interconnected, and some need to be applied in the correct order even. I've been pulling my hair out trying to figure out how all of the settings work. I've been using the mjpg-streamer control.htm file using the UVC input module. I'm not sure how control is implemented behind the scenes for this.
Here's what I've discovered so far:
- Image stabilization cannot be turned off once it is turned on without rotating or flipping the camera. This could explain at least some fraction of the 'why is my camera zoomed in' issue lots of people seem to be having. I'm fairly certain this is a bug, since disabling and enabling auto focus causes the image to zoom out ever so briefly.
- The 'Color Effect' and 'CbCr' setting is interlinked, but only for SOME of the color effects. If one chooses 'Aqua', 'Black and White' or 'Sepia', the CbCr setting will at first be ignored, but any later changes to the value of CbCr WILL affect the Color Effect. For the 'Set CB/CR' option, the CBCR setting of 0 will be used at first after selecting this option(no matter what the CbCr setting actually is), then any subsequent changes to CbCr will change the effect. Geesh!!!
- Red and Blue balance will only affect the image if White Balance, Auto & Preset is set to manual. That makes sense.
- JPEG Compression and JPEG Quality don't seem to do anything, but Video Bitrate setting definitely has a dramatic effect.
- H264 settings don't affect mjpg-streamer, at least as far as I can tell, and that is sort of expected.
- Auto Exposure setting only has an affect if Scene is set to none.
- Absolute exposure time only has an affect is Scene is none and auto exposure is set to manual.
- Exposure dynamic framerate does not seem to do anything. It's possible that my framerate is locked somehow (-f parameter??). Not sure how this works otherwise.
- Auto Exposure Bias only has an affect if the Scene setting != none OR auto exposure = Auto. Makes sense.
- Iso Sensitivity Auto (drop down box) only has an affect if scene != none or auto exposure = auto.
- Iso Sensitivity (slider) only has an affect if Scene setting != none OR auto exposure = Auto AND Iso Sensitivity Auto is set to manual.
Whoa boy, I'm sure there are other rules I don't know. What a crazy can of worms. The official documentation mentions that some of these settings only apply in some cases, but they never go into detail. If anyone is willing to confirm my findings I would be most appreciative.
Edits: Fix typos
I have modified octopi.txt so that camera="raspi" and camera_raspi_options="-x 1280 -y 720 -fps 15 -quality 85". I then run "service webcamd restart" followed by "service webcamd status". The status looks like things are set properly, showing resolution of 1280 x 720.
However, OctoPrint still shows the zoomed in video feed.
This was working perfectly before I did the last updates.
Anyone figure this out? Tried my first timelapse last night the the top 3" are cut off cause it's zoomed in to far.
i found an explanation here:
Raspi cam has different cominations for modes, Field of views, aspect ratios and binning. Take a look at the pictures... this might clear up the situation
thanks for the good link.
At the end was able to restore a older version and reset to system.
One hint for setup/activation of the infrared leds you have add a line to the /boot/conifg.txt with