Thank you. Yeah, the guitar is less obvious.
This is an AI image. I have mostly given up on photography now, having photographed many landscapes within a day or 2 daytrips.
2 Likes
Very nice! Do you do art sales (print-on-demand, etc.)? I have occasional success with that. Occasionalā¦ 
Thanks. I just do art for my personal use. Iām been retired for 16 years.
1 Like
Oh no, it will get even rustier in the salt water!
Seriously though, nice image!
To read more into it than Iām sure you intended, I like the dynamics and alive energy of the water combined with the stillness and ādecayā of the old car.
For some reason it makes me also think of the end scene in Planet of the Apesā¦
2 Likes
I have the same problem with Photo Ai 2.3.1. and 2.3.0 with the 72 dpi result after asking 200 dpi or 300 dpi.
I had this problem with Giga v7 and you correct it with v7.0.1 so.
Thank you for your speed to correct it.
Imac 2017 4,2 GHz Intel Core i7 4 cores, Radeon Pro 580 8 Go, 64 Go 2400 MHz DDR4, Ventura 13.6.4, 3 To storage.
4 posts were merged into an existing topic: Coupon code not working?
Ā Are all the develops AWOL?
Ā Itās been two weeks since this release, and since a serious bug in the face detection was revealed therein.Ā Has any progress been made toward fixing it?Ā Iāve seen nothing from any of the developers, regarding this, or any of a number of other concerns, for quite some time.
Ā I am also very concerned about a privacy issue that I thought had previously been resolved, but now it appears not to have been.
Same problem.
Iāve also reverted back to 2.3.0, which works just fine on faces.
Same problem for me: I just installed the Photo AI v2.3.1 upgrade today and have discovered it gets stuck on āDetecting facesā for an image which worked easily in v2.2.1. Iām using Windows 10 Home 64-bit, 32GB RAM, Intel Core i7-9700, Intel UHD Graphics 630.
Perhaps you should uninstall 2.3.1 and install 2.3.0 in its place for now.
You can get the prior installer from the Photo AI Product Releases tab in this forum.
Yes, thanks, Iāve reverted to v2.3.0 and the problem has stopped. Thereās clearly something wrong with v2.3.1.
1 Like
Yes, that seems to be the consensus. Glad you got 2.3.0 to work for you!
1 Like
And, now, with 2.3.2. They put out a new release without fixing what was wrong with the previous release. Two badly-broken releases in a row.
What do you mean, specifically?
Does 2.3.2 also have install issues like 2.3.1?
Does 2.3.2 also have a non-working Face Recovery feature?
What?
And, what are your system specs? It doesnāt help the rest of us if you make a generic statement to know whatās going on and it wonāt help devs know what to focus on either to make fixes.
Just some background, I was running a machine that worked perfectly up until 2.1.3 and then things quickly fell apart. Many of the issues people have now started for me on 2.1.3. I thought my machine was adequate.
Windows 11 Home
Version 10.0.22621 Build 22621
System Manufacturer LENOVO
Processor Intel(R) Coreā¢ i7-10510U CPU @ 1.80GHz, 2304 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date LENOVO BNCN43WW, 5/21/2021
Installed Physical Memory (RAM) 12.0 GB
Total Physical Memory 11.8 GB
Available Physical Memory 4.83 GB
Total Virtual Memory 13.3 GB
Available Virtual Memory 3.11 GB
It wasnāt, the system would use all available resources. Topaz support did everything they could to assist but the resources were the issue, especially when I tried to run PS and TPAI at the same time.
I invested in a new PC, it ran me $950.
Microsoft Windows 11 Home
Version 10.0.22631 Build 22631
System Model Victus by HP 15L Gaming Desktop TG02-0xxx
System Type x64-based PC
Processor AMD Ryzen 7 5700G with Radeon Graphics, 3800 Mhz, 8 Core(s), 16 Logical Processor(s)
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.3 GB
Available Physical Memory 21.6 GB
Total Virtual Memory 36.3 GB
Available Virtual Memory 22.2 GB
Now everything has worked perfectly and I can run a suite of software applications without issue. Updates load, models in TPAI and GP run smoothly and produce excellent results in seconds.
I wanted to blame the Topaz software, this issue was definitely local. No matter how you may want to slice it, improvements to the Topaz software are going to use resources and the listed minimum requirements are the rock bottom requirements and the performance will be questionable.
No answer yetā¦ Someone in the house ?
