Bug#968918: Threshold function is extremely slow - Unusable - possible regression

2020-11-02 Thread Jeff
On 21/10/2020 04:35, debian-testing wrote: > What version of gscan2pdf and imagemagick are you using to reproduce the > problem? It has to be recent versions on Debian 11 and the scan or image > also needs to be 600dpi (300 dpi is fast). Thanks. This was the detail that allowed me to reproduce

Bug#968918: Threshold function is extremely slow - Unusable - possible regression

2020-10-21 Thread debian-testing
Yes, the mageMagick issue #1819 (https://github.com/ImageMagick/ImageMagick/issues/1819) discusses performance also. See the following quotes: "...the dithering step takes so long that I haven't had the patience to let it finish yet...", "...Not sure why it is doing very slow dithering...",

Bug#968918: Threshold function is extremely slow - Unusable - possible regression

2020-09-04 Thread Jeff
Thanks for the report. https://github.com/ImageMagick/ImageMagick/issues/1819 doesn't mention performance problems, just corruption in the image. I can't reproduce your problem. The threshold tool works fine for me with or without conversion to PNG first. Please start gscan2pdf from the

Bug#968918: Threshold function is extremely slow - Unusable - possible regression

2020-08-23 Thread debian-testing
Package: gscan2pdf Version: 2.8.2-1 Threshold function is extremely slow - Unusable - Possible regression Applying threshold on a scanned image is extremely slow. Doing the same transformation using mogrify/convert is many times faster. This seems to be a regression during the last few months