Images become too compressed when synced from Scene7 to AEM

[todd_wheeler]

New install of AEM, so syncing images from Scene7 has never worked correctly. When we upload directly to the AEM DAM, images are correctly compressed. When we upload images directly to Scene7, the images are correctly compressed, as well.

However, when AEM syncs with Scene7, the images display extreme compression. Our integrator knew very little about Scene7, and now we’re unsure where to look for a solution.

Is it possible to determine where we can turn off the extra compression?

[mvance]

The polling importer, which pulls content from S7 into AEM should use the master assets. There is no manipulation of the source file.

The integration has changed a little, here is the doc for 5.6.1

http://docs.adobe.com/docs/en/cq/5-6-1/administering/integrating_with_adobe_marketing_cloud/scene7.h...

and 6.0

http://docs.adobe.com/docs/en/aem/6-0/administer/integration/marketing-cloud/scene7.html

It is possible there is some workflow which uses the S7 API to export a rendition of the master asset but I don't see why this would have been done as the polling importer does this job anyway

[todd_wheeler]

Thanks for the response, mvanceS7!

Our integrator recommended that we upload image assets first into S7, but place images into components in AEM from images shared from S7 into the DAM.

Image assets are indeed being sampled down once they appear in the DAM. An image uploaded into S7 that is 1800px wide by 1200px tall becomes 500px wide by 334px tall in AEM's S7 folder. Configuration of Adobe Scene7 via Cloud Services appears to be default settings, with the exception of the "Root Path" and "CQ DAM target folder".

In AEM, we have a "Scene7" workflow version 1.1 for uploading images from AEM to S7, and a "DAM Update Asset" v1.1 workflow shows an extensive set of behaviors, as indicated in the attached image.

Could a Preset within Scene7 determine the image compression and reduction in size?

Thanks and regards, Todd

[mvance]

There should not be any preset or Image Serving parameters to be applied when the assets sync from S7 into the local DAM.

Could there be a processing profile on the destination folder? http://docs.adobe.com/docs/en/aem/6-0/administer/content/assets/processing-profiles.html

You have verified the actual image file, not the renditions or presets defined locally in Assets?

[todd_wheeler]

I appreciate your patience! I think that I have been able to rule out the existence of a Processing Profile in AEM.

I don't know if you are able to view this image which I uploaded into S7: http://crown.scene7.com/is/image/crown/fc4500application?$main$

or: http://crown.scene7.com/is/image/crown/fc4500application?$S7product$

Despite uploading a 1500px by 1500px image at 72 ppi, I am only seeing compressed and reduced images like the those above in Scene7. In this case, the indicated urls link to 350 x 350px and 500 x 500px images, respectively. I don't see additional renditions in S7 that display the full 1500 x 1500px image size.

Does this, then, point to an errant Preset in Scene7?

Thanks again, Todd

[mvance · Accepted solution]

Both of those urls are using presets, yes.

$main$ is using these values ?wid=350&hei=350&fmt=jpeg&qlt=85,1&op_sharpen=1&resmode=bicub&op_usm=1,1,6,0&iccembed=0&printres=72&layer=COMP

$s7product$ is using ?wid=400&hei=400&fmt=jpeg&qlt=85,0&op_sharpen=1&resmode=sharp2&op_usm=1,1,6,0&iccembed=0&printres=72&layer=COMP

You can call at larger sizes, by using a different preset, or else by manually specifying the commands in the url:

http://crown.scene7.com/is/image/crown/fc4500application?hei=1200

Please be aware though that your current setup has a limit of 1800 x 1200 set, so higher values will cause a broken url:

[img]http://i.imgur.com/41qRsQ2.png[/img]

You may change this setting if you need to.

On the other side of the issue, when you are embedding the images in your CQ pages, via the S7 component in the DAM (AEM Assets), if there is some sizing issue, check the parameters being applied