Photoshop CC: Extract Assets Feature Is a Disaster (2014.2 update)

  • 13
  • Problem
  • Updated 5 years ago
  • In Progress
  • (Edited)
The new Extract Assets feature in Photoshop CC 2014 is a disaster. Take a look at Sketch for the proper way to do this that designers will actually want to use.

Problems & Suggestions:
1) Come up with a solution that doesn't mess with my layer or layer group names - let me name the asset in the Extract Assets window and then remember it.

2) Allow me to add padding around an asset when I export - with the flexibility to provide different padding on each side of the asset.

3) Provide a 100% export option - I work at Retina resolution and so the base asset is actually my @2x asset, so I want to be able to select an 100% option and give it the @2x suffix.

4) Remember where I last extract assets to and don't force me to rename a destination folder each and every time.

5) Let me decide what the default resolution options should be, so I don't have to keep opening a dialog to set the ones I want.
Photo of Jim Muirhead

Jim Muirhead

  • 9 Posts
  • 0 Reply Likes
  • frustrated

Posted 6 years ago

  • 13
Photo of Charles Pearson

Charles Pearson, Employee

  • 7 Posts
  • 1 Reply Like
Hi. I'm a researcher with the Photoshop team and this is great feedback, thanks for posting. I've forwarded it to the dev team, which is already at work on v2. If you have any more feedback be in touch.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Official Response
Hi Jim, I am the Product Manager for this feature.

> 1) Come up with a solution that doesn't mess with my layer or layer group names - let me name the asset in the Extract Assets window and then remember it.

Hah. I cannot tell you how much we wanted this! We had 2 months to build this feature and there were lots of internal conflicts on how to do this. But thanks for bringing this up, this gives us a lot more ammo to push to change this for the next release!

> 2) Allow me to add padding around an asset when I export - with the flexibility to provide different padding on each side of the asset.

We actually almost had it for this release! sadly, we had lots of performance issues and bugs to fix that we couldn't get this done for this release. We will do it for the next release (within the next six months for sure)!

> 3) Provide a 100% export option - I work at Retina resolution and so the base asset is actually my @2x asset, so I want to be able to select an 100% option and give it the @2x suffix.

This already exists. Did you not see the settings here: https://cloudup.com/cBvyPdHP4xj ? Clicking on the cog will allow you to give it the @2x suffix https://cloudup.com/cHzdFP_sNyp

> 4) Remember where I last extract assets to and don't force me to rename a destination folder each and every time.

Ugh. Good point. We should do that. I have filed a bug report.

> 5) Let me decide what the default resolution options should be, so I don't have to keep opening a dialog to set the ones I want.

Do you mean for different PSDs? Currently when you save default resolutions per document, it is saved forever.
Photo of Joshua Polk

Joshua Polk

  • 7 Posts
  • 0 Reply Likes
Hey, random comment for Divya. I'm an instructor at an online college. Every time you guys "redo the entire UI" we have to completely redo all our tutorials and course images that show any interface. Big pain and it makes me not want to add new features to my classes (what I am considering now). Food for thought...
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Good point! Yes we do understand the frustration, perhaps it might help being part of pre-release so you can preview the changes coming at least 2 months in advance? We would love to get your thoughts on how to make PS better though! Please do email me: manian@adobe.com thanks!
Photo of Sean Davis

Sean Davis

  • 2 Posts
  • 0 Reply Likes
3) I believe he is asking for the ability to add a suffix and folder for 1x items. You can set settings for 0.25x, 0.5x, 1.5x, 2x, 3x, but not for 1x. If you've designed everything at 2x already, when you extract assets, it'd be nice to be able to add "@2x" after the 100% scaled asset. I'm running into that same issue right now. I want to add @2x without scaling, and be able to put them into a folder.
Photo of Sean Davis

Sean Davis

  • 2 Posts
  • 0 Reply Likes
