On Sun, 2002-09-22 at 22:48, Henning Meier-Geinitz wrote:
> Hi,
>
> I'm interested in reports from testers. Especially if I broke the
> GT-6816 scanners (BearPaw 1200TA, 2400TA) while changing the
> gain/exposure control. And I want to know, which resolutions work for
> which scanner. I can only t
Hi,
There is a new version of the gt68xx backend: 1.0-11.
http://www.meier-geinitz.de/sane/gt68xx-backend/
Changes:
- 1200 dpi works now at least for the BearPaw 1200 CU. Maybe also for
the other scanners.
- Added manual and automatic offset/gain/exposure control for the CIS
scanners. The
Hi,
Backend freeze for 1.0.9 is now active. That means no new backends are
allowed to be added to the SANE distribution until release.
The schedule is:
2002-09-29 feature freeze
2002-10-13 code freeze
2002-10-20 release
Feature freeze means that only bug fixes and documentation updates are
allo
Major A wrote:
>>Could somebody give me a clue about the possible sample depths?
>
>
> There are only the three you mentioned -- 1, 8, 16. If a scanner
> supports, say, 12 bits, then the backend has to expand that to 16
> bits. The way this is usually done is that the scanned samples are
> left-j
Hi all,
I'm currently trying to improve the sane "glue layer" from PIL (Python
Imaging Library). One of things missing there is support for other
sample depths than 8. While it's obvious how to implement support for
line art, I'm become more and more puzzled, if support for other sample
depths
> Could somebody give me a clue about the possible sample depths?
There are only the three you mentioned -- 1, 8, 16. If a scanner
supports, say, 12 bits, then the backend has to expand that to 16
bits. The way this is usually done is that the scanned samples are
left-justified within the two byte
Once upon a time (on Sunday 22 September 2002 09:12), Jaeger, Gerhard wisely
wrote:
> No problems here with that test program! But you should run this one
> as root user.
Yes, ran as root. Segfaults. I've investigated in the code, and it really
crashes when trying to access the first device of
On Sunday, 22. September 2002 02:28, Yann E. MORIN wrote:
[SNIP]
> OK. In dmesg, the device identifies itself as VID/PID:0x4a9/0x220D, that is
> the same as a N670U. So the chip inside ought to be the same (or
> compatible). After some digging, I came up with these results: N676U scans
> at 48 bits
--Boundary-00=_TADTQDO6ABLCA9CNND8L
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
On Saturday 21 September 2002 12:49, you wrote:
> the chip inside should be a merlin LM9832 or 9833. I currently
> bought a Canon N670U which should be compatible with
