AEM Assets supports a number of proprietary and third-party file format libraries to cater to diverse file support requirements of users.
Supported Adobe libraries include, Adobe Camera Raw, Gibson, Adobe PDF Rasterizer, and Adobe InDesign Server. In addition, AEM Assets supports third-party libraries, including ImageMagick, Twelvemonkey, and so on.
For comprehensive details on supported file formats, see Assets supported formats.
The following topics describe some of the best practices pertaining to various areas around file support within AEM Assets.
- PSD files with layer masks or embedded thumbnails
The Adobe Camera Raw library supports CMYK color profile as input. However, it generates the output in RGB colorspace. It does not retain the source file colorspace (for example CMYK) in the thumbnails.
The Adobe Camera Raw library supports output in JPEG format only. It does not support output in PNG format. For more information on Camera Raw support in AEM Assets, see Camera Raw Support.
- Heavy, content intensive PDF files
- AI files with thumbnails not generated out of the box
- For AI files with SPOT (PMS) colors
Adobe recommends you use InDesign Server to extract Adobe InDesign-specific renditions, such as IDML and HTML. For more information, see Adding AEM assets as references in Adobe InDesign.
Dynamic Media generates and delivers multiple variations of rich content in real time through its global, scalable, and performance-optimized network. It serves interactive viewing experiences and streamlines the digital campaign management process. For details around enabling Dynamic Media, see Configuring Dynamic Media.
Currently, Dynamic Media can support videos up to 20 GB of content per file.
- To generate thumbnail renditions for EPS files
- To preserve image profile information
- To preserve transparency
To know how to set up the ImageMagic library in AEM, see Using ImageMagick.
AEM Assets encounters out-of-memory issues not only if the size of the image you upload is large but also if its dimensions exceed recommended limits. Generally, you can avoid such issues by allocating a higher heap size while starting AEM.
In addition, open Configuration Manager and set the threshold size to use intermediate temporary file property of the com.day.cq.dam.commons.handler.StandardImageHandler component to a value greater than 0.
If renditions are generated incorrectly, use the Camera Raw library to regenerate them. However, the Camera Raw library cannot process images that have more than 65000 pixels on their longest side. Moreover, irrespective of the file size, the Camera Raw library can only process images that contain a maximum of 512 MP (512*1024*1024 pixels).
It is difficult to accurately determine the maximum size of a TIFF image that can be processed. In addition to the size of the file, the ability to process depends on other factors, such as pixel size. For example, the Camera Raw library may be able to process a 255-MB TIFF file out of the box. However, it may fail to process an 18-MB file if it has a huge pixel difference.
The following table lists the sizes of Camera Raw-generated TIFF files that have been validated with a 14GB heap space.
In general, increasing heap size helps processing larger files efficiently. However, when processing compressed files (ZIP files), low resolution files may not be processed.