I’m also living in Spain, using English everywere, and it doesn’t work for me either (neither with a Spanish keyboard or an English keyboard)… oh well…
Decimal point/period: I’m just guessing, I have no idea why Topaz is still having trouble with this. I guess just setting the keyboard isn’t enough. I would try (Windows 11) in the regional settings (Region-Formats-Additional settings-Customize format-Numbers) to set the Decimal symbol from a point to a period, maybe that would help? (Or from a period to a point? I don’t know how you have it set up now, just try changing it, just in case…)
Good luck!
Hopefully it’s under the Effects tab.
Found it! Thanks for the tip about FS. I’d still prefer to have it as a standard within the options of the TPAI though, one step less for us to add a signature on the pictures. Lazy dog, I know…
1 Like
@unrelent THAT WAS IT!!! Perfectly working now, thank you!!!
This is something that @Imo and @Left_The_Building should read and try! Now it works as it was meant to.
Thanks again!
1 Like
The “fix” that @unrelent suggests is indeed a temporary solution that works, but the thing is…
I frequently see new (or in this case old) problems popping up (or reappearing), and for more and more of those problems the suggestion is that I should adapt my gear rather than the problem at hand getting fixed.
Have anyone else but me bothered to google comma vs. point separation for decimals? There is a huge amount of countries that use comma as a decimal separator, so that this isn’t solved yet is really puzzling.
2 Likes
Exactly. Besides, I posted this „fix“ already a looong time ago.
But some issues nobody at Topaz cares about as it seems..
Well… the general decimal comma/point problem is ancient, dating back to the last millennium, as can be confirmed by the yellowed pages of very old handwritten calligraphic chronicles. If they have that field defined as numeric in Topaz and are having some trouble with it, they could, for example, add to the parameter options an option for the user to specify whether a point or a comma will be used. Fixing it individually somewhere in the region parameters in Windows is really very emergency. Many “international” problems (font type, etc.) have been solved over the many decades, so perhaps the decimal separator could also be solved somehow… (The problem is not that users are so different in nationality; they simply are and will be.)
1 Like
I was actually thinking the same - something like a switch in preferences…
But on the other hand - I simply don’t see why you can’t just allow both?
Of course, both would (and should) be possible. I don’t know how and in what way it is implemented. They would probably have to add testing (a few extra bytes and microseconds). Or they can be inspired by setting the separator in Excel. Or… etc. The user doesn’t care, she or he is satisfied with the fact that the comma separates decimal places and is not a separator in the list, etc. I remember that this was already addressed for Topaz and perhaps even solved, and here it is again. The user should deal with optimizing photos and not solving implementation flaws such as the decimal point/comma. So hopefully Topaz will fix it for good.
I would think that setting this (and other things like currency symbols) would be best done in the Windows regional settings, rather than in a per-app solution. Switching amongst time & date formats needs to be available on the fly (I use both 12h & 24h, and m/d/y & ymd depending on the situation/need), but something like decimal separators is more likely to be system-persistent.
That said, I haven’t run into this issue as I’m using English/US settings and keyboard, so I’m not familiar with how pernicious it is across systems and software.
Yes, the change of Regional settings will work, but we want a fix that will not have users have to do this! If you prefer to leave the regional settings as is, this issue affects the text field only and the sliders still work. I added all 3 of your info on the development team ticket on this and once a fix found we can tag you to let you know.
5 Likes
There is probably no single optimal solution. In Topaz, it would be easiest to add a warning to the input field “Use a decimal point, not a comma”, but that would probably irritate many users (“why do they keep telling me that over and over again?!”). On the other hand, new “comma” users justifiably simply do not understand a series of commas when they typed numbers there and have to work hard to find a solution.
It can certainly be solved sensibly (but it must not appear repeatedly in future versions). When parsing texts (in different languages), there are worse things: units of length, weight, temperature, …, transcriptions of names… (And I hate the keyboard setting to QWERTZ the most, because I’ve been used to QWERTY since I was born with ancient Unix! 
)
Let’s leave it to Topaz, they will surely fix it somehow.
1 Like
I don’t know if this have changed, but when I first tried to figure this one out quite a number of versions ago (I belive it was 2.x-something) I remember that - if you didn’t have US locale - none of them actually worked for me. Like the absence of the right set of properties made it impossible to use either one.
Anyway - I’m glad that it seems to be on the radar of the devs, so hopefully a fix will come sooner rather than later.
1 Like
Hey. I know the feeling.
That’s why I like to use the PAI & GAI as Photoshop plugins. Because then it’s a convenient workflow and I’m not hopping in and out of misc programs (which, honestly, I wouldn’t do if the products couldn’t be used as plugins). Though I can’t - for some reason on my AMD desktop PC - send images for Cloud processing from inside Ps (File > Automate); which I want to be able to do because the AMD can’t handle the more ‘creative’ models.
Ciao.
1 Like
A post was split to a new topic: Getty Images Copyright Trial
Buenos días. A pesar de haber quitado la etiqueta “beta” en la reconstrucción de caras V2, todavía sigue apareciendo un molesto “sarampión” en la piel (manchas circulares).
¿Cuándo se va a solucionar?
Good day.
The issue you’ve experiencing is happening because, the faces within the image are Blurry possibly caused by Soft Focus or Motion Blur and you have the Recover Faces Strength intensity set to one hundred which is much to high
Try reducing the Recover Faces Strength or alternatively try applying Recover Faces V1 / Gen 1 instead which is far more forgiving when it comes to blurred faces and spots.
Hope this helps
1 Like
Two separate issues
The initial Raw Denoise occasionally gets stuck, and the wheel spins for several minutes. I’ve tried leaving it with no success. Can cancel the processing in TPAI, rerun, and it works in a few seconds.
Log files attached after this happened. (I had to repoen TPAI to get the location for the log file, so it is not the last session)
Topaz.zip (363.7 KB)
Second problem is that the Sharpen Subject mask occasionally disappears. So when I mouse-over ‘Subject’ before adding the Sharpen, it shows. But then sometimes it won’t display after I add it. And sometimes it will disappear after I’ve started refining it
@david.barker-2802 - can you send to support@topazlabs.com your System Profile, to make sure all drivers are up to date? Also seeing you are forcing in your AI Processor to be on NVIDIA, make sure to change this to Auto in Edit > Preferences > AI Processor > Auto, - Using Auto will use both CPU+NVIDIA and this will use your full machine capabilities. Make sure to not use the “optimization” settings in your NVIDIA app for Topaz Photo AI, all it does is change without your knowledge the AI Processor to solely use NVIDIA, and to use your full machine capabilities, you want to remain on Auto. If issues remain on Auto, test using same file on C drive (seeing you edit on D - to rule out D drive issues. If issues remain on C and on AI Processor Auto - send fresh logs to support@topazlabs.com and your System Profile as well and we can have a look: How To Obtain Your System Profile (Windows)
