phot0n0ob

Hi y'all

I recently downloaded a trial copy of Topaz DeNoise AI and found that it consistently crashes when I dial up all three settings (Remove Noise, Enhance Sharpness, Recover Details) to their maximum of 1.00. The application goes thru pre-processing, processing and post-processing, then crashes less than a second after the "post-processing" message goes away. This behavior is independent of the image I try to process.

I have already opened a ticket with Topaz, which has been put on hold until they "can find a fix for that issue", so I am not necessarily looking for a solution and merely wanted to check if others are seeing the same problem.

johnst1001a Loc: West Chester, Ohio

My guess is you are running out of ram.

phot0n0ob

It doesn't look like it. After I start processing an image, DeNoise's memory usage does of course increase (in one sample image from 300 MB to 1.8 GB) and it increases again at the beginning of the post-processing step (to 2.2 GB), before dropping back and staying stable until the app crashes. Thruout the entire process, the computer was never close to utilizing all 16 GB of physical RAM.

mborn Loc: Massachusetts

Why are you maxing all the settings?

kubota king Loc: NW , Pa.

Although I already own Topaz AI Sharpen and Topaz AI Gigapixel . I downloaded Topaz AI DeNoise Trial to see if I could notice and difference in sharpness and to see if my system would crash like yours . First I tried a 2.5 mb file , no problem when pushing all the settings to 100% . So , I decided to try a 10.5 mb Tif file saved as a Tif . It made the file size 26.1 mb with no problems set at 100% for all settings , and it finished in a few seconds . Now , I build my own systems and on my main desktop I use Hardware made for High Performance . I also do trouble shooting and repairs and buy computers for customers in my area if needed . None of them so far need a system as powerful as my main desktop . Using Windows 10 1803 version , I opened the task manager and clicked on the performance tab so I could see which of the hardware was being used the most as I slide the tabs in DeNoise to 100% one at a time . On my system All 3 of the Topaz programs I listed here use a lot of GPU vs CPU or Ram . My system has a 6 GB GPU , and I haven't had any of the crash problems or very slow rendering problems I have seen posted by many of the other members using these 3 programs . Maybe your system is low on GPU memory . I have read on the first 2 programs I listed that they recommend at least 4GB of GPU and they probably recommend the same on the DeNoise program too . If you have Windows 10 you can open the task manager like I did and click on the performance tap and watch as the DeNoise program works to see if you are maxing out any of the 3 hardwares I listed GPU - CPU - Ram .Tommy

phot0n0ob

Thank you for your tests and suggestions, Tommy. I'm running it on a Macbook Pro with a fairly low-performance Intel Iris GPU with only 1.5 GB of video memory, so maybe that is indeed the problem. What's interesting, though is that the app appears to finish the entire process, only to crash as soon as it is seemingly done.

phot0n0ob

Why not? ;-)

I just downloaded the app a few days ago and tried different settings before making a purchasing decision, when I pumped into the issue with all settings maxed out.

kubota king Loc: NW , Pa.

Does it crash when you click on the save tab or before ? I feel that is when most of the processing is being done in all 3 of the programs I listed , although it looks like it is when you move the sliders . The reason I think this , all 3 programs on my system when I first open a photo in any of the programs , it is very quickly done , it is when you click save that it takes the most time and that's when I see the most used GPU - CPU - Ram usage . So , to me that is the most obvious time it actually does the rendering by the settings used . Tommy

phot0n0ob

I have adjusted application settings so that the preview is not automatically updated every time I adjust the "denoising settings". When I click "Update Preview", the app continues to work. Afterwards, when I click "Save As" and then "Save" it goes thru the pre-processing step, the processing step (all the way to 100%) and appears to also finish the post-processing step before it crashes.

kubota king Loc: NW , Pa.

Since I have never owned a Mac computer or worked on one . I don't know if they have the ability to bring up a Performance Tab like Windows 10 has so you can see what hardware is being maxed out before the program crashes . Does it crash if you don't max out all the settings and just use it where they have the settings set to when you first open the program ?

phot0n0ob

Tommy thanks for your continued suggestions. Yes, macOS does have the ability to monitor the system's performance and while the CPU utilization can go up to 80 or 85% (making the machine noticeably slower), neither CPU nor memory utilization max out. The crash happens, when I max all settings and does not crash with settings at the halfway point or lower (I have not yet tried anything in between).

I have sent detailed information, including DeNoise's application log files to Topaz and they were not able to find a solution, so I doubt that there is an "easy fix", which is why - in my original post - I said that I did not necessarily post to find a solution, but rather to see if I was the only guy with this issue. As another poster has suggested with his ""why are you maxing all the settings?" question, this is probably not a very likely real-life scenario, anyways.

Dngallagher Loc: Wilmington De.

You have the option in Denoise A.I. to set either Cpu or Gpu use, so if you suspect a GPU issue, switch to CPU mode, it may end up being slower though. Set in preferences.

NCMtnMan Loc: N. Fork New River, Ashe Co., NC

Under preferences try changing from gou to cpu memory and see how it does. Is there a reason you are running it at 100%? I have never had to run it that high so I don't know how my system would react.

phot0n0ob

Thanks for that suggestion. Switching to CPU helped, at least in one test with one image (that had previously crashed the app)

camerapapi Loc: Miami, Fl.

No issues here EXCEPT that for larger files it takes up to 2 min. and 45 sec. to process.