kaffeeundsalz Posted November 30, 2018 Share Posted November 30, 2018 I just noticed this when I tried to implement some of the new 1.7 features into our production workflow. I edited an image with the current Affinity Photo Beta and exported it as a TIFF file. For export options, I basically set the same parameters that I have a preset for in 1.6 (TIFF, CMYK 8-bit, Uncoated FOGRA29, Embed ICC profile, do not embed metadata). When I try to place this TIFF image in Adobe InDesign, I get an error message saying that the file is incompatible or damaged. However, TIFF images exported in Affinity Photo 1.6 with the very same export options are readable by InDesign. Is there something that has changed in TIFF export, or am I doing something wrong? Link to comment Share on other sites More sharing options...
Wosven Posted November 30, 2018 Share Posted November 30, 2018 I confirm this, I had the same problem but no time to do more tests than importing one file. Link to comment Share on other sites More sharing options...
Staff MEB Posted November 30, 2018 Staff Share Posted November 30, 2018 Thanks kaffeeundsalz, Wosven, I'm logging this to be looked at. Wosven 1 A Guide to Learning Affinity Software Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted November 30, 2018 Staff Share Posted November 30, 2018 The tiff export format was deliberately changed so I'm not surprised to see this report. Disappointed, but not surprised Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
kaffeeundsalz Posted December 15, 2018 Author Share Posted December 15, 2018 This seems to be fixed since the previous beta, presumably because Serif "Fixed TIFF ZIP compression issues" as it says in the changelog. Just out of curiosity, @Patrick Connor: Do you mean disappointed in a way that you had hoped to fix compatibility issues with tiff export and accidentally created some new ones? If that is the case, wouldn't it be a good idea to reconsider giving us some more options in the TIFF export settings? Especially related to compression methods? I'm not saying that the export dialog should be as complicated as in Photoshop, but it seems to me that there are cases where you would need to tweak a specific setting currently not accessible in Affinity Photo to make exported TIFF files readable by other apps. I know that this has been discussed before, and sometimes extensively, but it seems to fit in here quite well. Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted December 15, 2018 Staff Share Posted December 15, 2018 5 hours ago, kaffeeundsalz said: Do you mean disappointed in a way that you had hoped to fix compatibility issues.... I was not hoping to fix anything. I head up the QA team. I was not surprised because with 10 years experience any change to export flushes out compatibility issues. The fix was to use a more modern compression algorithm that other applications "should" support, but the disappointment is that as always you will quickly find that other applications do not support all the features that tiff can implement. So this week we have NOT reverted to the original method, but are using another compression (one that Adobe use) so it should have less compatibility issues and still be better that LZW that we were using. I do not have a strong opinion about other options on the export dialog, though in this case it would have given a work around. kaffeeundsalz 1 Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
walt.farrell Posted December 15, 2018 Share Posted December 15, 2018 20 minutes ago, Patrick Connor said: So this week we have NOT reverted to the original method, but are using another compression (one that Adobe use) so it should have less compatibility issues and still be better that LZW that we were using. In case we have problems with other applications, can you tell us what method you're using now, if it isn't LZW? -- 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...
Staff Patrick Connor Posted December 17, 2018 Staff Share Posted December 17, 2018 On 12/15/2018 at 6:00 PM, walt.farrell said: In case we have problems with other applications, can you tell us what method you're using now, if it isn't LZW? We are now using Adobe Deflate in the latest 1.7 betas on Mac and Windows (i think this link is useful). kaffeeundsalz and walt.farrell 2 Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
fde101 Posted December 17, 2018 Share Posted December 17, 2018 Any particular reason to not make the compression method user-selectable? ronnyb 1 Link to comment Share on other sites More sharing options...
ronnyb Posted December 21, 2018 Share Posted December 21, 2018 Yes, PLEASE allow the user to select which type of compression; these issues are critical when working in legacy environments, and print shops are notorious for having legacy equipment... On 12/17/2018 at 7:47 AM, fde101 said: Any particular reason to not make the compression method user-selectable? 2021 16” Macbook Pro w/ M1 Max 10c cpu /24c gpu, 32 GB RAM, 1TB SSD, macOS Sequoia 15.1 2018 11" iPad Pro w/ A12X cpu/gpu, 256 GB, iPadOS 18.1 Link to comment Share on other sites More sharing options...
Fixx Posted December 29, 2018 Share Posted December 29, 2018 For most users compression on/off switch would be enough (and well liked). Link to comment Share on other sites More sharing options...
Recommended Posts