ImageEn Forum

Profile Join Active Topics Forum FAQ

All Forums

Image Size

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

View

UserName:

Password:

Format

Message

Check here to include your profile signature.
Check here to subscribe to this topic.

T O P I C R E V I E W
ChrmnMAO	Posted - Feb 03 2015 : 12:34:10 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? Thanks, Martin
2 L A T E S T R E P L I E S (Newest First)
ChrmnMAO	Posted - Feb 03 2015 : 13:37:13 Thanks Nigel, To my knowledge scanner compression has not changed. I will check with the customer to see if they have an older TIFF file imported with ImageLib that we can be compared to one imported using ImageEn. Thanks again, Martin
xequte	Posted - Feb 03 2015 : 12:57:12 Hi Martin Are they being scanned at the same resolution as previously? Can you supply a sample TIFF created by both ImageLib and ImageEn? Nigel Xequte Software www.xequte.com nigel@xequte.com