[Please describe your issue here. Try to include logs (Help → Logging) and add screenshots if necessary.]
Photo AI appears to cause a slight shift of the image (I use .tiff files). The shift appears to be extremely small when opening the image in Photo AI (stand alone), but appears to be a little larger if I use Photo AI as a Photoshop Elements plug-in. I believe earlier versions of Sharpen AI used to introduce the same kind of shift but new versions of Sharpen AI no longer introduce a shift.
Steps to reproduce issue:
Step 1 Simply run Photo AI and compare the “after” and “before” images.
Step 2
Step 3
Topaz Photo AI [v1.x.x] on [Windows/Mac]
Was about to open a post for this issue, but found you had already reported it.
This has been reported by a numbers of users in previous version release posts in the past as well.
Especially when applying sharpening, the subject or image -depending on the setting- shifts down+right several pixels.
The face recovery undoes the shift, slightly misaligning the head from the neck.
Objects that are sharpened appear to be slightly stretched from their upper/left boundary and compressed into their lower/right. This creates a kind of halo or brightening along the right and bottom border of the object.
In my case: working on Windows 10, 64bits, sending images to TPAI (1.2.10) as zipped TIFF from Capture One using the “edit with” menu. The same happens when using TPAI stand alone with .raf raw files.
Lingyu
April 13, 2023, 8:04pm
4
@rashid.nassar @Propheticus
This is a known issue that we are investigating. I was able to reproduce the issue, it looks like a bug due to the preview.
Does the output image also have a pixel shift?
Yes, the pixel shift is also in the saved output.
update: the issue persists in v1.3.0
To be sure: the pixel shifting when applying sharpening is not limited to the preview.
Reports of this behaviour go back a while:
When Sharpen is turned on the image shifts a few pixels.
PAI 1.2.9. Win 11 Pro desktop PC. Processor = Auto (AMD RX6800 XT, Intel i9 12th gen).
.JPG image test. No previous processing to it by me.
I hadn’t been able to test in past week. Over 3300 households w/out power in northern CA neighborhood for 4 days. So I’m commenting on things new to me. Changelog above has virtually nothing new relative to issues I experience (or, features I’ve requested in past roadmaps), so can’t comment on them.
My standalone implementation launched & ran. I did see 2…
Still existing problems :
slight move shifting of the picture when sharpened … can you please fix it once for all
the sharpening sliders are at the lowest level, but still it sharpens a lot …
Thanks
Yes. It is significant! Down & to the right. Some releases it’s less noticeable than others. This is a lot.
Jan’23
Positives:
Subject detection works well and often selects what I would select myself. Only when there’s really low contrast between subject and background it selects a bit too much.
Processing speed / preview speeds feel quite a bit faster than a few versions back.
It’s becoming a bit old by now, but these issues that have been reported many times still remain:
Pixel shift down+right when sharpening. When ‘subject only’ is enabled you see a stretching of the top-left boundary and squishing …
Same PC specs as immediately above.
This time working with Ps 2023 Plugin (to ensure it launched, processed, returned processed image to Ps layer stack).
Am seeing the same thing as prior releases. When Sharpening is used in PAI (plugin) I see a significantly more noticeable ‘hop’ (aka, pixel shift) after the image is processed and returned to the Ps layer stack (and I turn off/on the layer Eye icon).
Also, PAI Plugin introduced all sorts of artifacts into the image (it’s as if it copied all …
Still getting a slight shift on sharpened areas.
dec '22
Since I don’t see most of these mentioned in the known issues, I’ll link to my post from 1.1.2:
Ok, the pixel shift has been acknowledged but only mentions preview
It’s not only in the preview, upon sharpening the subjects (or whole image) is shifted in the saved/exported image as well.
This has an interaction with face recovery which undoes the shift, displacing heads relative to the (sharpened) body it’s attached to.
I’ve found mentions of this issue going back to version 1.0.4.
The (de…
Win 11, Ps 2023 Plugin. Working with full-color to BW converted (in Ps) .tif image.
I wanted to see if anything quirky would happen with a BW image. It didn’t.
I didn’t see any artifacts (rainbow or otherwise), blurry patches (there’s lots of empty sky that seems to give others issues…) or distortions of any kind after the processing by PAI.
It is an image I’d previously done processing on (in addn to the color → BW conversion). PAI detected (or else it was just lazy ) the image didn…
oct’22
Anthony,
I just tried the Ps 2022 Plugin vers. on my Win 11 Pro desktop PC also.
3 Issues were a Problem:
1- The plugin is back to not opening full-screen when launched from my Ps layer stack.
2- The processed image saved back to Ps is showing a significant Pixel Shift/Hop which it hadn’t been doing in the run of recent releases.
3- To get the test image sharp enough it ends up showing a lot of over-sharpening artifacts (‘snow’) back on the Ps layer.
** Orig. image is a jpg snip from one o…
I’m not enjoying this to be fair. Denoise and Sharpen now do a good job. I would be happy if this app just combined the lot into 1 convenient do it all app
Photo AI settings are way too strong. 1% starts like at 40-50% level of the old apps. Please bring back the levels of control.
Denoise function kind works on and off. Presumably it struggles with subject detection.
Sharpen is completely broken to me. It is like early v3.0 all over again. embossed out edges, high contrast, pixel shifts. Jus…
Aug '22
Just a quick test on this new version & i’m seeing pixel shift to the right and down when sharpening is applied.
I am using 1.3.0 and yesterday I turned on sharpen and the image shifted a few pixels.
Lingyu
April 20, 2023, 10:59pm
10
@Propheticus @henry.richardson
We have this documented and a few tasks batched together that will be worked on soon.
The developer who will work on this is currently finishing another task. It should be on deck for a fix once that project is finished.
1 Like