I just figured out a work around for this. I notice when I initiated extract assets is created a layer named according to my settings, I altered that layer name to add setting to 100% and it worked.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
FYI folks, this feature is now deprecated, we have released Export Options which tackles a smaller scope of problems of exporting. More info is available here: https://helpx.adobe.com/photoshop/using/export-artboards-layers.html
Photo of Philip Gomez

Philip Gomez

  • 3 Posts
  • 1 Reply Like
There is also an issue of the extracted item not matching the canvas size of the original PSD file. My canvas is 1000px x 300px but the jpg created with the extraction is 1,164px x 376px. It is including the image area that is cropped out from a smart object. Will have to stick with "Save for Web..." for now. And the quality percentages don't match the ones in "Save for Web..." and you have to guess at it. I guess not really ready for everyday use. I'll try to upload an example her...the first one is the proper crop from "Save for Web..." and the second one is the "Extract" version:

Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Yes! This is inconsistent with Save for Web and it is a feature of Adobe Generator. But we realise this is not consistent with how users expect assets to be extracted. So we will be cropping the assets to the canvas size in our next release! Till then you could use a layer mask to set the bounds on the smart object. 

What do you mean by quality %s is not the same? Are you looking to use 'low / high / very high / maximum' dropdown? 
Photo of ivan

ivan

  • 1 Post
  • 0 Reply Likes
Very helpful workaround:)
Photo of Philip Gomez

Philip Gomez

  • 3 Posts
  • 1 Reply Like
Thanks for helping me understand that the canvas size will change. I think we are expecting to output what we have on the canvas, not the size of the original cropped image...can't use that.

As far as quality is concerned, in "Save for Web..." if you choose "high" quality 60, this does not equal inputting 60% quality on the Extract feature so it is confusing. Maybe we are just used to it but the granularity and previews of "Save for Web" seem more intuitive. I know...different feature entirely but if "Save for Web" goes away eventually then "Extract" will need to catch up. Great idea, just not there yet and I understand you guys are working on it and we appreciate that.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
oooh that is a good point about quality consistency. We should ensure it does. I think someone else said the same, but I will confirm. Are JPGs primarily what you export and not PNGs? Any reason why you use JPGs than PNGs?
Photo of Philip Gomez

Philip Gomez

  • 3 Posts
  • 1 Reply Like
Both JPG and PNG...depending on the final use. In the end the "Save for Web..." feature has been a great tool and I hope it does not go away. But if this Extract feature is to replace it I would think we need more granular control and previews to finish it off. Hopefully that is not too much to ask for.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Oh yes yes of course! We have all of those granular controls planned for next major release. We had about 2 months to implement and release Extract Assets and had to choose the minimum features we could choose to expose first. Thanks for the feedback! 
Photo of Edward Sanchez

Edward Sanchez

  • 8 Posts
  • 4 Reply Likes
the 100% at 2x is definitely very important for me.

I have another related request. Android and iOS have different conventional prefixes/suffixes for the different resolutions. So ideally I would like to export 2 assets for each but with different names.

I know I can do that in the Layer Naming, but I can't do it within the Extract option.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Edward, you are right! We are looking at rethinking that whole UI for multiple-screen export.
Photo of Yaron Elharar

Yaron Elharar

  • 3 Posts
  • 0 Reply Likes
Another 3 points

1. When you select to extract an asset from the layer palette you expect only the selected layers to be presented in the export assets, since those were specifically selected for export.

Now every time you do that you need to go through everything and remove unnecessary layers just to export one of them.

2. When you assign a mask to a layer group you expect export assistant to treat the boundaries of the mask as the boundaries of the element you would like to export. currently, it will not use the mask as an indicator of boundary, it will just take the sub-layers unite them and assign size by pixel presence.

3. Consider having an option to report bugs especially in the early release cycles, or at a minimum a link directing people to the relevant forum where they can discuss issues and might get some help. most people won't bother sending anything in, but those that will, will help you move from a good product to an amazing product.

- 2 months is a long time to develop this. I know since I developed a similar one for CS5, especially with the resources available to you at adobe. It is nice that you started the shift in mentality to listen to user feedback, but since it's coming after years of "where doing our own thing here" approach then I think some frustration is in place.
Photo of Yaron Elharar

