![]() I processed the image with all four DeNoise methods at application default (Auto) and again with Sharpeness maxed at 100, output as TIF then converted to JPG in Lightroom 6.14. I used one Canon CR3 RAW image (a duck in flight) converted to TIF in four different programs: Affinity Photo 1., Digital Photo Professional 4.14, FastStone Image Viewer 7.5 and Luminar 4.3.3 (7895). The speed is a nice improvement.Īs to image quality output, I ran a series of settings to compare methods. The sharpening is very mild and could be a bit more aggressivs but not like 2.3.x. I thought 2.3.x noise reduction was quite good, the sharpening could get aggressive and the speed was acceptable.ģ.1.1 noise reduction is fairly good, not great, but not bad. This would also fix 3.3.0.Ĭopy LR template file: /Applications/Topaz Labs LLC/Topaz DeNoise AI/Topaz DeNoise AI.app/Contents/Resources/TopazDeNoiseAI.I haven’t had 2.3.x installed since 3.x came out so I have to go by memory. Once this is resolved in this version it should not have to be modified again.Īlso, worst case for Mac users is to copy the lrtemplate to the the Adobe LR external editor folder. As far as we’ve tested this should fix the LR flow, but it does require some additional steps due to how the integration works. Please make sure to close/reopen Lightroom after installing to ensure the latest file is loaded.I’ll have instructions for this at the top of the thread shortly. You will need to go to preferences and set your external editor to the new template file.You will need to open the standalone application for the template to install/update fully. I’m hoping with the 3.3.1 update you can restore the option to have Denoise overwrite the Tiff so I don’t need to do any synchronizing or deleting.įor anyone with Lightroom issues, please download 3.3.1. In past versions Denoise just overwrote the Tiff sent to it from LR and that then auto updated in LR once it was saved. With the 3.3.0 update I end up with an extra Tiff that I have to sync back into LR (easy enough to do but another annoying step) then need to delete the first Tiff (again, easy (hit X, hit CMD Del) but another step). Therefore I have always done my cropping LR first, then LR sends the cropped version of a Tiff to Denoise (via Edit In: Denoise) and that greatly speeds up the processing of Denoise when saving back to LR. I hope this will resolve back to the old way of roundtrip out of LR.Įven though I am tempted by the new RAW option and have now watched the video to show how to initiate the sync folders to show the new DNG, the issue I have is that I do a lot of cropping with my images. I am hopeful that you will reanimate the LR-plug-in, otherwise the version 3.2 will be the last DenoiseAI-version for me and I have to look for other denoise-programs with a better integration in the LR-workflow. Only when I exported the RAW-file to tif in LR and opened the tif-version in Denoise the result was as satisfying as in the plug-in-work but the work-flow was much more complicated (export, import, synchronise). I tested the workflow I saw in the video with the 3.2-version and had no satisfying results and a cumbersome workflow with dng- or nef-file. I choose to edit in DenoiseAI, LR creates a tif-file, gives it to Denoise, that program makes his great job and saved the changes back into the tif-file, that was automatically updated in LR. It is so easy to use DenoiseAI, right click on the RAW-file in LR opens the edit-dialogue. anymore? Must I in future use the stand alone version of DeNoise? Why did you change the workflow for Lightroom User? Did the plug-in do not work from version 3.3. This change prevents that from happening. Previously these would open in external editor mode and people would unknowingly overwrite their files. Sorry for all the issues with external editor mode, but this sudden change is required for us to fix drag and drop onto the icon to edit in standalone, as well as right click > open with flows as well. There also is a bug on Mac where if the template doesn’t exist it doesn’t get dropped correctly, and that will be resolved in 3.3.1 later today. I believe on both Windows and Mac if you have two entries and one opens Standalone and one opens External Editor, then you will need to restart LR, or update the template in preferences. Also if you have any manually created presets you will need to update them to point to the External Editor shortcut which is in the same directory as the Topaz DeNoise AI.exe file. ![]() If you are on Windows, make sure you close/reopen Lightroom if it was open during the install. I don’t think we messaged some of these changes correctly so there is some confusion. Quick update, we are working on the external editor issue and there should be a release later today that fixes it.
0 Comments
Leave a Reply. |