Processing profiles and Image Preset rules | Community
Skip to main content
A
Apmag
October 16, 2015
Solved

Processing profiles and Image Preset rules

  • October 16, 2015
  • 9 replies
  • 2295 views

Hello..

Good evening all,

Plan to work on image renditions,so when can we use these rules and i heard like  one workflow which is named as "DAM Update Asset" which is giving some image renditions.and also what is the need of Web enabled renditions?

is there any rules(Processign profiles and Image Preset rules) we can apply on "Web enabled renditions" 

Highly Appreciate some one respond to above questions

Thanks,
Venkatesham

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by edubey

Hi Venkatesham,

By default, upon image upload to CQ DAM, a “DAM Update Asset” workflow would be triggered and one of the many processes inside the workflow is to generate a web rendition of the uploaded image. And the default setting of CQ Image API is to always render the web-enabled version of the uploaded image. This combination helps to limit the size and the quality of the image displayed thus reducing the page load time.

The OOTB setting for the web-enabled image dimensions is set to 1280 pixels by 1280 pixels. And the image quality is set to reduce to 90%.

These can be configured based on the image size needed,

Example: You might want to have different size of images for iPad, Tab, Mobile, Desktop ..etc to give best experience to users, at that point you can configure these workflow to automatically generate images of different renditions.

You can find DAM Asset workflow at http://localhost:4502/cf#/etc/workflow/models/dam/update_asset.html

Thanks

9 replies

edubey
edubeyAccepted solution
October 16, 2015

Hi Venkatesham,

By default, upon image upload to CQ DAM, a “DAM Update Asset” workflow would be triggered and one of the many processes inside the workflow is to generate a web rendition of the uploaded image. And the default setting of CQ Image API is to always render the web-enabled version of the uploaded image. This combination helps to limit the size and the quality of the image displayed thus reducing the page load time.

The OOTB setting for the web-enabled image dimensions is set to 1280 pixels by 1280 pixels. And the image quality is set to reduce to 90%.

These can be configured based on the image size needed,

Example: You might want to have different size of images for iPad, Tab, Mobile, Desktop ..etc to give best experience to users, at that point you can configure these workflow to automatically generate images of different renditions.

You can find DAM Asset workflow at http://localhost:4502/cf#/etc/workflow/models/dam/update_asset.html

Thanks

edubey
edubey
October 16, 2015
Its seem this has been replied in your another question, if you haven't gone through ...please see        http://www.albinsblog.com/2015/04/how-to-create-different-image-renditions-in-adobecq5.html?m=1#.VetStvmqqkp
A
ApmagAuthor
October 16, 2015

Thanks for replying.

Is there any chance to apply Processing Profiles rules and Image Preset rules on this workflow?

 

Thanks in advance.

Venkateshamg

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
October 16, 2015

Hi Venkateshamg,

You can use media handlers to perform tasks on Assets[1]

adding to edubey's answer, you can create renditions when an image is uploaded, however the drawback to this is that every image imported will have the renditions created even if they are required or not. This can increase the size of your repository.

Other options include creating a servlet to render the image on demand[2], if you are using dispatcher, then the image is rendered for the first request and then cached. There is an ACS Commons Named Transform Image Servlet you can use as well[3]

If you have advanced requirements for your assets, you might investigate getting Dynamic Media for AEM[4][5]

Regards,

Opkar

[1] https://docs.adobe.com/docs/en/aem/6-1/develop/extending/assets/media-handlers.html

[2] https://docs.adobe.com/docs/en/aem/6-0/develop/mobile/responsive.html#Understanding%20Image%20Rendering%20in%20AEM

[3] http://adobe-consulting-services.github.io/acs-aem-commons/features/named-image-transform.html

[4] https://docs.adobe.com/docs/en/aem/6-0/administer/integration/dynamic-media/enabling-dynamic-media.html

[5] http://www.adobe.com/solutions/web-experience-management/dynamic-media.html

edubey
edubey
October 16, 2015
When you say  'Processing Profiles rules and Image Preset ', what do you exactly mean. Please share your use case so that community can help better.
A
ApmagAuthor
October 16, 2015

Thank you very much Opkar Gill for giving reply.

last question:

If i upload any image(480w,480h) into Dam,it is giving renditions like below.

Full Stack trace information:

com.day.cq.dam.core.impl.RenditionMakerImpl generated rendition: /content/dam/projects/cover12.jpg/jcr:content/renditions/cq5dam.web.500.500.jpeg
07.09.2015 22:56:50.412 *INFO* [JobHandler: /etc/workflow/instances/2015-09-07/model_907857176269342:/content/dam/projects/cover12.jpg/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl generated rendition: /content/dam/projects/cover12.jpg/jcr:content/renditions/cq5dam.web.1920.1920.jpeg
07.09.2015 22:56:50.446 *INFO* [pool-5-thread-1] org.apache.sling.event Service [QueueMBean for queue Granite Workflow External Process Job Queue,2999] ServiceEvent REGISTERED
07.09.2015 22:56:50.452 *INFO* [Apache Sling Job Queue Granite Workflow External Process Job Queue] org.apache.sling.event.impl.jobs.queues.OrderedJobQueue.Granite Workflow External Process Job Queue Starting job queue Granite Workflow External Process Job Queue
07.09.2015 22:56:50.539 *INFO* [JobHandler: /etc/workflow/instances/2015-09-07/model_907857176269342:/content/dam/projects/cover12.jpg/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl generated rendition: /content/dam/projects/cover12.jpg/jcr:content/renditions/cq5dam.web.1200.1200.jpeg
07.09.2015 22:56:50.591 *INFO* [JobHandler: /etc/workflow/instances/2015-09-07/model_907857176269342:/content/dam/projects/cover12.jpg/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl generated rendition: /content/dam/projects/cover12.jpg/jcr:content/renditions/cq5dam.web.768.768.jpeg
07.09.2015 22:56:50.626 *INFO* [JobHandler: /etc/workflow/instances/2015-09-07/model_907857176269342:/content/dam/projects/cover12.jpg/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl generated rendition: /content/dam/projects/cover12.jpg/jcr:content/renditions/cq5dam.web.320.320.jpeg

 

Clear information : uploaded image w:h is 480:480

DAM asset workflow is generated below renditions and given web enabled renditions configurations w:h=500:500

1) cq5dam.web.500.500.jpeg (this is i given)

2) cq5dam.web.1920.1920.jpeg

3) cq5dam.web.768.768.jpeg

4)cq5dam.web.320.320.jpeg

Am not sure how 2),3) and 4) renditions are created,so i want to change these renditions with and height to satisfy my requirement.

how to do?

i have gone through below files(OOTB bundle-com.day.cq.dam.cq-dam-core (415)) even i did not get how it is generating renditions.

1)CreateWebEnabledImageProcess.java

2)RenditionMaker

Can you help me how it is taking renditions width and height for 2),3) and 4) renditions?

Thanks,

Venkatesham

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
October 16, 2015

Dynamic media requires a separate licence, so you need to decide if the extra features will be required by your project.

A
ApmagAuthor
October 16, 2015

Thank you very much to Opkar Gill  for given clarity on renditions and solved my problem.

 

Thanks,

Venkatesham G

Terms & ConditionsAccessibility statement

Loading footer...