@roberto.avanzi - The Cloud team pushed a fix now that fixed the black artifacts that were happening with Standard Max on Cloud, can you retest an image?
So far it seems fixed!
Hangs on âAnalyzingâ. No files of size 0 bytes. New lows.
Edit: After âCalculating auto suggested valuesâ starts analyzing again.
The fix is not working on my end. I get an error and it gets stuck when trying to analyze the files from LrC to Topaz. Even opening the files in topaz, it is just not working ![]()
I think the only âsolutionâ which is provided for getting stuck on this analyzing image phase was to go back to version 1.3.3.
That was the only way which allowed me to get Topaz to work (at the time).
Itâs said that minimum VRAM requirements were Graphic Card with 6GB memory. I had 8 GB âŠ
https://community.topazlabs.com/t/see-steps-if-you-are-stuck-on-analyzing-image/101862/ 21
They said nothing about the processor, anyway mine was a 6-Core AMD Ryzen. And 32 GB RAM.
As requested, I sent all the information to support and have not got any comments or anything b ack.
Meanwhile, I made some updates to my hardware and now have new graphic card with 16 GB VRAM and Ryzen 9, 16-Core proce ssor.
And what you know, now 1.4.1 runs. And yes, Topaz is still not very fast, except Super focus, which is now u sable.
So, there was clearly nothing you can not solve by investing more money in your hardware.
Maybe this now is enough for a couple of next releasesâŠ
I have as much graphics memory as RAM, so up to 48GB. 1.41 still doesnât work.
I have to give a shout-out to Wonder 2 on my local machine; it works almost flawlessly for me! Itâs really fun to send him random images to zoom in on,
and at most 5% of the images donât feel quite right, like theyâre slightly out of focus (even though I always use manual maximum magnification, never auto).
Topaz Photo is fantastic with it now
(google translate)
Thanks for flagging! We reply within 8 business hours, and it would not be normal not to get a reply back. I have fetched your support email from our Spam folder and marked it as incorrect Spam in the hopes itâs not flagged as Spam anymore!
I looked at your logs, and we can see something happening with the graphics card in them. I sent back steps to test, let us know how it goes!
@elora.calhoun - and @radpopl - top right of the app there is a Help > Contact Support button, make sure to attach logs and we can have a look at what error are in logs with steps to fix it!
wow ![]()
Yeah! Thank god. mine got solved with your instructions. They must be missing somewhere. I was using this in conjunction with my edited pictures from capcut pc, thats where the problem was arising. Raw images worked perfectly well.
