Topaz Photo AI v1.1.0 - Product Releases / Topaz Photo AI - Topaz Discussion Forum (topazlabs.com) just noticed your post, this is a link back to 1.1.0 you can go back on any of the products you buy on topaz, i have found in a number of cases that an update can cause issue but it’s good to be able to try them out and roll back if needed, until it is sorted at a later date.
Desktop: HP ENVY TE01 Windows 11 version 10.0.22621 Build 22621
NVIDIA GeForce RTX 2060 Driver version 31.0.15.1694
Dedicated video memory: 6144 MB GDDR6
Same issue on my laptop.
HP PROBOOK 470 G5 Windows 11 version 10.0.22621 Build 22621
NVIDIA GeForce 930MX Driver version 31.0.15.2758
Dedicated video memory: 2048MB DDR3
Getting haloing around subject. Same pic using Sharpen AI does not show this.
Hi,
I’d like to report another issue - something is broken with the colours, see below:
The TIFF file freshly exported BEFORE adjustments:
The same AFTER saving the image in Photo AI:
1 Like
I’m very happy with your product. One improvement request: 90% of your “find subject” feature results do not align with my opinion of what the subject is (I can imagine how difficult that is). I then need to toggle the sharpen everything switch on. Can you make that setting sticky or allow a user set the default as desired? I don’t normally want to take the time to refine the subject on most photos. Thanks.
Same issue here. Also, opening a jpg file (that was exported from LR) in Photo AI removes the camera metadata.
Does the tif image have the same colour profile embedded after saving in PhotoAI? The muted colours suggests there is a colour profile mismatch between the input image and the output image.
i often use pai in batch mode.
unfortunately I can not set the facial restoration because I can not set a maximum value.
It is always worked with 100 percent.
Unfortunately, this often looks awful.
The latest version of Photo AI v1.1.1 seems to be broken with the message “Exception while opening image: Image is not supported”. The image in question is a Nikon NEF taken with a Nikon Z9. Previous version of Photo AI have worked fine.
TL;DR: Photo AI strips all metadata (including Color Space information) from the TIF upon saving which could be the reason for the muted colors, buth Lightroom is also not innocent as the Color Space information looks weird for both the panorama and a freshly created TIF from any dng.
More Details:
- I’ve checked the Color Space information with Exiftool for both the dng and the tif from my previous post - both were showing as “Uncalibrated”
OK, looks like I need a different sample
- Since the dng was a panorama stiched together in Lightroom I’ve checked another dng with Exiftool - this was showing correctly as “Adobe RGB” (I have Adobe RGB set up in my camera body)
- I’ve created a tif from that dng in Lightroom (Ctrl+Alt+E) with the following settings: ProPhoto RGB Color Space with 16-bit depth and 240ppi resolution
- After the tif file was created, I’ve enlarged it in Lightroom to trigger the update of the preview - colours match the dng
- Opened the tif in Windows Photo Viewer - colours look exactly the same as in Lightroom
- Ran Exiftool for the tif - Color Space: “Uncalibrated”
- Loaded the tif in Photo AI - colours immediately muted
- Saved the image in Photo AI - the preview in LR immediately updated to the muted colours
- Ran Exiftool on the tif saved by Photo AI - all EXIF info which was there before saving was gone (including the Color Space)
- Ran Exiftool on a TIF that was created in the previous version of Lightroom (12.0) and Photo AI (1.1.0) - Color Space is “Uncalibrated”, but there is an additional field called “Profile Description” which says “ProPhoto RGB”
See images attached.
1st image - Lightroom vs. Photo AI between steps 7 and 8
2nd image - Exiftool output for the original dng (green), the tif before (yellow) and after (orange) saving in Photo AI (steps 2, 6 and 9 respectively)
This version is unusable. As soon as I use an ADD brush to a mask the program disappears. Using JPG files and RAW files. This happens no matter what files I am using. Windows 10 64 gig RAM, Intel Core 9 i9 9900k Nvidia Geforce RTX 2070 Super ( selected as the processor)
1 Like
May need to drop back a version, as I’m encountering something completely different:
Canon R5 compressed RAW file. On processing from the RAW file, I’m seeing this on the interface. It seems to still process the end result correctly (see later attachment), but with this state it was difficult to refine the subject selection
trying to refine the subject it would seemlingly ‘lock’ on the calculations and take up to 30 seconds to come back to allow more refinement.
Once all the processing is complete, it ends up with a good output, but just the hassle and lack of being able to compare before/after leads me to just want to back out to the previous release and try on the next one.
I’m not sure that exiftool is useful in this instance. I have plenty of tif files that just state “Uncalibrated” in the meta data, but when opened in Photoshop have Adobe RGB or other profiles attached.
I’ve opened a ProPhoto RGB tif in PhotoAI, processed it and saved. The tif still has a ProPhoto profile when opened in Photoshop and the colours are unchanged throughout the process.
The tif I used was created in LR, but an earlier version. I’ll update to the latest version and try again sometime today.
I also noticed the sharpening of whole image instead of the “subject”, however the “subject only” switch is “on”.
The new update has removed my ability to control what the autopilot does when opened from photoshop. How can I stop the program from auto saving to photoshop. Thanks.
This is mentioned in the original post under “known issues”.
OK, thanks. I also have Photoshop, however couldn’t figure out how can I see the image’s Color Space within there, hence using Exiftool to check.
Also can you check and confirm if upon saving the tif in Photo AI, do you also lose all metadata, like myself and others highlighted above?
I hope you will update the upscale dialogue. I am using this function all the time, and I need to use Gigapixel AI instead of Photo AI. This because I can only use 2x, 4x or Max - or type in BOTH width and height in pixels.
I’m upscaling to a printshop, and then cm (or mm) is the meassuurement that is used. And in Gigapixel I can choose height or length in cm, and Gigapixel fix the rest.
As Photo AI function right now, this function is “useless”, since it takes “for ever” to get the job done.
Regards
Kent
With a tif exported from LR 12.1 I can’t replicate the colour problem. The file saved in PhotoAI retains its ProPhoto RGB colour profile and still seems to have all it’s metadata intact.
Updated to 1.1.1 today and I can no longer process CR2 files from Canon. The program crashes every time I try to save the file as a DNG. Using: Recover Faces, Remove Noise and Subject-only sharpening.
Windows 11.
