Re: [sane-devel] Release 1.3 anyone?

2024-01-16 Thread m. allan noah
Release sounds good to me. I think I made a mess during the last one,
possibly due to some incomplete release documentation. That might require
some cleanup first.

allan

On Wed, Jan 10, 2024 at 4:07 PM Ralph Little  wrote:

> Hi,
> Thanks for that info.
> I will update the documentation.
>
> Cheers,
> Ralph
>
> On 2024-01-10 12:10, Martin Gubser via sane-devel wrote:
> > Hi
> >
> > At the same time the list of supported devices could be improved:
> > The Epson XP-6100 is only listed with a WiFi-interface. But it has
> > also a USB-interface that works very well. That should be documented.
> > People looking for a new printer/scanner could not consider the
> > XP-6100 because they want to connect it with USB.
> >
> > Martin
> >
> > Am 10.01.24 um 20:31 schrieb Ralph Little:
> >> Hi,
> >> It has been pointed out that we haven't had a release for a while.
> >> Perhaps we should get the ball rolling for a 1.3 release?
> >>
> >> Cheers,
> >> Ralph
> >>
> >
>
>
>

-- 
"well, I stand up next to a mountain- and I chop it down with the edge of
my hand"


Re: [sane-devel] SANE with Samsung SCX-4x21F Getting IO Error

2024-01-16 Thread Ralph Little

Hi,

On 2024-01-14 06:20, sqe6nouc--- via sane-devel wrote:

Hello,

I am currently trying to get SANE to scan with a Samsung SCX-4x21F MFP 
on Arch Linux.


I have sane 1.2.1-5 and xsane 0.999-6 on kernel 6.6.10-arch1-1 (KDE 
Plasma Wayland) with the following driver packages:


samsung-unified-driver 1.00.39-7
samsung-unified-driver-common 1.00.39-7
samsung-unified-driver-printer 1.00.39-7
samsung-unified-driver-scanner 1.00.39-7

dmesg:

[75005.102178] usb 3-9: new full-speed USB device number 6 using xhci_hcd
[75005.245210] usb 3-9: New USB device found, idVendor=04e8, 
idProduct=3419, bcdDevice= 1.00
[75005.245235] usb 3-9: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[75005.245245] usb 3-9: Product: SCX-4x21 Series
[75005.245248] usb 3-9: Manufacturer: Samsung
[75005.245249] usb 3-9: SerialNumber: .
[75005.926529] usblp 3-9:1.1: usblp0: USB Bidirectional printer dev 6 
if 1 alt 0 proto 2 vid 0x04E8 pid 0x3419

[75005.926577] usbcore: registered new interface driver usblp

Error I am getting:
Failed to start scanner: Error during device I/O

If I wait a bit then click scan again, it starts scanning, however the 
scan head stuck at the end of the flatbed and XSane hangs for a bit 
then the following error is shown:

Error during read: Error during device I/O

After this, the scan head is still stuck at the end of the flatbed

Any help would be appreciated. Thank you.



I wonder why the xerox_mfp backend wouldn't provide you with support for 
this device. You have a very recent version of the backends and it is 
supposed to be supported.

Could you show us the output of:

scanimage -L

Cheers,
Ralph



Re: [sane-devel] Sheet Feed scanner, saving DPI info

2024-01-16 Thread Andy Bennett

Hi,


But I need the file to include DPI information for further processing.

The originals could be all different sizes.  tiny gas receipts, 
envelopes, super long walgreens receipts. seldom 8.5x11 because 
I use an ADF for that.


My sheet feed scanner is double sided, and I've been calling it thusly:
scanimage -d 'dsseries:usb:0x04F9:0x60E0' --format=jpeg -p -v 
--mode=Color --resolution=300 --batch=$(date 
+%Y%m%d_%H%M%S)p%d.jpg --batch-count=2 --batch-print


I'm not sure if scanimage puts the data in an exif tag in the JPEG.
I use PNM format, instead of JPEG, and that file is contains just the 
dimension of the image and a bag of pixels.


...so as you put "--resolution=300" on the command line, I would get the 
information manually from that and record it where you need it.




And scanimage tells me:
scanimage: scanning image of size 2548x4199 pixels at 24 bits/pixel

p1 is the front and p2 is the rear.  Obviously they scan at the 
same time.  The scanimage command "waits" for the first page to 
pull through, and the second page is instant because its 
probably held in a buffer in the scanner.



What do I need to add to my commandline to make it scan as long 
as it takes to pull the whole paper through???

Or to increase that max page length to something large, say 3 feet?


I use the options "--page-height=500.015mm -y 500.015mm" on my Fujitsu 
ix500.
At least on the Fujitsu driver, if you use a number that's too big it tells 
you what the largest number it supports is, sets it to that and then 
carries on. So you can find out the limit by putting in a really large 
number.


You might also be able to find it out from "scanimage --help" when the 
scanner is attached, as that will show you the driver specific options and 
some information about them.



Before it saves the file it needs to know the dimensions of the 
paper because it has to write the DPI.  And I won't know how 
long each sheet is until I scan them through.  I need the 
scanner to measure them in effect.


For driving scan image, all the --page-width, --page-height -x and -y 
options are all in millimeters, so you don't need to worry about pixels at 
all.


After you have acquired the image the JPEG will know how many pixels it has 
and the dimension of the image.

You can get the DPI from the command line as mentioned above.

That should give you what you need to process the image.

...but, even on the ix500 with the automatic document feeder, I find that I 
need to trim and straighten some documents, especially reciepts. Whilst the 
driver only acquires an image as long as the piece of paper inserted (up to 
the maximum length specifed with --page-height and -y), it always acquires 
the entire specified width, even if there is no paper there. So I need to 
straigthen the reciept up and chop the sides off.




Does that help?



Best wishes,
@ndy

--
andy...@ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF