-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alignment markers shifting after digit ROI changes #3035
Comments
The alignment marks are saved as images, while the ROIs are saved as coordinates. Process sequence correct: Process sequence wrong: |
In all of my instances, I did not change the reference image or camera settings. I was only fine tuning the digital ROIs. I then rebooted and the preview on the home page had the alignment markings off. If I went in to align markers and did NOT make any changes, but saved them, it returned to normal after another reboot. |
Apologies for the long delay. It was working and sending data to HA for 16 days straight. It then just stopped sending data, the webpage would not load, and after several reboots, I let it sit for a while. I then went to check the webpage last night, and it started loading again (faster than ever). The issue came up again, and I went through the same process. I went to Alignment>Alignment Markers, then I just clicked update marker, save new marker. I then repeated for my second marker. Rebooted and it worked again, successfully reporting the correct value. I did not change any other settings. I do have the algorithm set to the default as pictured above. Edit: I did need to change the previous value, as it was 7 days old. |
The Problem
When adjusting digit ROIs and rebooting, the alignment markers become misaligned. If I then update markers (without actually moving) and save the config, then reboot, it aligns properly in the next workflow after rebooting.
Version
Logfile
Expected Behavior
No response
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: