Can you test if you close Photo AI, then open Photo AI and before importing files, go to Edit > Preferences > Auto-Pilot, turn it on then import your files and SELECT ALL > Export if this works?
If not, go to Help menu at top of the app, then Open Logs folder then zip all the logs and send them over to support@topazlabs.com
Also make sure to send in this email your System Profile: How To Obtain Your System Profile (Windows)
Thanks, very much appreciated!
The CLI commands donāt work since the 3.4 update
When will that be fixed?
hi, same problem, error running model, when I apply current settings to selected images with version 3.4.3
I have to use version 3.3.1
same for me when I apply current settings to selected images
version 3.3.1 has no problem
Super Focus System requirements
"The Recover and Redefine models have higher requirements for processing than the basic models.
For Windows, 8GB VRAM is required for processing locally."
Do Recover and Redefine models = super focus?
SuperFocus (PAI) is a different feature than Recover or Redefine (GAI).
My desktop Win 11 Pro PC has 16GB VRAM, 64GB RAM, 8TB memory and up to date AMD drivers in the 6800 series processor and cannot run those features in a reasonable amount of time (I consider over 25-35 minutes - my avg quoted ETA render times for a single not super large (ie, not medium format) image - not reasonable. But, frankly, over 3-5 minutes for a single image to render I consider not acceptable or useful to me).
I confused then. This link and quote are for PAIās Super Focus not GAI.
In order to have a clean result with the preserve text function it has to be the last model when upscaling, like in previous version. Right now with the locked models, on every text i get fuzzy results.
This works for about 4 or 5 photos and then starts to crash again with face recovery Gen 2. When I delete CoreML Cache it works again for another 5 photos and crashes restart.
Email sent to support@topazlabs.com with requested logs and system report.
Here is the descriptive overview on PAI Super Focus (yāall):
Hereās the 35Kft overview of GAI Redefine:
I understand the differences. The question is why the Recover and Redefine models are mentioned in the webpage concerning Super Focus. Is the 8GB VRAM recommendation for Super Focus real or does it belong to GAI?
Ahhh, got it. That I cannot answer.
Plus, 8GB VRAM is too low for any of those models. They require workstation or supercomputer calibre processing power to work properly. 16GB absolute minimum VRAM.
Thanks for flagging! The web team was flagged and will change this to be Super Focus only.
Edit: Fixed now 
Super Focus | Topaz Photo AI
I have a 6GB VRAM and it works great, recommended is 8GB yes, but will work with 6GB of VRAM that is the minimum requirements! Above 8GB of VRAM, will be 12GB, then a few 16GB exists.
There is a minimum as well for RAM (not VRAM) to be 16GB.
Iāve got 8 GB on my RTX 3070 and itās working fine. But obviously, on large images, itās quite slow. And if the image is super super large, the problem is that after calculating the global preview, it will still calculate for quite a long time to show the result after processing. And thatās every time you hover over areas of the image.
Another example: if I want to increase the size of a poster image to something like A0 (14043 pixels on the longest edge) and the base image already has a resolution of over 3000 or 3500 pixels in length, rendering with Redefine or Recovery will take at least 60 minutes or a little longer.
I hope to reduce this calculation time by 2 or more with the next RTX 5000 series cards. Iām using a 5070 TI super with 16 GB Ram.
Are there any plans to adjust Super Focusā process so if only a portion of the image is selected only that portion will be processed? I would think that would speed it up.
@golder-50350 I am checking with Lingyu, our Technical Development Manager and will get back to you if we have plans/or a timeline for this.
Hello Michael,
Thanks for the files, I have added them to the development team ticket working on grid artifacts happening on files with a large similar background such as skies (like this case) or defocused similar-colored backgrounds. Will circle back once a fix is found, as I added your contact info on the development team ticket!
