ðòïåëôù 


  áòèé÷ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 

  óôáôøé 


  ðåòóïîáìøîïå 


  ðòïçòáííù 



ðéûéôå
ðéóøíá












     áòèé÷ :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: filmscanners: Scanning and memory limits in Windows



Do not assume that all reconstituted images are created equal.

Short cuts are sometimes taken in translating the file back into an
uncompressed image which might speed up decompression, but not represent
the full nature of the image.

Art

Rob Geraghty wrote:
> 
> "Dana Trout" <dana@troutcom.com> wrote:
> > A 25% faster drive won't necessarily get you 25% faster load/store
> > times. PhotoShop seems to be inordinately slow in dealing with
> > compressed TIFFs
> 
> Paintshop Pro is the same.  Opening a film scan in PSP takes *far* longer
> than in Irfanview.
> 
> > BTW, Ed's VueScan takes less than 30 seconds to read the same file.
> 
> It seems that Adobe and JASC have inefficient code for packing and unpacking
> LZW compression, so at least as far as opening and saving LZW TIFF files
> goes, CPU speed will matter as well.  But it still a valid point that a
> drive with a faster spin rate will improve the general operation of the
> machine - image editing programs aside. :)
> 
> Rob




 




Copyright © Lexa Software, 1996-2009.