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.

[tl78737245]

Thank you. Yes it is possible to expand on the selection and get some results but the muscling of the horse in this area (where the base of it's neck meets it's chest) are pretty specific. It would be nice if the simple task of removing a rope could be achieved.

[daniellei4510]

I hear ya. Gen Fill is a long ways from being perfect at this point and I suspect that there will always be (for now, at least) a need to use traditional editing tools to fix what Gen Fill doesn't. I have found this to be the case for all AI programs, even the best of the line. 

[positive_yogi98A4]

See attached image. Just want to clear the arm so the shadow of the horse is complete. So no violate guidline was violated. Got this alot. Also when I am just working on a horse to get rid of some line.

Not (yet) good Adobe.

[tl78737245]

Prompt "remove person" might help you here. 

[hectorgomezcreative]

I get this error in most of the generative fills with people/models.... I think Adobe is trying to protect themselves from creating NSFW images but it's taking it to absurd extremes...

[daniellei4510]

I know this does nothing to fix what appears to be a bug, but may I suggest going the old-fashioned way? I selected the horse's nose, copied it, pasted it, turned it black, and gave it a little blur.

[Graham24508943nobd]

I've had heaps of NSFW images generated. Adobe needs to look at their own stock first

[J.C. Scott]

You know, it would be great if I could use Generative AI, but in the last few days, it's become almost unusable for my needs. Attempting to fix anything attached to an individual results in a violation notice most of the time. For God's sake, Adobe, do something about this. I realize it's a beta, but this issue is getting worse.

OS: Windows 10

PS Beta: Current version

[daniellei4510]

It would be helpful if you could show us what you are trying to accomplish. Generative Fill is not and will never be the be all and end all of editing in Photosho, even when it is out of beta. I've seen so many instances where edits could have been accomplished with tools that have been available in Photoshop for years as well as more recently. 

[J.C. Scott]

It would be helpful if you could show us what you are trying to accomplish. Generative Fill is not and will never be the be all and end all of editing in Photosho, even when it is out of beta. I've seen so many instances where edits could have been accomplished with tools that have been available in Photoshop for years as well as more recently. 

By @daniellei4510

This is one of many examples. I generate AI art, and my use case is often defect removal. For this particular example, I could use something like Content Aware Fill or simply fill it in manually, but the former doesn't do the job as well as it could, which leaves some cleanup, and the latter would take a lot longer than using Generative AI.

Another example:

[daniellei4510]

I entered a "." as a prompt and had no problems. 

[J.C. Scott]

Great, but that doesn't resolve the issue, and it's obviously an issue. I didn't fabricate those images.

[daniellei4510]

I didn't suggest that you did. Point is, it's been shown here numerous times that adding a period often (though not necessarily always) fixes the issue. And until the issue is finally resolved, it's worth trying.

[J.C. Scott]

I'll definitely keep it in mind and give it a try next time.

[fanceygirl]

I have been using Photoshop Beta for the last few days with no problems but today I was editing a photo of a wedding. The Bride and her mother was in her bedroom as there was good light from the window however a part of the bed was in the photo and I tried to remove it with the generative fill and it gives me a message saying I am in violation of guidelines. I don't understand. there is no nudity or terrorism or violance..Just a bride and her mother and the part of a bed, which I want to remove.

[PictureArt]

For photographers in the field of portrait and nude photography, the new program is no longer usable, as the guidelines restrict too much. The idea is good, but you can't make art in the areas mentioned anymore!! As a photographer, I depend on working with bare skin.

Sincerely, Steffen Schiller

[RicardoTM05]

I know the guidelines, and I think it would be a good idea to have nudity filter as a preference instead of a violation to the guidelines for the final product.

I know a lot of us work with nudity and it's extremely annoying that we are getting an insane amount of guidelines violation messages when working on those pictures, even if we want to only change things on the background or props in the scene.

I also find amazing to be able to change models outfits, but there are a lot of times we work with transparent clothes (nudity again) and when trying to generate more options it will always throw a violation message, or if it works the transparent parts will be deleted, which is not really helpful.

I think that this software is directed to adults doing professional work and not kids wanting to generate perverted things. While I understand that problematic, I think that the focus should be mainly on the professional side.

So, having nudity as a preference would allow professionals to activate it and have better results and thus a better experience while working, and those who don't need it can keep it deactivated so they don't get any explicit result when working.

[defaultyfp7chz9kt23]

I have to say that beta version 25.0 is a complete mistep in terms of functionality and versatility, so much so that I resorted to using version 24.7 which I believe was the best iteratio . Unfortunately as of today August 14, 2023 generative fill can longer be used with version 24.7. This crusade to arbitrate the moral landscape in creation has become too authoritarian in my honest opinion.

[defaultyfp7chz9kt23]

Also worth noting. the placement of the trashcan on each generative thumbnail is poor. I have already accidently deleted many renderings. Thank goodness for crtl or command Z.

[Meital31671089a8l2]

The generated imeges were removed because they violate user guidelines.
I cant use the ia of photoshop, i work with artistic nudity and it gives me error when i just want to generate a background, I dont know what else to do.

[jane-e]

@Meital31671089a8l2 

Generative fill is in beta, not in the released version. I've moved your post to the Photoshop Beta forum for you.

Jane

[artstuffstl]

Things are a bit prudish, Adobe! I agree with the above!

[RLeintzPhotos]

I keep getting a guideline violation over and over when trying to work on skin retouching? Is this a real violation or a bug? 

[paula45587034]

i decided to look at the option of re-installing Lr and/or Ps Beta since the update of Ps Beta caused all these glitches. 

*i also noticed that Lr's external editor default was set  to Ps 2024 with no option to select Ps Beta.

i opened Adobe CC and saw that neither Adobe Ps nor Ps Beta was listed under the installed apps.

i installed Ps 24.7.0 and everything is now working fine (sending files to/fro Lr) and i now have (at least) the use of the Ai Remove tool.  

i am looking forward to using the generative fill tool sometime soon.

[RLeintzPhotos]

@CShubert @Pete.Green I'm a boudoir photographer, so yeah, the images that I work on are semi-naked women. Is that why I'm getting the flag? I'm making a section of skin (usually just the skin and no other body parts) and typing in "remove wrinkles and marbling" it was working fine for about 2 days, now I seem to get the violation everytime. If I close PS beta and open it again, it will still give me the error but generate one variation.