-
Notifications
You must be signed in to change notification settings - Fork 707
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
OCR problem? How I that possible? #2906
Comments
Can confirm this behavior with the same constallation with the last digit being 1 and still beeing recognised as 0 The ProblemOCR working but number not correctly used. Version'v15.6.0 Logfile[0d00h00m00s] 2024-02-14T13:29:51 [MAIN] ================================================= Expected Behaviorwhen recognising 1, then use 1 not 0 :D |
I have the exact same issue with the last digit being a 2 still being recognized as a 1. The Problem OCR working but number not correctly used. Version 'v15.6.0 Logfile Expected Behavior Report correctly recognized value |
Actually the problem continues as now recognizing 2 but setting the previous value again not to the recognized value. It seems to just adds +1. Now I have recognized 2 as the last digit but it show a 3 as the previous value. |
There was an issue in v15.5, maybe it is related to your issue, please update to rolling where we reverted this regression. |
Hi, Thank you |
no, try rolling or wait for the next release |
You can try the latest Automatic Build of the the |
are there any plans to build a release with this important fix in the next days ? |
We just released v15.7.0 which hopefully fixes this issue. |
I just saw the issue with 15.7.0 |
The Problem
OCR working but number not correctly used.
Version
'v15.6.0
Logfile
Expected Behavior
No response
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered: