I uninstalled the buggy version and went back to version 2.3.0 which you can find here
Version 2.3.0 works for me.
In the file Save As, you currently have JPEG as one of the options. Can you add jpg as another option, so I dont have to manually change all my exported files from .jpeg to .jpg? I do Windows File Manager searches by xnamex.jpg, so it misses all the ,jpeg files.
Not a show stopper, but its a pain.
THX
1 Like
Thank you! This got me working again.
Please don’t send any more updates until you fix the face recognition situation. The program is currently completely worthless. That needs to be the number 1 fix.
4 Likes
If you do a search with xnamex.jp* it will show you all jpg and jpeg files.
Good point, but 4 letter file types are an unnecessary albeit minor pain. Just because it’s allowed doesn’t mean it should be done - especially when it’s for the exact same file type as an alternative and existing 3 letter extension. There are over 17,000 possible combinations of 3 letters but Wikipedia lists well under a thousand existing file types, so there is no need for it, heic included. 33% more pain for no gain.
2 Likes
I am also facing this problem. The slider moved smoothly until v2.2.2.
1 Like
I agree. I don’t need 2 different file extensions for that same thing. Besides I am OCD about file naming conventions
I prefer to use High Fidelity model at high quality photos.
When that happens to me a computer reboot solves the problem.
Update chrashes
The “Face Detect Not Run” and the hanging at “Face Detection” from 2.3.1 were not corrected in 2.3.2.
Windows 11, 32G RAM
3 Likes
We’re just about at three weeks, now, since this bug emerged, and was reported by several users, and it still has not been addressed.
1 Like
It may not be as simple a problem as you are trying to make out. For example, I have a Ryzen 9/32GB RAM and a RTX 3060/6GB and do not have this issue.
I have noticed that many AMD GPUs are affected but I believe there is a hotfix available for those affected AMD GPUs on the AMD forums.
1 Like
Same here, Ryzen 9 but with an AMD GPU. No problems at all.
I am however kind of worried that whatever fix that - eventually - will be applied might actually put me in limbo together with everyone else currently having problems…
I can’t see that happening, it is obviously caused through the AI processor, i.e.tensorflow etc., that is being used in combination with the hardware.
I don’t have that problem at all on an M1 Mac
In fact, I haven’t had 90% of the problems that have been reported in the last year or two here on any of the Topaz products… I sometimes wonder what you guys do to create so many issues… 
What they do is buy PCs. There are so many different configurations that they can’t all be tested by developers.
I’d say about 10% or more are simple “installation” issues.
I’m not so sure about that.
A user has posted a theory that this might be due to a recent update to OpenVino Update in those TVAI versions that are affected (2.3.1 and 2.3.2); after he patched the newer version with the old OpenVino files it allegedly worked. This might be well due to the CPU not being supported by the new OpenVino version.
Unfortunately this post didn’t seem to get through to the devs, although I do believe that he’s on the very right track here.
Maybe you could forward this to the devs?
1 Like
