Open RAW file - CS2 -> post process (WB, etc) -> save as Tiff file -> open Tiff file ... clone, crop, -> convert to profile sRGB< -> resize image -> sharpen -> save for web -> close Tiff file and do not save changes. My RAW file would not be affected with any of the above changes as well.

Now in CS3 ...

Open RAW file -> post process (WB, etc) -> open image in CS3 - clone, crop, etc< -> convert to profile sRGB -> resize image -> sharpen -> save for web -> close RAW file. When I close the RAW file, it asks me if I want to save any changes and I say “no” ...

The difference is that CS3 changes my RAW file anyway. I found the 2nd system faster as I don't have to save in TIFF ... open that, etc. I could go right from RAW and keep moving. Why is CS3 changing my RAW file?

Thank you so much for any information you can give me.

In truth, CS3 RAW conversion has not changed your original RAW image. Nothing is lost. It is still there.

What happens is when you make the conversion, an auxilliary file with a .xmp suffix is saved which retains the corrections you made. This can be quite handy when you process the image again.

You can revert to the original RAW image by deleting the .xmp file (found stored with the original RAW file), or simply reworking the RAW converter.

By the way In following your work flow I note you do not save the processed TIFF file. Under the circumstances, you seem to be preparing the images for projection only. If you saved your work as a TIFF file it could be used for making a print without having to duplicate the work.

Regards,

By the way In following your work flow I note you do not save the processed TIFF file. Under the circumstances, you seem to be preparing the images for projection only. If you saved your work as a TIFF file it could be used for making a print without having to duplicate the work.

This may have been the method of saving first in TIFF and then “for web” for a class I took. However, the jpeg file is smaller for storage. I don't know why I don't save the final production with the TIFF file as well ... it is just what the instructor said to do. Does seem to delete information.

Why have a TIFF file and a jpeg file anyway?

Thank you for your info.

This may have been the method of saving first in TIFF and then "for web" for a class I took. However, the jpeg file is smaller for storage. I don't know why I don't save the final production with the TIFF file as well ... it is just what the instructor said to do. Does seem to delete information.

Your basic work flow is fine, but apparently you do not really understand it. The idea is

A: If you shoot JPEG or RAW to protect your 'negative'. You do this by storing the original and then working on a copy. If the capture was in JPEG (a lossy format = every time you change and save the file information is lost).your best bet is to first save it as a TIFF which is lossless.

B. When you process your image it is best to process it in it's full original size, then save it as a TIFF or PSD file. This way you preserve 100% of your original information without increasing file size. If you shoot RAW, the file size of the raw file is 1/3rd of the full size processed image.

C. When ready, you used the processed image for whatever output you need. You downsize for the web or projection, and print at full image size or even interpolate upward for large prints. The larger the print, the larger the required file to achieve 300dpi for the image. (N0TE: 300 -360 dpi are often required to produce a print.)

Sharpening is the last step and is performed after the image is sized as it is size sensitive.

THE THING TO UNDERSTAND IS WHEN YOU COMPRESS A FILE USING JPEG YOU ARE THROWING AWAY INFORMATION FOREVER! INTERPOLATION (UPRESING) can simulate lost datsa, but is a poor substitute for the real thing.

Why have a TIFF file and a jpeg file anyway? The original JPEG converted to TIFF would be your safe negative as explained above.

The JPEG's submitted for competition are abreviated files which are suitable for monitor or projection but UNSUITABLE FOR MAKING QUALITY PRINTS!

Regards,

If your first step in processing is to save a copy as PSD or TIFF, you have saved your original info, exactly the same info, in a form which may occupy 20 or more MB of space. Its value is that if in the next step you don't like what you've done you can quickly step back to the "2nd negative" without having to step backward thru Edit or Layers History to Undo what you don't like.

Then you work on the info/image which remains on your screen— which is actually the 3rd version of the image— and after you have made all the changes you wish to make, you save this image again, still as a PSD or TIFF, and its size may have grown to 25 or 30MB. Your original 3-7MB image now requires 50-60MB,or more, total of space to store.

Now the intended question: Why continue to save "negative #2," the one produced by saving the original jpeg as PSD/TIFF? Trashing it would free up 25MB of space, and as long as you labeled images expressly and you have this as your consistent workflow, is there anything lost? The original jpeg can be converted any number of times to PSD/TIFF, can't it? And if you accidentally hit "save" instead of "close" you can back out of this mistake by selecting "cancel," in the Save As dialog box.

If you then save it again as a TIFF, THE FILE SIZE REMAINS UNCHANGED! The only way the file size would be larger is if you interpolated it upward first.

I find myself wondering whether you are confusing saving a JPEG as a TIFF, with saving a RAW file (say 8 megs as RAW) that has been converted (approximately 3 times the size, i.e. 24 megs) as a TIFF.

Regards,

I shot some images of old army barracks on the Adkins Property (Fort Lowell) that turned out with a strong yellow cast. Shooting with a Nikon D80, I have the choice of either automatic, incandescent or florescent for controlling white balance. I tried all three and the results were the same - a strong yellowing color cast.

1. Color correction in the Shadows/Highlight option of Adjustment.
2. Blue color filter in the Photo Filter option in Adjustments
3. Adjusting the color balance of the shadows, highlights, and midtones.

Because you did not indicate the ambient light color temperature it is difficult to suggest a color control during shooting. I shoot only RAW and do not use filters at all even though I own an awful lot of them.

If you have PShop CS3, you can do something similar using the RAW converter on a JPEG.

Open H/S and then select the individual color you wish to change (yellow in this case). Use the saturation slider and the LIGHTNESS slider to get the effect you wish.

I suspect the above will satisfy your needs. PShop has a number of additional ways to change or adjust selected colors, but generally the HUE/Saturation approach works adequately.

Regards,
Marty
P.S. If you wish, come and visit and bring a few images for us to work on.

My files have become a little disorganized. I have a fairly large directory tree with a number of subdirectories. Throughout this tree there are many filename duplicates as the files got renumbered starting with 1 each time I performed a transfer from the camera. Some files have .xmp sidecars and some do not.

I would like to rename all files in the directory tree preserving common stems where the file extensions do not match. The result should be that after the operation completes there can only be one DSC_00001.NEF and perhaps one DSC00001.XMP but there cannot be anywhere in the tree two or more DSC_00001.NEF files. Just so we're on the same page - a stem refers to the portion of a filename before the three letter .NEF extension. In the above description DSC_00001 is a stem and .NEF is an extension.

My question is: Is there any utility or method that you are aware of that I could perform this operation with? There are a couple of utilities out there that work well if you're pointing to files that are all located in the same physical directory but not if you're pointing to an entire directory tree.

I gather you are using file numbers rather than names as a general rule.

XMP side cars indicate a raw file was processed, (and how). They will automatically go along with the raw file it relates to.

No matter what system you adopt, you have real work ahead getting organized.

When I name a processed file, I append the number and save in a different folder.

My completed files are saved in named & dated folders in the usual tree.

Hope this helps.