gw_westdale Posted June 19, 2024 Posted June 19, 2024 Imported vector brick wall from an *.ai file , wrote the graffiti as art text , rasterised the layers. Export to jpeg gave this error. Tried again and export just had a hang-loop. Question out of curiosity ... what sort of metadata is being exported here as there is no camera data or similar ? In my case a simple fix was to turn off 'export metadata' in the export dialogue as I did not have any need of it. Hope this may help in analysis of the problem. (Windows 11 Envy i7 desktop 32Gb RAM Designer 2.5.2) brickwall_brickwall2.afdesign Quote Win 11 PCs 64bit Envy and Envy tablet + Filter Forge Retired computer systems tester doing graphics for charities and politics etc.
Hangman Posted June 19, 2024 Posted June 19, 2024 5 hours ago, gw_westdale said: Export to jpeg gave this error. Same on Mac for JPEG, TIFF and PSD files when Embed Metadata is checked but fine exporting to PNG when Embed Metadata is checked... Quote Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
gw_westdale Posted June 19, 2024 Author Posted June 19, 2024 2 hours ago, Hangman said: Same on Mac for JPEG, TIFF and PSD files when Embed Metadata is checked but fine exporting to PNG when Embed Metadata is checked... For some people when including photos that may be because PNG does not contain EXIF ? I am just wondering, having typed that, if there is a problem when there is NO metadata to include 🙂 Quote Win 11 PCs 64bit Envy and Envy tablet + Filter Forge Retired computer systems tester doing graphics for charities and politics etc.
Staff NathanC Posted June 21, 2024 Staff Posted June 21, 2024 Hi @gw_westdale, On 6/19/2024 at 9:28 AM, gw_westdale said: Question out of curiosity ... what sort of metadata is being exported here as there is no camera data or similar ? Since the file started out life as an .AI file there's plenty of metadata that's carried over from AI. If you have access to Photo 2 open the 'Detail' tab in the Metadata panel you'll see there is both XMP and EXIF data within the file. There doesn't appear to be a way to clear the erroneous data within the app that is causing this error on export to JPEG/TIFF/PSD, I'll get this doc logged with the developers for further investigation. Since exporting to PNG works with the data embedded, I did find that importing the PNG back into the apps and subsequently exporting as JPEG again does appear to fix it, quite unusual. Also, do you have a copy of the original .AI file prior to importing and saving it in Designer? Quote
gw_westdale Posted June 22, 2024 Author Posted June 22, 2024 I did some further exploration for you. Opening Designer, placing the AI file, writing the text, exporting to JPEG - fine Opening the AI file with Designer , writing the text , exporting to JPEG - metadata error DD Vector Brick Wall Texture 34231_DD Vector Brick Wall Texture 34231.ai Quote Win 11 PCs 64bit Envy and Envy tablet + Filter Forge Retired computer systems tester doing graphics for charities and politics etc.
gw_westdale Posted June 22, 2024 Author Posted June 22, 2024 Quote --- it also fails if the wall is rasterised - so it looks as if the metadata is not stored in the layers but in the file data ? The one that fails DD Vector Brick Wall Texture 34231_DD Vector Brick Wall Texture 34231-openedin designer.afdesign Quote Win 11 PCs 64bit Envy and Envy tablet + Filter Forge Retired computer systems tester doing graphics for charities and politics etc.
hunter_sk Posted June 23, 2024 Posted June 23, 2024 You can delete all objects and layers from your design file and the metadata causing the export message is still there. Maybe for debugging is this small empty (almost) file better. metadata-error-on-jpeg-export.afdesign gw_westdale 1 Quote
Staff Affinity Info Bot Posted August 9, 2024 Staff Posted August 9, 2024 The issue "User File - 'Metadata could not be embedded' on export to JPEG/TIFF/PSD" (REF: AF-3589) has been fixed by the developers in the latest beta build (2.5.5.2613). 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. Quote
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.