Am 08.12.20 um 20:24 schrieb Jörg Frings-Fürst: > tags 942176 + moreinfo > thanks > > > > Hello Philipp, > > please can you check if the bug still exists in the current version?
I just checked usinghte current version in Debian testing. There are still problems at 2400 and 4800 resolutions, but they are different now. The main problem is now about wrong colors at these resolutions. Scans at reolutions up to 1200 still work well as before. I tried to scan a small area (3 cm x 7 cm) at 2400. xsane did hang for about 2 minutes, then scanned, then it took another 3 minutes (for recieving RGB data - the progress bar moving slowly), but then got a good scan result, which looked correct. Similarly when scanning the same area at 4800 (except that it took much longer to reeive the data). But this time the black text appeared bordeux. At a subsequent attempt using a smaller 2.5 cm x 1.5 cm area, the situation was the same, except that the color problem already appeared at 2400. I also tried scanning a large (20 cm x 20 cm) area at 2400 and 4800. There again was the hang at the beginning - about 1 to 2 minutes, but it did scan after that. For both resolutions, the result again had the wrong colors where black appearead as bordeaux. For 4800, I also got a different area than specified. rather than the 20 cm x 20 cm part I selected in xsane (and which I got at 2400), I got an area 20 cm wide and about 0.5 cm high. Summary: The situation improved somewhat, but is still far from perfect: There is still an odd waiting time when starting to scan at 2400 or 4800 (at 1200 and below the scan starts nearly instantly, after less than second). At 4800 colors ar wrong. Once one of these problems appears, it affects all resolutions until restarting xsane: Having done a scan at 2400 or 4800, subsequent scans at lower resolutions also have the waiting time at the start. Having done a scan at 2400 or 4800, where black appeared as bordeaux, subsequent scans at lower resolutions also have wrong colors.
