After hours of research, we discovered this is an issue-driven by the default configuration of two components responsible for rendering web-enabled images when the uploaded image has dimensions greater than 1280 pixels. Here are a couple of steps you can take to fix the issue.
1. Max Dimension Step: Day CQ DAM Buffered Image Cache Property
This property defines what maximum dimension is allowed to be generated. If your application involves dealing with dimensions larger than the default 1280×1280 pixels, then this property needs to be updated appropriately. Below is a sample configuration for handling a 1280 x 4704-pixel image.
This property defines what maximum dimension is allowed to be generated. If your application involves dealing with dimensions larger than the default 1280×1280 pixels, then this property needs to be updated appropriately. Below is a sample configuration for handling a 1280 x 4704-pixel image.
2. Workflow Step: DAM Update Asset, Process Thumbnails, Web-Enabled Image
This step is responsible for processing all thumbnails for the DAM Assets. Once the first step is complete, you need to define the Web-Enabled Image Width & Height.
Once these two steps are completed, all the assets created or modified will utilize these configurations to generate web-enabled renditions, and there will not be any downscaling of images.
This step is responsible for processing all thumbnails for the DAM Assets. Once the first step is complete, you need to define the Web-Enabled Image Width & Height.
Once these two steps are completed, all the assets created or modified will utilize these configurations to generate web-enabled renditions, and there will not be any downscaling of images.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.