date:20071218

Hi all,
I am slowly working on the coolscan2 backend and I am looking at
tiffscan for batch scanning.

What I see is that any frontend that would drive a batch scan should
manage different type of feeder and pages. Probably the easier one is
the ADF case where the scanner load/eject every page; but the trickier
one is the stripe case: we may load/eject a stripe, but we need to batch
frames inside the stripe.

When a frontend offer parameters like --batch-from-page/frame and
--batch-count, it should be able to understand what feeder is present
and how to ask for a specific frame.

So, my questions: is there already any standard for those action? Is
there any defined rule for how to name a backend parameter like
--frame-number? Is there any way to know what feeder types are
available at a given time?

Thanks,
Giuseppe

[sane-devel] frame and batch mode

2007-12-18 Thread Jonathan Buzzard

On Tue, 2007-12-18 at 12:13 +0100, Giuseppe Sacco wrote:
 Hi all,
 I am slowly working on the coolscan2 backend and I am looking at
 tiffscan for batch scanning.
 
 What I see is that any frontend that would drive a batch scan should
 manage different type of feeder and pages. Probably the easier one is
 the ADF case where the scanner load/eject every page; but the trickier
 one is the stripe case: we may load/eject a stripe, but we need to batch
 frames inside the stripe.
 
 When a frontend offer parameters like --batch-from-page/frame and
 --batch-count, it should be able to understand what feeder is present
 and how to ask for a specific frame.
 
 So, my questions: is there already any standard for those action? Is
 there any defined rule for how to name a backend parameter like
 --frame-number? Is there any way to know what feeder types are
 available at a given time?

Good grief, those feelings of d?ja vu. are pretty strong at the moment.

The basics are that as it stands the SANE standard is heavily geared to
transmission scanning on flatbed scanners. Understandable as it probably
accounts for 99% of users requirements.

However any work in extending the SANE standard to take into account
other types of scanners and things like ADF's scan buttons on scanners
etc. has all come to nothing.

The specific requirements for film scanners where detailed by myself
over five years ago. I guess it is just to easy to fork over the money
for Vuescan and just get on with actually using your film scanner under
Linux.


JAB.

-- 
Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk
Northumberland, United Kingdom.   Tel: +44 1661-832195

[sane-devel] frame and batch mode

Il giorno mar, 18/12/2007 alle 12.00 +, Jonathan Buzzard ha scritto:
 On Tue, 2007-12-18 at 12:13 +0100, Giuseppe Sacco wrote:
[...]
  So, my questions: is there already any standard for those action? Is
  there any defined rule for how to name a backend parameter like
  --frame-number? Is there any way to know what feeder types are
  available at a given time?
 
 Good grief, those feelings of d?ja vu. are pretty strong at the moment.
 
 The basics are that as it stands the SANE standard is heavily geared to
 transmission scanning on flatbed scanners. Understandable as it probably
 accounts for 99% of users requirements.

Is this problem solved with SANE2?