Yaron Elharar

  • 3 Posts
  • 0 Reply Likes
4 - Differences in language in the generator a transparent PNG is png-32
In the save for Web dialogue it's png-24 they are both the same.
as I remember the 24bit Transparent PNG is a long time standing mistake It
(24 Doesn't include transparency in the specification)
should have always been 32 which is correct, technically for the transparent PNG's

http://en.wikipedia.org/wiki/Portable...

Regardless of what you choose eventually, currently it's inconsistent and they both export the same file.
Photo of Frank Neulichedl

Frank Neulichedl

  • 1 Post
  • 0 Reply Likes
Hi guys,

great to see this discussion .. could I add some ideas for us Android Devs/Designers ...

1) In general it would be great if we could have templates where we can save the folder names in between files - and sessions.

2) Also, I like the latest improvements made to the Extract Assets feature - but it seems that is geared towards web and iOS Development.

In Android all Assets (also the 1x) are in sub-folders so - right now I have to create a folder and move the base assets into that folder.

To be more precise:
I do the base design for XHDPI resolution - then extract the layers to

0,5 -> drawable-mdpi/
0,75 -> drawable-hdpi/
1,5 -> drawable-xxhdpi/

then I have to create the drawable-xhdpi/ folder and move the contents of the base folder into drawable-xhdpi/

Any ideas, suggestions?

Thx
Frank
Photo of Kieran Black

Kieran Black

  • 2 Posts
  • 0 Reply Likes
Hey guys,

I thought I would throw my two cents in.

Bugs:
• Extractor doesn't allow me to change the destination folder for my 2x and 3x assets
• Doesn't allow me to have a 1x (normal artboard), 2x, 3x png and a 1x svg. Instead it does a 1x,2x,3x png and a 1x,2x,3x svg it would be nice to set the scale per generator tag instead of per layer.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
I didn't realise I forgot to respond to this one. 

• Extractor doesn't allow me to change the destination folder for my 2x and 3x assets 
We should be fixing this very soon. 

• Doesn't allow me to have a 1x (normal artboard), 2x, 3x png and a 1x svg. Instead it does a 1x,2x,3x png and a 1x,2x,3x svg it would be nice to set the scale per generator tag instead of per layer.
Yeah this is fundamental to the design of Extract Assets as it exists right now but we are looking to make some deep changes in the architecture to make something like this also possible. But that will take some time. 
Photo of Yaron Elharar

Yaron Elharar

  • 3 Posts
  • 0 Reply Likes
I don't think anybody is reading this anymore
Photo of Charles Pearson

Charles Pearson, Employee

  • 7 Posts
  • 1 Reply Like
We're still keeping tabs on the thread -- there's a load of excellent, substantive feedback here. Keep it coming all!
Photo of Kim Rock

Kim Rock

  • 1 Post
  • 0 Reply Likes
I was really excited when i found this function, but the fact that it exports my retina icons with uneven width pixels so not an exact % increase or decrease - this distorts them once in the code - looking forward to when it is fixed :-)
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Ah yes, we are looking to solving this soon too! I will respond here when we do! 
Photo of (DO)

(DO)

  • 2 Posts
  • 0 Reply Likes
Related to asset extraction, I would add that the feature should also not include any part of the layer that extends beyond the canvas. Sometimes I miss a pixel or two and create an asset larger than needed. When the Extract tool runs, those assets are the size they were created at, instead of cropped to the canvas width/height.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Yes! We are changing this behaviour for the next release! And the assets will be cropped in canvas width/height. 
Photo of (DO)

(DO)

  • 2 Posts
  • 0 Reply Likes
Hot dog! I'd love to be a beta tester so that all of the features discussed in this thread are implemented as desired before the update is pushed out for release.
Photo of Christopher Campbell

Christopher Campbell

  • 4 Posts
  • 0 Reply Likes
I have been using PSD for a while and recently moved computers. The new computers has a slightly different network setup linking to a different proxy.

