bill_d.1

Thank you Kevin for your response.

I don't know about smart filters, I don't think that's available in Elements.

As far as merging layers, again that defeats the purpose. My objective is to save each layer for tweaking later on. I don't see any difference between flattening and merging. Forgive me if I'm not making any sense, I have a feeling that there is some simple concept that I just don't understand.

Bill

"You would have all of your layers in place, all you'd have to do is just open up the file to see what was done."

In theory maybe, but in practice I have not been able to accomplish this. Maybe you could help me understand what I'm doing wrong. I think it's a workflow issue for me.

Here's what I mean... I always wanted to be able to do all my edits in layers and keep all the layers intact so I can go back and tweak just one of the edits without having to do them all over again. But not all editing can be done in adjustment layers. So for example if I have an adjustment layer for levels and another one for hue/sat and then I want to do some final output sharpening in a layer, there is no adjustment layer for sharpening (I'm using Elements 4.0). So I need to create a duplicate layer to do my sharpening in. But if I duplicate the top layer in the stack that doesn't work, I have to flatten the image first and well, there go my layers. If I duplicate the bottom layer (background) for my sharpening layer then in effect I am performing the sharpening before the levels and hue/sat are adjusted and I don't think that's a good idea.

I hope I'm not hijacking this thread but I think my problem is related to the original question. Any help would be appreciated.

I have taken some photos which will be incorporated into a video production.

The editor (not me) is using Final Cut Pro. I have some questions on how best

to prepare these photos.

I am not overly concerned with aspect ratio because the images may not

necessarily be full frame (there may be captions or there may be more than one

image in a single frame, etc.) therefore I assume some resizing would take

place in FCP.

What I am wondering about are things like resolution, color space, sharpening,

etc.

Should I save the images at 72ppi or something else?

Should I save the images using sRGB or something else?

Should I apply unsharp mask the same as if I was preparing the images for use

on a computer monitor, or would I get better results going heavier or lighter?

Are there any other things I should be aware of?

Thanks for your help.

Bill

I WAS having the exact same problem described by Thomas Sullivan and Bob Atkins above.

I know there was a post a week or two ago also describing the same thing.

If it helps I can tell you two things for sure:

It is definitely photo.net, not other sites.

The problem went away entirely when I updated from IE6 to IE7 two days ago.

Bill

After hours of reading about resolution and resizing and resampling

I hate to admit it but I'm still confused. So, I'd like to ask a

couple specific questions.

I send TIFF files out to a photo lab for prints. My questions are

only about printing, not web or monitor display.

From my 300D files open in PS Elements at 300ppi, 6.827"x10.24".

To get a 4"x6" print (same aspect ratio as original) which should I

do for the best quality print:

1. Resize to 4"x6" with resample on (resolution stays at 300ppi)

2. Resize to 4"x6" with resample off (resolution increases to 512ppi)

3. Don't resize at all, just order a 4"x6" print from the file, as

is.

To get a 12"x18" print (same aspect ratio) which should I do for the

best quality print:

1. Resize to 12"x18" with resample on (resolution stays at 300ppi)

2. Resize to 12"x18" with resample off (resolution decreases to

170ppi)

3. Don't resize at all, just order a 12"x18" print from the file, as

is.

Again, my questions are about print quality. I'm not concerned (for

now) with file size, upload time or screen display.

Thanks for your help.

Bill

I also had a similar problem.

In the menu, under communication, select normal (not PTP).