[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9

i would turn up the debugging level on the snapscan backend (which is
somehow already set to 2?):

SANE_DEBUG_SNAPSCAN=255 scanimage -L

and lets see if that gives us any more info.

allan

On 12/17/07, andy whelan bgbghq at gmail.com wrote:
 Hello,

 First off let me say that I am an absolute novice when it comes to any kind
 of a command line interface, so go easy on me.

 Here's my problem. I have installed: sane backends 10.0.18 and libusb 0.1.12

 on a G4 macintosh running MacOS 10.3.9 and I can't get my scanner to work
 using scanimage.

 This is what happens:

 Andy-Whelans-Computer:~ andywhelan$ sane-find-scanner

   # sane-find-scanner will now attempt to detect your scanner. If the
   # result is different from what you expected, first make sure your
   # scanner is powered up and properly connected to your computer.

   # No SCSI scanners found. If you expected something different, make sure
 that
   # you have loaded a kernel SCSI driver for your SCSI adapter.

 found USB scanner (vendor=0x067b, product=0x2303) at
 libusb:001:003-067b-2303-00-00
 found USB scanner (vendor=0x04b8 [EPSON], product=0x011f [EPSON Scanner]) at
 libusb:002:002-04b8-011f-ff-ff
   # Your USB scanner was (probably) detected. It may or may not be supported
 by
   # SANE. Try scanimage -L and read the backend's manpage.

   # Not checking for parallel port scanners.

   # Most Scanners connected to the parallel port or other proprietary ports
   # can't be detected by this program.

   # You may want to run this program as root to find all devices. Once you
   # found the scanner devices, be sure to adjust access permissions as
   # necessary.

 Which sounds okay to me. Then:

 Andy-Whelans-Computer:~ andywhelan$ scanimage -L
 [sanei_debug] Setting debug level of snapscan to 2.
 [snapscan] add_usb_device: error opening device
 libusb:002:002-04b8-011f-ff-ff: Invalid argument

 And that's all I know. It sounds to me like SANE doesn't like what it's
 getting from libusb, but like I said, I'm pretty inexperienced with this
 stuff.

 Any help would be greatly appreciated.

 Andy

 --
 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

[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9

2007-12-18 Thread Oliver Schwartz

Hi,

you also need to specify the path to the firmware file in  
snapscan.conf, which is installed in /usr/local/etc/sane.d/ on OS X,  
IIRC.

The firmware file itself (esfw30.bin) should be contained on the  
windows driver CD.

See http://snapscan.sourceforge.net for some additional infos on the  
firmware files. Let me know if that doesn't solve your problem.

Regards,

Oliver


On 18.12.2007, at 05:51, andy whelan wrote:

 Andy-Whelans-Computer:~ andywhelan$ scanimage -L
 [sanei_debug] Setting debug level of snapscan to 2.
 [snapscan] add_usb_device: error opening device libusb: 
 002:002-04b8-011f-ff-ff: Invalid argument

[sane-devel] frame and batch mode

On 12/18/07, Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org wrote:
 Il giorno mar, 18/12/2007 alle 12.00 +, Jonathan Buzzard ha scritto:
  On Tue, 2007-12-18 at 12:13 +0100, Giuseppe Sacco wrote:
 [...]
   So, my questions: is there already any standard for those action? Is
   there any defined rule for how to name a backend parameter like
   --frame-number? Is there any way to know what feeder types are
   available at a given time?
 
  Good grief, those feelings of d?ja vu. are pretty strong at the moment.
 
  The basics are that as it stands the SANE standard is heavily geared to
  transmission scanning on flatbed scanners. Understandable as it probably
  accounts for 99% of users requirements.

 Is this problem solved with SANE2?

would both of you please excuse my ignorance, as i primarily deal with
ADF machines, but-

why does the front-end need to be involved in the movement at all? can
the backend not detect the additional slides and move the feeder
automatically? perhaps i am not picturing the mechanism correctly...

allan

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

[sane-devel] frame and batch mode

On Tue, 18 Dec 2007 08:40:22 -0500
m. allan noah kitno455 at gmail.com wrote:

 
  Is this problem solved with SANE2?
 
 would both of you please excuse my ignorance, as i primarily deal with
 ADF machines, but-
 
 why does the front-end need to be involved in the movement at all? can
 the backend not detect the additional slides and move the feeder
 automatically? perhaps i am not picturing the mechanism correctly...

 it would be fine if the same option to obtain this same effect
 could be used in every backend.

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] permission request


 To:
Gerhard Jaeger
Henning Geinitz
Julien Blache
Oliver Rauch
Petter Reinholdtsen
M. Allan Noah

 Hello SANE Admins,

  I would like, in the interest of the SANE community of users and developers,
 to kindly ask the permission to add some much required frame types to the 
repository.

  Given that:

 - some types are already in use by in-repository backends
 - other types are in use by external backends 
 - the JPEG frame type has already been added
 - any well written frontend will not notice the change
 - the new types are not active by default 

  I ask you to ease the work of backend authors
 and allow this much requested change.
 
  Thanks in advance for your time and for your answer. 

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] frame and batch mode

Il giorno mar, 18/12/2007 alle 08.40 -0500, m. allan noah ha scritto:
 On 12/18/07, Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org wrote:
[...]
 why does the front-end need to be involved in the movement at all? can
 the backend not detect the additional slides and move the feeder
 automatically? perhaps i am not picturing the mechanism correctly...

You are right: the slide feeder works as you imagene, but if you have a
negative stripe, then you have to position on a variable offset from the
start of the stripe. The offset depends from how the camera moved it
when shooting, or based on the way you cutted the image.
This means that there is no fixed offset for frame, but there are
backend that coud accept an offset as parameter.

This offset require an interaction between user and backend.

Bye,
Giuseppe

[sane-devel] permission request

2007-12-18 Thread Julien BLACHE

Alessandro Zummo azummo-lists at towertech.it wrote:

