P: Generated images violate user guidelines

[Hematita]

So as you can see, it's a PG-13 relatively inoffensive image of a woman in a bunny outfit. The top worked fine, and I was able to complete the top ear, which is cool. When I tried to extend the bottom with generative fill, though, I got this warning. They're just a pair of legs wearing stockings, and I wanted to extend it.

It feels like a false flag - though I could be wrong? I find myself thinking it would do the same for women in swimsuits.

Figured I'd share here.

[Preston29196145tevi]

I wish I could clone myself just so I could feed my clone images to send to you about your broken Gen Fill Restrictive Guidlines. But alas, I only have so much time and you are already wasting enough of it.  This is too absurd to not send.  All night. long for my session, leaving gen fill blank results in 100% no render and your annoying restrictive guidlines window.  It doesn't work at all. It is absurd that a company your size let's this go on.   You are way below the standard for beta software.  This is an alpha problem. I wanted to add a 24k gold henna tattoo necklace on an elephant.  See below:

And guess what?  Voila!

Violation!!!!!  Please for the love of God tell me why this violates your guidlines?  Why?  I have fought this all night long guys.  There are really only two options here.  Either your engineers have made really bad code and your AI is not smart enough to run your guidlines parameters or you are doing this on purpose to be really really really really conservative.  Both answers are not good.   I beg you, please fix this. 

[georger2369527]

I keep getting the guidelines violations warning when i try to use generative fill (without a prompt) even though i'm only working on a picture of a piece of fabric

[Preston29196145tevi]

Here we go again, wasting users time.  For the love of God when are you going to fix this?  Seriously, I wonder if Wired Magazine would be interested in a story about your debacle

[Kenneth259883092lw8]

More and more I'm getting this message come up when I'm doing very simple things like removing people or objects from the edge of frame with generative fill. Today it won't even extend a black curtain without giving me this message, what could it be possibly generating that would go against guidelines when it's a black blob? It's almost becoming a useless tool because I'm forced to manually remove these things. So much promise but it's hampered by these stupid messages.

[FitzFoto]

It appears that this might be a bug, rather than a "violation".  Restarting PS enables generation without error.

But even simpler, is typing a fullstop/period ( . ) in the 'What would you like to generate' box.  Voila!  No error message.

[Kevin Stohlmeyer]

@georger2369527 this has been well documented in here that leaving the prompt blank is a known issue that can cause false flags. Adding even a period to the prompt improves results.

[Timfl]

Updated to 24.7 and ran generative fill again on an image that was causing the error. The error returned, but the fill was completed. Thank you Adobe.

[Preston29196145tevi]

Just wanted to add that 24.7 is working a little better, I made it half way through an image with no red flags on leaving prompt blank.  It was like heaven :). They still came back but it wasn't waterboarding and they all resolved themselves pretty easy

[Kevin Stohlmeyer]

Hi @Preston29196145tevi first - please keep things civil.

Second, as with any AI there is going to be a learning curve for users to write effective prompts that can give you the best results.

In your first examples, as documented heavily in here - leaving a prompt blank leads to false violations.

I took that example and entered "smooth skin" I did not get a violation and had some good results - no violations.

In your second post it's most likely in your case it is the word "henna" - the Generative Fill AI is using English only words at this time. I was able to take your example and create a result with "ornate gold tattoo" and again got results with no violations.

Keep in mind if you find this process so frustrating to the point of ranting on a forum, perhaps take a break and don't participate in a beta test for a bit.

[Preston29196145tevi]

Ooops, spoke too soon.  Literally my first render upon opening the project.  Left it blank and selected a tusk and got the window

Gonna be a long day....

[Preston29196145tevi]

Hi Kevin,

Sorry for being blunt, I will try to channel that into more constructive dialog.  You have to understand how maddening it can get trying to work with Gen Fill at this point.  Last night 100% of the time if I selected something and left it blank it wouldn't render.  That is unaccepatble.  My tone is always very direct though and I feel the need to be so with the response.  The point of all of this is to use it and not have a ridiculous thing impede workflow.  I can appreciate that things worked for you but it doesn't work for me.  The larger point is that somehting is broken in the Gen Fill code that is causing really bad amateur type errors.  Please look at this through the end users eyes.  Why does it most of the time if I leave it blank, give me guidlines window?  It shouldn't do that even in beta software.  I hope you guys are taking it seriously and not just going,"Well, it worked for me so it isn't a problem."

[Kevin Stohlmeyer]

Hi @Preston29196145tevi level set - you do realize you are voluntarily participating in a beta test phase for software correct? Constructive dialog is always welcome and helps move the progress forward. The software will get better but understand this is the first instance of Generative Fill AI in Photoshop. There is going to be growing pains. But also if this impedes workflow so much (keeping in mind this is only to be used for non-commercial work) - you always have the option to stop testing and move to the general public release to do your work. No one is blowing off replies in here and the team is monitoring.

