Den 17.05.2020 kl. 14.14 skrev Torfinn Ingolfsen: > On Sun, May 17, 2020 at 11:14 AM Frederik “Freso” S. Olesen > <[email protected]> wrote: >> >> I recently tried to do some scans and noticed they started turning out >> with a noticeable red tint which they didn’t have previously. You can >> see some comparisons and my initial explorations into the issue here: >> https://community.metabrainz.org/t/red-tint-on-scans/476126?u=freso > > This sounds similar to an old libtiff bug, see > http://bugzilla.maptools.org/show_bug.cgi?id=2150
That does sound like a possible candidate! At the very least, it’s a venue I didn’t look into yet. I currently have libtiff 3.9.7 and 4.1.0 installed. /usr/lib/libtiff.so points to libtiff.so.5.5.0 which should be the 4.1.0 version. My desktop has the exact same versions though. > Does the current xsane have options to change what format and / or > parameters to save the file as? > If so, try to change to a different format, in order to see if you > can narrow down where the bug might be. I was saving to PNG, but XSane has tons of options for saving in different formats and tweaking lots of knobs etc. (one of the reasons I couldn’t switch to something like simple-scan :)). Let me test a bit with various output… No additional changes, I get the same red tint saving to TIFF, PNM, JPEG, PNG, PS, PDF. I tried to tweak various compression settings and ended up turning compression off completely (under Settings → File type), but still get the same tint for both PNG and TIFF scans at least. Anything else you might be able to suggest I could try? -- Solidarity, Frederik “Freso” S. Olesen <https://freso.dk/> Like what I do? Check out <https://www.patreon.com/Freso>!
signature.asc
Description: OpenPGP digital signature