Hi,

   I would like, in the interest of the SANE community of users and developers,
  to kindly ask the permission to add some much required frame types to the 
 repository.

   I ask you to ease the work of backend authors
  and allow this much requested change.

I don't really have a say on this matter, not being either a backend
or frontend developer, but that's OK as far as I'm concerned.

Don't forget to update the SANE standard while doing so.

JB.

-- 
Julien BLACHE   http://www.jblache.org 
jb at jblache.org  GPG KeyID 0xF5D65169

[sane-devel] frame and batch mode

On Dec 18, 2007 9:05 AM, Giuseppe Sacco
giuseppe at eppesuigoccas.homedns.org wrote:
 Il giorno mar, 18/12/2007 alle 08.40 -0500, m. allan noah ha scritto:
  On 12/18/07, Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org wrote:
 [...]
  why does the front-end need to be involved in the movement at all? can
  the backend not detect the additional slides and move the feeder
  automatically? perhaps i am not picturing the mechanism correctly...

 You are right: the slide feeder works as you imagene, but if you have a
 negative stripe, then you have to position on a variable offset from the
 start of the stripe. The offset depends from how the camera moved it
 when shooting, or based on the way you cutted the image.
 This means that there is no fixed offset for frame, but there are
 backend that coud accept an offset as parameter.

 This offset require an interaction between user and backend.


ahh- so how does the user determine this offset? does he measure the
strip before placing it in the machine?

allan


 --
 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

[sane-devel] permission request

On Dec 18, 2007 9:01 AM, Alessandro Zummo azummo-lists at towertech.it wrote:
  Hello SANE Admins,

   I would like, in the interest of the SANE community of users and developers,
  to kindly ask the permission to add some much required frame types to the 
 repository.

   Given that:

  - some types are already in use by in-repository backends
  - other types are in use by external backends
  - the JPEG frame type has already been added
  - any well written frontend will not notice the change
  - the new types are not active by default

   I ask you to ease the work of backend authors
  and allow this much requested change.

i already have a patch to sane.h waiting on my disk. it moves
SANE_FRAME_JPEG, and adds all the other types that are in the bh
backend, and types for the various IR combinations, including your
RGBI at 0x10. I have not yet updated the standard, because i was
waiting to see if discussion would develop around the idea of calling
this SANE 1.1.0.

allan

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

[sane-devel] permission request

On Tue, 18 Dec 2007 09:45:10 -0500
m. allan noah kitno455 at gmail.com wrote:

   - the new types are not active by default
 
I ask you to ease the work of backend authors
   and allow this much requested change.
 
 i already have a patch to sane.h waiting on my disk. it moves
 SANE_FRAME_JPEG, and adds all the other types that are in the bh
 backend, and types for the various IR combinations, including your
 RGBI at 0x10. I have not yet updated the standard, because i was
 waiting to see if discussion would develop around the idea of calling
 this SANE 1.1.0.

 great. I think bumping rev to 1.1 would help to clarify the situation.
 so we have two favorable comments 'till now.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] frame and batch mode

Il giorno mar, 18/12/2007 alle 09.37 -0500, m. allan noah ha scritto:
[...]
 ahh- so how does the user determine this offset? does he measure the
 strip before placing it in the machine?

We do not behave all the same way, so I will tell you how I am used to
work. I preview the first frame, then change offset until I get the
first frame ok, then I would like to batch scan the complete stripe.

Currently this is how I work with other software.

Bye,
Giuseppe

[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9

2007-12-18 Thread andy whelan

Oliver and Allan,

Thank you for the help. I have editted the snapscan.conf file so that the
path points to the firmware file. I tried again with the debugging level at
255.

Andy-Whelans-Computer:~ andywhelan$ SANE_DEBUG_SNAPSCAN=255 scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.53
[snapscan] add_usb_device(libusb:002:002-04b8-011f-ff-ff)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:002:002-04b8-011f-ff-ff)
[snapscan] add_usb_device: error opening device
libusb:002:002-04b8-011f-ff-ff: Invalid argument
[snapscan] sane_snapscan_get_devices (0xb830, 0)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[snapscan] sane_snapscan_exit

Andy

On Dec 18, 2007 6:04 AM, Oliver Schwartz Oliver.Schwartz at gmx.de wrote:

 Hi,

 you also need to specify the path to the firmware file in
 snapscan.conf, which is installed in /usr/local/etc/sane.d/ on OS X,
 IIRC.

 The firmware file itself (esfw30.bin) should be contained on the
 windows driver CD.

 See http://snapscan.sourceforge.net for some additional infos on the
 firmware files. Let me know if that doesn't solve your problem.

 Regards,

 Oliver


 On 18.12.2007, at 05:51, andy whelan wrote:

  Andy-Whelans-Computer:~ andywhelan$ scanimage -L
  [sanei_debug] Setting debug level of snapscan to 2.
  [snapscan] add_usb_device: error opening device libusb:
  002:002-04b8-011f-ff-ff: Invalid argument


-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20071218/ca67f262/attachment.htm

[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9

On Dec 18, 2007 12:19 PM, m. allan noah kitno455 at gmail.com wrote:
 better add usb debugging as well:

 SANE_DEBUG_SNAPSCAN=255 SANE_DEBUG_SANEI_USB scanimage -L

 allan


 On Dec 18, 2007 11:44 AM, andy whelan bgbghq at gmail.com wrote:
  Oliver and Allan,
 
  Thank you for the help. I have editted the snapscan.conf file so that the
  path points to the firmware file. I tried again with the debugging level at
  255.
 
  Andy-Whelans-Computer:~ andywhelan$ SANE_DEBUG_SNAPSCAN=255 scanimage -L
  [sanei_debug] Setting debug level of snapscan to 255.
  [snapscan] sane_snapscan_init
  [snapscan] sane_snapscan_init: Snapscan backend version 1.4.53
  [snapscan] add_usb_device(libusb:002:002-04b8-011f-ff-ff)
   [snapscan] add_usb_device: Detected (kind of) an USB device
  [snapscan] snapscani_usb_open(libusb:002:002-04b8-011f-ff-ff)
 
  [snapscan] add_usb_device: error opening device
  libusb:002:002-04b8-011f-ff-ff: Invalid argument
  [snapscan] sane_snapscan_get_devices (0xb830, 0)
 
  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).
  [snapscan] sane_snapscan_exit
 
  Andy
 
 
 
  On Dec 18, 2007 6:04 AM, Oliver Schwartz  Oliver.Schwartz at gmx.de wrote:
   Hi,
  
   you also need to specify the path to the firmware file in
   snapscan.conf, which is installed in /usr/local/etc/sane.d/ on OS X,
   IIRC.
  
   The firmware file itself (esfw30.bin) should be contained on the
   windows driver CD.
  
   See http://snapscan.sourceforge.net for some additional infos on the
   firmware files. Let me know if that doesn't solve your problem.
  
   Regards,
  
   Oliver
  
  
  
  
  
   On 18.12.2007, at 05:51, andy whelan wrote:
  
Andy-Whelans-Computer:~ andywhelan$ scanimage -L
[sanei_debug] Setting debug level of snapscan to 2.
[snapscan] add_usb_device: error opening device libusb:
002:002-04b8-011f-ff-ff: Invalid argument
  
  
 
 
  --
  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




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

[sane-devel] frame and batch mode

2007-12-18 Thread Jonathan Buzzard

On Tue, 2007-12-18 at 08:40 -0500, m. allan noah wrote:
 On 12/18/07, Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org wrote:
  Il giorno mar, 18/12/2007 alle 12.00 +, Jonathan Buzzard ha scritto:
   On Tue, 2007-12-18 at 12:13 +0100, Giuseppe Sacco wrote:
  [...]
So, my questions: is there already any standard for those action? Is
there any defined rule for how to name a backend parameter like
--frame-number? Is there any way to know what feeder types are
available at a given time?
  
   Good grief, those feelings of d?ja vu. are pretty strong at the moment.
  
   The basics are that as it stands the SANE standard is heavily geared to
   transmission scanning on flatbed scanners. Understandable as it probably
   accounts for 99% of users requirements.
 
  Is this problem solved with SANE2?
 
 would both of you please excuse my ignorance, as i primarily deal with
 ADF machines, but-
 
 why does the front-end need to be involved in the movement at all? can
 the backend not detect the additional slides and move the feeder
 automatically? perhaps i am not picturing the mechanism correctly...
 

Imagine I have just stuck an APS adaptor into my film scanner and loaded
up a 40 frame APS film. I wish to scan *one* frame which I happen to
know from the contact print I got when they where developed.

How without the front end telling the scanner which frame to advance to
and scan do you propose scanning this? From memory a TIFF image from an
APS frame on my scanner is about 30MB and takes about 1min over 400Mbps
Firewire. Scanning the lot is utterly impractical.

