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. 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. 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 then launches Topaz Denoise AI and shows which files have been loaded. It first creates tif files for each raw file I have selected. ![]() ![]() 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. If you check the box in External Editor Preferences to "Stack with Original".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). The file returned may not meet the criteria for the Smart Collection and will be found in the folder with the original file.Īnother thing to consider is Stacking. Another mistake is working from a Smart Collection. The most common mistake is that the Grid view is sorted in "Added Order" and the last file added is going to be at the end of the group. If the file is returned to Lightroom and you can't find it, there are several possible situations the prevent you from finding the Topaz edited file. If I choose "Export", the saved Topaz file is returned to Lightroom. In some situations, I get an option to "Export " in Topaz. "Accept" is the function that I want to use to return the edited file to LrC. In some other situations, Topaz will ask me if I want to "Export". ![]() What I do find are two functions "Save Look" and " "Accept". In my Topaz Studio, I have neither "Save" or "Save As".It is the "Save" option that you want because that file was created by LrC and is already cataloged in Lightroom. Typically apps have a "Save" option to overwrite the file opened in the editor and a "Save As" option to create a new file. When you finish in your external Editor, you simply save the external editor changes in the image file created by LrC.This file (usually a TIFF) is sent to your external editor.creates a derivative image file with all of the LrC adjustments In general, all external editors work that same wrt Lightroom Classic I have Topaz Studio which is a different product by Topaz. Your problem has nothing to do with Topaz but external editors in general There is a very recent thread about the merits of using Topaz editors with a Lightroom Workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |