-
Notifications
You must be signed in to change notification settings - Fork 1
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
The encoder outputs incorrect qoi with some inputs #6
Comments
Interesting. Thank you for the report! |
So here what I found. I've added
which saves raw pixel data into files. Turned out, the output was exactly the same for all listed images except for 3 occurrences.
Those three have If you don't mind, I'll add modified version of your script to the repository to test that all four possible roundtrips produce exactly the same pixel values. |
Sure. I want to check the result. Could you like to push the raw-data output feature or put the patch for |
Yea, I will push changes to allow conversion to raw pixels data and the script. |
I wasn't active lately, but I've pushed fix and validation script. |
@zakarumych I've confirmed the new commit, but the
Let's ignore the two in |
@zakarumych In my persornal project
So, it seems that the core logic of In summary, |
According to below script, the encoder of
rapid-qoi
outputs incorrect data with some inputs:The text was updated successfully, but these errors were encountered: