u/ApplePicker99

I promise to tie this into Venice, as I'm a prospective Venice user and the knowledge base here in this sub when it comes to Seedream 5.0 is the best I've seen.

I've been noticing that making repeated edits to an image in Seedream 5.0 Pro Edit gives me a progressively more overexposed, washed out, "overbaked" look. Images 1-6 are the original image followed by 5 slight edits, rendered in Atlas Cloud and it's easy to see what's happening. The interesting thing is, images 7-12 is the original image followed by the exact same 5 edit prompts, still in Seedream 5.0 Pro Edit, but run in Fal.ai. Still progressively more washed out and overexposed, but not even close to the level of the Atlas Cloud renders. If you compare image 6 and image 12, it's a day and night difference, yet that's the 5th edit run (with the exact same prompting) in each service.

I figured the increasing overexposure and washed out look is just baked into the model the more edits you perform on an image. But apparently the API service has a lot to do with it as well. If anybody feels like testing this on Venice, I'd love to know if this is more or less pronounced on Venice. Images 1 and 7 are the original (same image).

I understand (and apologize) if this needs to be deleted since it wasn't generated in Venice.

First image was made in GPT Image 2.0, then I used it as a reference image in Seedream 5.0 Pro Edit and generated pretty much the exact same scene (I added a poster and a necklace). This is my workflow for all my content.

As you can see, the second image (the Seedream one) is noticeably brighter, washed out, higher exposure etc, however you want to phrase it. And then once I start making edits to THAT image in Seedream, it gets progressively worse.

I have a very lengthy, detailed prompt that I use for all my renders explicitly telling it NOT to brighten, lighten, white out, wash out, or overexpose the image. Preserve skin tone, color scheme etc. Yet this is always what happens with Seedream. Any suggestions or observations. Has anyone else experienced this? Or is it just a quirk of Seedream that I'll have to live with? (it also slightly widened the image even though they're both rendered at 9x16)

First image was made in GPT Image 2.0, then I used it as a reference image in Seedream 5.0 Pro Edit and generated pretty much the exact same scene (I added a poster and a necklace). This is my workflow for all my content.

As you can see, the second image (the Seedream one) is noticeably brighter, washed out, higher exposure etc, however you want to phrase it. And then once I start making edits to THAT image in Seedream, it gets progressively worse.

I have a very lengthy, detailed prompt that I use for all my renders explicitly telling it NOT to brighten, lighten, white out, wash out, or overexpose the image. Preserve skin tone, color scheme etc. Yet this is always what happens with Seedream. Any suggestions or observations. Has anyone else experienced this? Or is it just a quirk of Seedream that I'll have to live with? (it also slightly widened the image even though they're both rendered at 9x16)

I have tried everything I know how to do to prevent the images from progressively taking on that more washed out/overexposed tone. I'm super careful and detailed with my prompting to maintain her natural saturated skin tone but Seedream 5.0 seems to inevitably just add to the exposure and washed out tone and reduce the saturation over repeated generations.

I have tried everything I know how to do to prevent the images from progressively taking on that more washed out/overexposed tone. I'm super careful and detailed with my prompting to maintain her natural saturated skin tone but Seedream 5.0 seems to inevitably just add to the exposure and washed out tone and reduce the saturation over repeated generations.

I have tried everything I know how to do to prevent the images from progressively taking on that more washed out/overexposed tone. I'm super careful and detailed with my prompting to maintain her natural saturated skin tone but Seedream 5.0 seems to inevitably just add to the exposure and washed out tone and reduce the saturation over repeated generations.