This is a multi-part message in MIME format.
--050101050200040301050008
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
m. allan noah wrote:
> another possible cause might be usb packet timeouts. are there any error
> messages in /var/log/mess
Gerhard Jaeger wrote:
> Hi,
>
> the 1250 is a "stupid" LM983x based scanner which knows nothing about
> jpeg compression. The stop and go is a "feature" of the LM983x to avoid
> data loss (of course you encounter this problem...)
>
> I think that the libusb and or the usb-stack itself is the prob
Hi,
> the 1250 is a "stupid" LM983x based scanner which knows nothing about
> jpeg compression. The stop and go is a "feature" of the LM983x to avoid
> data loss (of course you encounter this problem...)
So I tried again in windows and here the stop and go just appears with
very high reslotions
Hi,
the 1250 is a "stupid" LM983x based scanner which knows nothing about
jpeg compression. The stop and go is a "feature" of the LM983x to avoid
data loss (of course you encounter this problem...)
I think that the libusb and or the usb-stack itself is the problem. I've
currently not testet here
Hi,
I am using sane-backends 1.0.14 with epson 1250 scanner and have
following problem:
When I try to scan with higher dpi (eg 600, but starts at 240dpi
already) the scanning process isn't done in one go. It is more like
scan-pause-scan-pause-scan-pause...etc. Not only the speed suffers by
th
if this scanner is usb 1.1 and capable of jpeg compression in hardware,
that might explain the difference, since color scans at anything above 200
dpi can usually fill the usb. windows might use the jpeg compression, and
sane might not.
another possible cause might be usb packet timeouts. are t
