P: Photoshop Beta Generative Fill produces different colors at the edges of the selection.

[Nehsa]

When trying to add additional areas to the edges of an image using Generative Fill, it creates mismatched colors at the junction of the new and existing parts. It deviates slightly from the original areas, resulting in a grid-like pattern in those areas where new parts were created using the Generative Fill option, even if I fill them with 1024x1024 pixel sections.

I have already uninstalled the app and reinstalled it, but the issue persists. I am using an iMac Pro running Ventura 13.3.1 system.

Photoshop Beta 24.7.0

[Silverbackstock]

Thank you , I rarely use an sRGB format (setting)  ,  I need to print my work so I work in 16 bit RVB . It is true this bug a has just walked over the best tool in Adobe,

[Leonardvv1]

You can keep your file in your preferred profile. Just setting the sRGB colorspace in photoshop is needed for getting the colors to match.

[defaultj7p2fi32ypbo]

Idéalement, j'aimerais ne pas avoir à travailler en CMJN... Est-ce que c'est possible? 

[PantheraStudio]

My color space is already on sRGB and it is still not matching

[Silverbackstock]

However you. have to go back into RVB to access the filters, such as CAMERA RAW and liquefy. So while the CMJN is a fix, it is not really an option in the long run.

[Leonardvv1]

Check that sRGB is set in Photoshop and not your file? And it does not turn allready made content to match just the newly generated content. If it still does not work try the standard color preset Europe general purpose 3 as maybe other settings might interfere and open and close the program and try again. Also I am on a mac and on the latest version of the Beta.

[christopheb35290502]

J'ai exactement la même chose depuis la dernière mise à jour, alors que tout se passait bien en RVB avant. Avez-vous trouvé une solution ?

[Leonardvv1]

A tip to make a generative content layer match color that was allready created:

1. Duplicate the mismatching generative fill layer and rasterize the duplicate layer.

2. Make the rasterized version of the layer into a smart object.

3. Open the smart object and convert it to sRGB, then assign it the color space the original document is in.

    Save and close the smart object window.

Now your color should match, only sometimes contrast is not perfect and might need a tweak.

[cedric fahy]

same problem

[cedric fahy]

 

[Jiri31574162k5gw]

Unfortunately, the update to 25.1 has just arrived and this bug is unresolved...

[Roberto30228320wb6i]

ciao sto riscontrando un grosso problema con le ultimi due aggiornamenti di Photoshop Beta. qualsiasi variazione sull'immagine crea dei colori che mal si fondono con l'immagine, ad esempio se copro un buco su un petalo di un fiore....tutta l'area generata ha un colore diverso dal contesto. stessa cosa se vado a modificare qualche cosa su una persona ad esempio il colore della pelle risulta diversa dall'orgininale lasciando una macchia visibile dove è avventuta la modifca.

versione photoshop 25.1.0

OS version: macOS Ventura 13.4.1

[Fréêèd2447816358ym]

j'ai aussi ce même souci.

[Nehsa]

It doesn't works to me. My original file is sRGB, and the smart object too. So nothing changed...

[Leonardvv1]

Hi Nehsa,

You are on a bit older version of the beta.

So to rule that out as the problem, if you upgrade to 25.1.0 and set that version of photoshop up with the "Europe general purpose 3" colors and start generating new parts for an image, does it work correctly then?

And if not, does it work correctly for generating new content after resetting preferences?

[kévin31975285d115]

I did the last update and since then I see a colour demarcation when I want to delete an item with the AI.

Do you have any solutions for correcting or reversing this?

Thank you.

[CShubert]

Hi everyone, for those of you with this issue, some questions:

1. Is your image 16bit?
2. How are you getting the image into Photoshop?
3. In Photoshop what is your working RGB space in Edit/Color Settings
4. In Color settings/ Conversion options which color engine is being used, and what is the rendering intent set to?
5. Can you grab a screen recording of the full session, and full application window of the issue happening?
6. Do you have a file that you can share that shows the problem?

[marcov4494512]

Hi there, i have a problem with PS Beta 25.0. I try to work with Generative Fill to remove object and result is not perfect. Look the example: 

[marcov4494512]

UPDATE \\ I open NEF file from LR to PS Beta v. 25.1. I assign sRGB profile to image then i use Generative Fill ... file is perfect without problems of colors. Then i convert in RGB and is all OK.

The problem is work in RGB?

[andreaa70348403]

Ciao, 

mi aggiungo anche io al proble in corso. Dopo la versione 24.7 che funzionava benissimo sono iniziati i problemi. Vi allego un parte di immagine dove si vede nettamente il problema. La parte generata è completamente diversa da come dovrebbe esere in base allo sfondo.

[andreaa70348403]

[Hélène3177918396zq]

Hi @CShubert , 

1) Images are 16 bits 
2) I open the image from lightroom (right clic on the picture to access it)

3) Screenshoot will show you the settings (sorry, it's in french)
4) Conversion options are in second screenshoot. No rendering intent, I never changed those parameters. 

5) for the video recording, it will be complicated to have it today... 

6) what kind of file do you want? Original file? Modified file? Exported from lightroom or photoshop? 

Thanks, 

Helene 

[andreaa70348403]

Ciao,

con queste impostazioni finziona!!!

[Nicolas32018124q3n7]

When we open an image from Lightroom classic 12.5 to Photoshop Beta 25.1 which is prophotoRGB profile, it doesn't give accurate results with Genrative AI in PS beta.

We have to supress the colour profile and then open the image in PS beta to make the generative Ai results work.

Please look into this bug and help with getting this fixed.

[Nevedu32018501euzc]

Hi Cory, version 24 didn't do it, but I know for sure that the problem is not in the PC but in the update, because of that I wanted to terminate the membership myself.
I hope you fix the bug soon and it will be normal again like in version 24.