https://bugs.kde.org/show_bug.cgi?id=430365
mountainai...@outlook.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Resolution|WORKSFORME |---
Status|RESOLVED |REOPENED
--- Comment #9 from mountainai...@outlook.com ---
I am re-opening this ticket because I ran into this issue last night and was
able to capture some guide logs.
In short, my rig was guiding well and dithering every 5 frames. When it
dithered, it would trigger one, two, sometimes 3 aborts of the image capture
because it thought the RMS was too high (> 2"). However, on the guiding
screen, the total RMS was still about 1" and I saw no bad spikes. I believe at
some point Jasem mentioned fixing the calculation so we wouldn't see it jump to
5, 10" RMS after a dither... so the guiding screen doesn't show that
artificially-high RMS value, but the capture module still aborts like it still
sees it. I hope this log captures a couple instances of it.
--
You are receiving this mail because:
You are watching all bug changes.
