Terrible aliasing and loss of detail began showing the last couple days when using NB Pro and NB 2 via api with img 2 img. If I use vertex through api the output is clean and perfect. I can’t use vertex because it’s too restrictive for rate limits. Is this temporary? Who else is seeing this? I’ve tried every single thing imagineable. I’ve re-written my config with every possible setting. I’ve adjusted my image to 2K with the most optimal resizing settings possible before sending it. Is there going to be an update soon to a 3.1 Pro that will give us a higher quality option? Why did we lose the quality to begin with?
As of today (2-3 days after it began happening) it’s looking like its back to normal. The lines are much smoother now and no more jagged aliasing. If anything some good came out of this because I was able to optimize my configuration better than it was before.
Well now I know why nobody else was seeing this. It has to do with my own workflow. I was converting from TIFF to JPG and changing the dpi from 300 to 350. I thought it was solely the dpi change that caused the issue but was my conversion from tiff to jpg that messed it up. Now don’t use the TIFF format at all in my workflow and it looks great.
The issue is back since about the 10th of March and it’s affecting seemingly everyone, even Ultra subscribers. Every single image, whether it’s an upscale, edit, or being generated from scratch, has these jpeg-style compression artifacts (aliasing, muddiness), to varying degrees, depending on which of the aforementioned things you are doing. You can even see it when you re-download your previous generations from My Stuff and compare side-by-side, with the same downloads, before this issue started. It’s really bad and it needs to be fixed.
I was wrong about the conversion being the issue also. It was just coincidentally not happening once i started doing that. It was happening intermittently since but i haven’t seen it in the past few days or so. When I tried it with Vertex there was no issue at all even with the Vertex API. It was only the NB2 api. I’m a Tier 3 api user and I believe it may have been happening when my workload was heavy. I think there’s a concurrency perhaps around 100 within a certain amount of time that was causing it to spend less quality time on my images. Or maybe that’s just me? Is there another forum discussing this somewhere? Is it still happening to some people? I did about 500 images today and didn’t see a single issue on the ones I personally looked at. I did also change my workflow to upload higher quality images which may be helping. I think the more compression your image already has the worse it comes out. I also include a step before sending to Gemini that pre-normalizes the images to 2K so that Gemini doesn’t do any downscaling before it modifies the image. I think that may be helping also.