[sane-devel] sane scans take so long

[m. allan noah]

try getting a scan of a small area at 600dpi and capture a log:

SANE_DEBUG_CANON630U=255 scanimage [arguments required to make small
scan] > /dev/null 2>sane.log

then do a similar sized scan with the windows driver, but capture a
trace with this tool:

http://www.pcausa.com/Utilities/UsbSnoop/

Then compress both of those files and send them to the list. Hopefully
this will be enough info to see the difference.

allan

On Sat, Feb 13, 2010 at 10:41 PM, tj <999alfred at comcast.net> wrote:
> Why do scans take so long on my Canoscan FB630U?
> I scan a 6"x4" color photo @600dpi and it takes just over four minutes. I
> boot the same machine to Windows XP and do the same exact scan using Paint
> Shop Pro and it takes only 43 secs.
>
> Don't even try to do a 600dpi black/white scan 8.5"x11" like a copier. Just
> start it and then go watch a TV show.
>
> Slackware 13
> xsane 0.996
>
> tj
>
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>            to sane-devel-request at lists.alioth.debian.org
>



-- 
"The truth is an offense, but not a sin"