P: Include additional metadata in XMP (flags, collections, VC's, etc.)

Hi Ethan!

We are investigating this issue with smart objects! Will post progress here when I get to know more!

I'm having a similar problem and posted it on the main Adobe communities forum and it was suggested that I post it here, too. To add to the comments above, these days photoshop will correctly render larger than 100% (if the source material allows, of course) if you made the raster layer a smart object after you import it, but not if you import it using the "place embedded..." file menu option (which is supposed to add the image to the document as a smart object and save you the extra step).

Here is the link to the original post in the other forum:
https://forums.adobe.com/message/6866...

"I'm trying to develop a retina workflow in photoshop for web projects. In doing this I found a strange irregularity in photoshop using smart objects and Photoshop CC 2014's new asset extraction.

Essentially what is happening is that when I import an image into an already open photoshop document and make that raster image a smart object (either by importing it using the "place embedded..." option or by converting the image to a smart object after placing it) I am getting different results when I try to extract those images at 2x using the new extractor. Of course you will have to perform a transform on the image to scale it down in the photoshop document after you make them smart objects (i.e. I know that 2x of the original smart object size will still be blurry — that's not what I'm doing). The image that is converted to a smart object after it's placed saves as 2x perfectly clearly and the one that was "place embedded..." comes out blurry as if it wasn't a smart object at all.

What should I do about this? I thought these two options were different ways of accomplishing the same thing. Honestly, I like to use the "place embedded..." option because it saves me steps, but it is the one that isn't working.

Thanks,

Ethan"

Scaling issues are clearly not the problem, as Save for Web does a perfect job.

To be honest ... i ́ve no idea 🙂 It is to avoid some scaling issues.

To be honest ... i ́ve no idea 🙂 It is to avoid some scaling issues.

Thanks for your answer (I'm curious why 5 ?).

I see that there are ways to bypass this problem (not compeletly as I need to create 22x22 and 44x44 pictures and not 45px). But I don't understand why "save for web" works fine in that case and not the generator.

I tried an external plugin (PNG Express) that works fine in any case. Adobe should be able to do better.

If you don ́t have any vectors ... try to choose final resolutions which are devidable by 5. So if you choose 45x45px instead of 44x44 the generator result will be:

But my icons are PNG, not vectors

strange ... maybe an syntax issue?

a few examples witch i had used succesfully.

50% Image1.jpg, Image1@2x.jpg

100% play_scale-100.png, 140% play_scale-140.png, 180% play_scale-180.png

100% SplashScreen-100.png, 868x421 SplashScreen-140.png, 1116x540 SplashScreen-180.png

Cheers

Hey Fabio,

at first you should always make stuff with pathlayers.

Left path, right pixel (your original) ... both done with generator.