The blank issue has been noted so much in this and other threads that at this point I would personally consider it user error if someone posts "I left it blank and it gave me an error" without reading the thread they are posting on.

I'm certain this and other errors will be addressed well before this is finally released to the public in a new version of PS. But at this point hammering the same issue over and over in a rant does nothing to help.

[Timfl]

Well said, Kevin. A year ago, none of this would have been possible! 

[Kevin Stohlmeyer]

Hi @Kenneth259883092lw8 are you entering any values in the Generative Fill prompt?

[Abhishek Ravi]

Use Any One Latter in Prompt Like . Dot and Generate... Thats Problem Solve

[tom061201]

Hello,

I'm writing to you because I've been having a problem since today (haven't used the beta version of Photoshop for a little while).

Many times when I try to AI-generate an image on top of another one of mine, without even entering any text, I get an error telling me I'm doing things against Adobe's policies. Except I don't generate anything illegal because it's just stone textures, moss, etc... which for once is quite unpleasant because there's no reason why it should prevent me from working.

I can tell that I am on the latest version of Photoshop beta (uploaded today, July 23, 2023), that I'm on Windows 10.

Looking forward to your potential feedback or improvements,

Tom S.

[jjaylad]

Hi there,

Editing a very crowded wedding. Found it impossible to get unobstructed photos of guests, so have been using Lightroom's remove tool where possible then flipping the image to PS Beta to do the rest. 

I am getting incredibly frustrated with Generative Fill, On 70% or more of the attempts I've made I get the 'violates guidelines' error. I get that when trying to remove people's heads which are right in the lower center of the frame like this one. This is cropped to about 20% of the frame. 

The policy doesn't really explain to me why it is a cardinal sin to remove an out of focus, overexposed face from a photo. I mean GF works great when it does but in cases like this I have to find other photos of tables with similar content and composite the image.

I think it's time for Adobe to have a tune up chat with Cardinal Dontletemdoit. He is far too conservative in making a sin out of doing this. I'm almost to the point of not even trying to use GF because it literally won't let me remove a spooky hand reaching into the frame and touching someone's shoulder.

Clone stamp, Spot Healing, Content Aware Fill etc. all work on those things and I absolutely do not understand what the problem is with Generative Fill. Is this just something they want to show off but don't really want us to use?

On that image I used Content Aware fill, which obliterated the head then I deselected all but that layer and ran GF after selecting the messed up area. 

Despite the fact that there are now no heads or body parts or Nuclear Codes ,,,I still got the same message:

This is completely NUTS!

[NickXVega]

Whenever I try using generative fill on a picture with a woman in it, it says it violates community guidelines. I have tried editing a very similar picture with a man and it works fine. I know the woman who was used for the picture and she said it is okay for me to edit them and use them, I am only trying to increase the canvas size by using fill on the side portions. 

[mrvoices]

Generative Fill is currently over-zealous in "censoring" image repairs. I understand if it cannot properly recognize a body part (i.e. an elbow) or mistakes it for something else which it deems might be offensive.

But, just now, it blocked and warned me when I was trying to remove a stained area from a jacket lapel?! If there's no workaround, please put me in touch w/ engineers for whom I can demonstrate the problem.

[Kevin Stohlmeyer]

Hi @NickXVega read this thread. Adding properly worded prompts, not leaving the prompt blank, etc. can resolve false flags.

[Graham24508943nobd]

as has been mentioned many times, try using a period ( or full stop for UK users ),  in EVERY generative message, even using that in a blank space stops 99 % of the stupid guideline errors.

[jjaylad]

Thanks for the reply. Big Ai Brother is definitely watching us. About an hour after my post, I was on YT, on nothing to do with this and was prompted to watch a video by Unmesh Dinda in which he demo'd putting a period (full stop) in the box. For sure Google is aware of every beat of our hearts! 

Anyway, late last night I tried it on several images I'd given up on, and it works great!

Thanks again. Great to know the answer would have surfaced here if G hadn't been eavesdropping and taken the situation in hand.

[Graham24508943nobd]

The admin should pin this info everywhere on the Beta pages. Might stop a lot of people giving up completely

[E250916993jnw]

Using the period option definitely is working as a work-around for the time being. I was skeptical that it would work but it is in fact working.

And now that I'm not getting constant errors I can finally see the power of this new tool. It is like turning photography into magic. Quite astonishing. And it even works on illustrations as well. Completely blows content-aware fill out of the water without question.

[NickXVega]

Turns out, just putting a black square over the centre of a person also allows it to work.