As far as I’m aware, the black output issue is indicative of not enough memory to export an image. However there were no major changes that I believe would cause this moving to 2.2.7. If you have a particular version you know worked you can revert to that one. I’d recommend contacting support and sending them your system info.
Adam i can. Can you let me know how ? And I have made a video of the things I do and what happened. Can I send you this to ?
You can copy the contents of the crash log, or I think there’s an option to save somewhere on the window. I’m not entirely familiar with Mac so I can’t point it out off the top of my head. For video I think uploading it would be easiest. You can upload both the log and the video to dropbox here: Submit files
Thank you and log files and movie are downloaded in your Dropbox. My compliments for the very quick reply and taking action. That’s really something. Thank you for this. Lonny
Hi Thomas,
here are my specs:
CPU Model: Intel(R) Core™ i5-8350U CPU
Ram size and MHZ: 16.0 GB and 1.70 GHz 1.90 GHz
GPU Model and VRAM size: Intel(R) UHD Graphics 620 and 1500 MB
GPU Driver revision number: 26.20.100.7812
Thanks, Brian
As Adam said.
GPU spec is too low, but you did write you don’t use it anyway.
you could try i again with OpenVino off (Intel Off, GPU Off) but then processing will take some time.
Thank you for the uploads. I’ve taken a look and will try to reproduce them locally, but it might take a bit since we are in the middle of updating our build process on Mac.
In the meantime, could you send me a copy of the text inside the Apple crash reporter that pops up after the program crashes? You should be able to show more info, click inside the text box that shows up, select all, and copy it to a text file. That will help me pinpoint where exactly it crashed.
For now I don’t really have any steps to help you. We are in the middle of trying to update libraries, so hopefully this along with some other improvements for 2.2.8/2.3.0 will resolve this in the future.
If you had an earlier version work, I can provide you a link and you can download whichever previous one you had. Unfortunately this means you will get update prompts when you start though. In order to download a particular version, just replaced the two instances of “2.2.0” with whatever version you want. So if you wanted “2.2.2”, replace both 2.2.0 with 2.2.2 in the URL.
Windows: https://downloads.topazlabs.com/deploy/TopazDeNoiseAI/2.2.0/TopazDeNoiseAI-2.2.0-windows-x64-Full-Installer.exe
Mac: https://downloads.topazlabs.com/deploy/TopazDeNoiseAI/2.2.0/TopazDeNoiseAI-2.2.0-osx-Full-Installer.dmg
I have placed the Apple log file in your Dropbox as you requested. Thanks again and I hope you can fix this. Good luck and stay healthy my friend. Lonny Drees
That crash report shows me the issue, thank you very much for taking your time to upload it! It might take a while since internally we are working on several things, but I’ll get this fix in before the next release.
Thank you, this has me back in business. I appreciate the help reverting back a version.
Problem solved - extreme user error.
I just noticed that using the GPU (RTX2070 Super) with 2.2.7 was producing inconsistent results. Some of the uniformly noisy image (1024x1024) was being denoised, but most of it was not. None of it was being cleaned up as well as the preview. I tried it as both a TIF and JPG file; in Photoshop and as a stand alone all with the same results each time. On a whim I tried it using the CPU and sure enough it works perfectly. I haven’t really used DeNoise AI since updating from 2.2.5, but I’ve never seen it do this in any of the previous versions.
Application & Version: Topaz DeNoise AI Version 2.2.7
Operating System: Windows 10 (10.0)
Graphics Hardware: GeForce RTX 2070 SUPER/PCIe/SSE2
OpenGL Driver: 3.3.0 NVIDIA 451.85
CPU RAM: 16312 MB
Video RAM: 8192 MB
Preview Limit: 8000 Pixels
Original
CPU Processed
GPU Processed
Yes, auto update is on.
I have also tried it with auto update preview off and manually pressing preview.
Both methods work fine with AI Sharpen but do nothing in DeNoise. I will grab some logs for you after work tomorrow.
Interesting. The GPU not only doesn’t remove a lot of the noise, it actually does remove some small details, and also adds artifacts on some of the edges.
Opened in finder with “open with”. Image was not shown. Clicked on auto and DeNoise crashed.
Process: Topaz DeNoise AI [86339]
Path: /Applications/Topaz Labs LLC/*/Topaz DeNoise AI.app/Contents/MacOS/Topaz DeNoise AI
Identifier: com.topazlabs.TopazDeNoiseAI
Version: 2.2.7 (2.2.7)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Topaz DeNoise AI [86339]
User ID: 501
Date/Time: 2020-08-19 08:54:23.373 +0200
OS Version: Mac OS X 10.15.6 (19G2021)
Report Version: 12
Anonymous UUID: 62455E77-8FF3-68F5-6F46-86ADEDCEF635
Time Awake Since Boot: 390000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
terminating with uncaught exception of type cv::Exception: OpenCV(4.1.1) /tmp/opencv-20190908-5592-1dqodtz/opencv-4.1.1/modules/imgproc/src/resize.cpp:3720: error: (-215:Assertion failed) !ssize.empty() in function ‘resize’
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
You should raise a support request at the main website with this error. Also open DeNoise AI, go to Help-Graphics info press Copy and send that info too.
Compared to other Software does it the best job of all, by far.
Yeah, the CPU output is great for sure, the GPU not so much.
A few of us have posted about this for a while (e.g., DeNoise AI 2.2.12 - #117 by excorp). GPU acceleration works fine for some. For others (myself included) it rarely saves the file correctly. I’ve had the issue dating back to February. Support has acknowledged that its an issue, but there’s no estimate on a fix.
I’ve been sticking to OpenVINO and living with the slower processing.


