![]() Then I have to actively load my new tifs into Lightroom. If I run through Topaz directly, at the end I have both the original tif files (which I no longer want) and the modified tif files. One benefit of the Topaz plug-in from Lightroom is that tif files are first created and then overwritten to the same filename after Topaz processing, so there is no need for me to actively find and delete the original tif. It appears to add a few other cumbersome steps. I am able to take un-Topaz-processed tif files and load them directly into Topaz Denoise and work from there, but I have not figured out a good workflow with that technique. If no one has any solutions, please share workflow suggestions as workarounds. I have corresponded with Topaz support, and they insist that it is a bug in Lightroom. I do not believe it to be a memory issue, since I've watched the Windows Task Manager during the batch processing, and it doesn't get above 60% memory. Not sure if there is a log file somewhere with more information. Going between the i5, i7, and i9 models only net a relatively small 13 increase in performance. There are no overt messages of any kind from either Lightroom Classic or Topaz Denoise, only my knowledge that there should be more files in Topaz but they aren't there. Based on our testing in Topaz Gigapixel AI, Sharpen AI, Denoise AI, and Video AI, the best overall CPU for Topaz AI is Intel’s Core 13th Gen family of processors. This is a huge workflow bottleneck as now it takes me much longer to process a large number of photos (I'm typically processing ~150-200). However, it is now at the point where, no matter how many times I re-do the process, it only loads a small number (sometimes 18, sometimes 25, etc) when it launches Topaz Denoise. Most of the time if it didn't work, it would work after I deleted all of the created tif files and re-tried the process. It used to be that sometimes it would load all of the tif files, sometimes it would load only a portion of them. ![]() It worked fine until midnight and after that it crashes every time I. It then launches Topaz Denoise AI and shows which files have been loaded. From today Topaz Denoise AI and Sharpen AI crashes on Macbook M1 Max (2021) 32 Gb/1 Tb. Now, On1 has launched their own specialist AI-driven software to snap at its. Then, Topaz DeNoise AI came along and changed the game. After I start processing an image, DeNoises memory usage does of course increase (in one sample image from 300 MB to 1. It first creates tif files for each raw file I have selected. In raw processing, it can leave images looking muddy. Now, both Denoise AI and Sharpen AI are CRASHING, every time. It was an unnumbered update, in that the version stayed at 11.5. I recently updated my MacBook Pro to the latest version of Big Sur. fogcitynative (fogcitynative) July 22, 2021, 5:24am 1. ![]() Note that I have had this same problem on prior versions of both Topaz Denoise and Lightroom Classic.įrom Lightroom Classic, I use the Photo -> Edit In -> Topaz Denoise AI command. Topaz Products Product Technical Support. I'm wondering if anyone has had the same problem as I have on Windows with Topaz Denoise AI (v 3.4.2) run as a plug-in on Lightroom Classic (v 11.1). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |