Hi Ralph,
> I won't get chance until Wednesday to deal with this further, so please
> bear with me as it is the first time trying to do this.
No worries from my side. Thanks a lot for doing this!
I just created a MR with some documentation updates. Would be nice to
have them in the release but
Hi,
> 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
Thanks for the heads up. I'll try to get as much as possible of the
pending epson2 stuff done until Sunday.
Happy hacking,
Wolfram
Hi,
> 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.
Yep, I am/was using this one.
> I think the new model is Epson Expression 13000XL (probably the
> overseas
> Any objections?
More the opposite, I am all for it!
signature.asc
Description: PGP signature
> What do you think about requiring merge requests for all incoming
> changes on the sane-backends repository?
I am all for it. I think there _always_ should be room for review,
regardless how unlikely it is that someone will actually do it.
> I can only think a single reasonable exception for
> I don't think we should duplicate commit messages. Release notes are for
> end users, commit messages are for other developers, so good release
> note and good commit message are completely different. It makes sense to
> write a release note only if the change impacts end users in a
>
> I also propose to apply the proposal to the upcoming 1.0.33 release and
> use 1.1.0 version for it.
I also think this is a good idea to have the minor number available for
bugfix releases. 1.0.32 would have needed that because of a problem in
the epson2 driver.
signature.asc
Description:
Hi all,
(I guess this is mainly for Povilas, though)
I had short access to a Plustek OpticBook 4600 scanner which is
currently unsupported. 'sane-find-scanner' raises hopes that it might be
easy to add:
found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x0c26 [USB2.0
SCANNER],
Hi,
> 1) This started out with focus problems.
>I appear to have confirmed that the 1640 accepts, but ignores, focus
>commands, so the current version of the backend
>(commit 3b47d1d26a73054b7138759fa7af57ed6c8e8e35 (HEAD -> master,
> origin/master, origin/HEAD)
>with
Nakamura-san, Yumoto-san,
> Changed Points :Just add new models' IDs
> Patch : We have attached patch to the latest ver. of
> epson2 / epsonds as below:
>
> Test Status : We have completed testing with actual devices.
Thank you for the
> I have had a very quick skim of epson2.c and a couple of other files.
> I can see a DBG macro which seems to be defined in sanei_debug.h
> but I am not sure how to invoke it just yet.
SANE_DEBUG_EPSON2= xsane
Sorry, I am stuffed with work currently. I'll try to check your other
mails until
> It is better in that it no longer crashes, but is still a
> regression: I suspect that I can no longer scan films.
>
> So it seems that commit 580c278dcafe4159213406b4307ee8598fe08fe7
> was too simplistic?
It is true that the option is not a boolean anymore but an integer. But
still, if you
> I tried this but I still have xsane Version: 0.999-12 so there was no
> change. I couldn't find a newer version of xsane, even in Ubuntu.
> Indeed in the Ubuntu pool that I checked, the xsane directory was empty.
You need a newer version of libsane than debian testing. Probably
packages
Hi,
thank you for reporting and sorry for the issues the focus updates
caused you.
> Ant suggestions or help? How can I revert to a working version?
It is more like "update to a newer version".
Either you wait until Debian updates "testing" to the new 1.0.33 version
which is already in
> Thanks Wolfram, please do !
Done. You're welcome.
signature.asc
Description: PGP signature
> Thanks. Compare works, but doesn't give me a "merge request" option :-(
I don't see why it is failing for you, but I fetched your branch and
pushed it to my gitlab fork. I see the option to create a merge request.
So, if all fails, I can create the merge request for you and apply it.
> Wolfgang has been managing milestones added to issues and MRs that are to be
Wolfram, please ;)
signature.asc
Description: PGP signature
Hi,
> > - Creating a milestone on GitLab to assign all relevant issues/MRs to
>
> I am willing to do this.
I created now the 1.0.33 milestone and, so far, added closed issues (by
code changes) and merged requests since 1.0.32. I will add open tickets
later today.
This is the first time I do
> - Creating a milestone on GitLab to assign all relevant issues/MRs to
I am willing to do this.
signature.asc
Description: PGP signature
Lots of Epson scanners were added since the last release. Would be
really nice to push this out to users. So, yay!
signature.asc
Description: PGP signature
On Tue, Jun 08, 2021 at 09:57:43PM +0200, Wolfram Sang wrote:
> Hi,
>
> I don't know how many developers also track pull requests on Gitlab. I
> have proposed one patch which affects 91 drivers, so I thought I
> advertise it here as well to collect reviews. It is this pull requ
> I understand that people sometimes have quite strong views on these things
> so I guess I'm putting it out there for comment.
No strong opinion here. Yet, all the channels and people I am interested
in moved to Libera in deed. I'd suggest to move with them. If not, well,
I will just connect to
Hi,
I don't know how many developers also track pull requests on Gitlab. I
have proposed one patch which affects 91 drivers, so I thought I
advertise it here as well to collect reviews. It is this pull request:
https://gitlab.com/sane-project/backends/-/merge_requests/632
with this description:
> I folded the patch now into the upstream code base. I did some generic
> cleanups to USB ids before applying your slightly modified patch. You
> can find all this in the "epson2-new-usbids" branch of my repo:
>
> https://gitlab.com/wsakernel/backends/-/tree/epson2-new-usbids
Merged now. Thank
Hello Nakamura-san, all,
I folded the patch now into the upstream code base. I did some generic
cleanups to USB ids before applying your slightly modified patch. You
can find all this in the "epson2-new-usbids" branch of my repo:
https://gitlab.com/wsakernel/backends/-/tree/epson2-new-usbids
I
Hello Nakamura-san,
> About your question, we have implemented Zeroconf support to implement auto
> scanner discovery.
> However, this is only needed for "epsonds", because "epson2" already has this
> feature by the other logic.
> i.e. We have accidentally implemented this feature to "epson2"
Hello Nakamura-san,
> The main update from the previous release is as below : (Please refer the
> included "Release Note for Epson SANE driver update patch.pdf" also.)
> + Fix the upside down issue for back side image when scanning with
> duplex ADF setting for some models
> +
Hello Nakamura-san,
> During our internal review about "split into epson2 and epsonds", we
> found the issues of "epson2". So, we will fix the issues of "epson2",
> split the patch into epson2/epsonds and release again for your review.
I understand. I will happily wait for the new version then.
Hello Nakamura-san,
> We have applied many pieces of changes for one improvement and we have much
> difficulties to separate them to smaller patches
> which are free from dependencies among each patches.
Yes, it is very difficult afterwards if the patch has already been
created. Do you think
included in the package.
> > Could you please verify the patch and investigate to apply to SANE
> > Project?
Thank you very much for your work at Epson so far!
> We have a new maintainer, Wolfram Sang for the epson2 backend and I
> believe that M. Allan Noah has been
Hi everyone,
I want to apply as a maintainer for the epson2 driver.
I started working on this driver when I added focus and autofocus
support. Since then, I fixed some more bugs and cleaned up the
description files. I have a PR pending to improve the timeout
behaviour. I think I got the hang of
> So I probably should wait a little bit longer but if he is not interested
> anymore I am going to send it to you.
Sure, let's hope he will send the address.
signature.asc
Description: PGP signature
Hi,
> I am from Germany/Munich so I am preferably looking for some one from
> Germany (would send it for free) or maybe otherwise from Europe (depends on
> shipping costs/probably also for free).
>
> Is anyone interested?
Well, since nobody else replied so far, I would have a try.
I can check
> AFAICS I am the only one to work on this branch, so I suspect that rebasing
> will be OK.
Yes.
> Just really looking for perspectives for the SANE project.
> I suspect different projects have views on this subject.
IMHO only if they don't care about annoyed developers ;)
signature.asc
Hi Ralph,
> I have an issue branch that now has conflicts with master.
> I have not had a lot of experience with rebasing, but I read somewhere that
> rebasing is not recommended if you have pushed changes to origin because of
> the dangers of someone else working on the branch.
I am still new
Hi Olaf,
> Actually, I've found a reference in my dead tree specs that all other
> values with the one byte limit are supported. 0x00 through 0x39 are
> below the glass plate, 0x41 through 0xfe are above. Units unknown but
> based on your observation of 0x59 being 25 steps away from 0x40 and it
> Sorry everyone!
> I am ashamed of my inattention!
No worries! :)
signature.asc
Description: PGP signature
> I am a "simple" user who
> has used the lineart setting on the scanner for many, many
> years. Now I was faced with the fact that it was discontinued
> by default and is missing in my work ...
> You are a scanner and IT pros and it was great to revive
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
> >
> > Why is the lineart option not supported in the sane 1.0.31 backend version?
>
> Probably because of commit a12083c8c44b7296fa98ecb83e8932d0f6bdeb05.
>
>
> https://gitlab.com/sane-project/backends/-/commit/a12083c8c44b7296fa98ecb83e8932d0f6bdeb05
>
> @povilas> The commit message doesn't
Some more news on 'focus'.
> b) It seems to me that set_focus is not working for this model because
>e2_set_extended_scanning_parameters() says "/* XXX focus */" and no byte in
>the buffer is filled with the focus value. Probably the location is
> unknown?
>And I'd need to snoop
Hi all,
thank you for SANE. We want to use it to scan a large collection of
astronomical photoplates. SANE allows us to script things nicely.
For that, I am currently working with an Epson 12000XL. And I have a few issues
/ questions regarding the epson2 driver:
a) The scanner reports level
42 matches
Mail list logo
