Max

I had the same issue a while back. Quick look in my code revealed: `tax.get_axes().set_aspect(1)` `tax._redraw_labels()` at the very end of plotting, right before saving. Maybe this did the trick?

I arrived here from Octoprint (new camera stack) and was impressed as my camera was detected out of the box by camera-streamer. Recently, I started to tweak camera settings and...

> Why it is happening is known, see: > > [#114 (comment)](https://github.com/ayufan/camera-streamer/issues/114#issuecomment-1792851339) > > That code simply needs to be fixed to parse correctly. Hmm, somehow I read this but...

I thin I found the issue: https://github.com/ayufan/camera-streamer/blob/54bdd9d4d6a2c67291ecc419cc482423605dedea/device/libcamera/options.cc#L427-L430 calls `libcamera_parse_control_value`, which itself separates the values by `,`: https://github.com/ayufan/camera-streamer/blob/54bdd9d4d6a2c67291ecc419cc482423605dedea/device/libcamera/options.cc#L357-L372 and calls `libcamera_parse_rectangle` for each `,`-divided section individually. * for `0,0,1000,1000` it is...

Hmm, as `case libcamera::ControlTypeRectangle: ` already looks like it knows that it is expecting a Rectangle. So an easy fix would be: ``` case libcamera::ControlTypeRectangle: control_value.set(libcamera_parse_rectangle(value)); ``` But I don't...

Last time I tried to test some local changes, I encountered error messages I did not understand. At least the error message looks identical to the recently merged #140 ....

I retested with the latest fix in `main` branch and the `libcamera` option `ScalerCrop`, [which does not need a span](https://libcamera.org/api-html/namespacelibcamera_1_1controls.html), and is supposed to crop the output video. So I...

> **Case 2: array set in options for `AfWindows`** > `OPTIONS='--camera-options="AfMetering=1" --camera-options="AfWindows=[(1152,1296,2304,1296)]"` Ok, looking at how `libcamera_parse_rectangle ` works, it either accepts `AfWindows=x,y,width,height` or `AfWindows=(x,y)/width,height`. Passing an array of multiple...

This might be a duplicate of #121 ?

I had the same issue. Updating from 2.1.2 to 2.2.0 fixed it for me. I believe the following correction did the trick: https://github.com/KartoffelToby/better-thermostat-ui-card/commit/7f1c52f2381f42315c69bd16905a035da9de80d5#diff-62f80f654a7b30de72bf3c9c3007b688a8cb713678d64c0f6b1a450234f2f98aL908-R914