TomM1 Posted November 29 Share Posted November 29 Batch processing tiff images to jpgs (horizontal and verticle). When I include a macro that changes 300 DPI to 72 Dpi, the aspect ratio is not preserved and the horizontal images get squished. See the screen shot of settings. Quote website Mac mini (2018) 3.2 GHz Intel Core i7 64 GB • Radeon Pro 580 8 GB • macOS Monterey Link to comment Share on other sites More sharing options...
GarryP Posted November 30 Share Posted November 30 I don’t know much about the batch exporting functionality but if I was telling the software to export as 640x640 and my images are not ‘square’ then I would expect to get some ‘squishing’ somewhere along the line, even with Preserve Aspect Ratio switched on (I would be essentially overriding the ratio preservation). Removing either the W or H value should get you what you want, I think. Quote Link to comment Share on other sites More sharing options...
PaulEC Posted November 30 Share Posted November 30 As long as the "A" is ticked, it should set the longest side (H or W) to the setting you've chosen, and the other to the right size to maintain the correct aspect ratio. However, AFAIK, the problem may be with the macro, which uses whatever image size you used when creating the macro. (There may be a way around this, but I don't use macros much myself.) Quote Acer XC-895 : Core i5-10400 Hexa-core 2.90 GHz : 32GB RAM : Intel UHD Graphics 630 : Windows 10 Home Affinity Publisher 2 : Affinity Photo 2 : Affinity Designer 2 : (latest release versions) on desktop and iPad "Beware of false knowledge, it is more dangerous than ignorance." (GBS) Link to comment Share on other sites More sharing options...
GarryP Posted November 30 Share Posted November 30 I’ve just done a quick test using three images of different aspect ratios, and exported them at 300x300 and Preserve Ratio, and each came out with the same aspect ratio as they had before the export, as far as I can tell. (So my initial assumption was wrong, I think.) So I think you might be right and the macro could be ‘messing with stuff’. Quote Link to comment Share on other sites More sharing options...
TomM1 Posted November 30 Author Share Posted November 30 There seems to be some issue with including a dpi change (without changing the pixel dimensions) in the macro. Quote website Mac mini (2018) 3.2 GHz Intel Core i7 64 GB • Radeon Pro 580 8 GB • macOS Monterey Link to comment Share on other sites More sharing options...
TomM1 Posted December 2 Author Share Posted December 2 So there must be a way to change the dpi in a batch process? Quote website Mac mini (2018) 3.2 GHz Intel Core i7 64 GB • Radeon Pro 580 8 GB • macOS Monterey Link to comment Share on other sites More sharing options...
David in Яuislip Posted December 2 Share Posted December 2 This has been an issue (AF-990) for yonks but a Bot post on November 26 claims that this has been fixed in beta 2.6.0.2900 and will be incorporated into the next customer release Until then you can use exiftool eg exiftool -Xresolution=96 -Yresolution=96 *.jpg Quote Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10 Link to comment Share on other sites More sharing options...
TomM1 Posted December 2 Author Share Posted December 2 36 minutes ago, David in Яuislip said: This has been an issue (AF-990) for yonks but a Bot post on November 26 claims that this has been fixed in beta 2.6.0.2900 and will be incorporated into the next customer release Until then you can use exiftool eg exiftool -Xresolution=96 -Yresolution=96 *.jpg Ok I will wait. Meanwhile I had to complete the project "manually". Quote website Mac mini (2018) 3.2 GHz Intel Core i7 64 GB • Radeon Pro 580 8 GB • macOS Monterey Link to comment Share on other sites More sharing options...
walt.farrell Posted Tuesday at 12:02 AM Share Posted Tuesday at 12:02 AM It is also possible to use one of the "change DPI" macros that have been provided in the Resources section and which were recorded in Affinity Photo 1.6, before the bug was introduced in 1.7. E.g., John Rostron 1 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...
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.