Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

[Ad 1.10.5] Slices' output filenames in Export persona missing extensions when coming from PSD


Recommended Posts

Until now I mostly created graphics inside Affinity and exported it with the export persona without any issues in both Photo and Designer.

Today I imported a PSD file into Affinity and created slices of all layers (without even editing inside Affinity). But to my surprise the Slices don't have extensions in the Slices tab of the Export persona and export to files without extensions, eventhough PNG is selected on each slice.

When creating a new file and create slices of the new layers everything still works fine; all slices get the PNG extension, because PNG is selected. So there is an issue in Affinity when starting with an already created PSD file to create and export layers as slices.

 

This is how it looks when layers are created inside Affinity (pixel-layers) and we create slices from those layers:
image.png.8e33000b85b3b7c68722804a65fe5f99.png

image.png.60566b5d38f3e1c217ff542bffff6b32.png

 

This is how it looks when layers are made externally and imported from PSD (to pixel-layers) and we create slices from those layers:

image.png.8814f2eaaf81d166a3e6fc065af17bca.png

image.png.c3d4086910f03e6074c653d2626e7acd.png

 

 

 

As you can see the files don't get an extention when exporting either:

image.thumb.png.1587d81e91c1776be1d4c9c60cec4f63.png

 

The issue is already in the slice-name, so it looks like we cannot even change it

 

[Edit] Added a test PSD file in the Attachment which throws this issue AND the Affinity file created from it where you can see the issue in the export persona. For the record; the PSD is created in the latest Krita (5.1.1).

test.afphoto test.psd

Link to comment
Share on other sites

BTW The 'main' export, so the sum of all layers (the 'master' so to say), which Affinity always automatically creates in the Export Persona, DOES have an extension. So it's only the slices we created that don't get the extensions we normally do get (and need).

This is the 'main'/'master' export in the slices tab:

image.png.bd8186d4f0961dfa84a42ff5261d2d45.png

Link to comment
Share on other sites

For what it is worth I am not seeing this here on Mac OS 11.7. All the slices, from layers and from me making some, from a .PSD file exported with automatically applied file extensions.

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

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

Link to comment
Share on other sites

1 hour ago, Old Bruce said:

For what it is worth I am not seeing this here on Mac OS 11.7. All the slices, from layers and from me making some, from a .PSD file exported with automatically applied file extensions.

That's info. What software did you use to create the PSD? I used Krita

Link to comment
Share on other sites

I just created a very simplified new PSD file with only 2 simple layers. It's making Affinity having the exact same issue after importing in Affinity in the Export Persona as the file I was working on. So this is a file the developers can bugfix with.

So I updated the opening post here and added both this new PSD file as well as the created Affinity Photo file from it with the slices without extensions issue, as an attachment to the opening post.

Link to comment
Share on other sites

Alright, I just created a PSD file now with a different program (MOHO this time) and tried the same in Affinity. THIS psd file DOES in fact work in the Export persona, so doesn't throw this issue in Affinity. And these are also pixel-layers, just like the krita-created psd file.

Which is weird, because the PSD file created with Krita is importing just fine in Affinity, doesn't throw any errors, looks exactly as expected, all layers are there, including their original names etc. 

I'm no expert on the PSD file format (guess nobody really is as it's propriatory to Adobe, but at least the PDF part could be known), but it looks like, by this short/simple test,  that the PSD Krita creates throws an issue in Affinity (eventhough everything else works just fine and no issue can be seen in the layers), while the PSD Moho is creating is not throwing this issue in the Affinity exporter (or at least not as I can see here with this simplified file). 

So beats me what the issue could be. 

What I can tell tho is that I don't see any reason why Affinity shouldn't be able to add the right slice names with extensions; all layer names are imported just fine, just like their content, so I would say it's only a matter of adding an extension...

Link to comment
Share on other sites

Okay, did some more tests and it looks like this might be easy to solve for the developers (or at least I hope so);

Please see video below: 

  • First you see the imported PSD in Affinity. As you can see the layer names show perfectly fine
  • I add slices from the two layers
  • You can see the output slices are getting the layer names, but aren't getting png extensions, making them create wrong filenames when exporting
  • Now I change the layer names in the normal photo persona to different names (which look the same in the layers panel)
  • When I remove the old slices and create slices from the renamed layers, now suddenly the new slices DO get PNG extensions

So it looks to me there's a difference between the layer names as displayed and the internal layer names used internally in Affinity to create slice names from. Perhaps internally the layer names aren't stripped from white spaces? Or some similar small issue like that causing this to fail, like illegal characters used in the layer name string?

If the visible layer names would be used instead to create slice names I won't see any reason why this shouldn't work from these PSD files as it is showing the right layers names and when changing the layer names to the exact same string-format it is working. Hope this makes sense.

 

 

Link to comment
Share on other sites

17 hours ago, MmmMaarten said:

That's info. What software did you use to create the PSD? I used Krita

A download from some website. So I have no idea. The PSD I exported from Affinity Photo wouldn't really answer the question so I didn't mention that that file also worked as expected. I think that this may be a Windows bug that isn't present in Mac.

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

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

Link to comment
Share on other sites

47 minutes ago, Old Bruce said:

I think that this may be a Windows bug that isn't present in Mac.

Looks like you missed my latest posts. Don't think this has to do with Mac vs Windows. Did you try the PSD in the opening post?

Link to comment
Share on other sites

1 hour ago, MmmMaarten said:

Looks like you missed my latest posts. Don't think this has to do with Mac vs Windows. Did you try the PSD in the opening post?

Those files show the problem as you describe. They also show a Profile I haven't seen before. A renaming of a layer will show the file extension on the export of that layer.

1020371361_ScreenShot2022-09-18at9_33_35AM.png.6882b6ab42477d868865f4d5fd415311.png

I suspect whichever application generated the files is part of the problem.

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

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

Link to comment
Share on other sites

1 hour ago, Old Bruce said:

A renaming of a layer will show the file extension on the export of that layer.

Exactly as I concluded for pc, so it's the same on mac. Thanks for checking

1 hour ago, Old Bruce said:

They also show a Profile I haven't seen before.

It's just sRGB, nothing weird about that. Also this obviously has nothing to do with this issue.

1 hour ago, Old Bruce said:

I suspect whichever application generated the files is part of the problem.

Could be, but shouldn't be in this case IMO;

1) There are no errors after importing the PSD in Affinity
2) Everything shows exactly as it should, including the layer names
3) Affinity is capable of displaying the layer names the right way perfectly fine in the layers panel, so I don't see any problem just glueing the extension to it. If we can workaround this issue by renaming to the exact same layers names, so could the code base I would think. Although there might be a reason to keep two variables of layer names internally I can't reason?

I suspect it's just a matter of sanitizing the layer name internally before adding the file extension when creating the slice name. Probably the layer name internally isn't trimmed after import, has some unexpected ascii character, like carriage return or line feed or something similar. If that's the case it shouldn't be that hard to fix it in code.

Anyway, thanks for checking on your side and hopefully Serif could take a look at it to make it work! :)

Link to comment
Share on other sites

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...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.