[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
Frank Zago ha scritto: Hello Andrej, Ralph sent me his code in April but went silent since then. I've attached what he send me, so you (or someone else) can start from there. Thanks, I will give a tray. Andrej
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
A month ago, you have post that you have developed a backend for Trust Imagery 9600SP for sane in which you appointed that you are the only possessor of an VM6552 device. In fact this is not true, because there are many possessors of this device. In fact I don't have such device, but my friend who don't use Linux have. I found that the only way to work out is to run with Sane. I not approved that you wouldn't release your backend, for the reason that there are so many people with this device. If you google a little bit, you find that so many people request for a windows xp driver. So if de device will ever work with sane, why do not to release this driver. I understand that you have to develop a new backend for a few scanner, but in time you can release your patch for teco3 for the other people who own a VM6552 device. Regards Andrej Suligoi
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
Hello Andrej, Ralph sent me his code in April but went silent since then. I've attached what he send me, so you (or someone else) can start from there. Regards, Frank. -- next part -- A non-text attachment was scrubbed... Name: teco3.tgz Type: application/x-compressed Size: 14932 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080611/7b95f26b/attachment.bin
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
On Fri, 2008-04-04 at 21:06 +0200, Ralph D. Ungermann wrote: Gerard Klaver wrote: On Thu, 2008-04-03 at 14:56 +0200, Ralph D. Ungermann wrote: Hello Ralph, I am the maintainer of the teco2 backend, if you have a link (or send a zip file with data to mailbox) to your backend i can have a look and add improvements to the teco2 backend. Hello Gerard, nice to meet you! I'll send you my sources ASAP. I hope, you'll like my resource management: - sane_init() doesn't open every device at startup - no device needs to allocate a 64KB scsi buffer - sane_read() doesn't wait for the whole image to be read - sane_read() polls for `cancel' While the device handling issues aren't so important on a desktop with a single scanner, the `no-wait' and `cancel' things have been major pain reliefs for me. And most surely you will like my color scans: my scanner just tells me, _which_ color it has sent; hence no more sophisticated guessing algorithms, no more huge color permutation tables, and no more restrictions to preselected resolutions. Just pick a line, and if the scanner says `red', distribute it to the red bytes. This change would save you many hundred lines of code. Unfortunately, you can't call this an `obvious bug fix'. So don't do it, unless you can test it for all supported scanners. Here is my offer: you tell me, which scanner models you have your hands on. Then I can try to include one of them into my backend. If we're lucky, it'll work, and we can build an enhanced new backend at least for the scanners we own, leaving the old drivers untouched. -- ralph I still own the Relisys Scorpio Super 3 VM3575 and the PRIMAX JEWEL 4800 VM356A For the VM3575 the color line sequence was different depending on the resolution of the scan, see also my gkall.hobby.nl/notes1.html page for some test images. So if there is scanner information which color is send, it would make things a lot easier. Just for information, one old testreport for the vm3575 http://gkall.hobby.nl/testreport-vm3575-2.html -- m.vr.gr. Gerard Klaver
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
Gerard Klaver wrote: On Thu, 2008-04-03 at 14:56 +0200, Ralph D. Ungermann wrote: Hello Ralph, I am the maintainer of the teco2 backend, if you have a link (or send a zip file with data to mailbox) to your backend i can have a look and add improvements to the teco2 backend. Hello Gerard, nice to meet you! I'll send you my sources ASAP. I hope, you'll like my resource management: - sane_init() doesn't open every device at startup - no device needs to allocate a 64KB scsi buffer - sane_read() doesn't wait for the whole image to be read - sane_read() polls for `cancel' While the device handling issues aren't so important on a desktop with a single scanner, the `no-wait' and `cancel' things have been major pain reliefs for me. And most surely you will like my color scans: my scanner just tells me, _which_ color it has sent; hence no more sophisticated guessing algorithms, no more huge color permutation tables, and no more restrictions to preselected resolutions. Just pick a line, and if the scanner says `red', distribute it to the red bytes. This change would save you many hundred lines of code. Unfortunately, you can't call this an `obvious bug fix'. So don't do it, unless you can test it for all supported scanners. Here is my offer: you tell me, which scanner models you have your hands on. Then I can try to include one of them into my backend. If we're lucky, it'll work, and we can build an enhanced new backend at least for the scanners we own, leaving the old drivers untouched. -- ralph
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
Hello Frank, A month ago, I learned, that you do not maintain these drivers any more (I thought it was the headline of http://www.zago.net/sane, but I can't find it there any more). I'm highly pleased to see you here. Let me take the chance to thank you for the code and its documentation. Without that, I'd have had no chance to get my scanner working (and I really had a minute's silence before deleting your function adjust_raster()). Frank Zago wrote: m. allan noah wrote: [to Gerard Klaver] Gerard- Sorry, I thought these backends were all unmaintained. I stand corrected. Can you say how similar the protocol is on all these machines? Is it reasonable to combine the backends? No. There is 3 backends for a reason. I could take a look at Ralph's code and make sure it's indeed different than the other scanners. In that case the best solution would be to create a teco4 backend. From a diff between teco2.c and teco3.c, I cannot figure out, why you decided to separate them. Your hints are welcome. I'll send you (and Gerard) my sources when I'm back home. But let me redirect the further discussion of this topic to my response to Gerard's post, please. For now, let me recapitulate: a) I have a working driver for the VM6552. We can *add* it to S.A.N.E. as teco4, so everybody in this world will have it on his/her hard disk tomorrow. Allan obvoisly has no problem with wasting other people's disk space, but I'm afraid, that nobody out there needs it, because today only one VM6552 scanner has survived, and that lucky one is sitting on my desk at home. So I'm still hesitating. b) I didn't intentionally add anything special to the VM6552. So I presume, that my driver will still work with the VM3552, and thus may *replace* the existing teco3 backend. This would actually _save_ the world's disk space. But I have no way to prove it, and I hesitate to deliver untested software. c) My main achievements are putting the colors right, and slimming resource usage. These may be also applicable to teco2. I'll stay in contact with Gerard for that purpose, and we'll take care, that this will _not_ lead to teco5. since I don't have any scanner left I don't think it's a good idea to patch an existing backend besides fixing obvious bugs. Agreed! Unless nobody with a VM3552 helps us, this will rule out b). I'll sleep over it, and probably become the maintainer of teco4. But I'd appreciate you having a glance at my code before. -- ralph
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann wrote: I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? m. allan noah wrote: though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) My scanner now runs fine! But unfortunately, it turned out to be not a patch, but a major rewrite (with 30% less lines). I presume, that my backend also solves major issues for the other supported scanners, chiefly with color scans and responsiveness (to cancel). But I have no way to test it for other teco models, and I don't want to fool millions of happy teco3 users. If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... Meanwhile: Anyone here need help coding or reviewing his code? -- ralph
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
On 4/3/08, Ralph D. Ungermann linux at mloge-ungermann.de wrote: On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann wrote: I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? m. allan noah wrote: though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) My scanner now runs fine! But unfortunately, it turned out to be not a patch, but a major rewrite (with 30% less lines). I presume, that my backend also solves major issues for the other supported scanners, chiefly with color scans and responsiveness (to cancel). But I have no way to test it for other teco models, and I don't want to fool millions of happy teco3 users. If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... why dont you go ahead and combine those drivers into a new teco backend, if it is easy enough. we can ship two backends that support the same scanners, and we can even disable teco1-3 in the dll.conf file. having currently active maintainers is worth the trouble. if you are looking for something else to do, there are plenty of other unsupported machines around :) allan -- The truth is an offense, but not a sin
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
m. allan noah wrote: On 4/3/08, Ralph D. Ungermann linux at mloge-ungermann.de wrote: If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... why dont you go ahead and combine those drivers into a new teco backend, if it is easy enough. Because I don't like to code for the museum. My VM6552 is 12 years old, and the original backend was for the VM3552; maybe these devices are all dead. I'll go ahead, as soon as somebody proves me wrong (though it will be _not_ easy to delete 4000+ more lines of code). if you are looking for something else to do, there are plenty of other unsupported machines around :) I still have 200 unread posts on sane-devel, but I've already bookmarked your Ricoh IS420 post. How about to - turn your scanner on - allow me to ssh -X ralph at ricoh.noah.org - put a sudoku in the top left corner - sit back and wait for the solution But no kidding -- there are many posts like My HAL9001 doesn't work with the HAL9000 backend. I can't tell, whether somebody else is working on that, or if this backend is orphaned. You are obviously more acquainted with S.A.N.E., so feel free to point me to any of these requests, that would otherwise remain unhandled. -- ralph
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
On 4/3/08, Ralph D. Ungermann linux at mloge-ungermann.de wrote: m. allan noah wrote: On 4/3/08, Ralph D. Ungermann linux at mloge-ungermann.de wrote: If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... why dont you go ahead and combine those drivers into a new teco backend, if it is easy enough. Because I don't like to code for the museum. My VM6552 is 12 years old, and the original backend was for the VM3552; maybe these devices are all dead. I'll go ahead, as soon as somebody proves me wrong (though it will be _not_ easy to delete 4000+ more lines of code). we have lately been discussing the future versions of SANE. it might happen that these older machines will not be directly supported, but rather, require a compatability layer. I would not ask you to do something you do not want, but consolidating those backends makes it more likely that they will be kept alive in the future. now, you might be the only living beneficiary :) if you are looking for something else to do, there are plenty of other unsupported machines around :) I still have 200 unread posts on sane-devel, but I've already bookmarked your Ricoh IS420 post. How about to - turn your scanner on - allow me to ssh -X ralph at ricoh.noah.org - put a sudoku in the top left corner - sit back and wait for the solution the backend devel and i are already working on that one :) But no kidding -- there are many posts like My HAL9001 doesn't work with the HAL9000 backend. I can't tell, whether somebody else is working on that, or if this backend is orphaned. You are obviously more acquainted with S.A.N.E., so feel free to point me to any of these requests, that would otherwise remain unhandled. recent thread (january) on: Mustek ScanExpress A3 600 USB Pro comes to mind. also an old machine i am afraid, but i was contacted by another user of it today, so perhaps we can get you some debug logs, etc. there has also been some discussion of rewriting the snapscan backend to not access the device from both threads... if you would rather look for a recent machine, it would seem that there are quite a few Brother brand machines that are only supported by a closed source backend. The same goes for some Canon and Epson machines. A quick trip to your favorite electronics boutique will show you many machines which dont work with SANE unfortunately. allan -- The truth is an offense, but not a sin
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
On Thu, 2008-04-03 at 14:56 +0200, Ralph D. Ungermann wrote: On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann wrote: I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? m. allan noah wrote: though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) My scanner now runs fine! But unfortunately, it turned out to be not a patch, but a major rewrite (with 30% less lines). I presume, that my backend also solves major issues for the other supported scanners, chiefly with color scans and responsiveness (to cancel). But I have no way to test it for other teco models, and I don't want to fool millions of happy teco3 users. If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... Meanwhile: Anyone here need help coding or reviewing his code? -- ralph Hello Ralph, I am the maintainer of the teco2 backend, if you have a link (or send a zip file with data to mailbox) to your backend i can have a look and add improvements to the teco2 backend. http://gkall.hobby.nl/scanner.html PS. Frank Zago is the maintainer for the teco1 and teco3 backend. -- m.vr.gr. Gerard Klaver
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
On 4/3/08, Gerard Klaver gerard at gkall.hobby.nl wrote: On Thu, 2008-04-03 at 14:56 +0200, Ralph D. Ungermann wrote: On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann wrote: I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? m. allan noah wrote: though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) My scanner now runs fine! But unfortunately, it turned out to be not a patch, but a major rewrite (with 30% less lines). I presume, that my backend also solves major issues for the other supported scanners, chiefly with color scans and responsiveness (to cancel). But I have no way to test it for other teco models, and I don't want to fool millions of happy teco3 users. If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... Meanwhile: Anyone here need help coding or reviewing his code? -- ralph Hello Ralph, I am the maintainer of the teco2 backend, if you have a link (or send a zip file with data to mailbox) to your backend i can have a look and add improvements to the teco2 backend. http://gkall.hobby.nl/scanner.html PS. Frank Zago is the maintainer for the teco1 and teco3 backend. -- m.vr.gr. Gerard Klaver Gerard- Sorry, I thought these backends were all unmaintained. I stand corrected. Can you say how similar the protocol is on all these machines? Is it reasonable to combine the backends? allan -- The truth is an offense, but not a sin
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
m. allan noah wrote: On 4/3/08, Gerard Klaver gerard at gkall.hobby.nl wrote: On Thu, 2008-04-03 at 14:56 +0200, Ralph D. Ungermann wrote: On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann wrote: I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? m. allan noah wrote: though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) My scanner now runs fine! But unfortunately, it turned out to be not a patch, but a major rewrite (with 30% less lines). I presume, that my backend also solves major issues for the other supported scanners, chiefly with color scans and responsiveness (to cancel). But I have no way to test it for other teco models, and I don't want to fool millions of happy teco3 users. If there is anybody else out there using backend teco1, teco2, or teco3, I'm willing to unify and maintain that driver. But now I sit idle, until somebody googles and finds this email... Meanwhile: Anyone here need help coding or reviewing his code? -- ralph Hello Ralph, I am the maintainer of the teco2 backend, if you have a link (or send a zip file with data to mailbox) to your backend i can have a look and add improvements to the teco2 backend. http://gkall.hobby.nl/scanner.html PS. Frank Zago is the maintainer for the teco1 and teco3 backend. -- m.vr.gr. Gerard Klaver Gerard- Sorry, I thought these backends were all unmaintained. I stand corrected. Can you say how similar the protocol is on all these machines? Is it reasonable to combine the backends? No. There is 3 backends for a reason. I could take a look at Ralph's code and make sure it's indeed different than the other scanners. In that case the best solution would be to create a teco4 backend. And since I don't have any scanner left I don't think it's a good idea to patch an existing backend besides fixing obvious bugs. Regards, Frank.
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
Hello, I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? -- ralph I've also posted to teco-sane-devel at yahoogroups.com, but this group appears to be dead.
[sane-devel] In progress: TRUST Imagery 9600SP (TECO_VM6552)
though there may not be much interest, we will accept patches if you get it working and it compiles cleanly. we might even make you maintainer of the code if you are not careful :) allan On Wed, Mar 5, 2008 at 8:41 AM, Ralph D. Ungermann linux at mloge-ungermann.de wrote: Hello, I'm about to adapt the teco3 backend to the VM6552. My question: Is there still any public interest in backends for such old scanners? -- ralph I've also posted to teco-sane-devel at yahoogroups.com, but this group appears to be dead. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
