Jump to content

Recommended Posts

Posted

Hello out there!

For an exhibition catalog, I need to edit several dozens photographs of different size. Now I have tried to set up a macro in AfPhoto, which should only change the resolution of the images (but not their absolute pixel size) and convert them to aRGB.

Now I realize that in the macro not only the new resolution is applied to the new image - but all subsequent images are also given the pixel size of the first image! Although I made sure to de-activate the “recalculation” checkbox in the size/resolution dialogue when recording the macro. Therefore the pixel counts are grayed out – and should be ignored while erecording the macro (as it is done in PSD...).

Is this another one of the Affinity development team's tricks?
How do I get a macro that simply changes the image resolution but not the size?

 

Thanks and best wishes!
Johannes

Posted
9 minutes ago, jweitzel said:

Now I realize that in the macro not only the new resolution is applied to the new image - but all subsequent images are also given the pixel size of the first image!

Yeah, it broke in a distant update and was never fixed

@John Rostron wrote some macros using a version that worked which should still work today

Add to your Library panel then test and see if they are OK

 

Change DPI 1.6.afmacros

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.

Posted
15 minutes ago, jweitzel said:

Is this another one of the Affinity development team's tricks?
How do I get a macro that simply changes the image resolution but not the size?

As far as I know you would record the macro using Affinity Photo 1.6. A bug was introduced in 1.7 that broke the handling of the Resample toggle in the Resize dialog for macros.

Try these: 

 

 

-- 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.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4

Posted

Many, many thanks to both of you!

I still had the thread you quoted in the back of my mind. But I find it a bit frustrating that nothing more has happened since then. They rather realize a "inverting spectral filter" or “walking on the moon”, which the community needs once a year. It seems to me (not for the first time) like a drilling machine where the development team is working on the 16-speed hydro gearbox, but the electrical plug always falls out of the socket by itself - but they have no time to fix it.

I'm so sorry...

Johannes

Posted
3 hours ago, jweitzel said:

...I need to edit several dozens photographs of different size. Now I have tried to set up a macro in AfPhoto, which should only change the resolution of the images (but not their absolute pixel size) and convert them to aRGB.

Maybe I am missing something. You want the 1200 x 900 pixel image to be 1200 x 900 pixels after conversion, correct? Why do you need to change the DPI/PPI?

You can run a batch job to change them to sRGB, no need for a Macro.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Posted

I am currently preparing the typesetting (and print) of a catalog of an artist's works. For me, this includes image processing, in the course of which I prepare the material to 300 dpi (delivered from the cameras as 72 or 144 dpi) and AdobeRGB. In terms of resolution, it is therefore a matter of setting this to 300 dpi WITHOUT changing the absolute pixel dimensions.

I have no interest in declaring any of those work steps superfluous or similar at this point. Some days ago I just have learned that AFPub is not even able to correctly convert a 4c document with process black text into an other 4c color profile without losing the black.

Best wishes to you, Bruce!
Johannes

Posted

FYI, the bug tag for this problem is AF-990. It would be good of them to fix this in V2.

-- 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.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4

Posted

Hello Walt, I am always impressed of your knowledge!

At my company, they had a small, young team to program the software themselves (media & publishing branch). The software was supposed to map all production processes, all administration, correspondence and even great parts of the warehousing. I was one of the people who had reservations and advised buying a commercial solution “off the shelf”. But the boss forced it through. Productivity dropped to what felt like 50%, and cries of despair and curses could be heard from every office. And the bug list or to-do list grew longer by every hour. After about 1.5 years, there were several thousand of bug items in the queue. But then came the decisive solution from the management team! The entire bug list was declared null and void, as no one would have been able to work through it anyway and no one would have been able to prioritize it. And everyone was asked to report bugs - if they found any.

That's how effective management works!

 

Posted
16 hours ago, walt.farrell said:

FYI, the bug tag for this problem is AF-990. It would be good of them to fix this in V2.

This was a regression; it should have been fixed a long time ago

Unless there's a reason for it, they are not telling us

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.

  • 4 months later...
  • Staff
Posted

The issue "Resample tickbox ignored and always true when recording a macro" (REF: AF-990) has been fixed by the developers in the latest beta build (2.6.0.2900). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.