[Resolved in v3.1.0] - Recover Faces tool issue with lighting and Balance color

When having face recovery together with lighting adjustment and color balance faces seem not to have all same filters applied as other parts of an image. There is also a specific rectangle visible from the face recovery processing step.

Steps to reproduce issue:

  1. Enable face recovery
  2. Enable adjust lighting
  3. Enable color balance

face-color-bug


Topaz Photo AI v2.4.2 on Windows

1 Like

I have not been able to replicate this on my machine with a few different images. Would you mind sending in some more information to get a better understanding of the problem you are having with this particular type of image? Please send the following information:

  1. The original image file.
  2. The processed image.
  3. A screenshot or description of the settings panel so I can see what adjustments were turned on.

You can securely submit your image(s) to my Dropbox using the link below.

Dropbox File Request

Please be sure to send me a note to let me know you sent something.

I have uploaded all requested files.

Thanks for sending in those files, I was able to replicate this problem you are reporting on my machine. I have reached out to some team members to see if we have any more information about this problem. In the meantime, I did notice that if you were to adjust some of the settings by lowering the Adjust Lighting feature this artifact seems to not be present.

1 Like

Thank you for your help. I’m looking forward for more information.

Hello I am having a very similar issue, without using Color Balancing. When I do face recovery, and then use adjust lighting, it looks perfect in the preview, but when saved the adjusted lighting is not used for the face. You then get a cut off line around the neck area and a darker (or lighter!) face than the rest of the image.
It looks fine in preview, but once saved, and click on close to return to the image, the preview then updates with the error and shows the incorrect lighting as per the saved file. I need to remove the adjust lighting layer entirely to resolve the issue.
To recreate, make sure you save after adjusting the lighting level. My images are pretty much always auto upscaled if that helps.



Thanks!

1 Like

Hello, i’m also having this issue. Very Frustrating . Applied face recovery, sharpen, remove noise, color correction, adjust lighting. Everything applies correctly until it does adjust lighting

2 Likes

Have you completed the output? I noticed that if you make some changes it will look okay in the preview window, but if you save the image it displays improperly with the boxes over the face.

Here is how it looks in the preview

here is how it saved

Our developers are looking into this issue that some users are reporting. I can assure you that they are working hard in order to address this issue in upcoming releases.

1 Like

Here’s an issue with Face Recovery that I’ve reported on with sample since 2.4.2, and it’s still not resolved. It has to be the model itself as the symptom actually follows the rotational angle at which the face object sits in the photo. I’ve been easygoing and almost nonchalant in my report as I didn’t think it would take so long to fix. Not anymore. It’s no longer fun to try an work around it. Image has be artificially brightened to make the fault more evident.

I’ve stopped using PhotoAI, and will stick with old tools until this can be resolved.

Steps to reproduce issue:

  1. Open photo
  2. Run Face Recovery as an optional enhancement
  3. See result.

PhotoAI as a hobby has become no fun anymore.

Steve

Topaz Photo AI [v3.01] on [Windows]

2 Likes

Would you mind sending in some more information to get a better understanding of the problem you are having with this particular type of image? Please send the following information:

  1. The original image file.
  2. The processed image.
  3. A screenshot or description of the settings panel so I can see what adjustments were turned on.

You can securely submit your image(s) to my Dropbox using the link below.

Dropbox File Request

Please be sure to send me a note to let me know you sent something.

Hi John - Thank you for the response. The files have been uploaded per your instructions. The PNG is the source, 8-bit. The target is exactly how it came out of PhotoAI 3.01.

As far as the “settings panel,” there’s really not an ‘image’ per se. I open the image. Add the 1st enhancement, like “Adjust Lighting” or “Balance Color.” I’ve done this same process enough times to KNOW that the problem is introduced when I use the “face recovery” option. I loaded the original source pic, and ran “Face Recovery” first, then “Adjust Lighting” and lastly “Balance Color.” The anomaly is there. Here’s a partial screenshot of my workspace at this very moment.


The light-difference band upper neck, just below the chin is very apparent.

I went back to the workspace, and “X’d” out the “Face Recovery,” effectively cancelling it.

