Affinity revert picture quality on saving?

[VB_Art]

Hello, I quickly edited a photo, saved it, several times! trying to export it as .JPG but it get reverted to a wrong, darker version what I did NOT save. Please, see video attached. I’m on Mac Sonoma. 
I must be doing something wrong, but can’t figure out what

[thomaso]

What is causing the brightening that also affects the interface background grey at 0:02 to 0:03 min. + 0:06 to 0:11 min.?

[VB_Art]

Thank you for the fast response:  I’m totally new to Affinity, probably why, I have no idea what you are talking about. Please, elaborate. Thanks again 

 

[PaulEC]

What are you doing to make the image lighter? The odd thing is that the background gets lighter as well as the image itself!

[VB_Art]

I’been trying the Enhancement tools, just to figure the basics of Affinity P2. 

[PaulEC]

But in the movie, which tool did you use to make the image look lighter?

[NotMyFault]

We have other users reporting that image rendering gets erratic on newer macs, including window background surrounding canvas gets much lighter, but this will only be visible but does not get recorded on Mac itself during screen capture.

And if memory serves me well, it might be related to the Apple color profile, and images shot on iPhone.

 

 

[thomaso]

5 hours ago, VB_Art said:

I have no idea what you are talking about. Please, elaborate.

The brightening of the image together with the gray interface background appears quite like in the video of this thread which got tagged as a bug:

Note, in the meantime the bug's tag got changed by Serif from AFP-5662 to AF-473:

https://forum.affinity.serif.com/index.php?/search/&tags=AF-473

[stokerg]

Hi @VB_Art,

From the recording, this does appear to be AF-473 which is logged with the Developers to resolve.

If you click on the Affinity Photo 2 menu in the top left corner, select Settings.  On Performance change the Display from Metal to openGL, close Preferences and you'll be asked to restart Affinity.  Once restarted, try opening and editing an image and you should no longer get the flashing workspace  

[Affinity Info Bot]

The issue "M2 Mac flashing workspace - when using Apple Wide Colour Gamut" (REF: AF-473) has been fixed by the developers in internal build "2.3.0.2150".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[R C-R]

6 hours ago, Serif Info Bot said:

The issue "M2 Mac flashing workspace - when using Apple Wide Colour Gamut" (REF: AF-473) has been fixed by the developers in internal build "2.3.0.2150".
This fix should soon be available as a customer beta....

Isn't the current customer beta 2.3.0.2157 & thus already available?

[Old Bruce]

Good catch R C-R.

[R C-R]

17 minutes ago, Old Bruce said:

Good catch R C-R.

I think it is more that @Serif Info Bot is not being updated with the latest beta release info as quickly as it should be.

[NotMyFault]

42 minutes ago, Old Bruce said:

Good catch R C-R.

No. The Info bot message says 

has been fixed by the developers in internal build "2.3.0.2150".

Old bruce says:

isn't the current customer beta 2.3.0.2157 & thus already available?

Yes. Both are unrelated. The is no catch or contradiction. The bug has been fixed, and Affinity published another Beta later probably with additional bug fixes. 

[walt.farrell]

12 minutes ago, NotMyFault said:

No. The Info bot message says 

has been fixed by the developers in internal build "2.3.0.2150".

Old bruce says:

isn't the current customer beta 2.3.0.2157 & thus already available?

Yes. Both are unrelated. The is no catch or contradiction. The bug has been fixed, and Affinity published another Beta later probably with additional bug fixes. 

There is a contradiction, in that the post by Serif Info Bot  7 hours ago says that the fix "should soon be available" in a beta, but it has been available for several days now.

I suspect in the process of posting the updates, which I think may be somewhat manual, someone posted the wrong insert. I think I've seen such messages that say "the fix is now available", and perhaps someone just picked the wrong version of the message.

The staff is very busy right now as they get ready for the 2.3 release, and post updates on the status of the problems that have been fixed.

[R C-R]

11 minutes ago, NotMyFault said:

Old bruce says:

First, it was I that said that, not Old Bruce.

12 minutes ago, NotMyFault said:

The is no catch or contradiction.

The contradiction is that @Serif Info Bot says:

Quote

This fix should soon be available as a customer beta ...

But it already was available well before the post was made, & the referenced beta build isn't even the most recent one that is available.

[NotMyFault]

The info bot uses a generic text template to keep this shorter than the package insert or typical terms and conditions of insurance policies.

It want to express the earliest version which contains the fix, even if that beta is not yet published. Naturally, a later beta with higher version might get published. The info bot does not inform about the actual availability of a certain beta version.

But I accept your point.

[EmT]

Hi @R C-R 

As you may be aware @Serif Info Bot is a bot that will automatically post a generic pre-determined message on forum posts when the tagged bug ticket is closed.
It works with minimal human interaction, which is great for passing along the information in real time, but it does mean that on occasion the content may not be grammatically accurate. 
We are always looking to improve our processes, so it may be one day that this no longer an issue. However I hope this explains why the bot is sometimes making these odd posts. 

In regard to this bug, it is accurate that the issue was fixed in build 2.3.0.2150, however the post should say it is available in the current beta.

[R C-R]

5 hours ago, EmT said:

... but it does mean that on occasion the content may not be grammatically accurate. 

OK, but please note for future improvement that it is factually inaccurate, not just grammatically inaccurate, because it says the fix should soon be available when in fact it already is, in this case for around 4+ days.

[Patrick Connor]

14 minutes ago, R C-R said:

OK, but please note for future improvement that it is factually inaccurate, not just grammatically inaccurate, because it says the fix should soon be available when in fact it already is, in this case for around 4+ days.

We know! we can read and understand

[R C-R]

3 minutes ago, Patrick Connor said:

We know! we can read and understand

Well, I hoped that you did but it was not clear from the "on occasion the content may not be grammatically accurate" comment if it was so I just thought I would mention it to make sure.

[EmT]

@R C-R 
Thank you for your input but I think we're all on the same page here and this is beginning to detract from the original point of this thread.
If you do have any further suggestions for the Bot then it may be best to create a new thread in the Beta Software Program Members Area