match
(actual pages in ADF vs. -b flag), abort_session() is being called and
suspect this might be causing some trouble. I haven't found where
that's happening yet. It doesn't appear to be from inside mp150_scan().
---
Henry Ptasinski
henry at logout.com
On 05/24/2013 08:55 AM, Rol
reboot the printer.
I'm using:
scanimage (sane-backends) 1.0.24git; backend version 1.0.24
with sources from today.
For comparison, Canon's scangearmp v2.10.33 doesn't seem to have issues
with empty ADF on this scanner.
---
Henry Ptasinski
henry at logout.com
On 05/27/2013
--source "ADF Duplex" > scanimage_test.pnm
I get a file with the first page of the scan (front side only),
scanimage quits with status 0, and then the printer hangs waiting for
something. Is it possible to scan multiple pages with scanimage, or do
I need to use xsane?
Thanks,
---
Henry Pta
ckends/sane-backends_1.0.23.orig.tar.gz
It worked fine for me, and the md5sum comes out correct.
---
Henry Ptasinski
henry at logout.com
dows machine with usbsnoop
> (http://benoit.papillault.free.fr/usbsnoop/). This program is old and
> runs with xp only, but we have a parser for the log files (spike4.pl).
>
> Cheers,
> Rolf
>
>
> Am 05.12.2012 00:57, schrieb Henry Ptasinski:
>> Rolf,
>>
&g
ment", and I'm not able to cancel out of the scan.
My recent tests were via network. I'll attach the scanner via USB and
try to collect some debug info.
---
Henry Ptasinski
henry at logout.com
On Thu, Nov 29, 2012 at 11:34:08AM +0900, Gernot Hassenpflug wrote:
> On Thu, Nov 29, 2012 at 2:43 AM, Henry Ptasinski wrote:
> > On 11/28/2012 09:38 AM, Henry Ptasinski wrote:
> >>
> >> Flatbed scans with resolutions up to 600 dpi all seem to be working
> >&
The MX890 series scanners do not need pixel reordering at high dpi, so
treat them the same as MX360, MX370, etc.
Signed-off-by: Henry Ptasinski
---
backend/pixma_mp150.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/backend/pixma_mp150.c b/backend/pixma_mp150.c
On 11/28/2012 09:38 AM, Henry Ptasinski wrote:
> Flatbed scans with resolutions up to 600 dpi all seem to be working
> fine. At 1200 and 2400 dpi, the images are mangled. Columns appear to
> be interleaved at both resolutions. I assume the problem is due to a
> missing check in
On 11/27/2012 10:51 PM, Henry Ptasinski wrote:
> With the change, I've done a handful of scans via both USB and network
> without any failures. I'll do more extensive testing with various scan
> settings and see if it continues to behave properly.
Flatbed scans with resolu
be an underlying timing issue somewhere, as the original value
of 60 seemed to correlate to about 3 seconds of real time (and setting
tmo to 120 mapped to 6 seconds of real time). I haven't traced back
through the code to see what the intended resolution is for tmo, but a
50 msec resolution seems odd.
---
Henry Ptasinski
henry at logout.com
On 10/02/2012 09:43 PM, Gernot Hassenpflug wrote:
> On Wed, Oct 3, 2012 at 12:31 PM, Henry Ptasinski wrote:
>> On 10/02/2012 10:22 AM, Gernot Hassenpflug wrote:
>>>
>>> On Tue, Oct 2, 2012 at 11:50 PM, Henry Ptasinski
>>> wrote:
>>>>
>>&g
On 10/02/2012 10:22 AM, Gernot Hassenpflug wrote:
> On Tue, Oct 2, 2012 at 11:50 PM, Henry Ptasinski wrote:
>> With the latest sane-backends sources from the git repo, my MX890 is
>> partially functional. Using scanimage to scan documents on the flatbed
>> works some of t
ey seem to be ignored. I think in those cases the scan is performed
using whatever settings were used on the previous scan, but I'm not sure
of that yet.
I haven't tried the ADF yet with sane, since basic scanning from the
flatbed is still somewhat unreliable.
---
Henry Ptasinski
henry at logout.com
14 matches
Mail list logo