The workspace NOW:

It’s weird. If the face were at a jaunty angle , the change-in-luminance line would be a close match to the base angle of the face at that moment - always at the neck, near the chin, but below.

Thanks,
Steve

Addendum - This ongoing journey is so fascinating. To see how the model perceives the images it’s working with.
Combined original resolution screenshots of what could be part of the genesis of this anomalous behavior.

On the left side, the model sees two faces, and on the right, the result, but this time with a “halo” on the left side of the subject’s face. Screenshots and the original were uploaded to John’s drop site.

[Please describe your issue here. Try to include logs (Help → Logging) and add screenshots if necessary.]
Artifacts appear when Upscale is set to 1x
Steps to reproduce issue:

  1. Step 1: Open B/W photo in Topaz Photo AI 3
  2. Step 2: Apply Denoise+Face Recovery+Adjust lighting
    NOTE: I was testing different upscales. Finally, I decided to leave it the same size, so I left upscale in 1x.
  3. Step 3: The result shows artifacts on all faces.
  4. Step4: If I remove “Upscale” from the workflow, it works as expected.

See attached example,



before and after processing sample.
Alex.-


Topaz Photo AI 3 on Mac

1 Like

Please send me your system profile information so I can check if your computer hardware is up to date.

You can securely submit your files(s) to my Dropbox using the link below.

Please be sure to send me a note here to let me know you sent something.

Hi John.

Here’s the system report, zipped.
Thanks,
Alex.-
iMac-Report-supergather.zip (414.8 KB)

Hello, Topaz team. I’ve stopped using the product in any ‘production’ capacity as I never know in what photo this “model”-behavior will appear.

My concern is that I reported this bug on March 13th, and here it is already May 20th. Updates have come out, and from appearances and my experiences, no further progress has been made on this issue.

This implies to me that the issue is still not fully understood and that no remediation plans can be completed until more about the phenomenon is known. You cannot fix what is wrong if you don’t know what the problem is.

Is reproducibility an issue? When one of my reports was combined with another with the same issue, I was excited that the issue was experienced by more people than just me. Is there model-operational logging? Verbose? If there is, can we turn it on, or does it need live debugging with display processes from the video subsystem debugger out USB to another video terminal? Does debugging like that even exist?

Does the issue occur only with NVidia hardware/drivers? Does AMD’s ROCm display system experience the same issue, or is this a CUDA thing?

I’m not a gamer, so I don’t give a rat’s axx whether I use AMD or NVidia (though it could be an issue to switch just because of the cost of the cards); I just want this issue to be resolved and am willing to allow debugging on my system (outside work hours - I WFH).

Thanks,
Steve

1 Like

I received an email with an invitation to continue participating in the long-lost Beta for PhotoAI. This time, the version is 3.0.3.0b.

When I clicked the link, it downloaded the binary, and I ran the setup. Surprisingly, the “beta” asked me to “activate.” When I logged into my account, the process came to a halt with a message telling me effectively, ‘Oh, your license expired on 05/24/24, and the last version you “own” is 3.0.2.’

There was more verbiage telling me that I could play with the software but could not save anything.

Note that all of this is happening two months after I reported this as-of-yet unresolved bug and provided the best documentation that I, as an end-user, could generate, including product process logging, photographic samples, and even crash dumps for WinDbg. I further stated that I could no longer effectively use the product for its intended purpose.

With this, I’m being told that I must fork over more cash to “test” this beta build to evaluate whether the problems I’ve reported here have been resolved effectively.

I’ve participated in testing software for well over 2 decades, and I’m not sure I’ve faced this type of situation before - it’s a first.

Forgive any delays in renewal while I digest the sheer hubris of this requirement before I decide how to approach it.

S’funny. You Topaz dev guys used to excel at communications- now, not so much.

Steve

Please reach out to us at the following link to help assist you with your account:

Topaz Labs | Support Page

Or you can send us an email at help@topazlabs.com.

Please include a link to this Forum thread that way the team is up to speed on this situation :slight_smile:

I have no issues with the taste of ‘crow.’ I will reach out.

Steve