Merging or stamping layers or exporting makes photo look different
Answered
Hello,
I searched the forum and noticed that many people claim that the exported photo looks different from the edited version but I couldn't find the exact solution for my case.
I put together four images as layers and chose "Lighten" for a merging option. Also, I applied "NoNoise AI" for three of the four images. In the Edit mode, it looked what I wanted. But when I exported it, the output looked different. I also tried "Merge Visible" and "New Stamped Layer" and the resulting layer also looked different before merging/stamping. The merged or stamped image looked the same as the exported image.
To separate the problem, I also made another version where the layers did not get NoNoise AI applied. Then, the exported image looked a bit closer to the image in Edit mode (but still different). So, maybe NoNoise effects have some problems when exporting the image?
Based on my search, I turned off "GPU Render" and I exported from "Browse" mode (so that all edits were saved). But the problem is still there.
See the screenshot. The left-side image is what I wanted with four layers and NoNoise AI applied. All four layers have masks in Effects. The right-side image is the exported TIFF, which looks more greenish and has a lot of unwanted stars, making brighter stars less obvious. Also, at a closer look, the bright stars of the exported TIFF look smaller or sharper than the image in Edit or Browse mode.
Here are the options in the export.
File Type: TIFF
Quality: None
Profile: sRGB IEC61966-2.1
Bit Depth: 16 bit
Preserve Transparency: Off
Resize: Off
Sharpening: Off
So, my questions are
- If all layers are on, do "Merge Visible" and "New Stamped Layer" produce the same layer?
- When exporting layered image, the layers are merged or stamped before exporting? In other words, is merged or stamped layer the image expected to get from the export?
- Why does the exported image look different from the image in Edit or Browse mode?
- Are there settings or workflow steps that prevent this problem?
- Do you experience the same issue that the image with NoNoise AI applied is exported more differently from the image in Edit mode than the one without NoNoise AI?
Thanks,
-
The image is supposed to look the same weather you merge, stamp or export it. If you're not seeing that, you should collect some before and after examples (not just screenshots) and send them to On1 tech support to look at.
0 -
- If all layers are on, do "Merge Visible" and "New Stamped Layer" produce the same layer? Yes. The only difference is that Merge removes the original Layers while New Stamped Layer leaves the originals in place.
- When exporting layered image, the layers are merged or stamped before exporting? In other words, is merged or stamped layer the image expected to get from the export? You'd have to ask tech support about that but my guess is no, there is no reason to merge or stamp them before exporting only to throw that merged/stamped Layer away after the export.
- Why does the exported image look different from the image in Edit or Browse mode? I can't answer that. I see no difference in your screenshots. Both images look the same to me. It could be different if I was looking at the actual files.
- Are there settings or workflow steps that prevent this problem? Probably not. Again, it is hard to say without seeing the actual images. As Rick said above, you can talk with tech support about this for a more definitive answer.
- Do you experience the same issue that the image with NoNoise AI applied is exported more differently from the image in Edit mode than the one without NoNoise AI? No. The only difference I see is the removal of the noise and whatever sharpening I've applied.
The differences in the stars you are seeing between NoNoise AI being used or not could be that the NNAI algorithm is removing some of the stars thinking they are noise. I hardly ever use the defaults that NNAI sets up when it is applied. I almost always zero out all the slider then do the noise removal and sharpening myself for better control over the results.
0 -
Thanks, Rick and Brian.
I will contact the tech support with actual images.
0 -
Hi again,
I haven't contacted the tech support but got another question regarding this issue.
It seems that when I add layers, the image's color space turns to "ProPhoto(2.2) RGB". I haven't done anything about the color space and the original raw (Nikon's NEF) images are given "sRGB IEC61966-2.1" The file type of the multiple-layer image is .ONPHOTO.
So, I guess that "ProPhoto(2.2) RGB" is the default color space for .ONPHOTO image. Is that true?
How can I change the color space from "ProPhoto(2.2) RGB" to "sRGB IEC61966-2.1" while in Edit mode (not at the time of export).Does this actually mean I'm editing the image using "ProPhoto(2.2) RGB" color space?
Does this explain why the exported TIFF with "sRGB IEC61966-2.1" looks slightly different from the image in Edit mode?
By the way, I use a HP all-in-one desktop (Windows 10 Home) and I don't believe it supports ProPhoto RGB or AdobeRGB.
Thanks,
0 -
Yes, you are editing in the ProPhoto(2.2) RGB colorspace. ProPhoto(2.2) RGB is the program's internal working colorspace. It is a wider space that includes both sRGB and Adobe RGB colorspaces so having it assigned as the colorspace for the image in the .onphoto file is no big deal. After all, there isn't any colorspace on the raw data.
When you export your images there could be some color shift as the new colorspace is reduced in size and any colors outside of that space would have to be brought into the new space.
The Editor lets you view your onscreen preview image in any colorspace you want. Go to View > Profiles and choose the colorspace you want to check after turning on the Enable Soft Proofing option. You can also turn on an out of gamut warning. See Soft Proofing on page 114 in the User's Guide.
0 -
Thanks, Brian.
I got a better understanding of the color spaces now. though I didn't see any obvious color shifts when I switched the profiles under the soft proofing. But this is really a very helpful tip.
Thanks again.
0
Please sign in to leave a comment.
Comments
6 comments