Janis1 Posted August 27 Share Posted August 27 I'm using Photo 2.5.3 on macOS 14.6.1 (23G93), Macbook Pro 16' M3 Max I have a macro "test" that I'm attaching here. The only step in macro is develop. When I apply macro manually and export picture as JPG it produces result test1.jpg (attached). When I apply the same macro in batch job and save as JPG it produces result test2.jpg (attached). How is this possible? I did many batch jobs before but did not encounter this problem. I tried both HW acceleration on and off, no difference. Original NEF file is attached as well. DSC_0031.NEF test.afmacro Quote Link to comment Share on other sites More sharing options...
Hangman Posted August 27 Share Posted August 27 Hi @Janis1 and welcome to the forums, I have to say I'm not seeing any difference when running your Macro manually or via a New Batch... The only way I can replicate the difference in appearance between your two images is by changing the settings in the Develop Assistant but that is a manual process which would need to be changed between processing the RAW file manually and using the Batch option... Perhaps a screen recording of you processing the file both ways would be helpful so we can see if there is anything obvious here that we're missing... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
carl123 Posted August 27 Share Posted August 27 If you open your 1 hour ago, Janis1 said: When I apply macro manually and export picture as JPG it produces result test1.jpg (attached). When I apply the same macro in batch job and save as JPG it produces result test2.jpg (attached). I'm seeing the same as you when doing it manually and via a batch file But... If I take your file into the develop persona and develop it, setting the Output: to Pixel Layer, then run the macro manually I get the image test1.jpg If I take your file into the develop persona and develop it, setting the Output: to Embedded or Linked,then run the macro manually I get the image test2.jpg So, I can recreate the issue without using a batch job Not sure what is going on so can you explain more about how you recorded the macro and what develop persona changes you made when recording the macro (Also please let us know what the Output: setting is defaulted to, when you first enter the persona) (Windows 11) Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Hangman Posted August 27 Share Posted August 27 8 minutes ago, carl123 said: If I take your file into the develop persona and develop it, setting the Output: to Pixel Layer, then run the macro manually I get the image test1.jpg If I take your file into the develop persona and develop it, setting the Output: to Embedded or Linked,then run the macro manually I get the image test2.jpg This appears to be influenced by the Develop Assistant Settings... When the Tone curve and Exposure Bias are set to Take no action, there is almost no difference between the Developed Image as a Pixel Layer or RAW (Embedded or Linked) Layer once the Macro is applied, however, there is a noticeable difference between the two images if a Tone Curve is applied once the Macro is run... The Exposure Bias on its own again makes little difference to the output of the two images... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
carl123 Posted August 27 Share Posted August 27 7 minutes ago, Hangman said: When the Tone curve and Exposure Bias are set to Take no action, there is almost no difference between the Developed Image as a Pixel Layer or RAW (Embedded or Linked) Layer once the Macro is applied, however, there is a noticeable difference between the two images if a Tone Curve is applied once the Macro is run... True But with the tone curve enabled and exporting to pixel or embedded/linked the effect is the same (no difference in the image) So, we need to know what's in that macro that is affecting the image so much Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 @Hangman screen recording attached How I created the macro: Open NEF, click develop, go to macro panel, click record, go to develop persona, adjust develop params (exposure, enhance and shadow & highlights parts), develop, stop macro recording. Screen Recording 2024-08-27 at 12.05.56 PM.mov Quote Link to comment Share on other sites More sharing options...
Hangman Posted August 27 Share Posted August 27 3 minutes ago, carl123 said: But with the tone curve enabled and exporting to pixel or embedded/linked the effect is the same (no difference in the image) On Mac, I'm seeing a noticeable difference... Develop Assitant Settings (Only Apply Tone Curve Applied)... Output set to Pixel Layer, Develop Button selected then the Macro Applied results in this... Output set to RAW Layer (Embedded) Develop Button selected then the Macro Applied results in this... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
Hangman Posted August 27 Share Posted August 27 4 minutes ago, Janis1 said: How I created the macro: Open NEF, click develop, go to macro panel, click record, go to develop persona, adjust develop params (exposure, enhance and shadow & highlights parts), develop, stop macro recording. Could you upload a screengrab of your Develop Assistant Settings... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
carl123 Posted August 27 Share Posted August 27 4 minutes ago, Hangman said: On Mac, I'm seeing a noticeable difference... What I'm saying there is no difference, with tone curve enabled. before applying the Macro whether you use pixel or embedded/linked So, the macro is what needs investigating Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 ... with tone curve set to "No action" the pictures are similar (both attached), but still there is a small difference. It seems that develop persona assistant is applying some changes to the picture that batch job is not. ... with tone curve set to "Apply tone curve" the pictures are vastly different (attached in original post above). Any idea how to achieve consistent results with both develop persona and batch job? Quote Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 6 minutes ago, Hangman said: Could you upload a screengrab of your Develop Assistant Settings... Attached. This is with tone curve set to "No action", i.e. the post above, where the pictures are very similar via batch and manual macro run, but still not the same. Quote Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 7 minutes ago, carl123 said: What I'm saying there is no difference, with tone curve enabled. before applying the Macro whether you use pixel or embedded/linked So, the macro is what needs investigating I'm not seeing the same. Even after opening RAW picture, disabling develop assistant and clicking develop and saving as JPG produces different result than simple batch job that converts RAW to JPG (i.e. no macro is involved in the process). Quote Link to comment Share on other sites More sharing options...
Hangman Posted August 27 Share Posted August 27 3 minutes ago, Janis1 said: ... with tone curve set to "No action" the pictures are similar (both attached), but still there is a small difference. Agreed, there is a subtle small difference... As @carl123 mentions above, I don't think running the Macro via the Batch option makes any difference, it seems to be whether you select Pixel Layer or RAW Layer (Embedded / Linked) from the Context toolbar before Developing the image that makes the difference... I'm seeing the same outcome on both Mac and Windows... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 2 minutes ago, Hangman said: Agreed, there is a subtle small difference... As @carl123 mentions above, I don't think running the Macro via the Batch option makes any difference, it seems to be whether you select Pixel Layer or RAW Layer (Embedded / Linked) from the Context toolbar before Developing the image that makes the difference... I'm seeing the same outcome on both Mac and Windows... True. Thanks for the insight. Can someone explain what is happening when "Pixel Layer" is selected so it changes the result so much? Quote Link to comment Share on other sites More sharing options...
carl123 Posted August 27 Share Posted August 27 5 minutes ago, Janis1 said: Thanks for the insight. Can someone explain what is happening when "Pixel Layer" is selected so it changes the result so much? That's what we are looking into now, now that we have the steps you do in the macro Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
carl123 Posted August 27 Share Posted August 27 1 hour ago, Janis1 said: Can someone explain what is happening when "Pixel Layer" is selected so it changes the result so much? OK, on the image below those are the values the macro sets when run against a RAW file. I manually entered these values on your Raw image in the develop persona and the result are the same. So, the macro is doing exactly what is set in the macro The fact that the macro appears to work when you develop the RAW file to a pixel layer, I think is a Red Herring. The macro contains settings that were recorded in the develop persona and thus specific to RAW files. So, when you run that macro on a pixel layer some of those settings may not be applicable or may be out of the range that a pixel layer can understand/process compared to a RAW file The question now becomes are these the values (below) you entered when you recorded the macro or have they become corrupted/changed somehow, when the macro was saved? Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 3 minutes ago, carl123 said: OK, on the image below those are the values the macro sets when run against a RAW file. I manually entered these values on your Raw image in the develop persona and the result are the same. So, the macro is doing exactly what is set in the macro The fact that the macro appears to work when you develop the RAW file to a pixel layer, I think is a Red Herring. The macro contains settings that were recorded in the develop persona and thus specific to RAW files. So, when you run that macro on a pixel layer some of those settings may not be applicable or may be out of the range that a pixel layer can understand/process compared to a RAW file The question now becomes are these the values (below) you entered when you recorded the macro or have they become corrupted/changed somehow, when the macro was saved? Those are correct values that I used in macro. Quote Link to comment Share on other sites More sharing options...
Janis1 Posted August 27 Author Share Posted August 27 Maybe vibrance was set as well, I don't remember exactly. Quote Link to comment Share on other sites More sharing options...
carl123 Posted August 27 Share Posted August 27 29 minutes ago, Janis1 said: Those are correct values that I used in macro. Then in that case I think the macro was recorded with Tone Curve off but when the batch file was run Tone Curve was on In V2 you can't be in the develop persona when you switch the Tone Curve settings as it is no longer dynamic. If you are in the develop persona when you change it you have to exit and reenter the develop persona to see any change There may be another anomaly which is contributing to this but I'll test that tomorrow walt.farrell 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
Janis1 Posted September 2 Author Share Posted September 2 Has there been any resolution to why this is happening? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 2 Share Posted September 2 1 hour ago, Janis1 said: Has there been any resolution to why this is happening? Did you check @carl123's idea about the Tone Curve setting in the Develop Assistant when you recorded the macro? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Ldina Posted September 2 Share Posted September 2 6 hours ago, Janis1 said: Has there been any resolution to why this is happening? Janis, it's not happening at all with me (assuming I have done it properly). Here's what I did... I opened a RAW DNG file (CR2 converted to DNG using Adobe DNG converter) and made only two adjustments in the Develop Persona. I set Exposure to -0.5 and Blacks to -10. No other changes at all. I had develop assistant set to 16 bit and to apply tone curve, color space set to Display P3. I developed it as a pixel layer and saved the file in afphoto format without making any additional changes. Then, I opened the same DNG file and developed it as a Linked file and saved it. When I copy and paste one file and place it above the other, then set the blend mode of the top layer to Difference, I see a completely black screen. Running my cursor over the image, the Info panel shows RGB 0/0/0, without any fluctuation, telling me the images are identical. Next, I recorded a macro (using my saved linked file). I started the Macro recording, clicked Develop, made sure my develop settings were the same as above, clicked on Develop (linked), and saved the resulting macro. I ran a Batch job on that one RAW DNG file, applied that macro, and saved it in afphoto format. I copied and pasted the batch created file over one of the manually developed files, set the blend mode to Difference, and I didn't see anything but black. Running my cursor over the image, the Info panel shows RGB 0/0/0, without any fluctuation, telling me the images are identical. So, in my simple test, manually developing to a Pixel layer, or linked, or running a batch file with a develop macro, all using the same Develop settings, resulted in identical files. Perhaps more aggressive Develop adjustments, (e.g.., saturation, WB, contrast, curves, etc), may yield different results, but I did not test that. EDIT: By the way, I left the Develop Assistant settings constant throughout, always set to 16 bit, Apply Tone Curve, and also had my default RGB profile set to Display P3. I never disabled the Tone Curve. EDIT: I'm on a MacBook Pro, and this morning's test was done using APhoto v2.5.5 (just released this morning). Quote 2024 MacBook Pro M4 Max, 48GB, 1TB SSD, Sequoia OS, Affinity Photo/Designer/Publisher v1 & v2, Adobe CS6 Extended, LightRoom v6, Blender, InkScape, Dell 30" Monitor, Canon PRO-100 Printer, i1 Spectrophotometer, i1Publish, Wacom Intuos 4 PTK-640 graphics tablet 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.