In November of 2013 we stopped using Skyline Tools ImageLib components in our software, and began using ImageEn components.
We have a client reporting that since the cut-over, images stored in the database are markedly larger then they were when stored using the ImageLib components. I am at a loss to explain this.
Some relevant information:
1) We are not explicitly applying any TIFF compression prior to the images being stored. (Nor were we with ImageLib)
2) Images scanned and viewed in TImageEnMView are already compressed using G3FAX1D compression. This appears to be applied as a scanner option.
Can anyone think of a reason why there might be this difference using ImageEn components? Is there a reason to try a compression algorithm other than G3FAX1D?
Search
Image Size
Posted - Feb 03 2015 : 12:34:10
