Hi,
this time it should indeed be an error in the escl backend. I downloaded and
installed the airscan backend and this seems to work, first tests have been
successful with Flatbed, ADF and 'ADF Duplex'. (The homepage of airscan
explicitly states that my scanner is supported.)
If you are inter
Hi,
you might remember that I am having trouble scanning from HP ScanJet Pro 4500
fn1 with the hpaio backend when using ADF or Duplex as source, but not when
scanning from the Flatbed.
Since this scanner supports AirPrint (according to the manual), I tried the
escl backend as well, but it does
For anyone following this thread. This is one place I posted what Mopria
Android saw when I had 2 scanners on same IP using different ports
https://github.com/alexpevzner/sane-airscan/discussions/219
Mark
On Fri, Mar 11, 2022 at 11:39 AM Mark Dm wrote:
> I do not know how it works out for AirSa
I do not know how it works out for AirSane but with Twain2AirScan I have
tried using different ports for different scanners. I think that AirScane
uses different paths per scanner if I recall correctly.
Having tested multiple port based shares on the same IP address and I had
bad results. Clients
Has anyone actually tested this other than the github airsane chatter about
it?
On Fri, Mar 11, 2022 at 6:38 AM Steven Santos
wrote:
> If you have not heard, ESCL is now supported on Windows 11. SANE scanners
> can now be shared with Windows workstations using AirSane.
>
> This means that it is
If you have not heard, ESCL is now supported on Windows 11. SANE scanners
can now be shared with Windows workstations using AirSane.
This means that it is now realistic to use a SANE server as the central
scan server for all OS's.
I suggest it might be time to make AirSane and AirScan dependenci
Be aware that, if you download the pdf on your (Android)Smartphone,
It will be downloaded as .pdf.apk , a Android Installation pack!
That happened to me twice.
Just rename and remove the .apk part and the file can be opened like any
other pdf file.
Cheers,
Jōrn-Ingo Weigert
Till Kamppeter sch
Great! This will be a lot of help for all of us.
Till
On 15/04/2021 19:05, Alexander Pevzner wrote:
Hi,
Mopria has published eSCL protocol specification. It can be downloaded
from the Mopria site:
https://mopria.org/spec-download
The protocol is basically the same as Apple AirPrint
Hi,
Mopria has published eSCL protocol specification. It can be downloaded
from the Mopria site:
https://mopria.org/spec-download
The protocol is basically the same as Apple AirPrint (Bonjour) scanning,
which is not officially published (yet?).
--
Wishes, Alexander Pevzner (p.
Many thanks for your explanations.
Rolf
Am 20.03.20 um 12:38 schrieb Till Kamppeter:
> On 20/03/2020 12:29, Thierry HUCAHRD wrote:
>> Hi,
>> No, this has nothing to do with eSCL.
>> ippusbxd allows you to use escl backends on the usb.
>> The problem is that sane doesn't detect the scanner on the
On 20/03/2020 12:29, Thierry HUCAHRD wrote:
Hi,
No, this has nothing to do with eSCL.
ippusbxd allows you to use escl backends on the usb.
The problem is that sane doesn't detect the scanner on the usb anymore,
so PIXMA can't be used anymore.
I don't know if ippusbxd solved the problem?
in any
Le 2020-03-20 12:04, Rolf Bensch a écrit :
Hello,
I've seen that some people need to purge ippusbxd before they can use
their scanner with escl backend (e.g.
https://gitlab.com/sane-project/backends/-/issues/256#note_307051019).
Is this a fix rule? Then I'd like to add a break dependency to
ip
Rolf, please do not add a break dependency against ippusbxd. It is most
probably only some models which cause problems.
If you want to use eSCL via the network it does not matter whether
ippusbxd is running or not. You only need to make sure to select the
correct scanner entry in the client so
Hi,
On 3/20/20 2:04 PM, Rolf Bensch wrote:
I've seen that some people need to purge |ippusbxd| before they can use
their scanner with escl backend (e.g.
https://gitlab.com/sane-project/backends/-/issues/256#note_307051019).
Is this a fix rule? Then I'd like to add a break dependency to
|ippu
Hello,
I've seen that some people need to purge |ippusbxd| before they can use
their scanner with escl backend (e.g.
https://gitlab.com/sane-project/backends/-/issues/256#note_307051019).
Is this a fix rule? Then I'd like to add a break dependency to
|ippusbxd| in my Ubuntu ppa.
Cheers,
Rolf
Le 2020-01-28 21:41, Ralph Little a écrit :
Hi,
My emailer garbled that. Here it is as an attachment.
Hopefully, this will be better.
Cheers,
Ralph
On Tue, Jan 28, 2020 at 12:22 PM Ralph Little
wrote:
Hi,
I finally got around to testing the new escl backend with my HP
OfficeJet 6978.
It does
Hi Ralph
On 1/28/20 11:22 PM, Ralph Little wrote:
I finally got around to testing the new escl backend with my HP
OfficeJet 6978.
It does appear to be supported on two ports, one encrypted:
There is an alternative eSCL backend, sane-airscan:
https://github.com/alexpevzner/sane-airscan
I wou
Hi,
My emailer garbled that. Here it is as an attachment.
Hopefully, this will be better.
Cheers,
Ralph
On Tue, Jan 28, 2020 at 12:22 PM Ralph Little wrote:
> Hi,
> I finally got around to testing the new escl backend with my HP OfficeJet
> 6978.
> It does appear to be supported on two ports, o
Hi,
Hopefully, this is a useful dump of the capability response from the
device, as reconstituted in Wireshark.
Cheers,
Ralph
http://schemas.hp.com/imaging/escl/2011/05/03"; xmlns:pwg="
http://www.pwg.org/schemas/2010/12/sm"; xmlns:dest="
http://schemas.hp.com/imaging/destination/2011/06/06"; x
Hi,
I finally got around to testing the new escl backend with my HP OfficeJet
6978.
It does appear to be supported on two ports, one encrypted:
device `escl:https://10.1.40.2:443' is a ESCL HP-OfficeJet-6978 SSL flatbed
scanner
device `escl:http://10.1.40.2:8080' is a ESCL HP-OfficeJet-6978 flatbe
20 matches
Mail list logo