[sane-devel] Fwd: Help Please with Nikon Super Coolscan 4000 ED

[Bob Louden]

Please see forwarded note -- I sent it before subscribing to the SANE
mailing list - and so am resending.

Thanks,

   Bob


-- Forwarded message --
From: Bob Louden 
Date: Tue, Mar 6, 2018 at 5:34 PM
Subject: Help Please with Nikon Super Coolscan 4000 ED
To: sane-devel@lists.alioth.debian.org


Dear mailing list.  Please excuse me if I am not using this mailing list
properly.

I created a request for help a few days ago in the Linux Mint Hardware
forum but have not had any luck with responses.

I have this very nice, albeit old, scanner that I cannot get to work --
though I feel like I am very close to having it work.  Alas, I am on the
brink of giving up on it.  I also have this not-as-good Plustek scanner
that I've started messing with and it was from searching for help with it
that I found your mailing list.

Anyway, if there is anyone out there who might be able to help me, here is
a link to my Linux Mint forum post:  https://forums.
linuxmint.com/viewtopic.php?f=51=264978

Please feel free to respond to me via either email or in the forum.

Thank you.

 Bob



-- 

https://www.google.com/+BobLouden


“Simple can be harder than complex: You have to work hard to get your
thinking clean to make it simple. But it’s worth it in the end because once
you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25,
1998 ]



-- 

https://www.google.com/+BobLouden


“Simple can be harder than complex: You have to work hard to get your
thinking clean to make it simple. But it’s worth it in the end because once
you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25,
1998 ]
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] HP5590 and scanbd button recognition

[Wilhelm Meier]

Please try the old scanbuttond-backend for this type of scanner - it
should work. The HP sane backend sadly doesn't support the buttons on
this scanner.

Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>>
>> Main question: does the HP 5590 support button presses or am I just setting 
>> this up incorrectly?
>>
>> I'm been successful using scanbd with SANE backends to get scanning working 
>> over my network and locally on the host machine, but I can't seem to get it 
>> to recognize button presses, either running scanbd in foreground or 
>> background.
>>
>> For past testing, it seems that actions defined in scanbd.conf are used to 
>> tie to the backend options? From searching /var/log/syslog, I expected to 
>> track button presses or get some sort of trigger feedback, and I didn't 
>> think I needed an action set up for it.
>>
>> Any help on this one would be much appreciated. Thanks.
>>
>> Jared H
>>
> 
> After a bit more research, it looks like doing this with the SANE backend for 
> HP 5590 is not possible. scanbd is used to tie custom actions to the options 
> available on the scanner. In this case, none of the 10 options seem to return 
> values. They all look to be ones that I designate from some client software.
> 
> scanbd: found active option[1] tl-x (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[2] tl-y (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[3] br-x (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[4] br-y (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[5] mode (type: 3) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[6] source (type: 3) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[7] resolution (type: 1) for device 
> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
> (type: 0) for device hp5590:libusb:001:008 
> scanbd: found active option[9] wait-for-button (type: 0) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[10] preview (type: 0) for device 
> hp5590:libusb:001:008
> 
> In this case, it looks like I will have to try the old scanbuttond backends 
> for this, or see if there are optional enhancements for the SANE hp5590 
> backend.
> 
> Jared
> 


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] HP5590 and scanbd button recognition

[Jared Hedegaard]

> 
> Main question: does the HP 5590 support button presses or am I just setting 
> this up incorrectly?
> 
> I'm been successful using scanbd with SANE backends to get scanning working 
> over my network and locally on the host machine, but I can't seem to get it 
> to recognize button presses, either running scanbd in foreground or 
> background.
> 
> For past testing, it seems that actions defined in scanbd.conf are used to 
> tie to the backend options? From searching /var/log/syslog, I expected to 
> track button presses or get some sort of trigger feedback, and I didn't think 
> I needed an action set up for it.
> 
> Any help on this one would be much appreciated. Thanks.
> 
> Jared H
> 

After a bit more research, it looks like doing this with the SANE backend for 
HP 5590 is not possible. scanbd is used to tie custom actions to the options 
available on the scanner. In this case, none of the 10 options seem to return 
values. They all look to be ones that I designate from some client software.

scanbd: found active option[1] tl-x (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[2] tl-y (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[3] br-x (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[4] br-y (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[5] mode (type: 3) for device hp5590:libusb:001:008 
scanbd: found active option[6] source (type: 3) for device 
hp5590:libusb:001:008 
scanbd: found active option[7] resolution (type: 1) for device 
hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout (type: 
0) for device hp5590:libusb:001:008 
scanbd: found active option[9] wait-for-button (type: 0) for device 
hp5590:libusb:001:008 
scanbd: found active option[10] preview (type: 0) for device 
hp5590:libusb:001:008

In this case, it looks like I will have to try the old scanbuttond backends for 
this, or see if there are optional enhancements for the SANE hp5590 backend.

Jared

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] daily git snapshots

[Olaf Meeuwissen]

Hi Rolf,

Rolf Bensch writes:

> Hi Olaf
>
> Am 04.03.2018 um 02:52 schrieb Olaf Meeuwissen:
>> ...
>>
>> Sorry about that.  Should be fixed now.
>
> The last file on the website is from 28-Feb-2018 00:05

Should be fixed now.  Looks like something is wrong with the changes I
made to the script and/or permission issues with me running the script
manually and Allan's cron job running it.  Will have a look.

>> # Not quite sure why that happened but I suspect I made a mistake with
>> # the ln command.  It doesn't seem to be caused by the update-htdocs.sh
>> # script.  IIUC, that script runs daily.
>>
>> Anyway, given the (in)frequency with which our repositories are pushed
>> to I wonder if it makes sense to drop the daily git snapshots in favour
>> of the source tarballs created by our CI setup on every push.
>>
>> # Sometimes weeks go by without a commit ;-)
>>
>> The git snapshots are *not* the same as the source tarballs.  The former
>> are the result of
>>
>>   git archive --format=tar --prefix=sane-backends-$(date +%Y%m%d) master
>>
>> whereas the latter are the result of
>>
>>   make dist
>
> This is exactly what I need.

If that's the case, you may want to take a look at changing the URL you
fetch your source tarballs from.  The details[1] are on GitLab, but you
basically want to grab

 
https://gitlab.com/sane-project/$project/builds/artifacts/master/download?job=archive

and use the sane-$project-*.tar.gz that's in the zip'd archive that that
URL provides.  This works for $project values of backends and frontends.
There may be other files in the zip'd archive but those are intended for
the website so you can safely ignore those.

 [1]: https://docs.gitlab.com/ce/user/project/pipelines/job_artifacts.html

You can also take a peek at

 alioth.debian.org:/home/groups/sane/bin/make-git-snapshots.sh

which does something similar for the Alioth hosted website.

>> So the latter are equivalent to what we eventually release.
>>
>> How easy/hard would it be to change things on your end to use the CI
>> source tarballs?  Should I submit an issue for that on GitLab?
>>
>> ...
>
> On my point of view, daily git snapshots without any changes make no sense.

That's exactly why I asked.  We now have CI builds with every push.
These are guaranteed to have a change.  It doesn't really matter how
often they happen, once a month or every five minutes ;-)
A new source tarball will be created for *every* push unless the build
fails.  Even so, the last successfull source tarball will be available
from the URL above.

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

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org