Every time I open PAI as a PS plugin, the image appears briefly, then disappears and the Export box pops up with “Skipped: no edits applied” When I close the popup, PAI acts as expected. So it’s an annoying extra step for every file, but PAI is still functional.
In the new version 3.1.2, the developers and product team changed Autopilot’s default behavior. It now suggests that by default, instead of applying , this could be why you are having this Skipped message.
To put the Autopilot back on so it applies the suggestions automatically, please follow these steps:
Open the Topaz Photo AI as a standalone application.
Go to Preferences > Autopilot and enable Automatically apply filters to on and click Apply.
After you have done this, your application should operate as it previously did.
I already did that, from a previous post about not automatically applying suggested filters.
This is something completely different. As I said, every time I open PAI as a PS plugin, it briefly displays the image, says it’s analyzing, then all that disappears and the Export dialog pops up. Closing the export dialog brings the image up again, it finishes analyzing, and generally acts normal.
So it’s trying to export before it finishes analyzing, and before I tell it to export. This is a bug.
My apologies for the misunderstanding. Could you confirm with me which Topaz Photo AI version you are currently using? The most recent version release of v3.1.2 had a path fix for a similar problem users reported.
Also I’d like to get a better understanding of the machine you are experiencing this problem with, to do so please send me your system profile information so I can check if your computer hardware is up to date.
Thanks for your reply. Update… this does not happen every time. I’d say about 8 out of 10 files, all opened via Filter > Topaz Labs > Topaz Photo AI. I haven’t been able to detect a pattern.
I uploaded the diag.txt file to your Dropbox account. I am using PAI v3.1.2
Hi John, I am going to send you my computer details.
I have sent my Diag txt file to your Drop Box.
I am using the Topaz AI 3.1.2 in my Photoshop CC.
It worked fine in 3.1.0. I did not update the 3.1.1. I went straight to 3.1.2 from 3.1.0.
I’d like to get some more information about the workflow you are using in order to help troubleshoot the problems you are reporting. To do so please take a screen recording of this behavior so I can see exactly what is happening.
John, I just uploaded a screen recording of the failure.
Please let me know you received it. On the failure, I clicked the Filter/Topaz Photo AI from the top of the dropdown, since I have used the filter before. Now right before the failure, I clicked on Filter/Topaz Labs/Topaz Photo AI selection down at the bottom of the dropdown menu and it worked. Hmmm. Strange.
I have received your Dropbox file and have directed it to our development team for further investigation. I will be sure to reach out to you on this thread once I have more information.
it does not happen when I go filter - topaz - photo AI
only when I go last filter , but I have a stream deck with short cuts so last filter is one of the shortcuts I use regularly
I also have the same issue. I am trying to run upscaling through a Photoshop action and I get the “Skipped: no edits applied” every time. Turning Autopilot back on to automatically apply filters does not do the trick, and even if it did, I don’t want Autopilot to automatically apply filters, I want to set my own filters - without that popup of course.
Key update. My steps to reproduce above are incorrect. I mistakenly assumed that PS calls PAI in the same way whether by Filters/Topaz Labs/PAI or after first use by Filter/PAI (Alt+Ctrl+F) from the recently used filters at the top of the filter list. Turns out, this is not true.
Upon first use after PS is opened, the user has no choice but to invoke PAI via Filters/Topaz Labs/PAI. On any subsequent use, if PAI is invoked by Filter/PAI (Alt+Ctrl+F) from recently used filters, this problem occurs. If PAI is invoked by Filters/Topaz Labs/PAI, the problem does not occur.
So, there must be something different in the way that PS calls PAI that is causing PAI to exhibit the problem.