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



if you go into the preferences dialogs, you will find a box in the "Saving
Files" dialog that says: Maximize backwards compatibility with older
versions of Photoshop.  Uncheck this!!! It is evil.  Unchecking this should
solve the problem of larger than normal files.

TaskInfo 2000 is a great program, well worth the download.  In my search for
a great memory manager/cleaner, I happenened upon a site with some great
utilites.  It hasn't been updated in awhile, but the software is still
there: www.analogx.com.  The program called MaxMem is a great tool; I use it
every time before I scan.  The RFS 3600software can be a bit buggy and seems
to be sensitive to other software runnig at the same time.  This cures the
problem like a champ.

Aloha!!!

Spencer Stone


-----Original Message-----
From: owner-filmscanners@halftone.co.uk
[mailto:owner-filmscanners@halftone.co.uk]On Behalf Of Lynn Allen
Sent: Saturday, July 28, 2001 7:00 AM
To: filmscanners@halftone.co.uk
Subject: Re: filmscanners: Scanning and memory limits in Windows


Steve wrote:
 >I've noticed PS is slow too. Worse still it doesn't compress well either -
try opening a file from Vuescan and then saving it with PS and it comes out
significantly larger.

And Rafe wrote:
>Sorry, this doesn't sound right.  For a given image,
>a given file format, and compression method, the
>file size should be deterministic....
>If this weren't so, it would not be possible to share
>files between applications.

It *is* right, though, and file sharing is due to other programs recognizing
(and adjusting to) PS files. This was not always so, but has been for many
years. I'd hoped some of the better Photoshop users would chime in here,
because I'm *not* one. But I learned early on --when a folder of PS-saved
images couldn't save to a disc which seemed to have plenty of space on it--
that PS has its own way of saving images, that can be 20% or more larger
that the original file.

First of all, PS writes and saves a thumbnail; this can be defeated in the
Preferences (I think is where that is). It then also saves various
Photoshop-specific flags and markers (like color space), whether or not
you've done any actual *work* on the image in PS, so it's the same image
that you saved in PS when you open it again in PS (I'd suspect it may also
mark memory space for certain PS modes and actions, but don't know that for
fact).

Ordinarily, this will cause no problems except that your PS files will be
larger than you anticipated, and if PS is your working Image Processor it's
good to have the stuff embedded in the file. Where it becomes a *problem* is
whenever you have file/memory size constraints--it's the equivalent of
putting 10 pounds of "stuff" in a 5-pound bag. It's particularly difficult
when you're doing JPEGs for a final destination like a CD (or web site, or
email)-- PS is going to make your files bigger than you want with what may
well be useless information, and AFAICT it doesn't ask for your opinion. :-|

Tony Sleep suggested the solution to this problem, which I personally went
with--save the final image in another program (Picture Publisher 8 in this
case), that has a user-selectable size-readout and visually-adjustable
Preview JPEG output. That's currently what I'm doing--adjust in PS and save
a TIFF to a Temp file, JPEG in PP8 to another file at a controlable size,
then save to disc. It involves extra steps, but since I'm publishing
multiple copies to a finite CD space, it's the best way to procede that I
presently know of.

Best regards--LRA


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp




 




Copyright © Lexa Software, 1996-2009.