With 35mm film, I load the strip into a holder and insert the holder. I
want to scan just two frames from the possible six in the holder, and
they are frame 2 and 4. Oh and I want to scan 4 first so that it is not
sticking out the scanner with dust settling on it.

Does that illustrate the point?


JAB.

-- 
Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk
Northumberland, United Kingdom.   Tel: +44 1661-832195

[sane-devel] frame and batch mode

On Dec 18, 2007 12:37 PM, Jonathan Buzzard jonathan at buzzard.me.uk wrote:

 On Tue, 2007-12-18 at 08:40 -0500, m. allan noah wrote:
  On 12/18/07, Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org wrote:
   Il giorno mar, 18/12/2007 alle 12.00 +, Jonathan Buzzard ha scritto:
On Tue, 2007-12-18 at 12:13 +0100, Giuseppe Sacco wrote:
   [...]
 So, my questions: is there already any standard for those action? Is
 there any defined rule for how to name a backend parameter like
 --frame-number? Is there any way to know what feeder types are
 available at a given time?
   
Good grief, those feelings of d?ja vu. are pretty strong at the moment.
   
The basics are that as it stands the SANE standard is heavily geared to
transmission scanning on flatbed scanners. Understandable as it probably
accounts for 99% of users requirements.
  
   Is this problem solved with SANE2?
 
  would both of you please excuse my ignorance, as i primarily deal with
  ADF machines, but-
 
  why does the front-end need to be involved in the movement at all? can
  the backend not detect the additional slides and move the feeder
  automatically? perhaps i am not picturing the mechanism correctly...
 

 Imagine I have just stuck an APS adaptor into my film scanner and loaded
 up a 40 frame APS film. I wish to scan *one* frame which I happen to
 know from the contact print I got when they where developed.

 How without the front end telling the scanner which frame to advance to
 and scan do you propose scanning this? From memory a TIFF image from an
 APS frame on my scanner is about 30MB and takes about 1min over 400Mbps
 Firewire. Scanning the lot is utterly impractical.

 With 35mm film, I load the strip into a holder and insert the holder. I
 want to scan just two frames from the possible six in the holder, and
 they are frame 2 and 4. Oh and I want to scan 4 first so that it is not
 sticking out the scanner with dust settling on it.

 Does that illustrate the point?

yes- though i did have to lookup what APS was :)

the original question was what to name the SANE options that would
control this mess, and i suppose what option type they should be.
sounds almost like a comma-separated list:

4,2 or 4,2-1 if you wanted to skip #3. that sounds a bit like the
gamma vector control that some backends use...

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