The one thing that broke immediately was "extract Assets" Why would the proxy connection make the Extract assets fail?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 859 Reply Likes
Sounds like your proxy broke the localhost (127.0.0.1) connection as well for some reason - so apps and servers can't communicate on your system.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Extract uses a local connection to the Generator server to get the image assets. It is likely that your proxy connection has tried to route all localhost requests to be via the proxy. Check this response from a user who has a similar issue with proxy in the forum https://forums.adobe.com/message/6930791#6930791  
Photo of Christopher Campbell

Christopher Campbell

  • 4 Posts
  • 0 Reply Likes
Thank you for the comments. Divya the link helped me resolve the issue.

Under network settings > Advanced > Proxy
I simply checked "Exclude simple hostname" (for Mac user)

This resolved the proxy issue on my machine.
Photo of Simon OKelly

Simon OKelly

  • 5 Posts
  • 2 Reply Likes
Good to see Divya letting us know what's going on here. Any news of the update to this feature?

I have been pulling my hair out for some time now with this one. I agree with all of the issues in this thread but the most painful (rendering the entire feature useless for me) is the fact that the exports crop the asset to the pixel and not 100% of the canvas.
Photo of Christopher Campbell

Christopher Campbell

  • 4 Posts
  • 0 Reply Likes
I was able to get round this by creating a mask over the entire canvas. This should constrain it to just the canvas and not the group or pixels.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
The newest update defaults to limiting the asset export to the canvas dimensions if it is larger than the canvas dimensions. Is that not working for you Simon? 

Addtionally we are working on better ways to get images out of PS. If you would like to give us feedback on our approach, please do email me! manian@adobe.com 
Photo of Simon OKelly

Simon OKelly

  • 5 Posts
  • 2 Reply Likes
Chris that's a neat little work around, don't know why I didn't think of trying that... thanks!

Divya, excuse me if I have misunderstood but my issue isn't with assets that are larger than the canvas dimensions and I feel that I shouldn't have to apply masks or tease the canvas in any way to achieve that end result.

Simply, If I have a a single layer that only covers, let's say, 25% of the canvas area but am wanting to export the asset at 100% of the canvas size (including 75% transparent padding), I would like to have the option to export exactly as it appears on the canvas, in the same way that saving the PNG manually would do without creating extra work for me.

A simple option in the export settings that allow you to choose from: 'Export 100% of canvas' or 'Constrain to pixels, group etc.' would be the most obvious solution in my opinion, without requiring masks or 'empty' layers etc.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Ah i see. This is something I have heard once earlier too. Can you email me manian@adobe.com possibly with a sample PSD where you have this issue? I want to understand your workflow so we can see what we can provide. 
Photo of Christopher Campbell

Christopher Campbell

  • 4 Posts
  • 0 Reply Likes
Is there any way to extract the assets to a folder and control the naming of the folder. When I extract all the assets Photoshop places them in a folder with the same name as the folder. I have not been able to work out how to say put the assets in a folder called "images" without renaming the PSD.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
You should be able to change the folder name to whatever you want when you choose the folder location to save the file into (as shown below). Does that not work for you?

 
(Edited)
Photo of Simon OKelly

Simon OKelly

  • 5 Posts
  • 2 Reply Likes
Ok, sorry for lengthy message but after some trial I have found a few more issues:

After being suggested that applying a layer mask will help with the extract, I thought I'd hit jackpot and would now use the extract tool across all of my PSDs.

Divya, I will send you my PSDs in an email as requested. You'll see better what I mean.

LAYER MASK FIX WORKED FOR SOME THINGS

The layer mask solution from Chris worked fine for an animation I was exporting assets for (for X-Code) where the canvas needed to be a constant size, just with lots of different asset states, and exported in 1x, 2x and 3x. Every asset kept the full canvas ratio and so the animation stitched nicely. That was cool.

1. EXTRACT SMART OBJECTS at 100% CANVAS SIZE

A problem arose when smart-object-placed-assets are only a small fraction of the canvas size (i.e an icon asset on an iPhone screen) and need to be 'sliced' out upon extraction. Therefore, layer masks do not work here.

