nater973

Again, thanks Lagarto. Your demonstrations and explanations clarify this for me. I don't personally use Windows Photo or Irfanview for my photography workflow. However, I have a lot of family and friends who like to see my photographs. They're not photographers so they typically use the stock or popular apps to view photos. My whole question originated because I started investigating how they are seeing my photos. And now I think I have my answer-- many of the common photo viewing apps are not color managed and thus won't look identical to them.

Both of these are noticeably different to me between APhoto and Windows Photos. I'm curious if you're able to see any difference when you open in APhoto vs. something basic like Windows Photos. 0825_2029_01.tiff _20200323_181839.tiff

Btw, Lagarto, I did open the TIFF files in the apps.

The hawk JPG had sRGB embedded, but here's an example that was taken with sRGB (Nikon RAW), processed in APhoto, and then exported to JPG with sRGB embedded. While the reds are not as pronounced in this one, when I open it in APhoto and then open it in Windows Photos and place them side by side, the Windows Photos has noticeably stronger red tones than APhoto. My preference is how APhoto renders it, but I'll be aware now that others may not see my photos with the exact same colors I intended.

Thank you, Lagarto. As expected the colors on the top row do look brighter (more vivid) since my monitor supports a color gamut beyond sRGB. I did do a further test based on something you mentioned. I uploaded the same image to my Smugmug account online (color management turned off). When I open the hawk image in Smugmug in Firefox (color management turned off), the image matches APhoto (= good). When I open the hawk image in Smugmug in Microsoft Edge, the image has the overly-red hues. What I'm inferring from this test is: settings in APhoto are fine monitor calibration is fine (though I'm going to re-calibrate to make sure) I'll just have to accept that how others see my images electronically will be largely dependent on both their screens and the applications they're viewing them in Psenda, Lagarto, or anyone else-- please correct any of my inferences above.

I have a BenQ SW271, calibrated using Spyder5 Pro hardware. I'm game for re-calibrating to see if that corrects the problem. Note that with the current calibration and APhoto processing and exporting, my prints are color matched correctly. It's when I open images (and this hawk is the most noticeable so far) on screen in other applications that I see the difference. Psenda, if I understand you correctly, I'm stuck with one of two options: non-calibrated monitor (setting profile to generic sRGB) or having non-print images that don't color match with APhoto. I'm unwilling to accept these as the only two options because this isn't a universal problem that everyone experiences. Thus my post asking for assistance. Please correct me if I'm misunderstanding. Thanks.

Thank you. If I change the monitor's color profile to SRGB, then I'm removing the calibration profile, which seems opposite of what I'd want to do. I can also accept that APhoto is unlike other image viewers, but if that's the case, then there should be some soft-proofing option for OS-color-managed-viewers. While I appreciate your reply, it doesn't really help understand a way to solve my problem. I'm not sure how changing my monitor to standard sRGB profile away from a calibrated profile would cause APhoto and basic/mid-range viewers to all display similarly

Please let me begin by acknowledging that somewhere in all the past posts, this has been addressed specifically. If so, please point me there. Also, please read my entire post before sending me to a previous post that's about general color management. Problem: In the attached photo, Affinity Photo displays the colors on my calibrated screen as I want them. However, after exporting in JPEG format, applications outside of AP display the photo differently (reds are to strong for my liking). I've found this to be the case in other photos as well. Setup and background: I have a color calibrated monitor. My AP (v1.8.2.620) color management settings are all at the default (see attached screenshot). I took the hawk photo with a Nikon camera in RAW (NEF); the camera shoots in Adobe RGB. Opened the photo in AP and did processing. When I was finished processing, I selected File > Export > JPEG > More > ICC Profile and selected sRGB IEC61966-2.1. I closed it and then exported. On the same screen I'd done all the AP work, I opened the JPEG in Irfanview. Whoa-- too much red. I opened the JPEG in Windows Photos-- it looked identical to the Irfanview image-- too much red. Then I opened the image in ACDSee Photo Studio and it looked identical to the Irfanview and Windows Photos renderings. At that point I decided that something was awry in AP. Conclusions: The problem is not my monitor. However, I'm guessing either I have a setting wrong in AP (I've already looked at the AP color management article and adjusted accordingly) or AP just renders different from everything else (seems unlikely) or all other programs read the image data differently than AP. I did take a look at the Soft Proofing to see if any of the options made it look like all other programs, but to no avail. Help? Thanks, Nathaniel

Thanks all. The Denoise bug was it. I removed that and the macro ran successfully!

Thanks Walt. The macro is attached. Part of my problem in exporting was that I was trying to figure out a way to do it without an image open. However, your response got me thinking and the problem is definitely in the macro somewhere. I tested other macros I had created and they ran fine in a new batch job. This macro, though, has a problem in it. Here's the descriptor part of the macro: Add White Balance Adjustment Set adjustment parameters Merge Down Noise Reduction Add Shadows/Highlights Adjustment Set adjustment parameters Merge Down Add Exposure Adjustment Set adjustment parameters Merge Down Would the crashing have anything do with my merging down after each adjustment? Thanks, Nathaniel Xmas Macro.afmacro

Hello, every time I try to run a macro using New Batch Job, AP crashes almost immediately. Using AP 1.7.3.481 on Windows 10. Windows 10 version 10.0.17763 Build 17763 Running AP off GeForce RTX 2070, version 441.41 Memory data rate: 14.00 Gbps Total available graphics memory 16 GB Dedicated video memory: 8 GB Share system memory: 8 GB I'm attempting to run the macro on multiple JPG files. I'll be glad to send the macro, but I'm not sure where to find it in Windows 10. In AP, right-clicking on the macro only gives me the option to rename or delete it. Thanks, Nathaniel

Thanks stokerg. I tried a different approach. Prior to focus merging, I used the Info tab and notated the RGBA values at a specific, bright X,Y coordinate in the lighter version of the image. Then I opened the slightly darker version and increased Exposure bit by bit, checking those same X,Y coordinates until they were almost identical with the lighter version. Then I saved both images as TIFF files and did the focus merge. Any differences were indistinguishable and it worked great!

Affinity Photo Desktop. I started a Focus Merge, only to realize that the shutter speed was different in my two photos. Both photo A and B have ISO=800, f/5.3. However, photo A was taken at 1/160 and photo B at 1/100. Because of this slight difference, when I'm cloning using Focus Merge, the difference in light is evident along the edges. I'm thinking I'll need to edit one of the photos to match the exposure in the second before using the clone tool in Focus Merging. Questions: 1. Am I correct that I can't compensate for or match the exposure while Focus Merging? 2. If I do need to edit one photo first, any suggestions on how to precisely match the exposure between the two (other than eyeballing it)? Thanks for any help.

Re: Hubert's post... I found the crash reports, but they are DMP files and I can't find a way to view them. I've had two more crashes since then. One of them prompted a recovery when I re-opened Affinity Photo, but the other one did not. However, I was able to recover the one today from the Autosave folder. Still, the crashes are toublesome.

Running Affinity Photo 1.7.2.471 on Windows 10 with GeForce GTX 860M 16GB RAM. Intel i7 at 2.4GHz. I had been working in Affinity Photo on a specific photo for about 15 mins. I was almost finished when poof! Affinity Photo just disappeared. Gone. Not in my ALT-Tab list of applications. When I clicked on my taskbar Affinity Photo icon, it opened from scratch with a blank canvas. Aaaaaaagh!! Any suggestions, tips, or ideas to recover all my work? Or how to prevent this in the future? With Affinity Photo do I need to start saving/re-saving every minute or two? Thank you. BNat