[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9

2007-12-18 Thread andy whelan

I set usb debugging to 255, I hope this isn't too much.

Andy-Whelans-Computer:~ andywhelan$ SANE_DEBUG_SNAPSCAN=255
SANE_DEBUG_SANEI_USB=255 scanimage -L
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: Looking for libusb devices
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found USB device at location 0x1800
usb_os_find_devices: Found 001-05ac-8005-09-00 on 001 at location 0x1800
usb_os_find_devices: Found USB device at location 0x1810
usb_os_find_devices: Found 002-05ac-1002-09-00 on 001 at location 0x1810

usb_os_find_devices: Found USB device at location 0x1820
usb_os_find_devices: Found 003-067b-2303-00-00 on 001 at location 0x1820
usb_os_find_devices: Found USB device at location 0x1811
usb_os_find_devices: Found 004-05ac-0204-00-00 on 001 at location 0x1811

usb_os_find_devices: Found USB device at location 0x1812
usb_os_find_devices: Found 005-05ac-0304-00-00 on 001 at location 0x1812
usb_os_find_devices: Found USB device at location 0x1900
usb_os_find_devices: Found USB device at location 0x1910
usb_os_open: 05ac:0304
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x302440 34 1000
skipped 1 class/vendor specific interface descriptors
usb_os_close: 05ac:0304
usb_os_open: 05ac:0204
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x302380 59 1000
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_close: 05ac:0204
usb_os_open: 067b:2303
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x302870 39 1000
usb_os_close: 067b:2303
usb_os_open: 05ac:1002
usb_os_open(USBDeviceOpenSeize): another process has device opened for
exclusive access
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x302900 25 1000
usb_os_close: 05ac:1002
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for
exclusive access
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x303e80 27 1000
usb_os_close: 05ac:8005
usb_os_find_devices: Found USB device at location 0x1800
usb_os_find_devices: Found USB device at location 0x1810
usb_os_find_devices: Found USB device at location 0x1820
usb_os_find_devices: Found USB device at location 0x1811
usb_os_find_devices: Found USB device at location 0x1812
usb_os_find_devices: Found USB device at location 0x1900
usb_os_find_devices: Found 001-05ac-8005-09-00 on 002 at location 0x1900
usb_os_find_devices: Found USB device at location 0x1910
usb_os_find_devices: Found 002-04b8-011f-ff-ff on 002 at location 0x1910

usb_os_open: 04b8:011f
usb_os_open(USBDeviceOpenSeize): another process has device opened for
exclusive access
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x301dc0 39 1000
usb_os_close: 04b8:011f
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for
exclusive access
usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
usb_control_msg: 128 6 512 0 0x304210 27 1000
usb_os_close: 05ac:8005
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look
like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x05ac/0x1002, interface 0 doesn't look
like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x05ac/0x1002: no suitable interfaces
[sanei_usb] sanei_usb_init: found libusb device (0x067b/0x2303) interface 0
at libusb:001:003-067b-2303-00-00
[sanei_usb] sanei_usb_init: device 0x05ac/0x0204, interface 0 doesn't look
like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x05ac/0x0204, interface 1 doesn't look
like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x05ac/0x0204: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x05ac/0x0304, interface 0 doesn't look
like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x05ac/0x0304: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look
like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces
[sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x011f) interface 0
at libusb:002:002-04b8-011f-ff-ff
[sanei_usb] sanei_usb_init: found 2 devices
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0010
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0030
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0130
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: Looking for libusb devices
usb_set_debug: Setting debugging level to 255 (on)
[sanei_usb] sanei_usb_init: device

[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9

well- thats pretty clear:

another process has device opened for exclusive access

what else is running on the machine that might do that?

allan

On Dec 18, 2007 12:51 PM, andy whelan bgbghq at gmail.com wrote:
 I set usb debugging to 255, I hope this isn't too much.

 Andy-Whelans-Computer:~ andywhelan$ SANE_DEBUG_SNAPSCAN=255
 SANE_DEBUG_SANEI_USB=255 scanimage -L
 [sanei_debug] Setting debug level of sanei_usb to 255.
 [sanei_usb] sanei_usb_init: Looking for kernel scanner devices
 [sanei_usb] sanei_usb_init: Looking for libusb devices
 usb_set_debug: Setting debugging level to 255 (on)
 usb_os_find_busses: Found 001
 usb_os_find_busses: Found 002
 usb_os_find_devices: Found USB device at location 0x1800
 usb_os_find_devices: Found 001-05ac-8005-09-00 on 001 at location 0x1800
 usb_os_find_devices: Found USB device at location 0x1810
 usb_os_find_devices: Found 002-05ac-1002-09-00 on 001 at location 0x1810
 usb_os_find_devices: Found USB device at location 0x1820
 usb_os_find_devices: Found 003-067b-2303-00-00 on 001 at location 0x1820
 usb_os_find_devices: Found USB device at location 0x1811
 usb_os_find_devices: Found 004-05ac-0204-00-00 on 001 at location 0x1811
 usb_os_find_devices: Found USB device at location 0x1812
 usb_os_find_devices: Found 005-05ac-0304-00-00 on 001 at location 0x1812
 usb_os_find_devices: Found USB device at location 0x1900
 usb_os_find_devices: Found USB device at location 0x1910
 usb_os_open: 05ac:0304
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x302440 34 1000
 skipped 1 class/vendor specific interface descriptors
 usb_os_close: 05ac:0304
 usb_os_open: 05ac:0204
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x302380 59 1000
 skipped 1 class/vendor specific interface descriptors
 skipped 1 class/vendor specific interface descriptors
 usb_os_close: 05ac:0204
 usb_os_open: 067b:2303
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x302870 39 1000
 usb_os_close: 067b:2303
 usb_os_open: 05ac:1002
 usb_os_open(USBDeviceOpenSeize): another process has device opened for
 exclusive access
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x302900 25 1000
 usb_os_close: 05ac:1002
 usb_os_open: 05ac:8005
 usb_os_open(USBDeviceOpenSeize): another process has device opened for
 exclusive access
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x303e80 27 1000
 usb_os_close: 05ac:8005
 usb_os_find_devices: Found USB device at location 0x1800
 usb_os_find_devices: Found USB device at location 0x1810
 usb_os_find_devices: Found USB device at location 0x1820
 usb_os_find_devices: Found USB device at location 0x1811
 usb_os_find_devices: Found USB device at location 0x1812
 usb_os_find_devices: Found USB device at location 0x1900
 usb_os_find_devices: Found 001-05ac-8005-09-00 on 002 at location 0x1900
 usb_os_find_devices: Found USB device at location 0x1910
 usb_os_find_devices: Found 002-04b8-011f-ff-ff on 002 at location 0x1910
 usb_os_open: 04b8:011f
 usb_os_open(USBDeviceOpenSeize): another process has device opened for
 exclusive access
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x301dc0 39 1000
  usb_os_close: 04b8:011f
 usb_os_open: 05ac:8005
 usb_os_open(USBDeviceOpenSeize): another process has device opened for
 exclusive access
 usb_control_msg: 128 6 512 0 0xbfffed70 8 1000
 usb_control_msg: 128 6 512 0 0x304210 27 1000
  usb_os_close: 05ac:8005
 [sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look
 like a scanner (9/9)
 [sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces
 [sanei_usb] sanei_usb_init: device 0x05ac/0x1002, interface 0 doesn't look
 like a scanner (9/9)
 [sanei_usb] sanei_usb_init: device 0x05ac/0x1002: no suitable interfaces
 [sanei_usb] sanei_usb_init: found libusb device (0x067b/0x2303) interface 0
 at libusb:001:003-067b-2303-00-00
 [sanei_usb] sanei_usb_init: device 0x05ac/0x0204, interface 0 doesn't look
 like a scanner (0/3)
 [sanei_usb] sanei_usb_init: device 0x05ac/0x0204, interface 1 doesn't look
 like a scanner (0/3)
 [sanei_usb] sanei_usb_init: device 0x05ac/0x0204: no suitable interfaces
 [sanei_usb] sanei_usb_init: device 0x05ac/0x0304, interface 0 doesn't look
 like a scanner (0/3)
 [sanei_usb] sanei_usb_init: device 0x05ac/0x0304: no suitable interfaces
 [sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look
 like a scanner (9/9)
 [sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces
 [sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x011f) interface 0
 at libusb:002:002-04b8-011f-ff-ff
 [sanei_usb] sanei_usb_init: found 2 devices
 [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0010
 [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0030
 [sanei_usb]

[sane-devel] Canon PIXMA MP130

2007-12-18 Thread Johnny Rosenberg

2007/12/10, Epostlistor gurus.knugum at gmail.com:

I visited http://www.sane-project.org/contrib.html and readed about
contributing to the project - Writing a Backend (Driver).

The page said that You don't need to be an experienced programmer.
Backends are usually written in C, so some basic knowledge of this
language helps. You need a lot of patience, however, especially if you
can't get programmer's documentation from your scanner's manufacturer.

I learned C many years ago and I still think I remember most of it, but I
am not programming very much these days. I am writing here because I think
I need all the help I can get. Maybe someone is already doing this, then I
might be able to contribute in some way. If not, it feels like there are a
lot of things I need to know. Maybe there are similar backend drivers out
there that I can get inspiration from and learn how to write things like
that.

I have the Canon PIXMA MP130 and my operating system is GNU/Linux Ubuntu
Studio 7.10. I also have a small partition with Windows XP, so I can use
the scanner that way, but of course I want to use it with Ubuntu. At the
moment I can only use the printing function with Ubuntu, but I needed to
install additional software before that was possible.

Is there some kind of software for Windows that can scan what's sent and
received to/from the MP130 while scanning etc? I guess that would help
somewhat.

My idea is to write a very basic driver just to make it possible to scan
with no fancy features (which are pretty useless anyway in most cases).
Some things, like basic image editing, is better done with dedicated
software, such as GIMP, I guess.

So, any comments to this? Will this task be too tough for someone like
me..?

Johnny Rosenberg

Okay, seems like nobody's interested in this, so I guess I'll just skip the
idea and buy another skanner instead. Besides, I guess that I would have
failed doing this anyway.

Johnny Rosenberg
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20071218/35efa32d/attachment.htm

[sane-devel] permission request

2007-12-18 Thread Gerhard Jaeger

Am Dienstag, 18. Dezember 2007 15:03:59 schrieb Alessandro Zummo:
   I would like, in the interest of the SANE community of users and
 developers, to kindly ask the permission to add some much required frame
 types to the repository.

   Given that:

  - some types are already in use by in-repository backends
  - other types are in use by external backends
  - the JPEG frame type has already been added
  - any well written frontend will not notice the change
  - the new types are not active by default

   I ask you to ease the work of backend authors
  and allow this much requested change.

No objections from here - but, will we branch off 1.1.0
and have 1.0.x as maintenance branch?

What about the future of sane2? 

- Gerhard

[sane-devel] permission request

On Tue, 18 Dec 2007 21:01:50 +0100
Gerhard Jaeger gerhard at gjaeger.de wrote:

 
I ask you to ease the work of backend authors
   and allow this much requested change.
 
 No objections from here - but, will we branch off 1.1.0
 and have 1.0.x as maintenance branch?

 I'd sugest so, yes. do you think the CVS can be setup
 to handle this?

 What about the future of sane2? 

 I don't know. Is too much an effort for me to undertake.

 we have 3 positive comments, 3 to go. 

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] Canon PIXMA MP130

2007-12-18 Thread Johnny Rosenberg

2007/12/18, James Crow james at ultratans.com:

You might want to check the list archives for Canon PIXMA driver
support. I have the MP160 and it is supported. There is driver that
works in CVS. It may also include support for your printer.
Start here: http://home.arcor.de/wittawat/pixma/

Thanks,
James

There's exactly where I looked. Here's a quote from that site:
Unknown protocol: These devices don't work with this backend and there is
no easy way to add supports because they use a different command set which
has to be analyzed first. Co-programmers are welcome! :-) I personally
cannot do this because I don't have the devices. MP110 4A9:1700 1200 N N - N
unsupported MP130 4A9:1701 1200 N N - N unsupported

I saw that someone wrote here about the MP110. Maybe the MP130 can use the
same driver?

Anyway, the site I referred to when I first wrote, suggested that someone
could write a backend to this and other unsupported drivers and it also said
that it is not a very hard thing to do for people who know a little C, for
example. Well, since I have studied C a long time ago, I thought that maybe
this isn't very impossible after all, but I guess I will need some help to
get me started. I don't know where to begin, kind of. I don't even know
exactly how a driver in general works... I need some basic knowledge to get
started, and I just thought that someone here could give me some kind of
clue where to start or some links that explain things...

What do I need (except a C compiler and the scanner)?
Can the fact that I also have Windows XP with a working driver be of any
help? Is there some kind of software for Windows that can give me any clues
about how the MP130 works?

Yes, I can do some C programming, but I need to know what I need to do...
otherwise it's kind of being told to create a schoilkus program in C without
also being told what a schoilkus program is (in this case nothing since I
just made it up...).

Johnny Rosenberg

On Tue, 2007-12-18 at 19:30 +0100, Johnny Rosenberg wrote:
2007/12/10, Epostlistor gurus.knugum at gmail.com:
I visited http://www.sane-project.org/contrib.html and readed
about
contributing to the project - Writing a Backend (Driver).

The page said that You don't need to be an experienced
programmer.
Backends are usually written in C, so some basic knowledge of
this
language helps. You need a lot of patience, however,
especially if you
can't get programmer's documentation from your scanner's
manufacturer.

I learned C many years ago and I still think I remember most
of it, but I
am not programming very much these days. I am writing here
because I think
I need all the help I can get. Maybe someone is already doing
this, then I
might be able to contribute in some way. If not, it feels like
there are a
lot of things I need to know. Maybe there are similar backend
drivers out
there that I can get inspiration from and learn how to write
things like
that.

I have the Canon PIXMA MP130 and my operating system is
GNU/Linux Ubuntu
Studio 7.10. I also have a small partition with Windows XP, so
I can use
the scanner that way, but of course I want to use it with
Ubuntu. At the
moment I can only use the printing function with Ubuntu, but I
needed to
install additional software before that was possible.

Is there some kind of software for Windows that can scan
what's sent and
received to/from the MP130 while scanning etc? I guess that
would help
somewhat.

My idea is to write a very basic driver just to make it
possible to scan
with no fancy features (which are pretty useless anyway in
most cases).
Some things, like basic image editing, is better done with
dedicated
software, such as GIMP, I guess.

So, any comments to this? Will this task be too tough for
someone like
me..?

Johnny Rosenberg

Okay, seems like nobody's interested in this, so I guess I'll just
skip the idea and buy another skanner instead. Besides, I guess that I
would have failed doing this anyway.

Johnny Rosenberg
--
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

-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20071218/54eb610b/attachment.htm

[sane-devel] Canon PIXMA MP130