Daniel Schmidt Posted December 2, 2016 Share Posted December 2, 2016 Affinity Photo 1.5.0.43 (Beta) should ignore unknown image ressource blocks inside PSD (and PSB) files. Currently it stops the export and shows an error message (unknown signature: psdM [1]). Photoshop simply ignores such blocks (and discards them, so they are not saved by Photoshop). This mechanism ensures older Photoshop versions can read the files of newer versions. In my case this block contains custom meta data embedded in an image ressource block (3D Data camera position from Autodesk 3ds max). This data is for example used by an After Effects plugin. PSD file is attached and a screenshot of the error message. This PSD file will import fine in all Adobe applications. I'm happy to test this again as soon as this is fixed. Let me know if you need any further details. Daniel Untitled.psd Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted December 2, 2016 Staff Share Posted December 2, 2016 Daniel, Welcome to the Serif Affinity forums :) Thanks for the clear report and the sample file, we will verify and report it 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...
local306 Posted December 4, 2016 Share Posted December 4, 2016 Hello, Any updates on this bug? I think I may have run into the same issue. I'm currently working with Marmoset's Toolbag 3 to bake textures for 3D assets. Whenever I toggle from Toolbag to save as multi-layer PSD, I am unable to import the document. For the time being, I have been baking maps individually so I can bring them in one at a time into Photo. This isn't the most ideal and is fairly time consuming. I'm hoping this will be cleared up soon :) Link to comment Share on other sites More sharing options...
Daniel Schmidt Posted December 7, 2016 Author Share Posted December 7, 2016 Hast this been logged? Still in RC2. Daniel Link to comment Share on other sites More sharing options...
Staff MEB Posted December 7, 2016 Staff Share Posted December 7, 2016 Hi Daniel, Welcome to Affinity Forums :) Yes, this is already logged and i believe the fix will be included in next Beta (or the following). Let me know if not. A Guide to Learning Affinity Software | Affinity Quick Reference Link to comment Share on other sites More sharing options...
Daniel Schmidt Posted December 15, 2016 Author Share Posted December 15, 2016 Is this fixed in the Customer Beta 1.5.1.46? I see there were some PSD related fixes (mainly for another reported bug I think) but I personally can't test without a license. If someone that has a license wants to help, just try to open the small file attached to the first post and see if it opens without error in 1.5.1.46. Daniel Link to comment Share on other sites More sharing options...
Staff MEB Posted December 15, 2016 Staff Share Posted December 15, 2016 Hi Daniel, Yes it opens without issues in 1.5.1.46 (Beta). A Guide to Learning Affinity Software | Affinity Quick Reference Link to comment Share on other sites More sharing options...
Daniel Schmidt Posted December 15, 2016 Author Share Posted December 15, 2016 Hi Daniel, Yes it opens without issues in 1.5.1.46 (Beta). Thank you for the fast reaction to the reported issues. Daniel Link to comment Share on other sites More sharing options...
Recommended Posts