I'd like to be able to extract assets (slice style) but with the extract tool maintaining 100% of the smart object canvas size (including any padding or empty space within the smart object) rather than constraining to the pixels as I have previously said in this thread. See image for example.



When I'm designing for iOS, I currently store all of my assets (1x, 2x, 3x) in a separate Asset PSD and export manually (see image). I also drop the @2x into my App Design PSD to work from. Even here, it would be great to just have ONE of each asset that I can use the extract tool to successfully export multiple sizes of. I created this work flow originally to get around the 'Generate Asset' feature's hidden layer issue where it would remove exported assets if the layer was hidden in the PSD. I stopped using that tool for all it's flaws a while ago - but it's good for some things. Anyway...



Either way, whether I want to extract assets from smart objects in bulk from the Asset or App Design PSD, neither works for me due to this canvas size issue and I still have to do it manually. This extract tool could save me (and I'm sure a few others) so much time if Adobe can just tighten a few things up.

The icons I create all have padding - or empty space - around the icon because the dev guys moan at me if they can't just place the asset straight in and create their button to be the same size as the asset file. They moan enough about Xcode as it is!!

2. BASE SIZE

Working from @2x as a base really isn't supported with your naming conventions. I can export at 1.5x with the suffix @3x which is useful and I can export at 0.5x with no suffix which is also useful. However, I can't export at 1x with an @2x suffix.

Likewise, if I name my layer with a 2x suffix to get around this, I can't then use the suffix tool for the 0.5 and 1.5 versions because it will become 'assetname@2x@3x.png' which again is useless.

I'd like the option to have 1x scale with an @2x (or otherwise nameable) suffix.

It may also be useful to consider that people designing at @3x would need a 0.66 and 0.33 option to extract that asset with a re-nameable suffix.

S
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
OMG. Simon! Thank you so much for the detailed feedback. This is great! Also did you email as an attachment, if so it is likely flagged somewhere as spam and I never received it :( Can you just send me a 'hi' email and we can take it from there? manian @adobe.com 
Photo of Peter Easdown

Peter Easdown

  • 2 Posts
  • 0 Reply Likes
For those wanting to know how to customise the folder names and sizes what I found was that after using the Extract Assets UI to set up an initial export of the default and one other size, PS creates a layer (on top) called Default with some size information in it.

The format of that seems to be:


Default [size] [folder/], [size] [folder/], ...


For example I have a 4" iPhone screenshot that I need to export for the 4", 4.7" and 5.5" (I don't have the hardware so this is my only option).

I changed the information in that layer name to:


default 100%, 1334x750 667h/@2x, 2208x1242 736h/


This produces 3 copies of the asset, all correctly sized, and in folders that make it easy to grab and upload to Apple.

Tell me if I'm teaching you guys to suck eggs. I'm new to PS, so this is a major convenience for me, though it could be improved by PS cropping to the canvas boundary.
Photo of Simon OKelly

Simon OKelly

  • 5 Posts
  • 2 Reply Likes
Peter

Not teaching us to suck eggs at all and I wouldn't worry about that, a lot of people will read this thread - however, layer naming conventions for export have been around a while and is ultimately time consuming, especially on large-scale projects with an insane amount of layers, smart-objects and asset states. It shouldn't be necessary, and this new tool is very close to nailing it.

It's not so much the output folder either with regards to the naming - I think that has been updated already since this thread began - but more the 'base' resolution and correct suffix naming of each asset which is still an issue. It doesn't accommodate people choosing to work at resolutions other than 'default' or 1x.

In short, yes, you can use layer naming with the generate asset feature but it will soon start to grate on you when you have such long, non-identifiable names for each layer and you're trying to move about the project quickly.
Photo of Jon Wallsten

Jon Wallsten

  • 1 Post
  • 0 Reply Likes
Don't know if you guys still read this. But I'm trying to convert a complete sprite map to SVGs. There a few hundred icons. And I need to normalize the height, but keep the aspect ratio.
I've tried to set the height with layer naming. Like:
* x 500px
? x 500px
But this doesn't seem to work.
Is it something you have o will add?
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Hi Jon, have you tried the following from the generate assets functional spec https://github.com/adobe-photoshop/generator-assets/wiki/Generate-Web-Assets-Functional-Spec (be aware of no space between x and the units)

100x? foo.png (wild card)
?x60in foo.png (wild card at beginning)
That should work on your PSD. If not, can you send me a sample PSD to my email id? Let me know!
(Edited)
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
I'm glad I found this little topic. I agree with all issues that have been made so far. I just wanted to get some clarification for the assets extract for document cropped vs pixel based cropped issue.

In my latest test, if I have a smart object, it still crops the image the size of the smart object, not the document size. Am I not correct on this?

Also, I know it was mentioned once, but I just want to add my vote on this issue about the quality difference between save for web vs Extract assets. Looks like if you use 60% in Extract assets, it's more like 30 in save for web, and with better results for the later at the same weight of file.
And while your at it, the export jpeg as a setting of 1-12, and save for web as 1-100 settings, shouldn't it be all the same? Consistency guys;-)
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Hi Jeff! Thanks for your feedback. We actually have updated it so assets outside of the bounds of the canvas will be clipped like so:

Original Smart Object: https://cloudup.com/cN2-oyF5ZXm 

Rendered Image: https://cloudup.com/cGpjmuBKsgI 

Have you updated your Photoshop yet? 

Are you talking about JPG quality when you are talking about quality? JPEG in Extract Assets and in Save for Web go up to 100%? Are you comparing vs 'Save as'? 
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
huh, I was sure I had retested this, that's great, thanks Divya!

As for the quality of the jpeg, I made two points.

One is the fact that the quality at equal settings between save for web and extract asset don't seem to do the same output quality. If you set the save for web at 30%, you get the same file size and quality as about 60% in extract assets.
I have an exemple of this but can't post it online so I'll try to email it to you directly.

And the second point was that when you save as a Jpeg, you get a 1-12 slider vs a 1-100% in save for web and extract assets.

So knowing that you can set the same percentage in one place and get the same results wether you use save for web or save as would be nice.

Thanks for listening!
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
Divya, I thought I could find your email on your profile, but I can't so shoot me an email if you can and I'll send you the two examples of what I mean for the quality issues in save for web vs extract assets.
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Yeah Extract Assets seeks to gain parity with what Save for Web offered, we will look at consistency with Save as once we are able to get users who use Save for Web on-boarded onto new export options. To be clear, this inconsistency between Save as and Save for Web has been in existence for at least 10 years :) 
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
I know it's been there since the beginning, I just didn't have to use it until recently;-) I've worked for print for a long time and just starting to have work for web.
Photo of Bryn Forbes

Bryn Forbes

  • 158 Posts
  • 22 Reply Likes
I'd like to be able to have extract assets export slices for each layers. this is the only page that comes up for extract assets slices. I see above that you are aiming for feature parity with save for web. Is this coming or am I missing something in the extract assets dialog?
Photo of Divya Manian

Divya Manian, Employee

  • 82 Posts
  • 9 Reply Likes
Hi Bryn! Woah, thats a lot of slices! What do you use it for? We haven't found many folks using slices actually so we are not prioritizing working on that at the moment. If it is easier to speak on the phone about this, please do email me: manian@adobe.com Thanks!
Photo of Chris

Chris

  • 4 Posts
  • 1 Reply Like
I thought I'd throw my hat in the ring here. I've been really wanting to be able to use this feature as it would save a lot of resizing when it comes to exporting retina-ready graphics. However I'm running into wall of inconsistency, weird color and quality behavior with smart objects.

My current workflow consists of this:
- Create images usually consisting of various smart objects
- Create slices
- Save for web

When saving 2x retina graphics I'll do a temporary image resize at 200% to and use the same defined slices and do a save for web.

What I've noticed is that Extract Assets and Save for Web yield very different results. I don't know if it's because I'm using a smart object and photo (although, I don't think that should matter) or if it's something else.

I first noticed the difference when I looked at the 2x version of an Extracted Asset JPG 100% quality it was very blurry almost as if the JPG had been upsampled without using the smart object (which is a very high resolution photo). Compared to the Save for Web version (also at 100% quality) it was very low quality.I tried another photo, created a new document thinking it was my PSD, but I kept getting the same poor results on the Extracted Assets JPG 100%.

In the non 2x version of the Extracted Assets I noticed a color shift, more contrast, and more brightness applied when the original had less contrast and wasn't as bright. So I don't know what is going on. I've included the comparison and a screen shot of the layers.

Please let me know if I need to do something different.

Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
Ok, I've done a few test and it doesn't work as you say it does and works as expected. It works fine on linked smart object and all. Fiew I was scared for a moment!
Photo of Chris

Chris

  • 4 Posts
  • 1 Reply Like
Thanks Divya for your quick response and the light shed on this topic. I concur with Jeff that this is the whole purpose of using Smart Objects is to be able to scale to 2x or whatever without losing fidelity.

Jeff, are you saying that you're not seeing the problems that I've encountered? Could this be an issue where it's just me and not everyone?

It is a little odd that you must Place the smart object into your document -> Rasterize your Smart Object -> Make rasterized layer Smart Object in order for Extract Assets to work. Will Placed Smart Objects (embedded and linked) soon work. I think this is the behavior that people expect, and I think a lot of people may not even realize that they've been exporting poor 2x assets.

But, in my tests using your instructions, I was able to get the same quality as I do in Save for Web (it wasn't blurry this time). However, I still am noticing the Extract Assets version brighter than the Save for Web (see original comparison).

Is anyone else seeing this brightness shift? I've replicated it on two different images. All sharing the same color profile (sRGB).
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
Hey Chris, I'm not seeing differences in my images in terms of colors. My document is in sRGB, and most of my images are for prints so they are in Adobe RGB, which is "converted" on the fly when I place them in my sRGB PSD. If you have a Adobe RGB file and extract the assets, then you'll have a shift in color because photoshop strips the profile of the resulting jpg as mentioned by Divya. Other than that, I'd check my color setting and see what's your setup there, maybe you have something that is set to ignore profile or something like that?

But you said you're all using sRGB so I don't know what's happening.
Photo of Chris

Chris

  • 4 Posts
  • 1 Reply Like
Thanks Jeff, after finding out that you weren't experiencing the same color brightness shift, I tried another test in a new document. This time I didn't see the shift. I don't know what could've happened before.

Other things that I've found worth noting, but aren't really a big deal to me:
- Smaller file size on the Extracted Assets version vs. Save for Web version is 37KB and 91KB respectively on the 1x version.

Hopefully there aren't any other surprises in using this new tool. I'll have to keep a close eye on the exports. Thanks for the help.
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
Chris, on the size comment, if you select the same setting, for exemple, 60% in save for web and 60% in extract assets, you won't get the same level of quality and compression, that's why you see a size difference. That is one of the things I mentioned to Divya and the team, and I'm not the only one who has seen this difference. I think it is important to have the same algorithm for both since people are probably coming from the save for web way of doing things, they will be accustomed to those percentage/quality and expect the same. Divya assured us that they are working hard to resolve this for the next major release. Lets hope they do:-)
Photo of Chris

Chris

  • 4 Posts
  • 1 Reply Like
I looked into the brightness shift a little more, and found out what was causing it, and I'm posting it here, because it could be a potential bug that Adobe would like to look at.

I found that the brightness shift was coming from an above turned off layer that contained a curves adjustment layer (also turned off). While the turned off curves layer didn't affect the image when turned off (as expected), it somehow retained the curves effects when using Extracted Assets. I've detailed this in the screenshot below.

I've cropped the Extract Assets dialog box a little so it may be hard to understand the relationship of everything in the screenshot. The portion in the middle of the screen grab is the Extract Assets dialog box with the actual image on the left. I've increased the curves layer adjustment to show the problem better.