andersp5 Posted July 15, 2023 Share Posted July 15, 2023 AFPhoto V2.1.1 Problem: Edited and saved Denoise Macro from existing Denoise Macro doubles the Luminance and Colour parameters in the resultant noise reduction layer when ran. note : Luminance Detail is not affected by this. 1) create a macro using live filter denoise with Luminance and colour set to 2. 2) Save the macro call it "test" 3) Run the macro and check the Noise Reduction layer parameters that it created, it will show correctly as Luminance 2 and Colour 2 4) Delete the Noise Reduction layer that the macro "test" created 5) Go to macro "test" in the library and select Edit macro. You will find Luminance and Colour will show as 1. Change them both to 4 6) Save this back into the library as "Test 2". Test 2 will have parameters of Luminance of 4 and Colour of 4 7) Run macro "Test 2" 😎 Check the Noise Reduction layer just created by Test 2 and you will see that the Luminance and Colour are both set to 8 and NOT 4 What appears to be happening is that when you edit a macro using the Denoise Filter as an example for Luminance and Colour from an existing macro, (I do not know if this applies to other filters) and increase the parameters, when that saved macro is then ran it doubles the saved parameters in the output noise reduction layer. It does this for any parameter figure such as 30 doubles to 60 etc! Check it and you will see what happens it only does this when you edit an existing Macro and save it back as a new macro and run the new saved macro for Luminance and Colour in denoise. It might do it with other parameters in other filters but I have not tested for that. Original Denoise macros work correctly when ran. Problem only applies to saved edited denoise macros where these parameters have been changed. Has anyone else come across this in other edited macro's? I had never checked the output was the same as the input for copied edited macros with parameter adjustments because until now I assumed it was just an edited copy and thus this doubling effect was not noted, till I saw a difference in the denoise output from the original macro to the edited macro copy and thus how I found this. It might just be this one filter hopefully? Quote Link to comment Share on other sites More sharing options...
Dan C Posted July 17, 2023 Share Posted July 17, 2023 Hi @andersp5, Thanks for your report! I can confirm that I've been able to replicate this here, and thus far it appears to only occur with the Live Denoise Filter as you've found. I'll be logging this with our dev team now to be resolved ASAP. I hope this helps Quote Link to comment Share on other sites More sharing options...
andersp5 Posted July 18, 2023 Author Share Posted July 18, 2023 Thanks Dan, very much appreciated. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.