Issue when I'm exporting: The photo get overexposed

[Christian Lavin]

Hi

This issue comes when I'm exporting my photos.

- Firts I began with my raw files (from a Sony a7iii).

- The final jpeg file it's getting overexposed all the time.

- Also when i create a screeshoot, the screeshot get overexposed but I'm wathing details in the affinity program.

 

In my mac using affinity photo i can see details on my baby skin.

 

[walt.farrell]

When you Develop, are you Developing to RGB-16 or RGB-32? That's a setting in the Develop Assistant. You can check it by clicking the Assistant icon on the Toolbar, or opening Preferences in Photo and clicking on Assistant. If it's set to 32-bit, you should probably set it to 16-bit and see if that helps. If you're already in the Develop Persona you'll need to close that image and start over with it from the RAW file.

[Swingnsaxman]

I'm on a Mac M1 that's well upgraded. When exporting HDR photos a few periodically come out over exposed. I have redone the photos, made all my edits and then to have it ruined is really frustrating. I have searched many hours all over forums and videos for this issue and I can not find a solution. If I can't figure this out, I can't spend hours beating my head against the wall, I am going to have to accept my loss of Affinity Photo as a software investment, trash it and utilize another platform. I also wasn't expecting that another version would come out that we need to pay for. This exporting issue shouldn't be an issue, I have never had that with Photoshop.  

[Ron P.]

6 hours ago, Swingnsaxman said:

I'm on a Mac M1 that's well upgraded. When exporting HDR photos a few periodically come out over exposed. I have redone the photos, made all my edits and then to have it ruined is really frustrating. I have searched many hours all over forums and videos for this issue and I can not find a solution. If I can't figure this out, I can't spend hours beating my head against the wall, I am going to have to accept my loss of Affinity Photo as a software investment, trash it and utilize another platform. I also wasn't expecting that another version would come out that we need to pay for. This exporting issue shouldn't be an issue, I have never had that with Photoshop.  

Hi Swingnsaxman,

Do you have a question, wanting help with over-exposure, exporting, or just making a statement?

Could it be, you actually over-exposed your image? You certainly know that doing so, the data is gone, no way to recover it. Also I think you really mean by your statement about "can't spend hours beating my head against the wall", you can't be bothered learning another software. You spent time learning Photoshop, a lot of time. PS is not an easy piece of software to learn, very complex.

I agree that there shouldn't be an issue with exporting. Are you using version 1 or 2 of Affinity Photo? You do know the Develop Persona is now non-destructive, so long as when you develop, you have the Output set to either Raw Embedded or Raw Linked. You can take the image right back into the Develop Persona and make changes. They're not baked in until you choose to rasterize the image. Can be really helpful when the exposure needs tweaking.

Yes there are problems still with Affinity apps. Serif is working on correcting the bugs. If they had 1/3rd the staff of Adobe, they would have them corrected by now. Since they don't, it takes a lot more time. Granted, some of the bugs have been around for way too long.

Photoshop, Affinity, On1, Lightroom, ect, are just tools. Use the one(s) that will get the job done for you. You ever work on cars? If the wrench you pick up does not loosen or tighten the bolt, might be the wrong size, do you just keep trying to make it work or grab another that will?

[Cepera]

It is November 2023 and the bug seems to be still there. I have exactly the same issue with the export. If the exposure correction layer is applied, then even mild corrections below 1EV yield jpg output of a quite-normally-looking image extremely overexposed. I use Affinity Photo 2.1.0 on Mac M1 / Sonoma. Frustrations of Swingaxeman are quite understandable to me. One thing is to learn new stuff, yet another is to work as a beta-tester for free, while nobody takes a note. 

[walt.farrell]

42 minutes ago, Cepera said:

It is November 2023 and the bug seems to be still there.

None of the users in this thread seem to have followed up to help determine if there is a bug or figure out what it is.

If you believe there's a bug, I encourage you to create your own topic in the Bugs section of the forums, provide sample files, and work with Serif and the users to figure out what's happening.