Re: [sane-devel] API clarification question
Yes, it seems that you want something more like: Member last_frame is set to SANE_TRUE if and only if the frame that is currently being acquired (or the frame that will be acquired next if there is no current frame) is the last (and possibly only) frame of the image (e.g., the current frame is the blue component of a red, green, blue image)." On Fri, Feb 2, 2024 at 12:01 PM Jonathan Schulz wrote: > Hello, > > I have posted a question on GitLab regarding the SANE API ( > https://gitlab.com/sane-project/standard/-/issues/10). Ralph suggested > that I also ask here. The sentence in question is > > "Member last_frame is set to SANE_TRUE if and only if the frame that is > currently being acquired (or the frame that will be acquired next if there > is no current frame) is the last frame of a multi frame image (e.g., the > current frame is the blue component of a red, green, blue image)." > > This sounds to me as if the following should be true: > > Whenever format is set to SANE_FRAME_GRAY or SANE_FRAME_RGB, last_frame > should be equal to SANE_False. > > However, both scanimage and the test backend behave differently. Does > anyone have any thoughts on this matter? Otherwise, I will open a MR to > adapt the API spec to the real usage. > > Best, > Jonathan > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Proposed timeline for 1.3.0 release
Sounds good to me. I have attached an updated copy of doc/releases.md, which contains some notes I made during the last release. There were a number of missing or poorly documented steps. allan On Sun, Jan 21, 2024 at 2:34 PM Ralph Little wrote: > Hi, > So it looks like we will do a 1.3.0 release. > I propose a fairly quick timeline since there isn't a lot of critical > stuff waiting to go in it. The only thing that I am aware of is the > longstanding problem for macOS USB support and I think we have a partial > solution for that which should push them on. > > Allan did the release last time, and perhaps I can go through the process > this time so that I am familiar. Are you OK with that Allan? > > 1) Code freeze: 1 week from now (28th January), I will create a release > branch and MRs targeted for the release should target that branch. Anything > else not intended for the release can still target master. I will send out > an email asking for translations after regenerating po files. During this > time, we will not normally accept functional enhancements but exceptions > will be considered in an emergency or if it is very safe. > > 2) Release: 2 weeks later (11th February) we will cut the release. I will > also do a PPA release for our Ubuntu users. > > Cheers, > Ralph > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" --- Copyright: © 2023 SANE Project SPDX-License-Identifier: CC-BY-SA-4.0 --- # Creating A New `sane-backends` Release This file summarizes most points to pay attention to when planning for a new `sane-backends` release. Content has been checked while working on `$old_version` and getting ready for `$new_version`, where: ``` sh old_version=1.1.1 new_version=1.2.1 ``` ## Timetable It is easiest to pick a release date well in advance so everyone knows what to expect. Ignoring security bug fix releases, `sane-backends` has been released on a roughly half-yearly schedule since `1.0.28`. Once you pick a date (and time), say `DT`, the planning is simply a matter of counting back from there: - `$DT - 35 days`: **schedule announcement** including the timetable. - `$DT - 21 days`: **feature freeze** branch, only bug fixes and translations allowed. - `$DT - 14 days`: **code freeze** only translations allowed. - `$DT - 0 days`: **release** :confetti_ball: Feel free to adjust the offsets if that works better. Also, pinging on the mailing list well in advance, say two, three months, about a suitable date for everyone involved is a good idea. > If you mention time of day, on the mailing list, in issues or merge > requests, use UTC times and mention that, e.g. 09:00 UTC. People > are in time zones all over the place and converting to and from UTC > should be relatively easy for everyone. Converting from other > time zones is generally cumbersome, even without things like DST. ## Schedule Announcement Part of the announcement of the release schedule is a request from translators to update translations. You can make this easier on them, by syncing the po files before the announcement: make -C po update-po git add po git commit -m "Update po files for sane-backends-$new_version release" git push Send an announcement to the `sane-devel` mailing list announcing the schedule. Make sure to request translators to checkout the current master branch, and produce updates (preferably before feature freeze starts). ## Feature Freeze A separate branch for the upcoming release is created in the repository. This marks the point when the code for the release effectively enters a feature freeze and no new features will be added to the release branch. At this point, no new text strings are likely to get added to the release branch. That means that po files should be stable, and it is a good idea to again sync the po files for translators. If we do this before we make the branch, we will not have to repeat it in both the master and release branches. make -C po update-po git add po git commit -m "Update po files for sane-backends-$new_version release" git push Name the branch in the format of `release-1.2.x` so that it's clear that further bugfix releases will happen on that branch. Here, we create the local branch, send it to remote, and then set our local to track the remote: ``` sh release_branch=release-1.2.x git branch $release_branch git checkout $release_branch git push origin $release_branch git branch -u origin/$release_branch ``` For backends added since the `$old_version`, make sure that its `.desc` file includes a `:new :yes` near the top. You can find such backends from the list of added files with: ``` sh git ls-files -- backend | while read f; do git log --follow --diff-filter=A --find-renames=40% \ --format="%ai $f" $old_version..$release_branch -- "$f" done | cat ``` Occasionally, you may notice changes that have not been documented, either in a `.desc` file or a manual page. Now is a good time to rectify the omission.
Re: [sane-devel] Release 1.3 anyone?
If you can find a way to verify, we'll update the supported scanner's list. But without verification, all we can do is mark it unknown. allan On Thu, Jan 18, 2024 at 7:41 AM Bryan wrote: > I was looking through the supported scanners recently. Epson Expression > 12000XL (overseas version of the DS-G2) is listed as Complete support > with the epson2 backend. > > I think the new model is Epson Expression 13000XL (probably the overseas > version of DS-G3). I wonder if this scanner is also supported. This is > one of the only high-grade flatbed scanners made today, and it would be > nice to be sure and keep documented if SANE supports it. > > > On Tue, 16 Jan 2024 18:39:23 -0500 > "m. allan noah" wrote: > > > 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" > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Release 1.3 anyone?
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] Error codes returned by Fujitsu fi-5900c?
The Fujitsu protocol is basically the same for all scanners, so you could pick up a used fi-5120 or similar for cheap. On Sun, Dec 10, 2023, 1:16 PM Wes Rishel wrote: > re: Really, for what you are trying to do, you might be better off > interfacing with the SANE API instead of trying to drive scanimage. > > Thanks. This is something I have thought before. Right now I invoke > scanimage as a subprocess for each batch, so there is a noticeable delay > while it polls the USB addresses. It would be nice to do that once and have > each batch start quickly. If I had more access to the scanner for debugging > I might use that approach. > > Meanwhile I will check out scanimage sources. > > > > > On Sat, Dec 9, 2023 at 2:49 PM m. allan noah wrote: > >> Look at the source code for scanimage, see how it translates SANE_status >> to exit codes. If that is not sufficient, you might need to catch its >> STDERR stream, and parse it. >> >> Really, for what you are trying to do, you might be better off >> interfacing with the SANE API instead of trying to drive scanimage. >> >> allan >> >> On Sat, Dec 9, 2023 at 2:25 PM Wes Rishel wrote: >> >>> I have a program that uses SANE to run a Fujitsu fi-5900c scanner, but I >>> only have access to the scanner when I am doing production work. So I am >>> writing code on a system where the scanner is not available. >>> >>> It would help to have a list of the return codes from scanimage while >>> working on a Fujitsu scanner. In particular, I would like to identify the >>> error codes returned for various errors where the operator might correct >>> them. Examples include stops due to double feeds, due to something stuck on >>> the page (like a sticky note), due to a failure to pass a single page >>> through the scanner, and so forth. I know that fujitsu.c somehow sets >>> different return codes for some of these situations but I haven't found the >>> list in sane-fujitsu(5) or sane-epjitsu(5). >>> >>> I believe that a good enough list is the SANE_status enum for the >>> general SANE specification. >>> >>> What I don't know is how to map the various values in the enum to the >>> return codes that scanimage uses on exit or whether there are specific >>> additional values for Fujitsu. >>> >>> Can someone share the secret decoder ring ;-) or point me to a document >>> or source file that has this info? >>> >>> Thanks in advance. >>> >>> -- Wes >>> >> >> >> -- >> "well, I stand up next to a mountain- and I chop it down with the edge of >> my hand" >> >
Re: [sane-devel] Error codes returned by Fujitsu fi-5900c?
Look at the source code for scanimage, see how it translates SANE_status to exit codes. If that is not sufficient, you might need to catch its STDERR stream, and parse it. Really, for what you are trying to do, you might be better off interfacing with the SANE API instead of trying to drive scanimage. allan On Sat, Dec 9, 2023 at 2:25 PM Wes Rishel wrote: > I have a program that uses SANE to run a Fujitsu fi-5900c scanner, but I > only have access to the scanner when I am doing production work. So I am > writing code on a system where the scanner is not available. > > It would help to have a list of the return codes from scanimage while > working on a Fujitsu scanner. In particular, I would like to identify the > error codes returned for various errors where the operator might correct > them. Examples include stops due to double feeds, due to something stuck on > the page (like a sticky note), due to a failure to pass a single page > through the scanner, and so forth. I know that fujitsu.c somehow sets > different return codes for some of these situations but I haven't found the > list in sane-fujitsu(5) or sane-epjitsu(5). > > I believe that a good enough list is the SANE_status enum for the general > SANE specification. > > What I don't know is how to map the various values in the enum to the > return codes that scanimage uses on exit or whether there are specific > additional values for Fujitsu. > > Can someone share the secret decoder ring ;-) or point me to a document or > source file that has this info? > > Thanks in advance. > > -- Wes > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] File Compression
What program produced the file? What is the file extension? allan On Tue, Oct 10, 2023 at 7:25 AM Matt Clark wrote: > How do I decompress a multifile scanned project with jpeg files? > > -- > Matt Clark > mmcae...@gmail.com > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Scanner Recommendation for long receipts?
Most ADF scanners need to be told how long the paper is, so they can do things like length-based double feed detection, buffering, blank page detection, etc. However, the maximum length should be fairly long on most machines I am familiar with. IIRC, some Canon and Fujitsu machines will go up to one meter in length? I'll try to look around for some examples. allan On Mon, Aug 21, 2023 at 9:11 AM Andy Bennett wrote: > Hi, > > I don't have a solution I'm afraid but can offer some solidarity below! > > > > like CVS/Walgreens long > > > > Is there a scanner out there that can scan up to 24"? or 36? > > > > I've been folding and making a multipage PDF. Is there a better way? > > > > Is there a reason scanners must have a maximum length or could > > they just stream data back to the PC continuously until the scan > > is complete. like a toilet paper roll for example. > > I have wondered about this too but not found any good implementations in > desktop scanners. > > My ix500 has a scanning length that's not quite long enough for some > things > such as certain kinds of official certificates that are A4 width but have > extra long fold out bits at the end. > > I'd suggest cutting the reciept into pieces, but I always hate a solution > like that when there seems to be No Good Reason why the product doesn't do > it in the first place. Besides, there may be good reasons to not want to > cut your document into pieces for the sake of a scan. > > For my scenarios it often suffices to scan it one way up and then the > other > because the documents are less than twice the length the scanner can > handle. > ...but that still leaves an annoying amount of post-processing to do. It's > even harder if the documents are particularly thin (like reciepts) because > you're more likely to get a wobbly horizontal registration between the two > scans. > > > > I have no problem scanning a 700 page document if I keep that > > ADF feder hopper full and keep the exit tray from filling up on > > my ADF scanners. But what reasons are there, that a single page > > can not be say, 100 feet long? > > I guess none in principle. This one (done with a line scan camera which is > similar to the single pixel-wide CCDs a scanner would use) is as long as a > train: http://elm-chan.org/works/lcam/g/Y0008.jpg > > (via http://elm-chan.org/works/lcam/report.html ) > > I've seen others that document entire long distance train journeys. > > > Good luck and please let us know if you find anything! > > > Best wishes, > @ndy > > -- > andy...@ashurst.eu.org > http://www.ashurst.eu.org/ > 0x7EBA75FF > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] fi-5000 backend
The fi-5000N, and all Fujitsu ethernet interfaces are not supported by SANE. Direct USB connection will work, however. allan On Sat, Jul 15, 2023 at 11:36 AM Dirk Meier wrote: > > > Hello, > I just tried to connect my fujitsu Fi-5220C scanner to my new opensuse > leap > 15.5 via a fi-5000 ethernet connector, but either the scanner nor the > ethernetadapter will be recognized by sane. > How to configure the fi-5000 to recognized by sane? > > -- > Dirk > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] What scanners are the developers using?
I do not have a Fujitsu scanner with network capabilities, nor any documentation about the protocol they speak. I also have no need to put something on the network that is sitting in arms reach :) So, I have not added support to the fujitsu backend for these scanners. allan On Sat, Mar 4, 2023 at 9:22 AM Billy Croan wrote: > I'm "going paperless" and I have been using an epson and hp multifunction > printer for their ADF, as well as an IRIScan for its ability to feed > receipt paper and flat objects straight through. All of those devices have > drawbacks and are showing age. > > I'm thinking of buying a Fujitsu SnapScan ix1600 to replace them all. > From all accounts, that's one of if not the best out there. But I looked > up support on http://www.sane-project.org/man/sane-fujitsu.5.html and it > said "Network interfaces are not supported on any scanner model." > > That can't be right can it? in 2023, the scanner model that I think most > folks agree is the best, isn't supported over the network? > > Are the docs just outdated, or is that real? I thought I'd ask before > spending $420 to find out, and maybe a dev would steer me towards other > hardware if IP connectivity is a priority. > > priorities: > ADF 30 or more pages > simultaneous (single pass) duplex imaging > handles receipts > handles credit cards with bumps > handles cardboard/thicker/non-bending materials (I guess this isn't a deal > breaker) > 8.5" wide with a little overscan > 14" long, hopefully longer for occasional weird stuff > IP connectivity, happy with ethernet or wifi > never, ever misfeeds (hahaha just kidding) > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
I've been struggling with it. Go ahead and commit your changes, anything I do for 1.2.2 will be on the 1.2.x branch. allan On Sun, Feb 19, 2023 at 6:34 PM Ralph Little wrote: > Hi, > > On 2023-02-07 17:43, m. allan noah wrote: > > Sounds reasonable, though at the moment I am pretty frustrated with > > how this backends release went. I know folks worked pretty hard on > > what we have now (particularly Olaf), but I think I am going to make > > an executive decision, and rip some of this out. Once I have done this > > (and cleaned up the snapshot build process), I'd like to quickly > > release 1.2.2. Hopefully, we can end up with a release that actually > > builds with a proper version number, and without autotools being > required. > > > > Is this still your intention? > I have a few fairly radical things in the pipeline (like changes to > sanei_thread) waiting in the wings to get checked in and I don't think > they would be appropriate for a 1.2.2 release coming out quickly. > > Cheers, > Ralph > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Library functions in backend
Frontends or backends? Either way, I am not opposed to abandoning quirks for ancient platforms. On Thu, Feb 9, 2023 at 12:29 PM Ralph Little wrote: > There has been a proposal to remove the library replacement functions from > the backend repo. > https://gitlab.com/sane-project/frontends/-/merge_requests/11 > > On the surface, this seems sensible. I can't see that there are many if > any platforms that the backends repo is built on that wouldn't have these > functions. In the past, there have certainly been non-standards conformant > variants (like snprint() on Windows which I believe is now fixed). > > What are the general views here? Are there some platform that would still > require some of these functions? > > Cheers, > Ralph > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
An accident. We also skipped 1.1.0, so I just did the same thing. allan On Wed, Feb 8, 2023 at 9:24 AM Ulf Zibis wrote: > Hi, > > why you start with version 1.2.1 instead 1.2.0 ? > > -Ulf > Am 08.02.23 um 02:43 schrieb m. allan noah: > > Sounds reasonable, though at the moment I am pretty frustrated with how > this backends release went. I know folks worked pretty hard on what we have > now (particularly Olaf), but I think I am going to make an executive > decision, and rip some of this out. Once I have done this (and cleaned up > the snapshot build process), I'd like to quickly release 1.2.2. Hopefully, > we can end up with a release that actually builds with a proper version > number, and without autotools being required. > > allan > > > On Tue, Feb 7, 2023 at 8:18 PM Ralph Little wrote: > >> Hi, >> On a slightly different note, perhaps we should consider doing a >> frontends release soon. >> Thierry has been working on a GTK3 port of the GUI apps in there which is >> going to become an issue shortly as some distros drop GTK2. >> >> Cheers, >> Ralph >> >> On 2023-02-07 04:48, m. allan noah wrote: >> >> This entire thing is a little crazy, because I spent more time fighting >> with the automation than I would have spent doing an old manual release. >> One of the steps there was simply to edit configure.ac and change the >> version number a couple of times. Seems easy enough to 'echo $new_version > >> .version' or something like that in this new scheme. I'll do some more >> research into how other projects handle this. >> >> And, I noticed the extra comments at the top of the NEWS file were being >> displayed in the release notes and manually removed that in the gitlab UI. >> >> allan >> >> On Tue, Feb 7, 2023 at 12:32 AM Ralph Little wrote: >> >>> Hi, >>> >>> On 2023-02-06 20:04, m. allan noah wrote: >>> >>> Hmm, looks like AC_INIT calls `./tools/git-version-gen --prefix '' >>> .tarball-version`, which returns UNKNOWN. Seems like our release process >>> might be leaving out some steps. I guess I'll dig more tomorrow. >>> >>> >>> IIRC, this has been a long-standing issue with the tar file included in >>> the GitLab release artifacts, in that they don't build. You have to instead >>> get the snapshot file. >>> I don't know how long it has been like that but we do get a complaint >>> every now again. I keep trying to remember to figure out what is going on >>> to do something about it. >>> >>> If it is the thing that I am thinking about, it might also be the thing >>> that always stuffs me up in the release PPA because the orig tar file >>> requires an extra .gitversion file with the release version in it, >>> otherwise it won't build when it is uploaded. >>> >>> We really need to get our collective heads together and fix it. I don't >>> pretend to really understand what the issue is though. Build systems aren't >>> really my thing. >>> >>> >>> As an aside, the release page seems to have some weird guff from the top >>> of the NEWS file in there. Not really sure what caused that. It is some of >>> the comment material. :`( >>> >>> Cheers, >>> Ralph >>> >>> allan >>> >>> On Mon, Feb 6, 2023 at 10:44 PM m. allan noah >>> wrote: >>> >>>> So, I was able to do the release on time (after filling in a few blanks >>>> in our documentation). But I only did the website updates tonight. I seem >>>> to have run into a small problem there- when I download the release >>>> tarball, and run ./autogen.sh, i get a ./configure file which has 'UNKNOWN' >>>> as the package version number. This also happens with 1.1.1 as well. Is >>>> this happening for anyone else? >>>> >>>> allan >>>> >>>> On Sat, Feb 4, 2023 at 10:05 PM Ralph Little >>>> wrote: >>>> >>>>> Hi, >>>>> OK, I think I have done that. >>>>> >>>>> Because we are short on time I cut and pasted the release note >>>>> fragments from my spreadsheet into the NEWS file with Apostrophe MD file >>>>> editor and whipped them into shape manually. >>>>> First time using it and it is pretty good. Obviously, this was a >>>>> manual process, but it wasn't too onerous. >>>>> >>>>> I couldn't get the towncrier thingy to wor
Re: [sane-devel] Happy new year- time for a sane-backends release!
Sounds reasonable, though at the moment I am pretty frustrated with how this backends release went. I know folks worked pretty hard on what we have now (particularly Olaf), but I think I am going to make an executive decision, and rip some of this out. Once I have done this (and cleaned up the snapshot build process), I'd like to quickly release 1.2.2. Hopefully, we can end up with a release that actually builds with a proper version number, and without autotools being required. allan On Tue, Feb 7, 2023 at 8:18 PM Ralph Little wrote: > Hi, > On a slightly different note, perhaps we should consider doing a frontends > release soon. > Thierry has been working on a GTK3 port of the GUI apps in there which is > going to become an issue shortly as some distros drop GTK2. > > Cheers, > Ralph > > On 2023-02-07 04:48, m. allan noah wrote: > > This entire thing is a little crazy, because I spent more time fighting > with the automation than I would have spent doing an old manual release. > One of the steps there was simply to edit configure.ac and change the > version number a couple of times. Seems easy enough to 'echo $new_version > > .version' or something like that in this new scheme. I'll do some more > research into how other projects handle this. > > And, I noticed the extra comments at the top of the NEWS file were being > displayed in the release notes and manually removed that in the gitlab UI. > > allan > > On Tue, Feb 7, 2023 at 12:32 AM Ralph Little wrote: > >> Hi, >> >> On 2023-02-06 20:04, m. allan noah wrote: >> >> Hmm, looks like AC_INIT calls `./tools/git-version-gen --prefix '' >> .tarball-version`, which returns UNKNOWN. Seems like our release process >> might be leaving out some steps. I guess I'll dig more tomorrow. >> >> >> IIRC, this has been a long-standing issue with the tar file included in >> the GitLab release artifacts, in that they don't build. You have to instead >> get the snapshot file. >> I don't know how long it has been like that but we do get a complaint >> every now again. I keep trying to remember to figure out what is going on >> to do something about it. >> >> If it is the thing that I am thinking about, it might also be the thing >> that always stuffs me up in the release PPA because the orig tar file >> requires an extra .gitversion file with the release version in it, >> otherwise it won't build when it is uploaded. >> >> We really need to get our collective heads together and fix it. I don't >> pretend to really understand what the issue is though. Build systems aren't >> really my thing. >> >> >> As an aside, the release page seems to have some weird guff from the top >> of the NEWS file in there. Not really sure what caused that. It is some of >> the comment material. :`( >> >> Cheers, >> Ralph >> >> allan >> >> On Mon, Feb 6, 2023 at 10:44 PM m. allan noah wrote: >> >>> So, I was able to do the release on time (after filling in a few blanks >>> in our documentation). But I only did the website updates tonight. I seem >>> to have run into a small problem there- when I download the release >>> tarball, and run ./autogen.sh, i get a ./configure file which has 'UNKNOWN' >>> as the package version number. This also happens with 1.1.1 as well. Is >>> this happening for anyone else? >>> >>> allan >>> >>> On Sat, Feb 4, 2023 at 10:05 PM Ralph Little wrote: >>> >>>> Hi, >>>> OK, I think I have done that. >>>> >>>> Because we are short on time I cut and pasted the release note >>>> fragments from my spreadsheet into the NEWS file with Apostrophe MD file >>>> editor and whipped them into shape manually. >>>> First time using it and it is pretty good. Obviously, this was a manual >>>> process, but it wasn't too onerous. >>>> >>>> I couldn't get the towncrier thingy to work anyway. I don't really have >>>> much experience with python and pip. Python seems an awful lot more >>>> complicated since the last time I used it :( >>>> >>>> I have pushed the release notes in NEWS to your branch. >>>> >>>> Cheers, >>>> Ralph >>>> >>>> On 2023-02-04 18:18, m. allan noah wrote: >>>> >>>> Awesome, thanks! I'm working on updating doc/releases.md, which I find >>>> to be hard to use. Maybe if you keep some notes on what you did, I can >>>> incorporate your method instead of towncrier. >>>> >>>>
Re: [sane-devel] Happy new year- time for a sane-backends release!
This entire thing is a little crazy, because I spent more time fighting with the automation than I would have spent doing an old manual release. One of the steps there was simply to edit configure.ac and change the version number a couple of times. Seems easy enough to 'echo $new_version > .version' or something like that in this new scheme. I'll do some more research into how other projects handle this. And, I noticed the extra comments at the top of the NEWS file were being displayed in the release notes and manually removed that in the gitlab UI. allan On Tue, Feb 7, 2023 at 12:32 AM Ralph Little wrote: > Hi, > > On 2023-02-06 20:04, m. allan noah wrote: > > Hmm, looks like AC_INIT calls `./tools/git-version-gen --prefix '' > .tarball-version`, which returns UNKNOWN. Seems like our release process > might be leaving out some steps. I guess I'll dig more tomorrow. > > > IIRC, this has been a long-standing issue with the tar file included in > the GitLab release artifacts, in that they don't build. You have to instead > get the snapshot file. > I don't know how long it has been like that but we do get a complaint > every now again. I keep trying to remember to figure out what is going on > to do something about it. > > If it is the thing that I am thinking about, it might also be the thing > that always stuffs me up in the release PPA because the orig tar file > requires an extra .gitversion file with the release version in it, > otherwise it won't build when it is uploaded. > > We really need to get our collective heads together and fix it. I don't > pretend to really understand what the issue is though. Build systems aren't > really my thing. > > > As an aside, the release page seems to have some weird guff from the top > of the NEWS file in there. Not really sure what caused that. It is some of > the comment material. :`( > > Cheers, > Ralph > > allan > > On Mon, Feb 6, 2023 at 10:44 PM m. allan noah wrote: > >> So, I was able to do the release on time (after filling in a few blanks >> in our documentation). But I only did the website updates tonight. I seem >> to have run into a small problem there- when I download the release >> tarball, and run ./autogen.sh, i get a ./configure file which has 'UNKNOWN' >> as the package version number. This also happens with 1.1.1 as well. Is >> this happening for anyone else? >> >> allan >> >> On Sat, Feb 4, 2023 at 10:05 PM Ralph Little wrote: >> >>> Hi, >>> OK, I think I have done that. >>> >>> Because we are short on time I cut and pasted the release note fragments >>> from my spreadsheet into the NEWS file with Apostrophe MD file editor and >>> whipped them into shape manually. >>> First time using it and it is pretty good. Obviously, this was a manual >>> process, but it wasn't too onerous. >>> >>> I couldn't get the towncrier thingy to work anyway. I don't really have >>> much experience with python and pip. Python seems an awful lot more >>> complicated since the last time I used it :( >>> >>> I have pushed the release notes in NEWS to your branch. >>> >>> Cheers, >>> Ralph >>> >>> On 2023-02-04 18:18, m. allan noah wrote: >>> >>> Awesome, thanks! I'm working on updating doc/releases.md, which I find >>> to be hard to use. Maybe if you keep some notes on what you did, I can >>> incorporate your method instead of towncrier. >>> >>> allan >>> >>> On Sat, Feb 4, 2023 at 9:12 PM Ralph Little wrote: >>> >>>> Hi, >>>> In this case I didn't generate the towncrier files. It's a lot of faff >>>> if you don't do it as you go along. >>>> I just put them into a spreadsheet. >>>> >>>> I will try to generate the release notes from that. >>>> >>>> Cheers, >>>> Ralph >>>> >>>> On 2023-02-04 17:57, m. allan noah wrote: >>>> >>>> I have pushed a branch called 'release-1.2.x'. I don't have this >>>> 'towncrier' thing, so maybe you can run that and merge the release notes? >>>> >>>> allan >>>> >>>> On Wed, Feb 1, 2023 at 11:39 AM m. allan noah >>>> wrote: >>>> >>>>> Awesome, thanks! I'll probably take a first stab at it on the 4th, and >>>>> see if I can follow our current instructions. >>>>> >>>>> allan >>>>> >>>>> On Sat, Jan 28, 2023 at 8:43 PM Ralph Little >>>>> wrote: >>>>>
Re: [sane-devel] Happy new year- time for a sane-backends release!
Hmm, looks like AC_INIT calls `./tools/git-version-gen --prefix '' .tarball-version`, which returns UNKNOWN. Seems like our release process might be leaving out some steps. I guess I'll dig more tomorrow. allan On Mon, Feb 6, 2023 at 10:44 PM m. allan noah wrote: > So, I was able to do the release on time (after filling in a few blanks in > our documentation). But I only did the website updates tonight. I seem to > have run into a small problem there- when I download the release tarball, > and run ./autogen.sh, i get a ./configure file which has 'UNKNOWN' as the > package version number. This also happens with 1.1.1 as well. Is this > happening for anyone else? > > allan > > On Sat, Feb 4, 2023 at 10:05 PM Ralph Little wrote: > >> Hi, >> OK, I think I have done that. >> >> Because we are short on time I cut and pasted the release note fragments >> from my spreadsheet into the NEWS file with Apostrophe MD file editor and >> whipped them into shape manually. >> First time using it and it is pretty good. Obviously, this was a manual >> process, but it wasn't too onerous. >> >> I couldn't get the towncrier thingy to work anyway. I don't really have >> much experience with python and pip. Python seems an awful lot more >> complicated since the last time I used it :( >> >> I have pushed the release notes in NEWS to your branch. >> >> Cheers, >> Ralph >> >> On 2023-02-04 18:18, m. allan noah wrote: >> >> Awesome, thanks! I'm working on updating doc/releases.md, which I find to >> be hard to use. Maybe if you keep some notes on what you did, I can >> incorporate your method instead of towncrier. >> >> allan >> >> On Sat, Feb 4, 2023 at 9:12 PM Ralph Little wrote: >> >>> Hi, >>> In this case I didn't generate the towncrier files. It's a lot of faff >>> if you don't do it as you go along. >>> I just put them into a spreadsheet. >>> >>> I will try to generate the release notes from that. >>> >>> Cheers, >>> Ralph >>> >>> On 2023-02-04 17:57, m. allan noah wrote: >>> >>> I have pushed a branch called 'release-1.2.x'. I don't have this >>> 'towncrier' thing, so maybe you can run that and merge the release notes? >>> >>> allan >>> >>> On Wed, Feb 1, 2023 at 11:39 AM m. allan noah >>> wrote: >>> >>>> Awesome, thanks! I'll probably take a first stab at it on the 4th, and >>>> see if I can follow our current instructions. >>>> >>>> allan >>>> >>>> On Sat, Jan 28, 2023 at 8:43 PM Ralph Little >>>> wrote: >>>> >>>>> Hi, >>>>> I have prepared the release notes whenever you are ready! >>>>> >>>>> Cheers, >>>>> Ralph >>>>> >>>>> On 2023-01-24 08:33, m. allan noah wrote: >>>>> >>>>> Sounds good to me, thanks for your help. I'm traveling this week, and >>>>> won't be able to work on this until the weekend. >>>>> >>>>> On Tue, Jan 24, 2023, 10:47 AM Ralph Little >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> On 2023-01-01 15:54, m. allan noah wrote: >>>>>> > It has been nearly a year since our last release, and there have >>>>>> been >>>>>> > many changes and bug fixes. I'd like to get 1.2.1 released in early >>>>>> > February. I've not done it in a few years, but I am certainly >>>>>> willing >>>>>> > to make the release package. >>>>>> > >>>>>> > Any objections to a code freeze on Jan 22, and a release on Feb 5? >>>>>> > >>>>>> > allan >>>>>> >>>>>> I think if we are going for your proposed plan, then we are official >>>>>> in >>>>>> code freeze for 1.2.1. >>>>>> If you want to proceed, I can prepare release notes. >>>>>> >>>>>> Cheers, >>>>>> Ralph >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> "well, I stand up next to a mountain- and I chop it down with the edge >>>> of my hand" >>>> >>> >>> >>> -- >>> "well, I stand up next to a mountain- and I chop it down with the edge >>> of my hand" >>> >>> >>> >> >> -- >> "well, I stand up next to a mountain- and I chop it down with the edge of >> my hand" >> >> >> > > -- > "well, I stand up next to a mountain- and I chop it down with the edge of > my hand" > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
So, I was able to do the release on time (after filling in a few blanks in our documentation). But I only did the website updates tonight. I seem to have run into a small problem there- when I download the release tarball, and run ./autogen.sh, i get a ./configure file which has 'UNKNOWN' as the package version number. This also happens with 1.1.1 as well. Is this happening for anyone else? allan On Sat, Feb 4, 2023 at 10:05 PM Ralph Little wrote: > Hi, > OK, I think I have done that. > > Because we are short on time I cut and pasted the release note fragments > from my spreadsheet into the NEWS file with Apostrophe MD file editor and > whipped them into shape manually. > First time using it and it is pretty good. Obviously, this was a manual > process, but it wasn't too onerous. > > I couldn't get the towncrier thingy to work anyway. I don't really have > much experience with python and pip. Python seems an awful lot more > complicated since the last time I used it :( > > I have pushed the release notes in NEWS to your branch. > > Cheers, > Ralph > > On 2023-02-04 18:18, m. allan noah wrote: > > Awesome, thanks! I'm working on updating doc/releases.md, which I find to > be hard to use. Maybe if you keep some notes on what you did, I can > incorporate your method instead of towncrier. > > allan > > On Sat, Feb 4, 2023 at 9:12 PM Ralph Little wrote: > >> Hi, >> In this case I didn't generate the towncrier files. It's a lot of faff if >> you don't do it as you go along. >> I just put them into a spreadsheet. >> >> I will try to generate the release notes from that. >> >> Cheers, >> Ralph >> >> On 2023-02-04 17:57, m. allan noah wrote: >> >> I have pushed a branch called 'release-1.2.x'. I don't have this >> 'towncrier' thing, so maybe you can run that and merge the release notes? >> >> allan >> >> On Wed, Feb 1, 2023 at 11:39 AM m. allan noah wrote: >> >>> Awesome, thanks! I'll probably take a first stab at it on the 4th, and >>> see if I can follow our current instructions. >>> >>> allan >>> >>> On Sat, Jan 28, 2023 at 8:43 PM Ralph Little wrote: >>> >>>> Hi, >>>> I have prepared the release notes whenever you are ready! >>>> >>>> Cheers, >>>> Ralph >>>> >>>> On 2023-01-24 08:33, m. allan noah wrote: >>>> >>>> Sounds good to me, thanks for your help. I'm traveling this week, and >>>> won't be able to work on this until the weekend. >>>> >>>> On Tue, Jan 24, 2023, 10:47 AM Ralph Little wrote: >>>> >>>>> Hi, >>>>> >>>>> On 2023-01-01 15:54, m. allan noah wrote: >>>>> > It has been nearly a year since our last release, and there have >>>>> been >>>>> > many changes and bug fixes. I'd like to get 1.2.1 released in early >>>>> > February. I've not done it in a few years, but I am certainly >>>>> willing >>>>> > to make the release package. >>>>> > >>>>> > Any objections to a code freeze on Jan 22, and a release on Feb 5? >>>>> > >>>>> > allan >>>>> >>>>> I think if we are going for your proposed plan, then we are official >>>>> in >>>>> code freeze for 1.2.1. >>>>> If you want to proceed, I can prepare release notes. >>>>> >>>>> Cheers, >>>>> Ralph >>>>> >>>> >>>> >>> >>> -- >>> "well, I stand up next to a mountain- and I chop it down with the edge >>> of my hand" >>> >> >> >> -- >> "well, I stand up next to a mountain- and I chop it down with the edge of >> my hand" >> >> >> > > -- > "well, I stand up next to a mountain- and I chop it down with the edge of > my hand" > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
Awesome, thanks! I'm working on updating doc/releases.md, which I find to be hard to use. Maybe if you keep some notes on what you did, I can incorporate your method instead of towncrier. allan On Sat, Feb 4, 2023 at 9:12 PM Ralph Little wrote: > Hi, > In this case I didn't generate the towncrier files. It's a lot of faff if > you don't do it as you go along. > I just put them into a spreadsheet. > > I will try to generate the release notes from that. > > Cheers, > Ralph > > On 2023-02-04 17:57, m. allan noah wrote: > > I have pushed a branch called 'release-1.2.x'. I don't have this > 'towncrier' thing, so maybe you can run that and merge the release notes? > > allan > > On Wed, Feb 1, 2023 at 11:39 AM m. allan noah wrote: > >> Awesome, thanks! I'll probably take a first stab at it on the 4th, and >> see if I can follow our current instructions. >> >> allan >> >> On Sat, Jan 28, 2023 at 8:43 PM Ralph Little wrote: >> >>> Hi, >>> I have prepared the release notes whenever you are ready! >>> >>> Cheers, >>> Ralph >>> >>> On 2023-01-24 08:33, m. allan noah wrote: >>> >>> Sounds good to me, thanks for your help. I'm traveling this week, and >>> won't be able to work on this until the weekend. >>> >>> On Tue, Jan 24, 2023, 10:47 AM Ralph Little wrote: >>> >>>> Hi, >>>> >>>> On 2023-01-01 15:54, m. allan noah wrote: >>>> > It has been nearly a year since our last release, and there have been >>>> > many changes and bug fixes. I'd like to get 1.2.1 released in early >>>> > February. I've not done it in a few years, but I am certainly willing >>>> > to make the release package. >>>> > >>>> > Any objections to a code freeze on Jan 22, and a release on Feb 5? >>>> > >>>> > allan >>>> >>>> I think if we are going for your proposed plan, then we are official in >>>> code freeze for 1.2.1. >>>> If you want to proceed, I can prepare release notes. >>>> >>>> Cheers, >>>> Ralph >>>> >>> >>> >> >> -- >> "well, I stand up next to a mountain- and I chop it down with the edge of >> my hand" >> > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge of > my hand" > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
I have pushed a branch called 'release-1.2.x'. I don't have this 'towncrier' thing, so maybe you can run that and merge the release notes? allan On Wed, Feb 1, 2023 at 11:39 AM m. allan noah wrote: > Awesome, thanks! I'll probably take a first stab at it on the 4th, and see > if I can follow our current instructions. > > allan > > On Sat, Jan 28, 2023 at 8:43 PM Ralph Little wrote: > >> Hi, >> I have prepared the release notes whenever you are ready! >> >> Cheers, >> Ralph >> >> On 2023-01-24 08:33, m. allan noah wrote: >> >> Sounds good to me, thanks for your help. I'm traveling this week, and >> won't be able to work on this until the weekend. >> >> On Tue, Jan 24, 2023, 10:47 AM Ralph Little wrote: >> >>> Hi, >>> >>> On 2023-01-01 15:54, m. allan noah wrote: >>> > It has been nearly a year since our last release, and there have been >>> > many changes and bug fixes. I'd like to get 1.2.1 released in early >>> > February. I've not done it in a few years, but I am certainly willing >>> > to make the release package. >>> > >>> > Any objections to a code freeze on Jan 22, and a release on Feb 5? >>> > >>> > allan >>> >>> I think if we are going for your proposed plan, then we are official in >>> code freeze for 1.2.1. >>> If you want to proceed, I can prepare release notes. >>> >>> Cheers, >>> Ralph >>> >> >> > > -- > "well, I stand up next to a mountain- and I chop it down with the edge of > my hand" > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage does not recognize basic long options
I'm ok with breaking code freeze if you want On Sat, Feb 4, 2023, 2:41 PM Ralph Little wrote: > Hi, > > On 2023-02-04 10:38, Karl Weber wrote: > > Hi Ralf, > > > > On Saturday, 4 February 2023 18:06:41 CET Ralph Little wrote: > >> The condition on SANE_OPTION_IS_SETTABLE(opt->cap) has been removed in > >> version > >>> 1.1.1 and this causes the problem. > >> I'm a bit confused by this comment. I thought that your issue was caused > >> by the backend sending NULL. > >> Which problem do you believe this causes? Or are you saying that the > >> NULL options issue is revealed by this change? That is certainly > possible. > > Yes, you may also say that the NULL options issue has been revealed by > this > > change. I didn't know, why this check has been removed and I don't know > why it > > had been there beforehand. I am really new to sane! I started to look at > the > > code two days ago. Before I was only an ignorant user of scanimage. So > please > > excuse me. > > > > But irrespective of the wording, are you going to do something about it? > Or > > where would be the right place to fix this problem? Currently I have no > idea, > > whether hplip-sane is open source and what the chances would be, to get > a fix > > in there, if this would be the right place for a fix. I don't even know, > > whether it is part of the SANE API specification, that there must not be > NULL > > options. > I suspect that the hpaio backend is doing something improper. However, > we must deal with it somehow. > I will do a fix. > > Cheers, > Ralph > >
Re: [sane-devel] scanimage does not recognize basic long options
I bet you are not running the version of scanimage you think you are. On Thu, Feb 2, 2023 at 4:35 PM Karl Weber wrote: > Hi, > > I came to the mentioned package through this issue > > https://gitlab.com/sane-project/backends/-/issues/440 > > Meanwhile, I worked with a git clone, however with the same result :( > > On Thursday, 2 February 2023 22:01:03 CET Ralph Little wrote: > > I downloaded and built said package and I don't see the same issue: > > > > scanimage --format=tiff -d 'test:0' --resolution 200 -x 210.000 -y > 296.985 > > --mode Color --batch="sid-600-%03d.tiff" --source 'Automatic Document > > Feeder' --batch-count=1 > > > > This works for me just fine. > > Ok. When I enter the command like you did, I get > > scanimage: rounded value of br-x from 210 to 200 > scanimage: rounded value of br-y from 296.985 to 200 > Scanning 1 page, incrementing by 1, numbering from 1 > Scanning page 1 > Scanned page 1. (scanner status = 5) > Batch terminated, 1 page scanned > > When I enter > > scanimage --format=jpeg --resolution 200 -x 210.000 -y 296.985 --mode > Color -- > batch="fff-%03d.jpeg" --source ADF --batch-count=3 > > I get > > scanimage: unrecognized option '--format=jpeg' > > The backend used in this case is hpaio. > > Thanks > Karl > > > > > > > > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
Awesome, thanks! I'll probably take a first stab at it on the 4th, and see if I can follow our current instructions. allan On Sat, Jan 28, 2023 at 8:43 PM Ralph Little wrote: > Hi, > I have prepared the release notes whenever you are ready! > > Cheers, > Ralph > > On 2023-01-24 08:33, m. allan noah wrote: > > Sounds good to me, thanks for your help. I'm traveling this week, and > won't be able to work on this until the weekend. > > On Tue, Jan 24, 2023, 10:47 AM Ralph Little wrote: > >> Hi, >> >> On 2023-01-01 15:54, m. allan noah wrote: >> > It has been nearly a year since our last release, and there have been >> > many changes and bug fixes. I'd like to get 1.2.1 released in early >> > February. I've not done it in a few years, but I am certainly willing >> > to make the release package. >> > >> > Any objections to a code freeze on Jan 22, and a release on Feb 5? >> > >> > allan >> >> I think if we are going for your proposed plan, then we are official in >> code freeze for 1.2.1. >> If you want to proceed, I can prepare release notes. >> >> Cheers, >> Ralph >> > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Happy new year- time for a sane-backends release!
Sounds good to me, thanks for your help. I'm traveling this week, and won't be able to work on this until the weekend. On Tue, Jan 24, 2023, 10:47 AM Ralph Little wrote: > Hi, > > On 2023-01-01 15:54, m. allan noah wrote: > > It has been nearly a year since our last release, and there have been > > many changes and bug fixes. I'd like to get 1.2.1 released in early > > February. I've not done it in a few years, but I am certainly willing > > to make the release package. > > > > Any objections to a code freeze on Jan 22, and a release on Feb 5? > > > > allan > > I think if we are going for your proposed plan, then we are official in > code freeze for 1.2.1. > If you want to proceed, I can prepare release notes. > > Cheers, > Ralph >
Re: [sane-devel] pthread change proposal
No way. It is not good practice to add a major, potentially breaking, and partially untested change to git mere days before a release. I propose that this change (or a derivative) gets merged a couple weeks after the release. allan On Tue, Jan 10, 2023 at 1:06 AM Ralph Little wrote: > Hi, > We have a long-running issue related to pthread use in SANE backends. > See here: https://gitlab.com/sane-project/backends/-/issues/153 > > I proposed a change to sanei_thread to try to sort some of these issues > while improving detection of builds that abuse the restrictions > surrounding pthread_t values. That proposal is here: > https://gitlab.com/sane-project/backends/-/merge_requests/750 > > Povilas and I had some discussions about this solution and given the > impending release of 1.2.1, someone has expressed a desire to see these > issues solved, particularly as they relate to MacOS, which is properly > broken at the moment. :( > > Could I get some further comments on the proposed solution and I would > especially appreciate if we could see some testing of that branch > solution on platforms other than Linux? > > Cheers, > Ralph > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
[sane-devel] Happy new year- time for a sane-backends release!
It has been nearly a year since our last release, and there have been many changes and bug fixes. I'd like to get 1.2.1 released in early February. I've not done it in a few years, but I am certainly willing to make the release package. Any objections to a code freeze on Jan 22, and a release on Feb 5? allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Time for a sane-backends release?
On Thu, Nov 10, 2022 at 1:58 AM Ralph Little wrote: > Hi, > > On 2022-11-09 20:41, m. allan noah wrote: > > It's been almost 10 months since our last release. It looks like we've > > added support for a number of new scanners and fixed a good pile of > > bugs. Thoughts on scheduling another release soonish? > > I agree! Povilas and I did discuss it a couple of weeks ago or so and he > added it to his TODO list. > Cool- Povilas, would you like some help? I've done a few sane releases over the years :) Maybe we could just set a rough schedule now, so that folks could wrap up any ongoing work. Let me know- allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
[sane-devel] Time for a sane-backends release?
It's been almost 10 months since our last release. It looks like we've added support for a number of new scanners and fixed a good pile of bugs. Thoughts on scheduling another release soonish? allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] epsonds backend ADF size with ES-50
With some brands of scanners, there can be limitations in things like resolution or bit depth when you enable larger size scans. So, be careful assuming you want to always use that mode. allan On Wed, Aug 31, 2022 at 12:58 PM Ralph Little wrote: > Hi, > > On Tue, Aug 30, 2022 at 10:36 PM Sean Greenslade > wrote: > >> Hi, all. I recently picked up an Epson ES-50 sheet-feed scanner. My >> intent is to use it for receipt scanning, so I tried it out with a >> ~700 mm long receipt and found that it would error out at around 450 mm >> into the scan. The manual claims the scanner is capable of a max of 72 >> inch document length, so I started poking around in the epsonds backend >> code. Something that jumped out at me was the eds_set_adf_area >> function. It seems that for this particular scanner, three ADF size >> values are reported: AREA, AMIN, and AMAX (in epsonds-cmd.c around line >> 445 on current git master). The eds_set_adf_area function is called with >> the values from AREA, which limits the document length to 14 inches. I'm >> assuming AREA is just meant to be a default value, but if anyone has any >> deeper insight into the meaning, I'd be interested to know. >> > > Looking at that code, AMIN and AMAX are pretty much ignored. > What do you get for all of the AREA/AMIN/AMAX parameters? > Perhaps we can figure out what they mean and code up something a little > better? > > >> >> The AMAX values reported seemed to match the manual's reported 72-inch >> maximum, so on a whim, I just moved the eds_set_adf_area call to the >> AMAX section. After recompiling, I was able to scan my long receipt no >> problem. >> >> Now I'm wondering if there is any downside to using the max ADF size? If >> not, would you consider the attached patch? >> >> > I don't believe that we have a current maintainer for this backend > although we do get some submissions from Epson Japan now and then for new > models. I wonder if they would be willing to shed some light on this or > provide us some documentation on this aspect of the protocol? > > Cheers, > Ralph > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Requiring GitLab merge requests for all changes
I thought I'd reanimate this discussion to see if I could get a little help. I've been working on SANE for many years, even before we used git. I've been committing and pushing to master from the beginning. I pretty much use the command line exclusively. I've never had a problem I could not recover from. But, I'm not well versed in gitlab. So, I need a cheat sheet for how you guys think changes should be committed now. Something simple that an old unix graybeard can handle :) thanks for your help- allan On Mon, Jan 3, 2022 at 4:29 PM Povilas Kanapickas wrote: > On 1/2/22 6:30 PM, Ralph Little wrote> On 2022-01-02 3:14 a.m., Povilas > Kanapickas wrote: > >> On 1/2/22 5:07 AM, Ralph Little wrote: > > Personally, I always make changes to branches. I don't believe that > > there should be functional changes direct to master, even for small > > corrections. > > I don't know if I would necessarily go all the way to require MRs for > > every change but I am open to be convinced. > I'm not sure I understood correctly, so instead of guessing, let's > double check :) Are you not convinced that we should add a rule in > GitLab that forbids direct pushes or are you against general policy? > >>> I don't think we should permit direct commits to master as a rule, > >>> enforced either by policy or by some mechanism (if such a thing exists) > >> Gitlab allows adding a per-branch rule that has 3 settings: > >> - Allowed to merge (Developers+Maintainers / Maintainers / No one / A > >> specific set of users) > >> - Allowed to push (Developers+Maintainers / Maintainers / No one / A > >> specific set of users) > >> - Allowed to force push (Yes/No) > >> > >> So for example we could configure the following for master branch: > >> > >> - Allowed to merge = Developers+Maintainers > >> - Allowed to push = No one (this would be relaxed to Maintainers for > >> the release commit) > >> - Allowed to force push = No > >> > >> Myself I slightly prefer the above strict rule because pushes of wrong > >> branch to wrong remote happen to everyone. An agreement would work > >> fine too. > >> > >>> I'm not sure about requiring MRs for all branches though but I am open > >>> to persuasion. > >>> I think that was my point. > >> I'm still not sure I understand :-) Are you talking about requiring a MR > >> from any arbitrary branch abc to another branch xyz? Or about requiring > >> a MR from any arbitrary branch abc to "master" branch? Could you please > >> explain like I'm five with a couple examples? > >> > > I guess my point is that I don't really care much about requiring Merge > > Requests for any changes to the repo as much as I care about not pushing > > changes directly to master without branching and merging (and benefiting > > from our pipeline checks). > > It is too easy to break master by a careless single push. > > I finally understood. I was not thinking about the third option of not > using merge requests, but just using separate branches, checking the CI > results and merging via local git instance. > > > Referring to your original proposition: > > > >> What do you think about requiring merge requests for all incoming > >> changes on the sane-backends repository? > > > > ... I am open to discussion certainly and I can see the advantages. > > Making sure the changes work via pushing branches and checking CI solves > the issue of broken commits being pushed just like requiring merge > requests. > > In addition to the above, requiring merge requests solve this: > - there's a place to conveniently comment about any change landing to > the master branch far into the future > - the chance of accidental push to master is eliminated (happened to > even to me, though on a different project) > > I don't know whether these are important points to convince you. Myself > I only have slight preference for requiring merge requests and Wolfram > indicated that he strongly supports it due to ability to do code reviews. > > Cheers, > Povilas > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] [canon_dr] Imprinter detection
Please create a new function, like init_panel(), and call it after init_model. allan On Thu, May 5, 2022 at 5:39 PM Charles Quarra via sane-devel < sane-devel@alioth-lists.debian.net> wrote: > > Good afternoon, > > I've been working on the MR for imprinter support for the canon_dr backend (MR: https://gitlab.com/sane-project/backends/-/merge_requests/706 ) > canon_dr: add imprinting support for DR-X10C (!706) · Merge requests · sane-project / backends · GitLab > enables all imprinting features exposed by the TWAIN driver: pre-imprinting and post-imprinting with all addon modes font size, orientation and spacing > gitlab.com > > > > Since imprinters are optional hardware modules, it makes sense to detect them at runtime and make the corresponding SANE options inactive. I have some implementation for runtime detection of the imprinters. > > My question is what would be the preferred place to do this runtime detection. > > My instinct would be to add the required read cmd inside the init_model function, specifically here: > > https://gitlab.com/sane-project/backends/-/merge_requests/706/diffs#bd44e4ec108bed0a73ccda8521103ba2ba4b2a5b_1894_1905 > canon_dr: add imprinting support for DR-X10C (!706) · Merge requests · sane-project / backends · GitLab > enables all imprinting features exposed by the TWAIN driver: pre-imprinting and post-imprinting with all addon modes font size, orientation and spacing > gitlab.com > > > > The reason I want to check with the backend maintainers first, is that I've not seen other usb/scsi commands done inside init_model, wondering if perhaps there is a good reason for that? > > Thanks for your help, > > Charles Quarra > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu SP-1425
The 'SP' machines are not supported by the sane-backends package that we provide. Some of the earlier ones were Genesys Logic scanners, so perhaps yours also is. It might be possible to extend the existing genesys sane backend to support these scanners too. allan On Tue, Feb 15, 2022 at 2:36 PM Rainer Dorsch via sane-devel < sane-devel@alioth-lists.debian.net> wrote: > Hi, > > is it correct that for operating the Fujitsu SP-1425 I would need binary > drivers from Fujitsu > > http://imagescanner.fujitsu.com/global/dl/agree/ubuntu-64-220-sp.html > > which implement the SANE-API? > > At least I read the information on > > https://origin.pfultd.com/downloads/IMAGE/driver/ubuntu/220/ > P2U3-0210-03ENZ0.pdf > > like this. > > That would be a no-go for me, since I can break at any time if I upgrade > my > OS. > > Or do I need the binary stuff from Fujitsu only for the management tool > pfuspconsumables and standard scanning functions are already supported by > sane? > > Many thanks > Rainer > > -- > Rainer Dorsch > http://bokomoko.de/ > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fast fi-65F slow with SANE
'epjitsu' backend, in this case. allan On Tue, Feb 8, 2022 at 12:52 PM Ralph Little wrote: > Hi, > > On Tue, Feb 8, 2022 at 9:02 AM m. allan noah wrote: > >> An easier mechanism might be to comment out all the backends you are not >> using in /etc/sane.d/dll.conf >> >> allan >> >> > On Tue, Feb 8, 2022 at 11:54 AM Felix E. Klee wrote: >> >>> Ralph Little writes: >>> > If you don't specify the scanner to scanimage with the -d option, then >>> > it will poll around all the backends to obtain a list of the available >>> > scanners first. This typically can take quite a good few seconds. >>> >>> This is the explanation, thanks! Glad I asked. Now this is fun: >>> >>> scanimage -o out.png -d "epjitsu:libusb:003:007" --resolution 200dpi >>> >>> :D >> >> > I concur. > > Since you have a USB connection, the device name is likely to change every > time you power cycle the scanner as the USB subsystem will assign a > different address. Leaving only the fujitsu backend available in the > dll.conf file, the startup delay will be next to nothing. > > Cheers, > Ralph > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fast fi-65F slow with SANE
An easier mechanism might be to comment out all the backends you are not using in /etc/sane.d/dll.conf allan On Tue, Feb 8, 2022 at 11:54 AM Felix E. Klee wrote: > Ralph Little writes: > > If you don't specify the scanner to scanimage with the -d option, then > > it will poll around all the backends to obtain a list of the available > > scanners first. This typically can take quite a good few seconds. > > This is the explanation, thanks! Glad I asked. Now this is fun: > > scanimage -o out.png -d "epjitsu:libusb:003:007" --resolution 200dpi > > :D > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fast fi-65F slow with SANE
What debugging messages are produced right before the delay? On Tue, Feb 8, 2022 at 9:25 AM Felix E. Klee wrote: > The Fujitsu fi-65F can scan an A6 page in just one second. This works > as advertised with the included “PaperStream Capture”. It even works > when using SANE, except that before each scan there is a delay of almost > ten (!) seconds: > > $ cat /etc/lsb-release > LSB_VERSION=1.4 > DISTRIB_ID=Arch > DISTRIB_RELEASE=rolling > DISTRIB_DESCRIPTION="Arch Linux" > $ uname -a > Linux felix-arch 5.16.4-arch1-1 #1 SMP PREEMPT Sat, 29 Jan 2022 > 19:08:13 + x86_64 GNU/Linux > $ scanimage --version > scanimage (sane-backends) 1.1.1; backend version 1.1.1 > $ scanimage -L > device `epjitsu:libusb:003:006' is a FUJITSU fi-65F 0A01 scanner > $ scanimage -o out.png --resolution 200dpi > > *Why the delay?* > > I also tried with `SANE_DEBUG_EPJITSU=255 scanimage`, but that didn’t > tell me anything: During the delay there is no output. > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Upcoming changes for handling release notes
I don't recall this conversation, where did it take place? In the past, we had a Changelog that everyone modified for every merge, and it was largely a duplicate of their commit messages. So, we stopped doing it. Are you proposing a return to that type of duplication? allan On Wed, Dec 29, 2021 at 4:57 PM Ralph Little wrote: > Hi, > > On 2021-12-29 1:30 p.m., Povilas Kanapickas wrote: > > Hello, > > > > There were some discussions on how to make handling release notes easier > > in the past so that releases are not as difficult. Time has come to > > actually implement them. > > > > What changes? > > > > Developers will need to write a short one or two sentence description to > > a new file in newsfragments directory when submitting the feature for > > review. That's it. > > > > Longer version: > > > > We'll write release notes as part of merge requests that introduce the > > features or bug fixes instead of deferring everything until the release > > time comes. > > > > This has the benefit that the release notes will be written by a more > > knowledgeable person than the release manager and we will not wait > > months only to forget what merge request was actually about. The side > > benefit of this will be that creating releases will become easier as no > > one will need to hunt all merge requests that comprise the release. > > > > The release notes for unreleased features will be stored in > > "newsfragments" directory in the repository. At the time of the release, > > the files will be combined into a single text block, edited by the > > release manager and added to the NEWS file. Storing release notes in > > separate files before the release makes it easy to avoid merge conflicts. > > > > Like I said above, for the developers almost nothing changes: just add a > > new file to the newsfragments directory with a one sentence description > > before creating a merge request. > > > > I've created a merge request with all unreleased changes since 1.0.32, > > you can see how the new process looks like in practice: > > https://gitlab.com/sane-project/backends/-/merge_requests/676 > > > > Regards, > > Povilas > > > Sounds great! > Will we clean this directory out on every 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] Changing versioning scheme (1.1.0, 1.2.0, 1.3.0 instead of 1.0.33, 1.0.34, 1.0.35)
Sounds like you are proposing something different from what Till described. I think what you suggest is a fine alternative, and it does not conflict with the sane standard: https://sane-project.gitlab.io/standard/api.html#version-control We must be careful not to break compatibility, say by accidentally bumping the soversion. allan On Mon, Dec 27, 2021 at 5:10 PM Ralph Little wrote: > Hi > I agree with this. Something I wanted to also propose. > > Cheers > Ralph > > On Mon, Dec 27, 2021, 13:04 Povilas Kanapickas wrote: > >> Hello, >> >> The current versioning scheme does not allow proper bugfix releases of >> SANE backends. That is, only 3 components in the version are supported >> properly in the build scripts and elsewhere. For example version codes >> for 1.0.33.1 would be identical to 1.0.33. Version codes are the only >> thing that I found, there are likely other problems because people >> writing code did not expect a 4-component version. >> >> The above is bad, because e.g. if we release 1.0.33 and notice a serious >> problem, we can't release a bugfix without risking breakage in various >> places even if it's a single line change. >> >> Fixing all the code that expects 3-component version is probably not >> good use of the time we have. >> >> Therefore I propose we switch to increasing the second version component >> instead of the third for future releases of SANE. E.g. instead of >> 1.0.35, 1.0.36 and 1.0.37 we will have 1.2.0, 1.3.0 and 1.4.0 releases. >> This way we would have the third version component reserved for bugfix >> releases. >> >> I also propose to apply the proposal to the upcoming 1.0.33 release and >> use 1.1.0 version for it. >> >> Please let me know what you think. >> >> Regards, >> Povilas >> > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon DR-G2090
Hello again Furio- It has been a decade since we worked together on the 7550! A few thoughts: 1. Have you added the scanner to /etc/sane.d/canon_dr.conf ? 2. Can you produce a log file of the scanner making a low resolution scan? (SANE_DEBUG_CANON_DR=35 scanimage --resolution=100 --mode=lineart 2>2090.log >2090.pnm) 3. Are you able to get logs of windows driver, using wireshark? allan On Sun, Dec 19, 2021 at 9:36 AM Furio Settimi wrote: > I have a canon dr-g2090 that I can't get to go on linux. > On Windows it works. > You have already helped me with a DR-9070 a few years ago > I also tried with canon proprietary drivers but it didn't work. > Can you help me? > Thanks > Furio > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Interactive use of scanner buttons
On Fri, Dec 3, 2021 at 11:39 AM Paul Wolneykien wrote: > > В Fri, 3 Dec 2021 11:08:23 -0500 > "m. allan noah" пишет: > > > On Fri, Dec 3, 2021 at 9:33 AM Paul Wolneykien > > wrote: > > > > > В Fri, 3 Dec 2021 09:02:43 -0500 > > > "m. allan noah" пишет: > > > > > > > Many backends are single threaded currently, so this would be a > > > > pretty invasive change. > > > > > > But that's not a required change, isn't it? If a backend isn't > > > ready for it, it just should not add SANE_CAP_DYNAMIC to the > > > options. > > > > That makes things hard for front-end developers, because of the > > variation between backends. This will negate one of the strengths of > > sane (few frontends supporting lots of backends). > > > > I wonder if there is another approach here- middleware? Similar to how > > backends are unaware that they are being used over the network with > > saned, perhaps we could have a kind of intermediary poller, which ran > > on the machine with the scanner? It could emit events, and not > > require all backends which support buttons to be updated? > > As far as I know, SANE provides exclusive access to the scanner for > one client only. So, we can run a poller or a frontend, but not both. > That's why I would like to see the polling process running "inside" > backend (be launched from the backend as a thread). > right, the poller acts as a pass-thru, acts as a front-end when talking to the backend, and acts as a backend when talking to a front-end. We don't have exclusive access problems because the applications make a chain. > Emit events to be handled (how?) by the frontends? Doesn't this > really would make things harder for frontends? No, we could use your proposed mechanism, but we don't have to change backends to support it. > > And again: I don't want to require any backend to support > notification features. The same for the frontends. All what I propose > is the use of two additional constant values, indicating new type of > capability and a new type of action --- thanks to the completely > abstract sane_get_option_descriptor() and sane_control_option() design. > I understand, but many backends are unmaintained, and we have a history of front-end authors complaining because of inconsistencies in our backends. As a front-end author, I would not add support for something that only one backend does, and as a backend author, i would not implement a feature that no front-ends support. We can close that gap, and speed adoption of features by using a layered stack of software. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Interactive use of scanner buttons
On Fri, Dec 3, 2021 at 9:33 AM Paul Wolneykien wrote: > В Fri, 3 Dec 2021 09:02:43 -0500 > "m. allan noah" пишет: > > > Many backends are single threaded currently, so this would be a pretty > > invasive change. > > But that's not a required change, isn't it? If a backend isn't ready > for it, it just should not add SANE_CAP_DYNAMIC to the options. > That makes things hard for front-end developers, because of the variation between backends. This will negate one of the strengths of sane (few frontends supporting lots of backends). I wonder if there is another approach here- middleware? Similar to how backends are unaware that they are being used over the network with saned, perhaps we could have a kind of intermediary poller, which ran on the machine with the scanner? It could emit events, and not require all backends which support buttons to be updated? allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Interactive use of scanner buttons
Many backends are single threaded currently, so this would be a pretty invasive change. Frankly, polling over the network once per second is not that much traffic, and certainly easier to implement. allan On Fri, Dec 3, 2021 at 8:50 AM Paul Wolneykien wrote: > В Thu, 2 Dec 2021 17:29:13 -0800 > Ralph Little пишет: > > > However, regular polling can be > > detrimental as a general feature. One commentator suggested that over > > a network, this could become an unnecessary bandwidth hog. In SANE we > > would want to add polling features in a generic fashion and we should > > wary of undesirable side-effects. Flooding a network just because you > > are sitting in an idle instance of xsane is certainly such an > > example. It is something that we should discuss carefully before > > enhancing the standard. > > Yes, polling over the network is a very bad idea. That means, we need > something like subscribe+notify interface in SANE. What about the > following API upgrade? > > A new capability for dynamic options (not only the buttons, but all > things that could be changed by the scanner inself): > > + #define SANE_CAP_DYNAMIC > > Then a new action for sane_control_option() indicating we want to > subscribe to scanner-initiated updates of the given value: > > + SANE_ACTION_SUBSCRIBE > > Then a function type for a notification handler pointer: > > + typedef void (*sane_option_change_callback)(SANE_Int option, void > *value); > > Having these minor API changes, it's become possible to make a call to > sane_control_option() like the following: > > sane_control_option(sane_handle, option_number, SANE_ACTION_SUBSCRIBE, > my_handler, NULL); > > And if the option option_number is marked as SANE_CAP_DYNAMIC in the > option descriptor, the backend should setup the given notification > handler and invoke it each time the option is updated. > For options not explicitly marked as dynamic it should return > SANE_STATUS_UNSUPPORTED. So, no changes are required for the present > backends. > > How the backend could monitor the option changes? It's up to the > backend. But with the present codebase/hardware polling would be used > most of the time, I guess. That will be, however, a local-only polling > over USB or SCISI interfaces, not a polling over the network as the > backend code runs on the server connected to the scanner in the > client-server scenario. Of course we also need to implement the proper > RPC in order to support callbacks over the network, but that doesn't > affect the backends and doesn't require more API changes. > > As to a resident polling process inside the backend, we already have > sanei_thread_*() functions for that. > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Interactive use of scanner buttons
There is a great deal of variation between scanners and backends regarding what buttons are available and how they are exposed. You also have the exclusive device access problem. In the end, I think you need a new frontend, or modifications to an existing one, rather than a separate monitor. allan On Thu, Dec 2, 2021 at 5:35 PM Paul Wolneykien wrote: > > Hi! > > As I can see, XSane doesn't poll the scanner's hardware buttons. > And if I understand the scanbd manual right, the daemon locks the SANE > interface to the scanner until a button is pressed, and then gives > exclusive access to the scanner for the frontend. So, the daemon is > primarily for launching a frontend, but not for controlling the > frontend while it is running. Am I right? > > I've grep'ed the mailing list archives a little and it seems that the > main purpose of various button daemons (scanbuttond, scanbd) is to > implement such a facility as "push scan": the user goes to a remote > (possibly, network) scanner, places a standard material into it, > presses a button on the scanner and the system performes an automatic > (that's important!) scan. > It also seems that in other situations, when a user wants to use an > interactive frontend (for making previews, selecting the scan > area, adjusting black and white points and gamma) the scanner is > expected to be placed on the table near PC. Or, at least, that the > material for scan can be placed into the scanner without a need for > further attention (i.e. a sheet material), so the user can set it up > and then back to his/her keyboard and mouse to make a scan or a number > of scans with different settings using the GUI frontend. > > These two stories (the "push story" and the "desktop story") are nice > and simple, but are more or less unapplicable in the world of book > scanning! > > Firstly, books are all different, so you need to make previews, > select areas and adjust things for each one. Secondly, books aren't > flat, so even if you use a special hardware you almost always need > to handle the book with both your hands! > > So, for scanning books, it would be nice to be able to control such a > frontend as XSane with the scanner's hardware buttons. Because most of > the time you can reach the hardware button even if you handle the book > using both hands (however, a configurable delay after the button is > pressed may be helpful option). > > (The other possible way to solve the described problem is to use a > separate triggering device. May be a pedal! But that's another story...) > > I want to know/discuss, what a design of a button monitor for > use with interactive frontends would fit into SANE better. Any ideas? > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] wont produce PDF
there are many frontend programs in the sane world. You need to tell us which one you are using. allan On Thu, Oct 21, 2021 at 7:30 AM Ian wrote: > Does produce PNM Even when PDF selected > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu fi-5900c command option for single-sided scanning
On Sun, Sep 26, 2021 at 3:14 PM Simon Matter wrote: > Hi, > > > I usually use the parameters below, and I am trying to modify them to > scan > > the front side only while still using compression and imprinting > > > > Previously I thought that the change I needed was *--source ADF Front* > but > > Did you try --source "ADF Front"? > > Simon > > Yes- I expect the quotes will be needed. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Unable to use Canon Unit201 scanner with Linux Mint
The FSU-101 says the same thing, but it is a normal scanner. The limitation is just in canon's windows software. I'm not sure we know how to get canon's linux software to work, or if it also contains this limitation. allan On Tue, Aug 17, 2021 at 8:29 AM Heinz Rohde via sane-devel < sane-devel@alioth-lists.debian.net> wrote: > Hello, > > I found this advice on Canon Product Website: > > > * The Flatbed Scanner Unit 201 needs to be used with a DR-series > scanner; it cannot be used independently. > > visit > https://hk.canon/en/business/flatbed-scanner-unit-201/product?subCategory= > > > Am Montag, dem 16.08.2021 um 07:55 +0100 schrieb ebaysales: > > Hi, > > > > I cannot get this scanner to work on my 64 bit Linux Mint 20.1 > > Cinnamon computer. I have asked on the Mint forums and > > received a lot of help but still unable to use the scanner. rather > > than a long post here can I ask you to read up on the > > progress so far on my Mint forum post to be found at > > https://forums.linuxmint.com/viewtopic.php?f=51=355033 > > > > Any offers of help or advice will be gratefully received. > > > > Alan > > > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] New Scanner Request: $$$
There are other scanners in this size class, like the Fujitsu Scansnap series. But, it sounds like to me that you may not need a new scanner or backend. Rather you need changes to the frontend, or a new one. The various adf waiting things in the pixma backend really should be features of a frontend like scanimage or scanadf. Perhaps treat the 'no docs' error as non fatal, and loop. Another alternative is to investigate scanbd, and see if it can do what you want. allan On Wed, Aug 4, 2021 at 7:55 AM Spencer Davis wrote: > Looking for someone to write a sane backend for an Epson > RapidReciept RR-60 or if anyone knows of something similar that would be > simpler for the use-case below and looks/priced the same. > > Issue: > The current epson backend sort of works. Using scanimage I can get the ADF > to scan with --prompt to take a receipt, load another->hit enter, etc but > as soon as it doesnt detect a page, it dies. So I know most of the leg work > is there, just might need some alterations but it's outside of my > development ability paygrade. > > What I'm looking for: > I need a compact, sheet-fed scanner to be *always* waiting for the next > receipt and automatically save it to disk. > I haven't done a ton of research but I think I need something similar to > the adf-wait parameter in sane-pixma: > http://manpages.ubuntu.com/manpages/cosmic/man5/sane-pixma.5.html > > Epson Product Link: > > https://epson.com/Support/Scanners/RapidReceipt-Series/Epson-RR-60/s/SPT_B11B252204 > > > Any more questions feel free to reach out. I'm going to need a bunch of > these so I can absolutely get one shipped to you. There may also be future > work needing help making a completely proprietary scanner w/ patent, if > anyone has good knowledge on internals w/ the ability to mock up test > hardware, shoot me an email. > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Chances are, you are wrong :) allan On Sat, May 8, 2021 at 4:50 AM Andrew Goodbody wrote: > > Chances are that rather than interfering with Sane, the proprietary > software does something that made the scanner work the next time you ran > Sane after having just run the ScanSnap app. > > Andrew > > On 07/05/2021 22:12, Media Mouth wrote: > > Well noting yet. Any reason to think that using the proprietary > > software that comes with a Fujitsu scanner "ScanSnap.app" might do > > something that interferes with SANE. (I'm suspect SANE is their > > underlying engine) > > > > We are and have been able to scan using ScanSnap, and for a brief moment > > yesterday we were /also/ able to run `scanimage` and save a .pnm > > > >> On May 7, 2021, at 12:05 PM, m. allan noah >> <mailto:kitno...@gmail.com>> wrote: > >> > >> Unknown- look for OSX system logs that might include USB related errors. > >> > >> allan > >> > >> On Fri, May 7, 2021 at 2:09 PM Media Mouth >> <mailto:commun...@gmail.com>> wrote: > >>> > >>> So we're apparently back to the original question... > >>> > >>> "Re: [sane-devel] scanimage -L detects no scanners / > >>> sane-find-scanner does -- on MacOS" > >>> > >>> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 > >>> [Fujitsu], product=0x132b [ScanSnap iX500]) at libusb:000:002` > >>> and > >>> `scanimage -L` returns `No scanners were identified. If you were > >>> expecting something different` etc. > >>> > >>> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > >>> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > >>> that it suddenly started working, so I wondered if by some magic that > >>> was waking something up, but running it again made not difference > >>> this go around. > >>> > >>> Any ideas? > >>> > >>> > >>> On May 7, 2021, at 6:26 AM, MediaMouth >>> <mailto:commun...@gmail.com>> wrote: > >>> > >>> It did ... and then it didn't. Right after successfully scanning a > >>> page, subsequent attempts, using the same command, failed with error > >>> "invalid argument". > >>> > >>> On May 7, 2021, at 05:14, m. allan noah >>> <mailto:kitno...@gmail.com>> wrote: > >>> > >>> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 > >>> scanner" > >>> > >>> looks like it works? > >>> > >>> > >> > >> > >> -- > >> "well, I stand up next to a mountain- and I chop it down with the edge > >> of my hand" > > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
I mean currently running and talking to the scanner. Perhaps something like monitoring for button presses. In general, you would not have both the factory software and sane on the machine at the same time. On Fri, May 7, 2021 at 7:26 PM MediaMouth wrote: > > Control, meaning 'currently scanning' or meaning it has run, therefore made > some kind of a settings change, such that even when not launched retains > "control" > > > On May 7, 2021, at 16:23, m. allan noah wrote: > > > > The proprietary software does not use sane, and if it currently has > > control of the scanner, sane will not be able to work. > > > > allan > > > >> On Fri, May 7, 2021 at 5:12 PM Media Mouth wrote: > >> > >> Well noting yet. Any reason to think that using the proprietary software > >> that comes with a Fujitsu scanner "ScanSnap.app" might do something that > >> interferes with SANE. (I'm suspect SANE is their underlying engine) > >> > >> We are and have been able to scan using ScanSnap, and for a brief moment > >> yesterday we were also able to run `scanimage` and save a .pnm > >> > >> On May 7, 2021, at 12:05 PM, m. allan noah wrote: > >> > >> Unknown- look for OSX system logs that might include USB related errors. > >> > >> allan > >> > >> On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: > >> > >> > >> So we're apparently back to the original question... > >> > >> "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner > >> does -- on MacOS" > >> > >> `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], > >> product=0x132b [ScanSnap iX500]) at libusb:000:002` > >> and > >> `scanimage -L` returns `No scanners were identified. If you were expecting > >> something different` etc. > >> > >> It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > >> SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > >> that it suddenly started working, so I wondered if by some magic that was > >> waking something up, but running it again made not difference this go > >> around. > >> > >> Any ideas? > >> > >> > >> On May 7, 2021, at 6:26 AM, MediaMouth wrote: > >> > >> It did ... and then it didn't. Right after successfully scanning a page, > >> subsequent attempts, using the same command, failed with error "invalid > >> argument". > >> > >> On May 7, 2021, at 05:14, m. allan noah wrote: > >> > >> "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 > >> scanner" > >> > >> looks like it works? > >> > >> > >> > >> > >> -- > >> "well, I stand up next to a mountain- and I chop it down with the edge > >> of my hand" > >> > >> > > > > > > -- > > "well, I stand up next to a mountain- and I chop it down with the edge > > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
The proprietary software does not use sane, and if it currently has control of the scanner, sane will not be able to work. allan On Fri, May 7, 2021 at 5:12 PM Media Mouth wrote: > > Well noting yet. Any reason to think that using the proprietary software > that comes with a Fujitsu scanner "ScanSnap.app" might do something that > interferes with SANE. (I'm suspect SANE is their underlying engine) > > We are and have been able to scan using ScanSnap, and for a brief moment > yesterday we were also able to run `scanimage` and save a .pnm > > On May 7, 2021, at 12:05 PM, m. allan noah wrote: > > Unknown- look for OSX system logs that might include USB related errors. > > allan > > On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: > > > So we're apparently back to the original question... > > "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does > -- on MacOS" > > `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], > product=0x132b [ScanSnap iX500]) at libusb:000:002` > and > `scanimage -L` returns `No scanners were identified. If you were expecting > something different` etc. > > It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > that it suddenly started working, so I wondered if by some magic that was > waking something up, but running it again made not difference this go around. > > Any ideas? > > > On May 7, 2021, at 6:26 AM, MediaMouth wrote: > > It did ... and then it didn't. Right after successfully scanning a page, > subsequent attempts, using the same command, failed with error "invalid > argument". > > On May 7, 2021, at 05:14, m. allan noah wrote: > > "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" > > looks like it works? > > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
Unknown- look for OSX system logs that might include USB related errors. allan On Fri, May 7, 2021 at 2:09 PM Media Mouth wrote: > > So we're apparently back to the original question... > > "Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does > -- on MacOS" > > `sane-find-scanner` returns `found USB scanner (vendor=0x04c5 [Fujitsu], > product=0x132b [ScanSnap iX500]) at libusb:000:002` > and > `scanimage -L` returns `No scanners were identified. If you were expecting > something different` etc. > > It was after your request for the stdout of `SANE_DEBUG_FUJITSU=50 > SANE_DEBUG_SANEI_CONFIG=10 scanimage -L` > that it suddenly started working, so I wondered if by some magic that was > waking something up, but running it again made not difference this go around. > > Any ideas? > > > On May 7, 2021, at 6:26 AM, MediaMouth wrote: > > It did ... and then it didn't. Right after successfully scanning a page, > subsequent attempts, using the same command, failed with error "invalid > argument". > > On May 7, 2021, at 05:14, m. allan noah wrote: > > "device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" > > looks like it works? > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS
"device `fujitsu:ScanSnap iX500:330189' is a FUJITSU ScanSnap iX500 scanner" looks like it works? On Fri, May 7, 2021 at 8:03 AM Media Mouth wrote: > > RE: > > Could we see the output of this? > > SANE_DEBUG_FUJITSU=50 SANE_DEBUG_SANEI_CONFIG=10 scanimage -L > > > Sure thing. See below. Curiously, having run that command, I'm suddenly > (finally) seeing the scanner on `scanimage -L` alone. > > [23:20:21.769223] [sanei_debug] Setting debug level of sanei_config to 10. > [23:20:21.769482] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.769564] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.769576] [sanei_config] sanei_config_open: attempting to open > `./dll.conf' > [23:20:21.769594] [sanei_config] sanei_config_open: attempting to open > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/dll.conf' > [23:20:21.769653] [sanei_config] sanei_config_open: using file > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/dll.conf' > [23:20:21.769768] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.769778] [sanei_config] sanei_config_open: attempting to open > `./dll.aliases' > [23:20:21.769788] [sanei_config] sanei_config_open: attempting to open > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/dll.aliases' > [23:20:21.769806] [sanei_config] sanei_config_open: could not find config > file `dll.aliases' > [23:20:21.785252] [sanei_config] sanei_configure_attach: start > [23:20:21.785275] [sanei_config] sanei_config_get_paths: using config > directories .:/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d > [23:20:21.785290] [sanei_config] sanei_config_open: attempting to open > `./xerox_mfp.conf' > [23:20:21.785313] [sanei_config] sanei_config_open: attempting to open > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/xerox_mfp.conf' > [23:20:21.785374] [sanei_config] sanei_config_open: using file > `/usr/local/Cellar/sane-backends/1.0.32/etc/sane.d/xerox_mfp.conf' > [23:20:21.785419] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3324' > [23:20:21.785465] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3325' > [23:20:21.785472] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3326' > [23:20:21.785477] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3327' > [23:20:21.785482] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3331' > [23:20:21.785488] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3332' > [23:20:21.785493] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3409' > [23:20:21.785498] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x340d' > [23:20:21.785503] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x340e' > [23:20:21.785508] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x340f' > [23:20:21.785513] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3412' > [23:20:21.785518] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3413' > [23:20:21.785523] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3419' > [23:20:21.785551] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341a' > [23:20:21.785574] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341b' > [23:20:21.785580] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341c' > [23:20:21.785585] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341d' > [23:20:21.785590] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x341f' > [23:20:21.785595] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3420' > [23:20:21.785600] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3421' > [23:20:21.785605] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3425' > [23:20:21.785610] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3426' > [23:20:21.785615] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3427' > [23:20:21.785620] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3428' > [23:20:21.785625] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x3429' > [23:20:21.785630] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x342a' > [23:20:21.785635] [sanei_config] sanei_configure_attach: trying to attach > with 'usb 0x04e8 0x342b' > [23:20:21.785641]
Re: [sane-devel] canon dr-7550c batch scan only scans single page
On Tue, Apr 13, 2021 at 9:43 AM wrote: > > From: m. allan noah > Date: Tue, Apr 13, 2021 at 09:17:05AM -0400 > > On Tue, Apr 13, 2021 at 8:39 AM wrote: > > > > > > From: m. allan noah > > > Date: Tue, Apr 13, 2021 at 08:28:24AM -0400 > > > > Interesting- the scanner reports it does not have any more paper in > > > > it. Some questions: > > > > > > > > 1. does this happen if source=ADF Front? > > > > > > Yes, no difference, but only one face of the first page gets scanned, of > > > course. > > > > > > > 2. does the second sheet of paper get pulled into the scanner when the > > > > error occurs? > > > > > > No, it doesn't. > > > > > > > 3. does this happen at lower resolution? > > > > > > I see no difference at --resolution 100. Still lower resolutions don't > > > really make sense. Higher resolutions (600) make no difference either. > > > > > > This is a large, bulk volume scanner. On executing the scanimmage > > > command, the bottom of the tray moves up so the paper on top touches the > > > rollers. After the first page, the tray moves back down. Trying to keep > > > the paper up at the same level doesn't make any difference. > > > > > > Thanks, > > > Jurriaan > > > > I think the version you are running might have a buffermode option? > > Can you try enabling that, and see if the feeder stays up? > > > It didn't, so I added the pa:sane-project/sane-git repository and I > retested with these versions: > > ii libsane:amd64 1.0.32+git20210410-focal0 amd64 > API library for scanners [transitional package] > ii libsane-common 1.0.32+git20210410-focal0 all > API library for scanners -- documentation and support files > ii libsane-hpaio:amd643.20.3+dfsg0-2 amd64HP > SANE backend for multi-function peripherals > ii libsane1:amd64 1.0.32+git20210410-focal0 amd64 > API library for scanners > ii sane 1.0.14-15 amd64scanner > graphical frontends > ii sane-utils 1.0.32+git20210410-focal0 amd64 > API library for scanners -- utilities > > sudo scanimage -v --mode=Gray --batch --batch-count 999 --format=tiff -y 297 > --buffermode=yes --page-height 297 --resolution 600 '--source=ADF Duplex' > > and lo and behold, that did make a large difference - it works. > > Thanks, > Jurriaan > Sounds good. It has been many years since I had access to one of these scanners with an elevator. In the past, that buffermode option was not required to make it work. Perhaps something changed in the interim. I suppose we could try to find it by using git bisect, but I am not sure it is worth the effort. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] canon dr-7550c batch scan only scans single page
On Tue, Apr 13, 2021 at 8:39 AM wrote: > > From: m. allan noah > Date: Tue, Apr 13, 2021 at 08:28:24AM -0400 > > Interesting- the scanner reports it does not have any more paper in > > it. Some questions: > > > > 1. does this happen if source=ADF Front? > > Yes, no difference, but only one face of the first page gets scanned, of > course. > > > 2. does the second sheet of paper get pulled into the scanner when the > > error occurs? > > No, it doesn't. > > > 3. does this happen at lower resolution? > > I see no difference at --resolution 100. Still lower resolutions don't > really make sense. Higher resolutions (600) make no difference either. > > This is a large, bulk volume scanner. On executing the scanimmage > command, the bottom of the tray moves up so the paper on top touches the > rollers. After the first page, the tray moves back down. Trying to keep > the paper up at the same level doesn't make any difference. > > Thanks, > Jurriaan I think the version you are running might have a buffermode option? Can you try enabling that, and see if the feeder stays up? allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] canon dr-7550c batch scan only scans single page
Interesting- the scanner reports it does not have any more paper in it. Some questions: 1. does this happen if source=ADF Front? 2. does the second sheet of paper get pulled into the scanner when the error occurs? 3. does this happen at lower resolution? allan On Tue, Apr 13, 2021 at 7:44 AM Jurriaan wrote: > > I have recently bought a uses Canon DR-7550c scanner for a non-profit > organisation. It scans, but it doesn't scan multiple pages. > > output of > > SANE_DEBUG_CANON_DR=15 scanimage -v --mode=Gray --batch --batch-count > 999 --format=tiff -y 297 --page-height 297 --resolution 200 > '--source=ADF Duplex' > > below. > > The interesting part is > > Scanned page 2. (scanner status = 5) > Scanning page 3 > [15:37:33.785430] [canon_dr] sane_start: start > [15:37:33.785448] [canon_dr] started=1, side=1, source=3 > [15:37:33.785461] [canon_dr] update_i_params: start > [15:37:33.785474] [canon_dr] update_i_params: finish > [15:37:33.785486] [canon_dr] clean_params: start > [15:37:33.785498] [canon_dr] clean_params: finish > [15:37:33.785511] [canon_dr] object_position: start > [15:37:33.785523] [canon_dr] object_position: load > [15:37:33.785536] [canon_dr] do_usb_cmd: start 1618234653 785535 > [15:37:33.793366] [canon_dr] stat: clearing error 'Error during device I/O' > [15:37:33.793414] [canon_dr] do_usb_clear: start > [15:37:33.893510] [canon_dr] do_usb_clear: clear halt > [15:37:33.894486] [canon_dr] do_usb_cmd: start 1618234653 894484 > [15:37:33.896116] [canon_dr] do_usb_cmd: finish 1618234653 896115 > [15:37:33.896141] [canon_dr] sense_handler: start > [15:37:33.896154] [canon_dr] Sense=0x5, ASC=0x3a, ASCQ=00, EOM=0, ILI=0, > info= > [15:37:33.896170] [canon_dr] Illegal request: no paper > [15:37:33.896182] [canon_dr] do_usb_clear: finish after RS > [15:37:33.896195] [canon_dr] stat: bad RS status, 7 > [15:37:33.896209] [canon_dr] sane_start: ERROR: cannot load page > [15:37:33.896222] [canon_dr] sane_start: error 7 > scanimage: sane_start: Document feeder out of documents > > I think. Could anyone give me hints on what to try next? Other options, > higher level of debugging, install development-version of sane? > > Thanks, > Jurriaan > > [15:37:26.088273] [sanei_debug] Setting debug level of canon_dr to 15. > [15:37:26.088404] [canon_dr] sane_init: start > [15:37:26.088423] [canon_dr] sane_init: canon_dr backend 1.0.58, from > sane-backends 1.0.29 > [15:37:26.088436] [canon_dr] sane_init: finish > [15:37:26.088449] [canon_dr] sane_get_devices: start > [15:37:26.199669] [canon_dr] sane_get_devices: reading config file > canon_dr.conf > [15:37:26.199821] [canon_dr] sane_get_devices: looking for 'scsi CANON CR' > [15:37:26.200104] [canon_dr] sane_get_devices: looking for 'scsi CANON DR' > [15:37:26.200329] [canon_dr] sane_get_devices: setting "duplex-offset" to 840 > [15:37:26.200347] [canon_dr] sane_get_devices: setting "vendor-name" to CANON > [15:37:26.200360] [canon_dr] sane_get_devices: setting "model-name" to > DR-2080C > [15:37:26.200374] [canon_dr] sane_get_devices: setting "version-name" to > [15:37:26.200387] [canon_dr] sane_get_devices: setting "padded-read" to 1 > [15:37:26.200400] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1601' > [15:37:26.200414] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1602' > [15:37:26.200428] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1603' > [15:37:26.200441] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1604' > [15:37:26.200455] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1606' > [15:37:26.200468] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1607' > [15:37:26.200482] [canon_dr] sane_get_devices: setting "duplex-offset" to 432 > [15:37:26.200494] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1608' > [15:37:26.200508] [canon_dr] sane_get_devices: setting "padded-read" to 1 > [15:37:26.200521] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1609' > [15:37:26.200535] [canon_dr] sane_get_devices: setting "duplex-offset" to 840 > [15:37:26.200547] [canon_dr] sane_get_devices: setting "vendor-name" to CANON > [15:37:26.200560] [canon_dr] sane_get_devices: setting "model-name" to > DR-2050C > [15:37:26.200573] [canon_dr] sane_get_devices: setting "version-name" to > [15:37:26.200586] [canon_dr] sane_get_devices: setting "padded-read" to 1 > [15:37:26.200599] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x160a' > [15:37:26.200612] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x160b' > [15:37:26.200625] [canon_dr] sane_get_devices: looking for 'usb 0x1083 0x160c' > [15:37:26.200639] [canon_dr] sane_get_devices: looking for 'usb 0x1083 0x160f' > [15:37:26.200651] [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x' > [15:37:26.200665] [canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1614' > [15:37:26.200678] [canon_dr] sane_get_devices: setting "duplex-offset" to 400 > [15:37:26.200691] [canon_dr] sane_get_devices: looking for 'usb
Re: [sane-devel] success report fujitsu fi-7140
The fujitsu.conf file was updated in a prior version of sane, but I had no user reports of success. So, I have just committed an update to that. Thanks for the report. allan On Sat, Feb 13, 2021 at 12:10 PM Filippo Bardelli wrote: > > Hi folks > > I am scanning documents with scanner id 0x04c5/0x14df that is flagged as > "untested" > > I have used fujitsu backend. simply adding this lines at > /etc/sane.d/fujitsu.conf > > #fi-7140 > usb 0x04c5 0x14df > > I am using slackware 14.2 > > let me know if you need more testing. > > best regards > > Filippo -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] newbie
Regarding the colors of the iX500, they are not strictly raw data. The scanner self-calibrates, which removes most of the high frequency noise. But, the default brightness and contrast values may still need some manual tweaking. It is also possible that the windows software does some further enhancement, which is not done in the sane backend. allan On Mon, Jan 25, 2021 at 11:36 AM Andy Bennett wrote: > > Hi, > > > I'm looking to get into scanning in the GNU/Linux world - I do > > not yet own a scanner. I know the SANE compatibility matrix > > exists [0], but I am hoping for some anecdotal recommendations. > > Welcome! > > > > What scanners are people using and how happy are you with your > > scanner and your SANE front-end? > > I have a Fujitsu ScanSnap iX500 and I'm very please with it. > > However... > > > > Also, I read a short blog post [1] about the author's scanner > > yielding different results under Windows and GNU/Linux. The > > author claims that the Windows driver can have better color > > accuracy. Does anyone have any commentary about such notions? > > > [1] https://www.digitaltidying.com/dont-use-linux-to-scan-photographs/ > > I can't speak to this issue particularly, but the iX500 has colour issues > of its own. > > I scan to pnm files with the included "scanimage" backend. > > I then have my own toolchain that does the things I want to these files. > > > AFAICT, the data that ends up in the pnm files is the raw data from the > scanning head. i.e. its. plain RGB intensity values. > > On the one hand, this is great because getting the raw data leaves me with > the most options. > > On the other hand, it's a pain. > > These files look terrible on Linux. Weirdly, the exact same files look fine > under Windows. > > > If I correct the files with pnmgamma, applying the sRGB or CIE profiles > then they look fine. > > > Also, > > The scanner is a duplex unit and therefore has a scanning head and a bright > light on both sides of the page. This means that the exact colour > reproduction varies greatly with the thickness of the paper. > > I have a stock set of colour curves that I use to correct things to how I > like them. > > > ...but in general, all colour is lies, and faithful or accurate conversion > between CMYK (used for print) and RGB (used for screen) is particularly > difficult. > > > Perhaps if you use one of the more featureful SANE frontends then it does a > lot of this stuff for you, but I was keen to make my own toolchain. > > > When I first got the scanner I read this guide: > http://www.samhallas.co.uk/repository/scanning.htm and learnt a lot. > > > > Getting passable scans from any toolkit (Windows or Linux) is fairly > straightforward. Getting "stunning" scans is always an art, similar to > digital photo manipulation. > > > > What you'll need to go alongside SANE will depend a lot on what you want to > use the scanner for. > For example, documents might benefit from OCR (optical character > recognition). Photos might benefit from a full Photoshop style package. > > > > Let us know some more of your requirements, such as use case, budget, etc, > and I'll try to offer some more anecdotes (if I have any). > > > > > Best wishes, > @ndy > > -- > andy...@ashurst.eu.org > http://www.ashurst.eu.org/ > 0x7EBA75FF > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] newbie
You need to tell us what kind of scanner you are looking for, and a general price range. allan On Mon, Jan 25, 2021 at 9:41 AM Matt Zagrabelny via sane-devel wrote: > > Greetings SANE folks, > > I'm looking to get into scanning in the GNU/Linux world - I do not yet own a > scanner. I know the SANE compatibility matrix exists [0], but I am hoping for > some anecdotal recommendations. > > What scanners are people using and how happy are you with your scanner and > your SANE front-end? > > Also, I read a short blog post [1] about the author's scanner yielding > different results under Windows and GNU/Linux. The author claims that the > Windows driver can have better color accuracy. Does anyone have any > commentary about such notions? > > Thanks for helping me get my feet wet. > > Cheers, > > -m > > [0] http://www.sane-project.org/sane-supported-devices.html > [1] https://www.digitaltidying.com/dont-use-linux-to-scan-photographs/ -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Sane backend for an intraoral X ray camera
On Thu, Dec 17, 2020 at 8:11 PM Mayuresh wrote: > > On Thu, Dec 17, 2020 at 07:42:06AM -0500, m. allan noah wrote: > > I took a quick look at the protocol and did not recognize it. > > > Perhaps someone else will recognize the protocol. > > If that is not recognized, what is the way out? Just play back as it is by > hard coding the values? > If the windows driver gives you some options, then you make a series of logs each with a different combination of settings. Then compare the logs to determine what changes. Anything that remains, you may have to hard code. > If I were to do that what tools are suitable? I tried python libusb once, > but could not mimic even 1 step, was getting input/output error or timeout > error. If you want to use sane, you copy a backend that seems readable to you, and pound it into shape. For instance, the cardscan backend is small, and uses USB. > Also, the 'END POINT' numbers reported by wireshark (by double clicking on > any event) aren't matching those reported by lsusb or usbmon. So when > mimicing it's unclear which end point numbers to trust. Oddly, the in vs out end points will have a difference in the highest bit (eg, 0x01 vs 0x81), and some logging programs don't show that distinction. I am not sure if that is what you are seeing. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Sane backend for an intraoral X ray camera
I approved both mails days ago, but the web-based download is a good idea. I took a quick look at the protocol and did not recognize it. Seems to be a few control URBs for setup, and then perhaps a string of interrupt URBs as the scanner waits for the x-ray source to fire? The image data is visible in the log, appears to be 12 bit, padded to 16 bit. I don't currently have a dicom viewer to look at the images. Perhaps someone else will recognize the protocol. allan On Thu, Dec 17, 2020 at 3:36 AM Mayuresh wrote: > > On Tue, Dec 15, 2020 at 11:25:32PM +0530, Mayuresh wrote: > > There were 3 x rays taken, just to give more room for observation, out of > > which first was discarded as it was completely dark. Attaching a zip of > > the remaining two. Have chosen an export format called 'carestream large' > > which presumably preserves maximum details relevant to the exercise. > > > > Request moderators to please let this and the previous mail pass through > > to relevant recipients. > > The mail with attachment is not yet approved or rejected by the moderator. > > I have kept the image contents here: > http://mayuresh.sdfeu.org/snaps.zip > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Sane backend for an intraoral X ray camera
usbmon is truncated, and the final image is necessary to determine top vs bottom, left vs right, etc. So we need a wireshark and an image from the same scan. allan On Sun, Dec 13, 2020 at 9:45 PM Mayuresh wrote: > > On Sun, Dec 13, 2020 at 05:08:31PM -0500, m. allan noah wrote: > > I don't see anything immediately obvious in the protocol, but we > > really need to see some scans. Even without the xray source we may > > learn something. But certainly the xray source, and the final image > > produced by the windows software will be required to be sure. > > Right now I am having the attached usbmon output where 2 back to back > snaps (x rays) were taken. This one has missed some initial part which is > present in the previous snaps (wireshark and usbmon) that I attached. > > The final image produced by windows software is probably not of much use > for the protocol for 1. It is compressed while the device returns raw. > Both snaps consistently show 3648832 bytes were returned as bulk out by > the device while the final images are around 1MB. 2. It adds additional > information such as patient name, date etc which is not really coming from > the device. So wireshark/usbmon may offer better clues than image produced > by the windows software. > > Will try and share the image over some time. -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Sane backend for an intraoral X ray camera
I don't see anything immediately obvious in the protocol, but we really need to see some scans. Even without the xray source we may learn something. But certainly the xray source, and the final image produced by the windows software will be required to be sure. allan On Sun, Dec 13, 2020 at 10:59 AM Mayuresh wrote: > > On Sun, Dec 13, 2020 at 09:39:03AM -0500, m. allan noah wrote: > > I think you have far more work to do than you realize.The first step > > would be to get some usb logs of the scanner in action using wireshark > > on windows. Someone here may recognize the image format or protocol. > > Yes, I have those with wireshark as well as usbmon (attached). These are > prior to actually getting the image (which requires going to a dental > clinic to get the device exposed to x ray, so might take some time). > > For wireshark following filter selects the device: > > usb.bus_id == 1 and usb.device_address == 6 > > usbmon has a limitation that it won't show more than 32 bytes per event. > > I am baffled by the difference in end-point numbers shown by wireshark and > usbmon. Those in usbmon match with lsusb, those in wireshark don't. > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Sane backend for an intraoral X ray camera
I'm not familiar with the pint interface, but I'd be surprised if it works generically with any twain scanner. How would the windows twain driver run on BSD without some kind of OS emulator? I think you have far more work to do than you realize.The first step would be to get some usb logs of the scanner in action using wireshark on windows. Someone here may recognize the image format or protocol. allan On Sun, Dec 13, 2020 at 9:10 AM Mayuresh wrote: > > I am trying to get sane work with a digital X ray device used for > dentistry described here [1] on Linux (Ubuntu 20.04) or on NetBSD 9.1. > > The device works only on Windows with proprietary software bundled with > the driver provided by the manufacturer. However [1] says "Allows for > direct acquisition with TWAIN compliant third party imaging software" > which gives a hope that it might work with sane on Linux / NetBSD. > > The device is detected by sane-find-scanner as: > found USB scanner (vendor=0x082b, product=0x000c) at libusb:001:009 > > I believe, TWAIN device requires pint backend > > In dll.conf I have mentioned pint and in pint.conf mentioned the device as > /dev/ugen0.0 on NetBSD (that's how it is detected), but scanimage -L > doesn't detect it. Or trying to use scanimage -d pint:/dev/ugen0.0 doesn't > work. > > On Ubuntu sane backends do not include pint and I might have to build from > sources. But before that thought of asking whether it has a chance of > working. Also, on Linux systems what path should be mentioned in pint.conf > - is it something like /dev/bus/usb/001/009 etc or something else? > > > [1] > https://de.slideshare.net/smokeypike/the-rvg-5200-from-carestream-dental-digital > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Pixma future
On Wed, Nov 25, 2020 at 2:01 AM Alexander Pevzner wrote: > > Obviously, this is better not to implement emulation of missed (in > hardware) features in the drivers, to avoid code duplication and having > an assortment of independent, often incompatible implementations of the > similar features. > Nonsense. You can have every driver implement a consistent level of features, and only have a single implementation of emulated functions. You just need a library like sanei_magic, which is already used by a number of existing backends to provide software deskew and autocrop functions. It would be pretty easy to do something similar for binarization. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu Scansnap ix500 stops after 2 pages
Several years ago, I had a bug report about buffermode problems with this scanner. it is possible that there are some hardware limitations here. You might see if buffermode works at lower resolutions like 100. High resolutions are generally slower, much more data is being collected. allan On Wed, Oct 28, 2020 at 8:17 AM Jens Wulf wrote: > > Am 27.10.2020 um 12:51 schrieb m. allan noah: > > If you stop using buffermode, does the problem also stop? > > > > allan > > yes, that helps, thank you for the hint. > I thought buffermode helped with the Speed-Problem, but it was the 300dpi > setting. > When changing this to 600dpi the scanner works really slow. > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu Scansnap ix500 stops after 2 pages
If you stop using buffermode, does the problem also stop? allan On Tue, Oct 27, 2020 at 7:45 AM Jens Wulf wrote: > > I tried to scan 3 pages with: > scanimage -b --format=tiff --mode Color --resolution 300dpi --source "ADF > Duplex" --buffermode On > I get: > Scanning page 1 > Scanned page 1. (scanner status = 5) > Scanning page 2 > Scanned page 2. (scanner status = 5) > Scanning page 3 > scanimage: sane_read: Error during device I/O > Scanned page 3. (scanner status = 9) > > The scanner stops after 2nd page and blinks orange until power off. > > Does anyone have a hint for me? > > Jens > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] sane 1.0.31 backend version not supported lineart. Why?...
On Thu, Sep 24, 2020 at 6:04 AM Wolfram Sang wrote: > > On Thu, Sep 24, 2020 at 11:59:39AM +0200, Ulf Zibis wrote: > > > > Am 24.09.20 um 11:45 schrieb Wolfram Sang: > > > > > > !458 explains some more: "The LINEART support within the backend is > > > implemented as a pure software filter. I think this should live in a > > > higher level and be reusable by all backends instead of being duplicated > > > within each backend." > > > > I agree, that having a gray->lineart filter in each backend is nonsense, > > but is there a possibility for such a filter in a intermediate layer? > > Well, I assumed the answer is 'no'. If it was 'yes', then the proper > path would be to first code it, convert the users, and only finally > delete the now obsolete stuff, no? > Agreed. Removing code that your users have come to rely on, without providing a replacement is bad form. In this case, this is a sort of expected feature for most scanners. I think it should not be provided by another layer, instead it could be a shared library that all backends can use. I wrote sanei_magic to provide software deskew and cropping algorithms to all backends, for just this reason. I've got a pretty good lineart function in the epjitsu backend, that I could move up to sanei_magic if other backends wanted to use it. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon DR-C225 II - black scan
I have just pushed v59 of the canon_dr backend up to our git repo. This is an updated version of the patch I shared previously. The calibration values are currently hard-coded for the C225, so the quality is poor. But, we can at least get duplex color scans now. I expect grayscale scans will segfault until I do some more work. allan On Thu, Jul 30, 2020 at 4:57 PM m. allan noah wrote: > > Marek et al- > > I've spent a couple evenings looking at all the various logs that I > have for the C225, and have discovered that it does a different type > of fine calibration from other models. So, I've worked up the attached > patch, against the current sane-backends sources. The idea is to > re-use some of the existing calibration code instead of writing a new > version just for this scanner. I expect this may not work, and if it > does, it will only give us poor quality images. But, it should be > enough to validate that the issue is caused by calibration. You will > need to apply this patch to sane-backends source, and > rebuild/reinstall. I don't have access to any Canon scanners at this > time, so I have only verified that this compiles, unfortunately. > > Let me know what you find out, or if you need help. > > allan > > On Thu, Jul 23, 2020 at 8:53 PM m. allan noah wrote: > > > > Marek, I'm sorry it has taken me a month to reply, life is a little > > 'different' these days :) > > > > So I have gone back through every email thread I have had about the > > DR-C225, and do have a set of logs from the windows driver. I will > > attempt to determine which bit of magic we are missing. It will take > > me some time, as I am travelling now. If you do not hear from me soon, > > please feel free to reach out. Also, if you want to study up on > > rebuilding sane-backends from source in the meantime, we will need it. > > > > allan > > > > On Fri, Jun 26, 2020 at 4:33 PM Marek wrote: > > > > > > Dear developers, > > > I wonder if you could help me with resolving a problem with Canon > > > DR-C225 II scanner (canon_dr backend). The output scan is all black. In > > > 2015 there was a thread on the predecessor of this scanner: DR-C225 > > > (without 'II'), which suffered from similar problem. Unfortunately that > > > thread seems to be prematurely abandoned without solving the issue. > > > I'm attaching a scanimage log for a page scanned in a grayscale mode (for > > > the color mode the output scan is black as well). > > > Best regards, > > > Marek > > > > > > > > -- > > "well, I stand up next to a mountain- and I chop it down with the edge > > of my hand" > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] SOLVED: Fujitsu fi5900c JPG compression fails with ADF Duplex
I have just pushed v137 of the fujitsu backend up to our git repo. This fixes the bug Wes reported with the fi-5900, and also includes some updated brightness/contrast code which should fix a bug with the iX1500. allan On Mon, Sep 21, 2020 at 3:02 PM Wes Rishel wrote: > > M. Allan Noah provided a patch for fujitsu.c in Sane 1.0.31 that solves this > problem. He has identified it as build#137 > > Thanks, Allan for the rapid response! > > -- Wes > > On Fri, Sep 18, 2020 at 12:07 PM Wes Rishel wrote: >> >> Apparently my including debug created a messae that is too large. >> >> This time, the debugging output is in an attached zip. >> >> >>> Working with 1.0.31. >>> scanimage -V >>> scanimage (sane-backends) 1.0.31; backend version 1.0.31 >>> >>> These work: >>> scanimage --mode color --source 'ADF Duplex' > x.jpg (produces a .pnm file) >>> scanimage --mode color --compression JPEG > x.jpg (produces a .jpg file) >>> >>> This produces a Segmntation fault/core dump: >>> scanimage --mode color --source 'ADF Duplex' --compression JPEG > x.jpg >>> >>> So does this: >>> scanimage --mode color --compression JPEG --source 'ADF Duplex' > x.jpg >>> >>> >>> Attached is the output runnng the failing options with SANE_DEBUG_FUJITSU=15 >>> -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] RESEND: Fujitsu fi5900c JPG compression fails with ADF Duplex
Wes, I'm going to need a more detailed log to figure this out. Also, there is no point in doing a command line redirection when doing a duplex scan, you will throw away the back page. SANE_DEBUG_FUJITSU=35 scanimage --resolution 100 --mode grayscale --source 'ADF Duplex' --compression JPEG --batch=out%d.jpg 2> 5900a.log If that doesn't demonstrate the error, you could try changing to color mode or increasing the resolution. I am trying to avoid that to keep the log size small. Then you will likely need to compress 5900a.log and send it to me directly. If it is too big, you will need to use something like dropbox to send it. allan On Fri, Sep 18, 2020 at 3:08 PM Wes Rishel wrote: > > Apparently my including debug created a messae that is too large. > > This time, the debugging output is in an attached zip. > > >> Working with 1.0.31. >> scanimage -V >> scanimage (sane-backends) 1.0.31; backend version 1.0.31 >> >> These work: >> scanimage --mode color --source 'ADF Duplex' > x.jpg (produces a .pnm file) >> scanimage --mode color --compression JPEG > x.jpg (produces a .jpg file) >> >> This produces a Segmntation fault/core dump: >> scanimage --mode color --source 'ADF Duplex' --compression JPEG > x.jpg >> >> So does this: >> scanimage --mode color --compression JPEG --source 'ADF Duplex' > x.jpg >> >> >> Attached is the output runnng the failing options with SANE_DEBUG_FUJITSU=15 >> -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon Canoscan 9000F customise document length
Download the source code, and start reading. On Mon, Aug 31, 2020 at 4:25 PM Michael Rose wrote: > > HI Allan, > > Thanks for your input. For my purposes I probably won't need to scan beyond > 40 inches. I use the scanimage frontend on the command line. Where can I > find information on how to modify the SANE backend for this model? If the > value for document length is somehow sent to the scanner before the scan then > I would like to be able to put in my own values for this. I think this way I > could discover what the firmware limit is. Do you know where can I find > information on how to modify the Canoscan 9000F backend driver or any > information related to modifying/enhancing SANE scanner drivers? Thanks. > > Mike > > ____ > From: m. allan noah > Sent: 31 August 2020 20:03 > To: Michael Rose > Cc: sane-devel@alioth-lists.debian.net > Subject: Re: [sane-devel] Canon Canoscan 9000F customise document length > > There is no reason to think that any particular scanner will support > that capability. Many of them get information about the total length > of the scan before they start, and there is a firmware limit to that > value. > > You will need a simplistic scanner that just streams data of an > indeterminate length until the host stops asking for data. > > allan > > On Mon, Aug 31, 2020 at 3:05 PM Michael Rose wrote: > > > > Hello everyone, > > > > I'm new here so please forgive me if I'm not doing things right. I was > > hoping someone could help me. I am trying to modify a Canonscan 9000F > > scanner so that I can scan A4 width documents of any length beyond 11.7 > > inches. I can modify the scanner enclosure and extend or replace the glass > > platter. I need help with modifying the sane backend driver. Does anyone > > know if this is possible? How would I go about doing this? I Any > > suggestions would be most welcome. Thanks. > > > > Mike > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon Canoscan 9000F customise document length
There is no reason to think that any particular scanner will support that capability. Many of them get information about the total length of the scan before they start, and there is a firmware limit to that value. You will need a simplistic scanner that just streams data of an indeterminate length until the host stops asking for data. allan On Mon, Aug 31, 2020 at 3:05 PM Michael Rose wrote: > > Hello everyone, > > I'm new here so please forgive me if I'm not doing things right. I was hoping > someone could help me. I am trying to modify a Canonscan 9000F scanner so > that I can scan A4 width documents of any length beyond 11.7 inches. I can > modify the scanner enclosure and extend or replace the glass platter. I need > help with modifying the sane backend driver. Does anyone know if this is > possible? How would I go about doing this? I Any suggestions would be most > welcome. Thanks. > > Mike -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Question SANE and Canon Scanner
"Unable to open device: Device busy"
do you have something else installed that is talking to the scanner?
like canon's scangear software, or a VM running another OS?
allan
On Tue, Aug 25, 2020 at 5:28 AM <2bfr...@posteo.de> wrote:
>
> Dear SANE team,
>
> thanks for a great FOSS project ! Can I bother you with a question, you
> are my last resort, I tried various forums;
> regarding the Cannon LiDE 300 Scanner. I bought it because it is listed
> as "completely supported" in the SANE list
> (http://www.sane-project.org/sane-mfgs.html#Z-CANON),
> but I can't get it to work. Here's what I tried:
>
> I am on Linux Mint 20 (Ubuntu 20.04 base), and the scanner is
> recognised:
>
> lsusb
> Bus 003 Device 004: ID 04a9:1913 Canon, Inc. LiDE 300
>
> scanimage -L
> device `pixma:04A91913' is a CANON CanoScan LiDE 300 multi-function
> peripheral
>
> sane-find-scanner
> found USB scanner (vendor=0x04a9 [Canon], product=0x1913 [LiDE 300]) at
> libusb:001:004
>
> I found out that it works with sane-pixma, provided by
> libsane-common_1.0.22-7ubuntu1_amd64 bug
> I have 1.0.29 installed, so it should be OK too? According to
> https://packages.debian.org/buster/amd64/libsane-dev/filelist
> it is provided by the libsane-dev package, so I tried
>
> sudo apt install libsane-dev
> still no result...
>
> simple scan output:
>
> simple-scan -d (debug mode)
> +9,45s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
> [+9,45s] DEBUG: scanner.vala:353: Device: name="pixma:04A91913"
> vendor="CANON" model="CanoScan LiDE 300" type="multi-function
> peripheral"
> [+9,45s] DEBUG: scanner.vala:353: Device:
> name="escl:http://127.0.0.1:6; vendor="ESCL" model="LiDE 300 HTTP"
> type="flatbed scanner"
> [+13,68s] DEBUG: simple-scan.vala:455: Requesting scan at 300 dpi from
> device 'pixma:04A91913'
> [+13,68s] DEBUG: scanner.vala:1676: Scanner.scan ("pixma:04A91913",
> dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
> paper_height=0, brightness=0, contrast=0, delay=3000ms)
> [+13,68s] DEBUG: scanner.vala:828: Processing request
> [+14,20s] DEBUG: scanner.vala:889: sane_open ("pixma:04A91913") ->
> SANE_STATUS_DEVICE_BUSY
> [+14,20s] WARNING: scanner.vala:893: Unable to open device: Device busy
>
> XSane says the same thing. Unable to open device: Device busy
>
> here's what dmesg said:
>
> dmesg
> 41353.742838] usb 1-3: new high-speed USB device number 5 using xhci_hcd
> [41353.804289] usb 1-3: New USB device found, idVendor=04a9,
> idProduct=1913, bcdDevice= 1.00
> [41353.804292] usb 1-3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [41353.804295] usb 1-3: Product: LiDE 300
> [41353.804297] usb 1-3: Manufacturer: Canon
> [41353.804298] usb 1-3: SerialNumber: 486D04
> [41353.864304] usb 1-3: usbfs: process 20985 (ippusbxd) did not claim
> interface 0 before use
> [41353.906525] audit: type=1400 audit(1598002277.392:90):
> apparmor="DENIED" operation="open" profile="ippusbxd"
> name="/etc/nsswitch.conf" pid=21004 comm="ippusbxd" requested_mask="r"
> denied_mask="r" fsuid=0 ouid=0
>
> I found in a forum that ippusbxd might be the problem, removed the
> package, but no result.
>
> I also manually added line in file /etc/sane.d/genesys.conf and
> /etc/sane.d/canon.conf
> # Canon LIDE 300
> usb 0x04a9 0x1913
>
> as well as in
> /lib/udev/rules.d/60-libsane.rules
> # Canon LIDE
> ATTRS{type}=="3", ATTRS{vendor}=="04a9", ATTRS{model}=="1913",
> ENV{libsane_matched}="yes"
>
> -
> I'm really sorry to use you as a hotline, but if there are any ideas, I
> would be grateful;
> All the Best
> Frank
>
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
[sane-devel] RIP, Russell Kirsch, inventor of the scanner
In 1957, Kirsch's group developed a digital image scanner and made the first digital scans, including an innovative multi-pass technique to manufacture grayscale data. He passed away August 11. https://en.wikipedia.org/wiki/Russell_Kirsch allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon DR-C225 II - black scan
Marek, I'm sorry it has taken me a month to reply, life is a little 'different' these days :) So I have gone back through every email thread I have had about the DR-C225, and do have a set of logs from the windows driver. I will attempt to determine which bit of magic we are missing. It will take me some time, as I am travelling now. If you do not hear from me soon, please feel free to reach out. Also, if you want to study up on rebuilding sane-backends from source in the meantime, we will need it. allan On Fri, Jun 26, 2020 at 4:33 PM Marek wrote: > > Dear developers, > I wonder if you could help me with resolving a problem with Canon > DR-C225 II scanner (canon_dr backend). The output scan is all black. In > 2015 there was a thread on the predecessor of this scanner: DR-C225 > (without 'II'), which suffered from similar problem. Unfortunately that > thread seems to be prematurely abandoned without solving the issue. > I'm attaching a scanimage log for a page scanned in a grayscale mode (for > the color mode the output scan is black as well). > Best regards, > Marek -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] SANE Color Management
I believe that most backends are doing no transformation at all. Since most backends are reverse engineered, I think we consider ourselves lucky just to get image data out of the scanner. If the blacks look black, and the whites look white, we ship it :) allan On Sun, Jul 5, 2020 at 10:38 AM Jürgen Mellinger wrote: > > Hi, > > many SANE backends provide gamma correction options, but I could not find any > information about the default color space in which scan data are being sent > to sane_read(). I mean, if there is no custom gamma table used, then a > backend should be able to use its knowledge about a scanner’s CCD’s gamma > value to transform it into a pre-defined color space, such as sRGB, or linear > gamma. If there is no such pre-defined color space, then each and every user > will have to determine the correct gamma for their each and every scanner, > and perform custom gamma correction just to obtain a reasonable image. > > From this I suspect that SANE backends indeed transform scanner data into a > standard color space. My experience with the genesys backend suggests that > it’s linear gamma. But I cannot find any documentation on this issue. > > Could someone point me to more information on this topic? > > Thank you, > Jürgen -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] ADF support in SANE API
On Sun, Jun 28, 2020 at 7:09 PM Alexander Pevzner wrote: > > So my question is: What can I do in order to monitor ADF status? Call > > sane_start() after setting an empty > > scan region, so the scan is done at the first call to sane_read()? This is > > obviously not an option, as in the > > case of a loaded feeder this would consume the first original rather than > > just read ADF status. > > Cancel the scan immediately after sane_start() using sane_cancel()? I have > > no idea whether this is possible. > > There are actually no such API that will return ADF status before actual > scan attempt. > This is not exactly true. Several sane backends present read-only options which report the status of various hardware sensors. Unfortunately, these options are generally inconsistent between backends. A few of them do have an option called "page-loaded", which should be used for this purpose. Look for SANE_NAME_PAGE_LOADED in the source, you will find them. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon Scanner DRG-2140 USB 3.0 on Red Hat Linux 6.7
The DR-G2140 is not yet supported by sane-backends. Perhaps you can
get a log and we can try to figure out what it needs. Many times, this
does not give us enough info, so we need to get a log of the Windows
driver in action instead. But for now, lets try sane. Please run the
following as root:
SANE_DEBUG_CANON_DR=35 scanimage -L 2> init.log
SANE_DEBUG_CANON_DR=35 scanimage --resolution=50 > scan.pnm 2> scan.log
allan
On Sun, Jun 14, 2020 at 11:58 PM Nomee via sane-devel
wrote:
>
> Hi Sane Team,
>
> I have been struggling with this error "no sane device found". Red hat
> workstation is not able to establish two way communication.
>
> Here is my configuration,
> I installed sane packages into Linux Workstation
> yum -y install sane-backends-1.0.24-100.el6.x86_64.rpm
> sane-backends-libs-1.0.24-100.el6.x86_64.rpm
> sane-backends-libs-1.0.24-100.el6.i386.rpm
>
> Added the following into /etc/sane.d/canon_dr.conf
>
> DRG-2140
> usb 0x1083 0x166e
> Added into /etc/udev.d/rules.d/50-wic.rules
>
> ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1083", MODE:="0666"
>
> I really appreciate the response.
>
> Thanks,
> Nomee.
>
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
Re: [sane-devel] Building backends on FreeBSD?
You set the BACKENDS env var after the call to configure. I don't think that works. On Thu, Apr 30, 2020 at 11:37 AM Torfinn Ingolfsen wrote: > > Ok, I remembered to look at the FreeBSD port, and check how things are > done there. Now I'm using this configure line: > tingo@kg-core1$ MAKE=gmake CPPFLAGS=-I/usr/local/include > LDFLAGS=-L/usr/local/lib ./configure --disable-locking > --enable-pthread --without-api-spec --without-systemd BACKENDS="epson2 > plustek" > > unfortunately, gmake still wants to build other backends (yes, I have > done 'gmake clean' first): > cc -DHAVE_CONFIG_H -I. -I../include/sane -D_REENTRANT > -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d > -DPATH_SANE_DATA_DIR=/usr/local/share > -DPATH_SANE_LOCK_DIR=/usr/local/var/lock/sane -DV_MAJOR=1 > -DV_MINOR=0 -I. -I. -I../include -I../include -I/usr/local/include > -Wall -Wextra -pedantic -g -O2 -MT ../backend/umax_pp_low.o -MD -MP > -MF $depbase.Tpo -c -o ../backend/umax_pp_low.o > ../backend/umax_pp_low.c &&\ > mv -f $depbase.Tpo $depbase.Po > ../backend/umax_pp_low.c:1174:4: error: use of undeclared identifier 'found' > found = 0; > ^ > ../backend/umax_pp_low.c:1175:4: error: use of undeclared identifier 'fd' > fd = open (name, O_RDONLY); > ^ > ../backend/umax_pp_low.c:1176:8: error: use of undeclared identifier 'fd' > if (fd < 0) > ^ > ../backend/umax_pp_low.c:1194:34: error: use of undeclared identifier 'fd' > sanei_umax_pp_setparport (fd); > ^ > 4 errors generated. > gmake[2]: *** [Makefile:656: ../backend/umax_pp_low.o] Error 1 > gmake[2]: Leaving directory '/zs/tingo/work/sane/backends/tools' > gmake[1]: *** [Makefile:480: all] Error 2 > gmake[1]: Leaving directory '/zs/tingo/work/sane/backends/tools' > gmake: *** [Makefile:590: all-recursive] Error 1 > not sure how to fix this, as the (FreeBSD port) patch for this backend > already is in the source file, as far as I can see. > > On Thu, Apr 30, 2020 at 4:36 PM Torfinn Ingolfsen wrote: > > > > So I'm trying to build master on FreeBSD. FreeBSD version is 11.3-stable: > > tingo@kg-core1$ uname -a > > FreeBSD kg-core1.kg4.no 11.3-STABLE FreeBSD 11.3-STABLE #2 r352605: > > Sun Sep 22 22:53:27 CEST 2019 > > r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > > > > I've checked out backends from git: > > tingo@kg-core1$ git log --oneline | head -1 > > 9aad35503 Merge branch 'update-epkowa-documentation' into 'master' > > > > I've done > > $ bash ./autogen.sh > > $ MAKE=gmake CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib > > ./configure > > > > but gmake fails: > > tingo@kg-core1$ gmake > > Making all in include > > gmake[1]: Entering directory '/zs/tingo/work/sane/backends/include' > > gmake[1]: Nothing to be done for 'all'. > > gmake[1]: Leaving directory '/zs/tingo/work/sane/backends/include' > > Making all in lib > > gmake[1]: Entering directory '/zs/tingo/work/sane/backends/lib' > > gmake[1]: Nothing to be done for 'all'. > > gmake[1]: Leaving directory '/zs/tingo/work/sane/backends/lib' > > Making all in sanei > > gmake[1]: Entering directory '/zs/tingo/work/sane/backends/sanei' > > gmake[1]: Nothing to be done for 'all'. > > gmake[1]: Leaving directory '/zs/tingo/work/sane/backends/sanei' > > Making all in backend > > gmake[1]: Entering directory '/zs/tingo/work/sane/backends/backend' > > gmake all-am > > gmake[2]: Entering directory '/zs/tingo/work/sane/backends/backend' > > /bin/sh ../libtool --silent --tag=CC --mode=compile cc > > -DHAVE_CONFIG_H -I. -I../include/sane > > -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d > > -DPATH_SANE_DATA_DIR=/usr/local/share > > -DPATH_SANE_LOCK_DIR=/usr/local/var/lock/sane -DV_MAJOR=1 > > -DV_MINOR=0 -I. -I. -I../include -I../include > > -DLIBDIR="\"/usr/local/lib/sane\"" -DBACKEND_NAME=epsonds > > -I/usr/local/include -Wall -Wextra -pedantic -g -O2 -MT > > libepsonds_la-epsonds.lo -MD -MP -MF .deps/libepsonds_la-epsonds.Tpo > > -c -o libepsonds_la-epsonds.lo `test -f 'epsonds.c' || echo > > './'`epsonds.c > > epsonds.c:240:4: warning: implicit declaration of function > > 'setsockopt' is invalid in C99 [-Wimplicit-function-declaration] > > setsockopt(s->fd, SOL_SOCKET, SO_RCVTIMEO, > > (char *), sizeof(tv)); > > ^ > > epsonds.c:240:22: error: use of undeclared identifier 'SOL_SOCKET' > > setsockopt(s->fd, SOL_SOCKET, SO_RCVTIMEO, > > (char *), sizeof(tv)); > > ^ > > epsonds.c:240:34: error: use of undeclared identifier 'SO_RCVTIMEO' > > setsockopt(s->fd, SOL_SOCKET, SO_RCVTIMEO, > > (char *), sizeof(tv)); > > ^ > > 1 warning and 2 errors generated. > > gmake[2]: *** [Makefile:4718: libepsonds_la-epsonds.lo] Error 1 > > gmake[2]: Leaving directory '/zs/tingo/work/sane/backends/backend' > > gmake[1]:
Re: [sane-devel] Fujitsu fi-6130: x-offset duplex
Interesting, but unrelated. allan On Sun, Mar 22, 2020 at 11:14 AM Ulf Zibis wrote: > > See also: > https://gitlab.com/utsushi/utsushi/issues/68 > https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1828638 > https://gitlab.com/sane-project/frontend/xsane/issues/1 > https://gitlab.gnome.org/GNOME/simple-scan/issues/103#note_510586 > > -Ulf > > Am 08.03.20 um 18:45 schrieb Max Voit: > > Dear all, > > > > I've been trying to duplex scan A4 paper with the fi-6130. Setting > > "page-size" and "page-width" accordingly was not sufficient. There is > > about 2mm empty (grey) space on the right hand side for the front page, > > on the left for the back. And the bottom is cut off by about 1cm. > > > > After some tweaking I've found a parameter set that works for > > the front page: > > > > scanimage --mode Color --resolution 300 \ > > --batch-count=2 --batch=%d.pnm --batch-start=0 \ > > --source "ADF Duplex" --buffermode On \ > > --page-width 212.5 -x 210 --page-height 299 -y 297 > > > > However, then the back side has about 4mm empty space on the > > left and is cut off on the right. > > > > Can you please give me some hints on how to best resolve this issue? > > > > Is there something similar to the duplex-offset option but in > > x-direction? > > > > Best regards, > > Max > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu fi-6130: x-offset duplex
I have enough docs at this point to figure out the required commands to write to the eeprom, but I agree that it is not something I'd implement as part of SANE. Perhaps a standalone program would be useful for someone who did not have a windows machine available. allan On Sat, Mar 21, 2020 at 9:49 AM Max Voit wrote: > > On Sun, 8 Mar 2020 21:42:40 -0400 > "m. allan noah" wrote: > > > Hmm, the X offset setting is controlled by the scanner itself. It is > > stored somewhere in the scanner firmware, but I'm not sure how we > > write to it. I can ask my contacts at Fujitsu for information. > > Thank you for your help, Allan. > > After hooking up a Windows machine, I realized that the Windows driver > also provides a "settings" page. There it's possible to set the offsets. > It says it's writing to eeprom, so the setting is persistently stored > in the device. Thus, after configuring the offsets from Windows, scan > results have correct offsets with sane as well. > > Unfortunately I was unable to aquire usb logs of the eeprom writing > procedure. I installed wireshark and pcap-usb, but it doesn't show a usb > capturing device. Hints on that would be appreciated. > > On the other hand I'm not sure whether writing to the eeprom is not out > of scope of sane? > > Best regards, > Max -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] AXIS 1650 support for Pixma backend - work in progress
I'm confused- are you proposing to add a new backend that lets pixma scanners work over this AXIS machine, but not other scanners? allan On Fri, Mar 20, 2020 at 2:58 PM Rolf Bensch wrote: > > Hi Ondrej, > > Many thanks for your message. > > Am 20.03.20 um 18:44 schrieb Ondrej Zary: > > Hello, > I have a Canon MF5730 MFP with external AXIS 1650 print server: > https://www.axis.com/techsup/prtsrv/axis_1650/index.htm > > I've reverse engineered the print data format and wrote CUPS driver couple of > years ago so printing works fine. > > Now it's time for scanning. Thanks to SANE and Pixma backend, scanning works > when connected directly using the USB port (except for the buttons). > > The scan mode of AXIS 1650 works as USB-over-TCP. > The Windows AXIS Scan Client discovers and identifies local scan-capable print > servers using a simple UDP-based WIMP protocol: > https://www.axis.com/techsup/prtsrv/axis_1650/technotes_1650.htm#2 > > Then it connects to the selected print server using TCP, locking it for the > current user, and creates a virtual USB device so the Canon driver could be > used to scan. > > I've based AXIS support for Pixma backend on the BJNP code. > What works: > - autodetection > - connect > - scan starts > What does not: > - data gets messed up somehow > - scan does not finish successfully > - set_timeout, interrupts not implemented > > > I just created a merge request here: > https://gitlab.com/sane-project/backends/-/merge_requests/361. > > Please check if your code still is working. I needed to fix some issues while > merging to recent master branch. > > Please follow the merge request and provide your fixes there. > > Hope this helps. > > Cheers, > Rolf > > > !361 > > > !361 -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon P215II
Thanks for the report. I've been unable to correct the calibration issues on these scanners in the past, as all the calibration code is reverse engineered. It would be helpful if someone else could pick it up and try to improve it. allan On Thu, Mar 19, 2020 at 10:58 AM Tony wrote: > > Hi all, I tried to test Canon P215II, backend version: 1.0.29. > > ./scanimage --format=png > test.png > > test.png is gray; > > ./scanimage --format=png --mode=Color > test.png > > test.png is color, but seems brightness high. The image looks like adjust > > brightness to max effect on Windows OS; > > ./scanimage --format=png --mode=Color --brightness=-100 > test.png > > test.png always like that, Maybe brightness option has no effect for now. > > And scan speed is slow. > > that's all. if you need more, just email me. I'll try to be the best tester. > :P > > kangear -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu fi-6130: x-offset duplex
Hmm, the X offset setting is controlled by the scanner itself. It is stored somewhere in the scanner firmware, but I'm not sure how we write to it. I can ask my contacts at Fujitsu for information. allan On Sun, Mar 8, 2020 at 2:02 PM Max Voit wrote: > > Dear all, > > I've been trying to duplex scan A4 paper with the fi-6130. Setting > "page-size" and "page-width" accordingly was not sufficient. There is > about 2mm empty (grey) space on the right hand side for the front page, > on the left for the back. And the bottom is cut off by about 1cm. > > After some tweaking I've found a parameter set that works for > the front page: > > scanimage --mode Color --resolution 300 \ > --batch-count=2 --batch=%d.pnm --batch-start=0 \ > --source "ADF Duplex" --buffermode On \ > --page-width 212.5 -x 210 --page-height 299 -y 297 > > However, then the back side has about 4mm empty space on the > left and is cut off on the right. > > Can you please give me some hints on how to best resolve this issue? > > Is there something similar to the duplex-offset option but in > x-direction? > > Best regards, > Max > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Canon Flatbed 101 Scanner
The flatbed unit has a Genesys chipset, and would need to be added to the Genesys backend. There was some debate about it being a GL846 or GL123 chipset, but I've heard nothing further in 8 years or so. On Wed, Mar 4, 2020 at 7:57 AM Ismet Bahadir wrote: > > Hi All, > > > > This is my first message to this group. I’m sorry if I’m writing to the wrong > group. > > > > We have two scanners we are trying to use on Linux Ubuntu 64 bit. These > scanners are: > > > > Canon Flatbed Scanner Unit 101 > Canon DR-M160 > > > > When we use DR model, it works on Ubuntu just fine and Sane recognizes the > scanner automatically. However, we can’t make Flatbed work no matter how hard > we tried. There is no corresponding driver for 64 bit Linux and we can’t get > it work. > > > > We need help and I thought this group might help us. Is there any way to get > this scanner work? > > > > Best Regards -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Brother MFC-L2750DW sane backend ?
If it is not connected to a USB port, lsusb cannot find it...
allan
On Tue, Mar 3, 2020 at 6:55 AM Richard Stein wrote:
>
> I seek information that I can apply to identify my brother
> printer/scanner. When I use lsusb on UBUNTU 18.04.1, I obtain this
> output. Where's the scanner device? It is connected to a WiFi interface.
> I require the productID, I think.
>
> root@rmsbox:/lib/udev/hwdb.d# lsusb
> Bus 002 Device 003: ID 0a5c:21e1 Broadcom Corp. HP Portable SoftSailing
> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 04f2:b230 Chicony Electronics Co., Ltd Integrated
> HP HD Webcam
> Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> I added this text to /lib/udev/rules.d/60-libsane1.rules:
> # Brother scanners
> ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"
> LABEL="libsane_rules_end"
>
> However, the device is not recognized. Kindly advise. Thx.
> --
> Richard M. Stein
> rmst...@ieee.org
>
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
Re: [sane-devel] Fujitsu Backend
Yes, I mistyped- the backend should auto detect the need for LUT on the ix1500 too. I'll note that your example command lines have weird emdashes before the contrast and brightness, not a proper double dash. Any chance that is related? If not, can you get a debug log like so: SANE_DEBUG_FUJITSU=35 scanimage --mode=gray --contrast=20 --brightness=20 --format=tiff --ald=yes --device-name=fujitsu:ScanSnap\ iX1500:94839 --resolution=200 --batch=Scan-Designer-TAWS27-144246-%d.tif 2>ix1500.log then compress ix1500.log and send it to me directly? allan On Fri, Feb 14, 2020 at 4:53 PM Tom Buckler wrote: > It's with the ix1500's not 500. I also have an ix100 that works fine. > > So for example > > /usr/local/bin/scanimage --mode=gray —contrast=20 —brightness=20 > --format=tiff --ald=yes --device-name=fujitsu:ScanSnap\ > iX1500:94839 --resolution=200 --batch=Scan-Designer-TAWS27-144246-%d.tif > > Looks exactly the same as > > /usr/local/bin/scanimage --mode=gray —contrast=-40 —brightness=0 > --format=tiff --ald=yes --device-name=fujitsu:ScanSnap\ > iX1500:94839 --resolution=200 --batch=Scan-Designer-TAWS27-144246-%d.tif > > > Note this is with 1.0.28, where I've added this model to fujitsu.conf. > > Tom > > > -- > *Tom Buckler* | Buckler Microelectronics Inc. > 17008 - 90 Avenue NW | Suite 272 | Edmonton | AB | Canada | T5T 1L6 > *Cell:* (780) 499-5525 > > -- > > > > > On Feb 12, 2020, at 6:23 PM, m. allan noah wrote: > > actually, we are able to detect that LUT is needed, and that should be > working for the ix500. Can you give a few example command lines with > scanimage that demonstrate the problem? > > allan > > On Wed, Feb 12, 2020 at 4:02 PM m. allan noah wrote: > >> Some fujitsu machines have native brightness/contrast support, others >> require that a LUT be calculated by the backend and uploaded. I don't think >> there is a way to detect which is needed. I will investigate further. >> >> allan >> >> On Wed, Feb 12, 2020 at 1:32 PM Tom Buckler wrote: >> >>> Hi Allan, >>> >>> Do you know if the iX1500 should respond to —contrast and —brightness ? >>> I'm not getting any change with those parameters, and no details in the >>> manpage. —resolution —mode —ald work just fine… >>> >>> Thx, >>> Tom >>> >>> >>> >>> >>> -- >>> *Tom Buckler* | Buckler Microelectronics Inc. >>> 17008 - 90 Avenue NW | Suite 272 | Edmonton | AB | Canada | T5T 1L6 >>> *Cell:* (780) 499-5525 >>> -- >>> >>> >>> >>> >>> On Feb 11, 2020, at 9:33 AM, m. allan noah wrote: >>> >>> Which scanner are you using? >>> >>> allan (fujitsu backend author) >>> >>> On Tue, Feb 11, 2020 at 11:31 AM Tom Buckler wrote: >>> >>> >>> Thanks Allan, >>> >>> I'm not sure how to deal with that, as libusb-dev isn't a separate >>> package from libusb as far as I know. But I seem to have gotten past that >>> with pkg-config as per Olaf's suggestion previous. >>> >>> >>> Cheers, >>> Tom >>> >>> >>> >>> Tom Buckler | Buckler Microelectronics Inc. >>> 17008 - 90 Avenue NW | Suite 272 | Edmonton | AB | Canada | T5T 1L6 >>> Cell: (780) 499-5525 >>> >>> >>> >>> >>> >>> On Feb 11, 2020, at 6:41 AM, m. allan noah wrote: >>> >>> Do you have the header files for libusb installed? On other platforms >>> this would come from a package called libusb-dev or libusb-devel. >>> >>> allan >>> >>> On Tue, Feb 11, 2020 at 3:00 AM Olaf Meeuwissen >>> wrote: >>> >>> >>> Hi Tom, >>> >>> Tom Buckler writes: >>> >>> Hello, >>> >>> I am wanting to install a new instance of sane on OSX: >>> >>> When I go to >>> $ ./configure BACKENDS="fujitsu" >>> I get >>> *** Warning: sane-backends will be built without USB support. There may >>> >>> Yet libusb is installed via homebrew: >>> taws27 on TAWS27: /usr/local/lib$ ls -l libusb* >>> lrwxr-xr-x 1 taws27 admin 46 10 Feb 23:16 libusb-1.0.0.dylib -> >>> ../Cellar/libusb/1.0.23/lib/libusb-1.0.0.dylib >>> lrwxr-xr-x 1 taws27 admin 40 10 Feb 23:16 libusb-1.0.a -> >&g
Re: [sane-devel] Using "scanimage" under Gentoo
Did you compress the file? allan On Fri, Feb 14, 2020 at 11:32 AM Dr Rainer Woitok wrote: > > Olaf, > > On Friday, 2020-02-14 14:28:16 +0100, I myself wrote: > > > ... > > I've compressed the debug output from tests 1 and 3, but the files are > > still huge: > > > >$ ls -l *.bz2 > >-rw--- 1 rainer rainer 28659462 2020-02-14 13:35 paperjam.log.bz2 > >-rw--- 1 rainer rainer 56919612 2020-02-14 13:37 success.log.bz2 > >$ > > > > As per your suggestions I'll send these files in two separate mails as > > attachments to both, yourself and the list and will leave it to the list > > moderator to decide. > > No joy: "Sending failed", even with the smaller file :-( > > So I bit the bullet and created just another account in order to submit > an issue. Again in vain: "File is too big (27.33MiB). Max filesize: > 10MiB". > > What's next? Reduce the value of "SANE_DEBUG_BJNP"? But I can't guar- > antee I can reproduce this particular behaviour. > > And I'm pretty sure I don't want to create just another account with > "pastebin" or some such site :-\ > > Sincerely, > Rainer > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Fujitsu Backend
Some fujitsu machines have native brightness/contrast support, others require that a LUT be calculated by the backend and uploaded. I don't think there is a way to detect which is needed. I will investigate further. allan On Wed, Feb 12, 2020 at 1:32 PM Tom Buckler wrote: > Hi Allan, > > Do you know if the iX1500 should respond to —contrast and —brightness ? > I'm not getting any change with those parameters, and no details in the > manpage. —resolution —mode —ald work just fine… > > Thx, > Tom > > > > -- > *Tom Buckler* | Buckler Microelectronics Inc. > 17008 - 90 Avenue NW | Suite 272 | Edmonton | AB | Canada | T5T 1L6 > *Cell:* (780) 499-5525 > ------ > > > > > On Feb 11, 2020, at 9:33 AM, m. allan noah wrote: > > Which scanner are you using? > > allan (fujitsu backend author) > > On Tue, Feb 11, 2020 at 11:31 AM Tom Buckler wrote: > > > Thanks Allan, > > I'm not sure how to deal with that, as libusb-dev isn't a separate package > from libusb as far as I know. But I seem to have gotten past that with > pkg-config as per Olaf's suggestion previous. > > > Cheers, > Tom > > > > Tom Buckler | Buckler Microelectronics Inc. > 17008 - 90 Avenue NW | Suite 272 | Edmonton | AB | Canada | T5T 1L6 > Cell: (780) 499-5525 > > > > > > On Feb 11, 2020, at 6:41 AM, m. allan noah wrote: > > Do you have the header files for libusb installed? On other platforms > this would come from a package called libusb-dev or libusb-devel. > > allan > > On Tue, Feb 11, 2020 at 3:00 AM Olaf Meeuwissen > wrote: > > > Hi Tom, > > Tom Buckler writes: > > Hello, > > I am wanting to install a new instance of sane on OSX: > > When I go to > $ ./configure BACKENDS="fujitsu" > I get > *** Warning: sane-backends will be built without USB support. There may > > Yet libusb is installed via homebrew: > taws27 on TAWS27: /usr/local/lib$ ls -l libusb* > lrwxr-xr-x 1 taws27 admin 46 10 Feb 23:16 libusb-1.0.0.dylib -> > ../Cellar/libusb/1.0.23/lib/libusb-1.0.0.dylib > lrwxr-xr-x 1 taws27 admin 40 10 Feb 23:16 libusb-1.0.a -> > ../Cellar/libusb/1.0.23/lib/libusb-1.0.a > lrwxr-xr-x 1 taws27 admin 44 10 Feb 23:16 libusb-1.0.dylib -> > ../Cellar/libusb/1.0.23/lib/libusb-1.0.dylib > > Thoughts appreciated, > > > Please run `./configure --with-usb BACKENDS=fujitsu` and send the > `config.log` file to the list. You may want to compress the file > as large messages end up in the moderator queue. > > That is not a problem per se, but it slows down communication. > > Even when compressed, the message may be too large. > > Alternatively, you could create an issue for this at > > https://gitlab.com/sane-project/backends/issues/new > > I don't have access to any MacOS systems, so can only really debug > this via that log file. > > That said, do you have `pkg-config` installed? If not, that is most > likely why libusb is not detected. > > Apologies but we don't see many MacOS folks around here so our build > instructions may be lacking a bit for that OS. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" > > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] libusb not available
Do you have the header files for libusb installed? On other platforms this would come from a package called libusb-dev or libusb-devel. allan On Tue, Feb 11, 2020 at 3:00 AM Olaf Meeuwissen wrote: > > Hi Tom, > > Tom Buckler writes: > > > Hello, > > > > I am wanting to install a new instance of sane on OSX: > > > > When I go to > > $ ./configure BACKENDS="fujitsu" > > I get > > *** Warning: sane-backends will be built without USB support. There may > > > > Yet libusb is installed via homebrew: > > taws27 on TAWS27: /usr/local/lib$ ls -l libusb* > > lrwxr-xr-x 1 taws27 admin 46 10 Feb 23:16 libusb-1.0.0.dylib -> > > ../Cellar/libusb/1.0.23/lib/libusb-1.0.0.dylib > > lrwxr-xr-x 1 taws27 admin 40 10 Feb 23:16 libusb-1.0.a -> > > ../Cellar/libusb/1.0.23/lib/libusb-1.0.a > > lrwxr-xr-x 1 taws27 admin 44 10 Feb 23:16 libusb-1.0.dylib -> > > ../Cellar/libusb/1.0.23/lib/libusb-1.0.dylib > > > > Thoughts appreciated, > > Please run `./configure --with-usb BACKENDS=fujitsu` and send the > `config.log` file to the list. You may want to compress the file > as large messages end up in the moderator queue. > > That is not a problem per se, but it slows down communication. > > Even when compressed, the message may be too large. > > Alternatively, you could create an issue for this at > > https://gitlab.com/sane-project/backends/issues/new > > I don't have access to any MacOS systems, so can only really debug > this via that log file. > > That said, do you have `pkg-config` installed? If not, that is most > likely why libusb is not detected. > > Apologies but we don't see many MacOS folks around here so our build > instructions may be lacking a bit for that OS. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] [janitorial] Code Freeze for 1.0.29 heads up
Hmm, this is a fresh install of Fedora 31. I am no longer able to
reproduce the issue, but have done OS updates in the meantime.
I'll note that the debian build you linked to does not even have
libusb installed (along with tiff/jpeg, etc), so I wonder how much
code is not being built in that case?
allan
On Mon, Jan 27, 2020 at 6:11 AM Olaf Meeuwissen
wrote:
>
> Hi Allan,
>
> m. allan noah writes:
>
> > I noticed that it is not possible to build sane-backends without
> > libtiff installed, because hp3900 backend requires it, but configure
> > does not check for it. This patch seems to fix:
>
> Thanks for noticing and the patch but our CI has been running builds
> without libtiff installed since the very beginning. The latest such
> build for release/1.0.29 is at
>
> https://gitlab.com/sane-project/backends/-/jobs/408050891
>
> Checking the hp3900 source code shows that all TIFF functionality is
> predicated on HAVE_TIFFIO_H. The sane_cv_use_libtiff variable is
> set based on the presence of tiffio.h *and* a TIFFFdOpen function in
> libtiff, though. Would you happen to compile on a system with the
> header file present and no library with TIFFFdOpen by any chance?
>
> # BTW, TIFF seems to be used only by debugging related functionality in
> # the hp3900 backend.
>
> Can you provide the config.log and config.status files for the build
> where you run into this? What distribution/version is this on? What
> are the TIFF related packages that are installed?
>
> > diff --git a/acinclude.m4 b/acinclude.m4
> > index 7c90c64f..f0d7d295 100644
> > --- a/acinclude.m4
> > +++ b/acinclude.m4
> > @@ -598,6 +598,13 @@ for be in ${BACKENDS}; do
> > fi
> > ;;
> >
> > +hp3900)
> > +if test "${sane_cv_use_libtiff}" != "yes"; then
> > + echo "*** $be backend requires TIFF library - $DISABLE_MSG"
> > + backend_supported="no"
> > +fi
> > +;;
> > +
> > dell1600n_net)
> > if test "${sane_cv_use_libjpeg}" != "yes" || test
> > "${sane_cv_use_libtiff}" != "yes"; then
> >echo "*** $be backend requires JPEG and TIFF library - $DISABLE_MSG"
>
> While I agree that applying this patch is a probably a good idea, there
> is something inconsistent in the checking that I'd like to fix as well.
>
> # The TIFF library check was added for the dell1600n_net backend. It
> # may be that the hp3900 backend's link flags picks up a library from
> # one check and activates code based on another check (which happens to
> # be *duplicated* by the library check).
>
> > On Sun, Jan 26, 2020 at 7:02 AM Olaf Meeuwissen
> > wrote:
> >>
> >> Hi all,
> >>
> >> Olaf Meeuwissen writes:
> >>
> >> > Hi all,
> >> >
> >> > Just so you all don't forget ;-)
> >> >
> >> > On 2020-01-26 around 12:00UTC, we'll be entering Code Freeze. This only
> >> > affects the release/1.0.29 branch. The master branch is still open for
> >> > code changes, new features, bug fixes and what not.
> >>
> >> We're past that point in time now and the release/1.0.29 branch is in
> >> Code Freeze. As per milestone[1] description, only "fixes for hardware
> >> destroying bugs, compile failures, fixing completely unusable backends
> >> and documentation fixes are allowed" now.
> >>
> >> [1]: https://gitlab.com/sane-project/backends/-/milestones/3
> >>
> >> [...snip...]
>
> Seeing that this is a compile failure, I'm inclined to include it in the
> upcoming 1.0.29 on the condition that I understand what's going on with
> your build.
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
> Support Free Softwarehttps://my.fsf.org/donate
> Join the Free Software Foundation https://my.fsf.org/join
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
Re: [sane-devel] Help
Thomas was subscribed using a different email address, which I have removed from sane-devel. allan On Sun, Jan 26, 2020 at 6:03 AM Thomas Escher wrote: > > Hi Olaf, > > yes indeed, but however it does not work for me. I think, actually I'm still > getting the issue-mails. > > Can you please disable my subscription completely? > > Thanks, Tom > > > > Von meinem Samsung Galaxy Smartphone gesendet. > > > > Ursprüngliche Nachricht > Von: Olaf Meeuwissen > Datum: 26.01.20 10:01 (GMT+01:00) > An: Thomas Escher > Cc: sane-devel@alioth-lists.debian.net > Betreff: Re: [sane-devel] Help > > Hi Thomas, > > Thomas Escher writes: > > > Help, please remove me from All subscriptions. > > Thanks > > Have you tried any of the unsubscribe instructions you quoted below? > > > [... snip ...] > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel > > or, via email, send a message with subject or body 'help' to > > sane-devel-requ...@alioth-lists.debian.net > > > > You can reach the person managing the list at > > sane-devel-ow...@alioth-lists.debian.net > > > > [...snip...] > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Converting Raw Image Data to PNG
Please note that the image could be truly raw data from the scanners read heads, not like the 'raw' files produced by cameras, which typically contain lots of meta information about the camera and the image. The data you get could be scrambled, interlaced, interleaved, inverted and uncorrected, and (unless it is JPEG) will contain no header at all. Fortunately, you can open such a file with a good text editor, and add a PNM header, then tweak the header until you start to see an image form. The latter part of this presentation I gave a few years ago shows the process I use: https://www.youtube.com/watch?v=pJ60vVOKVr0 allan On Fri, Jan 10, 2020 at 11:05 AM Chris Moller wrote: > > ufraw and dcraw will handle that conversion. > > On 10/01/2020 00:09, dan...@pixelgrease.co wrote: > > Hello, > > I have been trying to get a device running for a few weeks now. After failing > to build a backend I decided to hack together my own LibUSB driver for my > unsupported A8 scanner, given my use case is pretty simple I went in with a > "how hard can it be?" attitude. > > Great success so far. Hasn't been easy but it hasn't been really that bad. I > have managed to ask my tiny A8 feed scanner to scan a 300dpi colour image. I > have been able to save the data to a file (about 8mb worth) but that's where > the fun ends. > > Can't seem to figure out how to get that raw data into a usable format. 2 > questions: > > 1. What format is that raw data likely to be? I naively expected it to be png. > 2. Does SANE have some code that handles that sort of conversion I could have > a look at? Looked around the internet and the SANE docs. Read some things > about frames, but couldn't find much else. > > THANK YOU! > > Daniel > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: [sane-devel] Database of scanners with CCD tech?
Many (most) flatbed scanners are CIS now. ADF machines are more likely to be CCD. CCD tends to be more expensive, and the carriage has to be thicker and heavier to hold the fold mirrors, etc. So cost tends to be a good indicator as well. allan On Tue, Dec 31, 2019 at 3:26 AM 2600den...@gmail.com <2600den...@gmail.com> wrote: > > Hey SANE developers and users, > > Does anybody know of a database of scanners of various manufacturers > which lists their as-full-as-possible specs? I am trying to find a > secondhand (or new) flatbed scanner to use with SANE that is CCD-based > and hopefully has a greater depth-of-field and speed than my current one > but it's tricky to search for such a device especially given that it > would likely be a non-current model. > > Does any such database exist? Does any manufacturer provide combined > spec lists for their models going back say the past 10 years? Anybody > have suggestions for models they've found good in this arena? > > Thanks in advance to anybody who can help me with this project, > > Alex > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
[sane-devel] test message, please ignore 2
-- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
[sane-devel] test message, please ignore
-- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: Missing list subject header
On Thu, Sep 12, 2019 at 4:36 AM Jonathan Buzzard wrote: > > On Wed, 2019-09-11 at 16:37 -0400, m. allan noah wrote: > > Probably not, as this seems to cause problems with sending mail to > > yahoo and gmail users because of DMARC policy checking. > > > > This significant change (because it is going to break a large number of > subscribers filtering) should have been announced to the list not > silently implemented. Housefires and wars are significant. This is just a change to an email subject line :) But otherwise, I agree with you, I should have announced this particular change more widely. I'm going to turn the feature back on now, and we can see if posts from Yahoo email addresses cause all our gmail subscribers to be unsubscribed, again. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: Missing list subject header
Well, I changed a few different settings at the same time, to stop the mass unsubscribes quickly. I could do a binary search, and turn the subject line manipulation back on. If that causes a problem, I'll revert the change. allan On Wed, Sep 11, 2019 at 5:40 PM Ulf Zibis wrote: > > So bad :-( > > I'm subscribed to many lists, which all have such tags in the subject > line.. So I'm wondering why only [sane-devel] has this problem. > > -Ulf > > Am 11.09.19 um 22:37 schrieb m. allan noah: > > Probably not, as this seems to cause problems with sending mail to > > yahoo and gmail users because of DMARC policy checking. > > > > allan > > > > On Wed, Sep 11, 2019 at 4:16 PM Ulf Zibis wrote: > >> Hi, > >> > >> since some days, the header [sane-devel] is no more in the subject line > >> of the list messages. > >> > >> Is there a chance, that it will come back? > >> > >> -Ulf > >> > >> -- > >> Von meinem Seibert gesendet > >> > >> > > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: Missing list subject header
Probably not, as this seems to cause problems with sending mail to yahoo and gmail users because of DMARC policy checking. allan On Wed, Sep 11, 2019 at 4:16 PM Ulf Zibis wrote: > > Hi, > > since some days, the header [sane-devel] is no more in the subject line > of the list messages. > > Is there a chance, that it will come back? > > -Ulf > > -- > Von meinem Seibert gesendet > > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: License pop-up
Ha! I happen to work with the guy who filed that bug report. He's no longer particularly interested, but I agree with his original assessment. We should remove the popup, it is silly. allan On Sun, Sep 8, 2019 at 1:43 PM Ralph Little wrote: > > Hi, > Regarding my previous posting on this, I found the original, at times > heated, discussion at Debian: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=132679 > > Oliver actual took part in that discussion and expressed his preference > that the click-through license remain. > However, they decided to remove it in Debian. > > I'm not sure that I am in a position to decide on this regarding whether > or not to apply the patch and remove it for all. > Oliver had some very specific reasons for leaving it in. > > If anyone would like to weigh in on this issue, then I would be happy to > listen to arguments. > > For me, I'm happy to leave it as-is for the moment. > > Cheers, > Ralph > -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
Re: Recent mass unsubscribes from sane-devel
We just had another round of this, so I flipped a few buttons in our mailman config. Perhaps the next time Ralph sends an email, we won't get the boot :) allan On Tue, Aug 13, 2019 at 6:56 AM m. allan noah wrote: > > Recently, some of you (particularly gmail users) got unsubscribed from > this mailing list. This seems to be caused by emails from yahoo.co.uk > users coming to this list, which gmail refuses to accept. It is > possible that our list configuration may manipulate the messages > enough to break DMARC checking. I'll be playing with the list config a > bit over the next few days, to try to fix this. > > So, sorry in advance for the noise this generates. > > allan > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
[sane-devel] Recent mass unsubscribes from sane-devel
Recently, some of you (particularly gmail users) got unsubscribed from this mailing list. This seems to be caused by emails from yahoo.co.uk users coming to this list, which gmail refuses to accept. It is possible that our list configuration may manipulate the messages enough to break DMARC checking. I'll be playing with the list config a bit over the next few days, to try to fix this. So, sorry in advance for the noise this generates. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
