Hi,
I finally updated my DeNoise AI install to version 2.
I have just spent an hour trying to get it to process one of my Canon 5DSR images as a plug in in Photoshop CS6. I tried every combinations of GPU or openVINO settings. Each time the plug in processed all the way to 100% and then the plugin crashed leaving Photoshop running and the image unprocessed.
Finally, I reduced the image size from the original 8688x5792 to 3000x2000 pixels and the plug in ran successfully, which suggests that the issue is related to the file size.
It is very disappointing to think that the latest upgrade has introduced this problem.
Based on that, it is very unlikely to be HW related.
To the OP, I would:
a) turn file-logging on: [Help->File-logging] (debug dump/trace logs will be created while toggled)
b) run v2 with File-X and let it crash (important to have crash reproduced)
c) open a support ticket (support@topazlabs) and get a DropBox link to upload your file-X.
d) tell them that you have crash-dump files for them to analyze. They can tell you what dir the files will have been output/written to
e) upload the crash-dump files to the DropBox link
f) wait for the devs to analyze the trace and see where the app is crashing
This sounds like a memory allocation (ie SW) defect introduced in v2.
So, the change of the install location dir caused the preferred GPU setting to go back to the default setting? There was no avoidable way to prevent that? Could the settings not have been automatically copied from the old location? That’s a bad burn.
In any event, if v1 does not crash with whatever the selected GPU/memory is set to then v2 should not crash either, correct?
Yes that is so because the GPU settings on Windows, in these Apps cases, are set either using the respective Control Panels for the GPU manufacturers or through the Win 10 Graphics settings. I guess this is a limitation of the Qt interface because of the cross platform portability.
In any case we don’t even know the posters OS, RAM, GPU etc, in many cases the updates may be getting closer and closer to requiring the minimum technical requirements but this case is a little strange because the standalone version is crashing also, if it was just PS I would recommend reducing the resources available to PS as it pre-allocates those on start up.
In any case your recommendation will work but it may take longer to process as if it is a simple resource issue it can be readily solved.
Yes, the OP should double-check and make sure no inadvertent changes were made to the GPU selection. As you mentioned, Help->Graphics-Info is the quickest way to verify that.
Although the official support response was a diagnosis that my computer did not meet the minimum requirements to run Denoise AI v2, someone at Topaz fixed the actual problem and the latest version 2.2.1 runs great on my machine.
Great! Did they make a change on your system? Or a change to the application?
BTW, even when if a system doesn’t meet the min requirements, the app should NOT crash. That’s a programming defect anyway you slice it ie an ungraceful catch of an error condition.
I just ran a test; In addition to being able to run the Denoise version 2.2.1 process on my native resolution Canon 5DSR files, which are 8688 x 5792 pixels, my system can also process images that I have doubled in size using Gigapixel. In other words, version 2.1.6 could not, on my system, process a image that was 8,688 x 5,792 pixels, but version 2.2.1 can process an image that is 16,602 x 11,122 pixels. That’s quite an improvement.
FWIW, version 1 could and does run the process on the same 16,602 x 11,122 pixel files as well.
