[sane-devel] Image Compression doesn't support in SANE protocal
Hi All, Do you have any update on this thread? This is way back 2006, perhaps it is now supported. It's about adding frame type for JPEG or other compressed format. http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017606.html Best Regards, Ariel IMPORTANT NOTICE: This e-mail and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of KYOCERA Document Solutions Development Philippines, Inc. If you are not the intended recipient of this e-mail and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this e-mail in error. The integrity and security of this message cannot be guaranteed on the Internet. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140314/32529825/attachment.html
[sane-devel] Image Compression doesn't support in SANE protocal
There has been little improvement of this situation. There are some commented out frame types for jpeg and ir in the source, and some backends will use them if they are uncommented. But, since they are not part of the sane standard, most front programs will not handle them. allan On Fri, Mar 14, 2014 at 2:35 AM, Ariel Ramonito Edera ArielRamonito.Edera at ddp.kyocera.com wrote: Hi All, Do you have any update on this thread? This is way back 2006, perhaps it is now supported. It's about adding frame type for JPEG or other compressed format. http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017606.html Best Regards, Ariel IMPORTANT NOTICE: This e-mail and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of KYOCERA Document Solutions Development Philippines, Inc. If you are not the intended recipient of this e-mail and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this e-mail in error. The integrity and security of this message cannot be guaranteed on the Internet. -- sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] Image Compression doesn't support in SANE protocal
On Fri, 14 Mar 2014 08:30:39 -0400 m. allan noah kitno455 at gmail.com wrote: There has been little improvement of this situation. There are some commented out frame types for jpeg and ir in the source, and some backends will use them if they are uncommented. But, since they are not part of the sane standard, most front programs will not handle Btw.. do we have stats regarding the most common frontend used with sane? -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] Image Compression doesn't support in SANE protocal
On 14/03/2014 15:11, Alessandro Zummo wrote: On Fri, 14 Mar 2014 08:30:39 -0400 m. allan noah kitno455 at gmail.com wrote: There has been little improvement of this situation. There are some commented out frame types for jpeg and ir in the source, and some backends will use them if they are uncommented. But, since they are not part of the sane standard, most front programs will not handle Btw.. do we have stats regarding the most common frontend used with sane? Hello, for me most common frontends are the ones that pop up in the mailing list: - scanimage - xsane - scanadf - simplescan I think that checking default frontend installed by various linux distributions will also give an idea of the most commonly used frontends. Regards, Stef
[sane-devel] Image Compression doesn't support in SANE protocal
Skipped content of type multipart/alternativeFrom yann.morin.1998 at anciens.enib.fr Sat Aug 26 20:42:11 2006 From: yann.morin.1...@anciens.enib.fr (Yann E. MORIN) Date: Thu Sep 7 16:04:44 2006 Subject: [sane-devel] [TRANSLATION] French translation update. Message-ID: 200608262242.11677.yann.morin.1...@anciens.enib.fr Hello all! After more than three years (sorry for that long a time, I strictly use english MMIs), here is an updated version of the french translation for the sane backends. The only messages not translated are very technical in essence and would need professional graphics knowledge (I'm just a amateur here). Please comment. Because I only recently re-enabled my subscription, I haven't followed what's happening here. So if you did arrange for any other way to submit translations, please tell me, I'll do it. Regards, Yann E. MORIN. -- .-..--.. | Yann E. MORIN | Real-Time Embedded | /\ ASCII RIBBON | Erics' conspiracy: | | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^| | --== ?_? ==-- ?---.: X AGAINST | /e\ There is no | | web: ymorin.free.fr | SETI@home 3808 | / \ HTML MAIL|conspiracy. | ?-??--?? -- next part -- A non-text attachment was scrubbed... Name: sane-backends.fr.po Type: application/x-gettext Size: 99448 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060826/a6ecf48d/sane-backends.fr-0001.bin
[sane-devel] Image Compression doesn't support in SANE protocal
On Tue, 2006-08-22 at 13:35 -0400, m. allan noah wrote: On Tue, 22 Aug 2006, Ren? Rebe wrote: On Aug 22, 2006, at 2:51 PM, m. allan noah wrote: now that many low-end scanners support jpeg natively (some ONLY do jpeg!) i expect we will see more need for this. Oh! as a short term fix, rather than adding a new sane_frame type, the backend can extract the compressed data, convert to raw bitmap. then frontend can convert to any compressed format it wants. this is not as efficient as keeping the compressed version the entire way through, but it works now. dell networked scanner backend works this way. Well that stinks as you lose a lot of detail with the lossy jpeg decompression. even worse, if you are running the thing over the net backend, you convert to huge bitmap just before you transfer it over the network! Maybe let's add the JPEG frame type rather soon (even in SANE 1) and let's add an IR (infra red) frame specification on the way as good film scanner deliver for dust and the-like removal. agreed. though i would think we would need to make a well-known option like 'compression' or 'format' that such backends would have to implement, with the default being 'bitmap'. these backends would then 'unjpeg' the files before passing to frontend, and existing frontends will continue to work. then the user must manually set the option to something other than 'bitmap', if he knows his frontend supports this. SANE2 could require that the frontend support jpeg, and that could become the default for the 'format' option. allan Yours, Also for webcam devices the jpeg option is a welcome feature, devices like pac207 and sq930c/b support jpeg (and many other webcam usb bridges). -- m.vr.gr. Gerard Klaver
[sane-devel] Image Compression doesn't support in SANE protocal
On Wed, 23 Aug 2006, Michael Hennebry wrote: On Tue, 22 Aug 2006, m. allan noah wrote: On Tue, 22 Aug 2006, Ren? Rebe wrote: Well that stinks as you lose a lot of detail with the lossy jpeg decompression. even worse, if you are running the thing over the net backend, you convert to huge bitmap just before you transfer it over the network! Maybe let's add the JPEG frame type rather soon (even in SANE 1) and let's add an IR (infra red) frame specification on the way as good film scanner deliver for dust and the-like removal. Perhaps with carefully crafted code, decompression compression could be made an identity operation. If not, perhaps it could be made idempotent. elaborate SANE2 could require that the frontend support jpeg, and that could become the default for the 'format' option. Not having a default would better than making it a lossy compression method. If one is going to do compression, perhaps it would be good to have a non-loosy method as one of the options. agreed. zlib ok? allan -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera From henne...@web.cs.ndsu.nodak.edu Wed Aug 23 19:20:50 2006 From: henne...@web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Wed Aug 23 19:20:57 2006 Subject: [sane-devel] Image Compression doesn't support in SANE protocal In-Reply-To: pine.lnx.4.61.0608231212310.23...@limos.pfeiffer.edu Message-ID: 20060823140429.s16938-100...@web.cs.ndsu.nodak.edu On Wed, 23 Aug 2006, m. allan noah wrote: On Wed, 23 Aug 2006, Michael Hennebry wrote: On Tue, 22 Aug 2006, m. allan noah wrote: On Tue, 22 Aug 2006, Ren? Rebe wrote: Well that stinks as you lose a lot of detail with the lossy jpeg decompression. even worse, if you are running the thing over the net backend, you convert to huge bitmap just before you transfer it over the network! Maybe let's add the JPEG frame type rather soon (even in SANE 1) and let's add an IR (infra red) frame specification on the way as good film scanner deliver for dust and the-like removal. Perhaps with carefully crafted code, decompression compression could be made an identity operation. i.e. compression(decompression(x))=x If not, perhaps it could be made idempotent. i.e compression(decompression(compression(decompression(x= compression(decompression(x)) elaborate The idea is to put a useful bound on the amount of damage done by repeated decompressions and compressions. The jpeg compression algorithms are not invertable. For every jpeg compression algorithm, there are distinct X and Y such that compression(X)=compression(Y). The same might be true for decompression, but I'm not sure. If one is going to do compression, perhaps it would be good to have a non-loosy method as one of the options. agreed. zlib ok? ok. -- Mike henne...@web.cs.ndsu.nodak.edu it stands to reason that they weren't always called the ancients. -- Daniel Jackson
[sane-devel] Image Compression doesn't support in SANE protocal
I found no image compression support is added in SANE. When scanning with high resolutions such 600 x 600 dpi and uses color scan, the result image will be very large! So many scanners support compress transfer:scanner compress the image data and transfer compressed data to driver. In SANE the images transfered between backend and frontend are strict limited.I think it' better if SANE add some file transfer type like TWAIN. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060822/074cc0df/attachment.htm From r...@exactcode.de Tue Aug 22 09:19:43 2006 From: r...@exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=) Date: Tue Aug 22 09:20:44 2006 Subject: [sane-devel] Image Compression doesn't support in SANE protocal In-Reply-To: 00df01c6c5b1$a6d22130$4300a...@vp.com References: 00df01c6c5b1$a6d22130$4300a...@vp.com Message-ID: b5e8d17b-61ef-4cca-a228-0e096bea1...@exactcode.de On Aug 22, 2006, at 8:10 AM, zf wrote: I found no image compression support is added in SANE. When scanning with high resolutions such 600 x 600 dpi and uses color scan, the result image will be very large! So many scanners support compress transfer:scanner compress the image data and transfer compressed data to driver. In SANE the images transfered between backend and frontend are strict limited.I think it' better if SANE add some file transfer type like TWAIN. Most scanners do not support compression anyway. Such features are only found in 5000 EUR and above devices. If you just want to save files in a compressed format just use a decent application such as xsane and not the example programs such as xscanimage ,-) Yours,
Re: (ÈðÐÇÌáʾ-´ËÓʼþ¿ÉÄÜÊÇÀ¬»øÓʼþ)Re: [sane-devel] Image Compression doesn't support in SANE protocal
Yes, xsane can save file in a compressed format. But before that we must decompress the data from scanner and then transfer it to xsane and then xsane compress the image So we can't use the compressed data from scanner directly, then the scanner's speed is slow down. - Original Message - From: Ren? Rebe r...@exactcode.de To: zf zfan...@163.com Cc: OrgSane-Devel@Lists. Alioth. Debian. sane-devel@lists.alioth.debian.org Sent: Tuesday, August 22, 2006 5:19 PM Subject: (-)Re: [sane-devel] Image Compression doesn't support in SANE protocal On Aug 22, 2006, at 8:10 AM, zf wrote: I found no image compression support is added in SANE. When scanning with high resolutions such 600 x 600 dpi and uses color scan, the result image will be very large! So many scanners support compress transfer:scanner compress the image data and transfer compressed data to driver. In SANE the images transfered between backend and frontend are strict limited.I think it' better if SANE add some file transfer type like TWAIN. Most scanners do not support compression anyway. Such features are only found in 5000 EUR and above devices. If you just want to save files in a compressed format just use a decent application such as xsane and not the example programs such as xscanimage ,-) Yours, From an...@pfeiffer.edu Tue Aug 22 12:51:32 2006 From: an...@pfeiffer.edu (m. allan noah) Date: Tue Aug 22 12:52:33 2006 Subject: [sane-devel] Image Compression doesn't support in SANE protocal In-Reply-To: 016601c6c5cf$1447a6a0$4300a...@vp.com References: 00df01c6c5b1$a6d22130$4300a...@vp.com b5e8d17b-61ef-4cca-a228-0e096bea1...@exactcode.de 016601c6c5cf$1447a6a0$4300a...@vp.com Message-ID: pine.lnx.4.61.0608220843390.6...@limos.pfeiffer.edu now that many low-end scanners support jpeg natively (some ONLY do jpeg!) i expect we will see more need for this. as a short term fix, rather than adding a new sane_frame type, the backend can extract the compressed data, convert to raw bitmap. then frontend can convert to any compressed format it wants. this is not as efficient as keeping the compressed version the entire way through, but it works now. dell networked scanner backend works this way. allan On Tue, 22 Aug 2006, zf wrote: Yes, xsane can save file in a compressed format. But before that we must decompress the data from scanner and then transfer it to xsane and then xsane compress the image So we can't use the compressed data from scanner directly, then the scanner's speed is slow down. - Original Message - From: Ren? Rebe r...@exactcode.de To: zf zfan...@163.com Cc: OrgSane-Devel@Lists. Alioth. Debian. sane-devel@lists.alioth.debian.org Sent: Tuesday, August 22, 2006 5:19 PM Subject: (-)Re: [sane-devel] Image Compression doesn't support in SANE protocal On Aug 22, 2006, at 8:10 AM, zf wrote: I found no image compression support is added in SANE. When scanning with high resolutions such 600 x 600 dpi and uses color scan, the result image will be very large! So many scanners support compress transfer:scanner compress the image data and transfer compressed data to driver. In SANE the images transfered between backend and frontend are strict limited.I think it' better if SANE add some file transfer type like TWAIN. Most scanners do not support compression anyway. Such features are only found in 5000 EUR and above devices. If you just want to save files in a compressed format just use a decent application such as xsane and not the example programs such as xscanimage ,-) Yours, -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera From r...@exactcode.de Tue Aug 22 12:56:17 2006 From: r...@exactcode.de (=?ISO-8859-1?Q?Ren=E9_Rebe?=) Date: Tue Aug 22 12:57:50 2006 Subject: [sane-devel] Image Compression doesn't support in SANE protocal In-Reply-To: pine.lnx.4.61.0608220843390.6...@limos.pfeiffer.edu References: 00df01c6c5b1$a6d22130$4300a...@vp.com b5e8d17b-61ef-4cca-a228-0e096bea1...@exactcode.de 016601c6c5cf$1447a6a0$4300a...@vp.com pine.lnx.4.61.0608220843390.6...@limos.pfeiffer.edu Message-ID: 7cbc1e6c-1e62-4faa-a01e-afae88a8c...@exactcode.de On Aug 22, 2006, at 2:51 PM, m. allan noah wrote: now that many low-end scanners support jpeg natively (some ONLY do jpeg!) i expect we will see more need for this. Oh! as a short term fix, rather than adding a new sane_frame type, the backend can extract the compressed data, convert to raw bitmap. then frontend can convert to any compressed format it wants. this is not as efficient as keeping the compressed version the entire way through, but it works now. dell networked scanner backend works this way. Well that stinks as you lose a lot of detail with the lossy jpeg decompression
[sane-devel] Image Compression doesn't support in SANE protocal
On Tue, 22 Aug 2006, Ren? Rebe wrote: On Aug 22, 2006, at 2:51 PM, m. allan noah wrote: now that many low-end scanners support jpeg natively (some ONLY do jpeg!) i expect we will see more need for this. Oh! as a short term fix, rather than adding a new sane_frame type, the backend can extract the compressed data, convert to raw bitmap. then frontend can convert to any compressed format it wants. this is not as efficient as keeping the compressed version the entire way through, but it works now. dell networked scanner backend works this way. Well that stinks as you lose a lot of detail with the lossy jpeg decompression. even worse, if you are running the thing over the net backend, you convert to huge bitmap just before you transfer it over the network! Maybe let's add the JPEG frame type rather soon (even in SANE 1) and let's add an IR (infra red) frame specification on the way as good film scanner deliver for dust and the-like removal. agreed. though i would think we would need to make a well-known option like 'compression' or 'format' that such backends would have to implement, with the default being 'bitmap'. these backends would then 'unjpeg' the files before passing to frontend, and existing frontends will continue to work. then the user must manually set the option to something other than 'bitmap', if he knows his frontend supports this. SANE2 could require that the frontend support jpeg, and that could become the default for the 'format' option. allan Yours, -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera From terren...@ak.net Tue Aug 22 17:57:51 2006 From: terren...@ak.net (terren...@ak.net) Date: Tue Aug 22 17:59:19 2006 Subject: [sane-devel] Best scanners to use with SANE? Message-ID: Pine.LNX.4.64.0608220952560.6829@Knoppix Does anyone have any suggestions on the best scanner for working with Sane? I'm thinking I'll probably get a scanner in October specifically based on what works with SANE, instead of what I did last year, getting the scanner and then realizing too late that it wouldn't work. I'm looking for something that will be the least time-consuming to get working as I want to be able to spend the time scanning, not fighting with my scanner. I'm running SANE on an e-machines 433MHZ PC with Oralux, a Knoppix-based operating system without X11. Any advice on this would be greatly appreciated. Thanks, Terrence