In earlier products there was an on/off switch in Prefs for users to turn logging on or off.
I’d personally turn it on while beta testing then off for the commercial releases. If something was misbehaving, it was easy - with that approach- to turn logging back on to send troubleshooting details to tech spt folks or devs at Topaz.
I think that approach would be welcome vs unilaterally disable.
Thx for the pointer to the vote option.
That’s exactly what I suggested - give us users the option 
SUBJECT-MASK
maybe an error at least dont work
if i press “subject” and manual add a mask, red color lets say portrait but leave a part lets say the mouth.
now i recover the image but face-recover recovers the whole image and dont accept my mask 
Nothing to do with face recovery, the subject mask is used to restrict sharpening. If there is a subject mask only the subject is sharpened.
Face recovery works on small faces but not extremely large ones. But you can also select/deselect the faces to recover.
See the user guide here …
Back to this.
I did calculate some stuff.
The EOS R3 (24MP) has a pixelsize of
0.006 mm
The EOS R5 (45MP)
has a pixelsize of
0.0043 mm
The GFX 100 II (102MP)
has a pixelsize of
0.0037 mm
So the
R5 has 40% more resolution than the R3, and the GFX 100 II has 62% more resolution than the R3.
A House with a window in 1.5 Kilometers distance that is 6 Pixels in height with the R3 will have 9.7 pixels in the same space with the GFX 100 II.
This is interesting for me because I have seen that the resolution advantage is not as obvious as you might think from the pixel numbers.
The imaging errors of the lens are often magnified, as was the case with the EOS R5, where hardly any more details came out in the end.
The data processing effort is often not worth the many pixels.
I am currently planning a large print and thought it might be better to recreate a certain photo with a medium format camera.
But as it stands, it’s not worth the money, time and effort.
Absolutely.
But, I added Nikon Z8 (45 Mp) to my older Canon lineup, and am absolutely happy with the resolution compared to the older Canon 5Diii (22 Mp). Even when used the same Canon EF lenses via an adapter. I certainly have a better flexibility including cropping, and do not see image degradation. May be my senile eyes are too weak
Sometimes also for downsampling to reduce motion blur… although this perhaps would be same at a lesser resolution if the final image size is not important. But I’m just happy with this extra space, no regrets!
If you specify the width or height size in centimeters, the program sets the photo resolution in pix/cm. This should not be the case, the resolution should always be measured in pix/in . This is an international standard. And there is no way to fix it in the settings. The same happens in Gigapixel. Now you have to specify 118 pix/cm to get an adequate result.
How to set the size in centimeters and resolution in pix/in?
I realized that my original wording said “disable logging” vs “allow users to disable logging” so I can see why you might have thought I was suggesting that logging just be disabled vs providing a user option to do so!
Updated the wording in my post to be more clear that I want the option to disable logging not just disable it entirely.
Cool! Yes, that’s what prompted my comment. B/c being able to log, only when desired, can help troubleshooting. 
Huge bug. The beta eraser no longer works at all on version 2.3.0. I hadn’t tested it on that version yet, but every time it finalises the calculation the software crashes.
Here are the logs:
Logs.zip (165,9 Ko)
I notice some color differences at the transitions when using face recovery. Typically, the colors inside the “box” where face recovery is used are slightly lighter than outside the “box”.
Is it color shift (hue) or brightness (tone) that you see? Do you have a Before/After snip example?
Please remove the “Repeatedly crashes on startup” feature!!!
I’m trying to get work done!!!
My machine has 48GB of RAM, an Nvidia video card with 8GB of dedicated video RAM.
And I’m only opening a JPG file this time! Why should Topaz be using over 7 GB of RAM? And why should it crash or freeze, as it did in my last attempt to edit a photo?
I started using the latest version right in these days and what I did notice is that I do struggle to move the adjustments sliders (whatever is the adjustment) while the image is being processed.
This is something that was not happening in the previous version and it is quite annoying since you have to wait for some kind of pre-processing in order to move the sliders.
Is there anything I can do to solve this?
It seems that the DeNoise models are still soft, this is an ISO320 image and RAW conversion is still not suitable:
Compared to alternative:
I think I found what might cause the crashes with the Remove tool! If I turn on upscaling and then turn it off before I use the Remove tool, the latter no longer crashes until the next launch of the program! I think there is some dependency that makes the Remove tool crash if something from the upscaling models is not loaded first.
I hope this helps with fixing this bug. Let me know if you need any more info.
I notice that either the software crashes without warning or I get this error message
Strangely enough, there’s no problem with jpg images. But only on png or certain png images. This problem didn’t occur before.
However, the image in question is not very large.
As a reminder, my configuration is as follows:
Windows 10 22H2 with the latest cumulative updates installed.
32 GB Ram
8 GB MSI Ventus RTX 3070.
MSI MPG-Z390-GAMING-Pro-Carbon motherboard
NVIDIA drivers updated to version 551.23
Also, I’ve just tested on this image here:
Edit, I reinstalled photo AI cleanly but the same thing happened
That’s very interesting. It confirms that I’m not the only one with this problem. It’s true that the crashes I’ve had, I didn’t load an upscalle models beforehand. And the few images I’ve used that worked, I’d done an upscalle just before.
Edit, I’ve just done the test and can confirm that you need to activate an upscalle model first if you want the suppriemr tool to work without crashing. I activate the upscalle and deactivate it. Then I do my test with the delete tool and indeed no more software crashes. It’s really a very curious bug.
It’s really fascinating
