diff options
| author | foucault <foucault@users.noreply.github.com> | 2022-05-17 14:02:12 +0200 |
|---|---|---|
| committer | fiaxh <git@lightrise.org> | 2022-05-17 14:08:22 +0200 |
| commit | 186361fd8a381ef3c3334683dfb9cc4de1417596 (patch) | |
| tree | 0f03291d8772710c8616e6871da0d394d388451e /plugins/omemo/data | |
| parent | 99c076254abc6e2b03b784732a76a389e5a4f801 (diff) | |
| download | dino-186361fd8a381ef3c3334683dfb9cc4de1417596.tar.gz dino-186361fd8a381ef3c3334683dfb9cc4de1417596.zip | |
Fix calculation of best camera framerate
When the algorithm iterates over all the available v4l2 capabilities it tries to determine the best framerate for each one of YUYV (video/x-raw) modes presented by the hardware (best_fraction, line 357 in device.vala). Regardless of what's determined to be the "best" YUYV mode from within the conditional right after (line 385) the best fractional framerate will always point to the last iterated framerate, which might be an extremely low one, like 7 or 5 FPS. When the framerate is then stored in the Gst.Structure (line 394) the fractional framerate will always be that last value which might be different than the correct one as calculated by best_fps (line 386). This workaround solves this issue by only updating best_fraction when the conditional in line 385 is satisfied.
from issue #1195
Diffstat (limited to 'plugins/omemo/data')
0 files changed, 0 insertions, 0 deletions