Best way to reduce a big MGDB file?

[Willow Photography]

The files from MFDB ( and DSLR ) gets bigger and bigger, but for
the most part the end result is a A5 to A3 size file or websize.

Whats the best way to reduce size and keep the IQ.

Willow


Sorry, cannot edit wrong spelling in heading  

[Graham Mitchell]

Whats the best way to reduce size and keep the IQ.

I assume you mean the file size and not the number of pixels?

It really depends on your work flow and the amount of retouching etc. I assume you are shooting in RAW and have a lossless workflow to begin with. RAW files are generally a lot smaller than TIFFs so you could keep the RAW files and not the TIFFs, assuming there is very little processing to be lost.

If you want to keep more processed images, the next question is really do you need lossless compression or is a smaller, lossy file acceptable? There still doesn't seem to be a viable mainstream alternative to beat JPEGs for lossy compression. Just choose the quality/size ratio which suits best. If you want to keep the maximum quality, you could try comparing the size of TIFF files saved with lossless compression (e.g. LZW) or simply try zipping the TIFF file.

Other simple space savers are cropping unnecessary parts of an image out, and converting from 16 bit to 8 bit (after post processing).

[feppe]

I assume you mean the file size and not the number of pixels?

It really depends on your work flow and the amount of retouching etc. I assume you are shooting in RAW and have a lossless workflow to begin with. RAW files are generally a lot smaller than TIFFs so you could keep the RAW files and not the TIFFs, assuming there is very little processing to be lost.

If you want to keep more processed images, the next question is really do you need lossless compression or is a smaller, lossy file acceptable? There still doesn't seem to be a viable mainstream alternative to beat JPEGs for lossy compression. Just choose the quality/size ratio which suits best. If you want to keep the maximum quality, you could try comparing the size of TIFF files saved with lossless compression (e.g. LZW) or simply try zipping the TIFF file.

Other simple space savers are cropping unnecessary parts of an image out, and converting from 16 bit to 8 bit (after post processing).

Good advice above. To elaborate, workflow dependent on Lightroom editing takes an order of a magnitude less space than pixel-level editing in PS. Also, PS Smart Filters should have the same benefit, although I haven't investigated this.

Here's a topical article, one of my favorite articles on post-processing: Erase, merge and flatten. I used to be fastidious at saving every single step which resulted in multi-gig files out of original weighing only tens or a few hundred megs. While I still don't erase, merge and especially flatten in abandon, I take a look at what I imagine might come useful later.

[Willow Photography]

I think he just wants ideas/suggestions about methods of downsizing files for final output.

Jepp, thats what I need.

When I am finished with my photoshoping, how to preserve this
beautiful MFDB file that I pay so much to create  

[Henry Goh]

I normally keep the full size photoshopped TIF as Masterfile.  From this I reduce the dimensions to whatever size the file needs to be used at within Photoshop Image->Size->
From here, I then sharpen the file at that resolution. If I need to convert to CMYK, then I would skip the sharpening until I have finished the conversion.  Don't really know if that's what you wanted to hear Willow.

[David Eichler]

The files from MFDB ( and DSLR ) gets bigger and bigger, but for
the most part the end result is a A5 to A3 size file or websize.

Whats the best way to reduce size and keep the IQ.

Willow


Sorry, cannot edit wrong spelling in heading  

For output sizing and sharpening large files for the Web, this process seems to work very well: http://www.foliolink.com/resources_articles/tucker.asp

[CBarrett]

I find that when I do a one step downsize to websize, that Photoshop creates softer images and sometimes aliased diagonals, a big deal since I shoot architecture.

I have created two Photoshop actions that downsize my P65+ Tiffs in 10% steps (one for horizontals, one for verticals).  This has provided me with the best quality for web portfolio.  I then duped the actions and threw out the bottom half of the steps which left me with a nice print  size.  All this makes it easy to put multiple size files on a disc (which clients appreciate)

From there, sharpening is up to you, and of course sRGB.

Best,

CB

First Image is one step downsize, second is incremental (better sharpness and contrast... neither was sharpened)

[carstenw]

I find that when I do a one step downsize to websize, that Photoshop creates softer images and sometimes aliased diagonals, a big deal since I shoot architecture.

I have created two Photoshop actions that downsize my P65+ Tiffs in 10% steps (one for horizontals, one for verticals).  This has provided me with the best quality for web portfolio.  I then duped the actions and threw out the bottom half of the steps which left me with a nice print  size.  All this makes it easy to put multiple size files on a disc (which clients appreciate)

From there, sharpening is up to you, and of course sRGB.

Best,

CB

First Image is one step downsize, second is incremental (better sharpness and contrast... neither was sharpened)

How do you down-size in one step? I thought that the bicubic sharpener was meant to make this approach superfluous.

[Dick Roadnight]

When I am finished with my photoshoping, how to preserve this
beautiful MFDB file that I pay so much to create  

MFDBs cost money and produce quality files, but DSLRs with Anti-aliasing filters... and, if the AA filter spreads the light destined for one pixel over the neighbouring pixels... 9 pixels in all... you can reduce your pixel count by about a factor of ten without drastically reducing the quality - this is why a 2 Mpx HD TV screen looks as good as a 20Mpx DLSR pic.

[Willow Photography]

MFDBs cost money and produce quality files, but DSLRs with Anti-aliasing filters... and, if the AA filter spreads the light destined for one pixel over the neighbouring pixels... 9 pixels in all... you can reduce your pixel count by about a factor of ten without drastically reducing the quality - this is why a 2 Mpx HD TV screen looks as good as a 20Mpx DLSR pic.

 So what you say is that reducing a DSLR file is less damaging than reducing a MFDB file??

[Dick Roadnight]

So what you say is that reducing a DSLR file is less damaging than reducing a MFDB file??

...yes... the per pixel quality of a DSLR picture is such that you have less to lose in reducing the pixel count.

If you have a good MFDB file you can reduce pixel count by cropping, but if you shot what you wanted in the first place, it does not help.

Perhaps the ideal camera for web work is a very early low-res MFDB? ... or perhaps a 3 CCD cine-type system?

...of course, if you have a quality MFD file you have options.