Open stuntsman opened 3 years ago
Hello stuntsman,
Please send an example and I will have a look. The cause could even be the variation of the yellow colour. All thresholds were taken from a bigdata analysis using few different scanners.
Best wishes
El mar., 23 feb. 2021 12:48, stuntsman notifications@github.com escribió:
Our Kyocera printer has the tracking dots which can be seen using graphic software easily (they're literally over the entire page when green channel levels are adjusted), however deda is not recognizing the dots in a 600dpi PNG.
I can't see any options for threshold or anything else. Is there anything I should try or would you accept an example for further developments?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dfd-tud/deda/issues/23, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCBCD57F6YZ4EHBA4REFH3TAOIYNANCNFSM4YCK2WJA .
I've got a Kyocera M5526cdn, here's my scan. We also have the same MFP at work, so if it helps, I can also do a test print there.
Sorry for the late answer. As far as I see, the printer prints the dots repeatedly over the whole page. As we know, such a small yellow dot is omitted by the printer sometimes. Unfortunately, in your example, I have not managed to find one complete valid matrix. At least one dot is wrong in each copy. What you can do:
Also, we could implement the code error correction for Kyocera pattern (pattern 2) which would tolerate one wrong dot per block.
Our Kyocera printer has the tracking dots which can be seen using graphic software easily (they're literally over the entire page when green channel levels are adjusted), however deda is not recognizing the dots in a 600dpi PNG.
I can't see any options for threshold or anything else. Is there anything I should try or would you accept an example for further developments?