Why create Renditions?
Convert everything to PDF, MP4 or MP3 outputs. The outputs are independent of the hardware, operating system and application software used to create the file. PDF, MP4 and MP3 formats were designed to create transferable files that can be shared across multiple computer platforms. Moreover, raw source files are compressed (Word, WAV, HD video) to a more shareable size.
What happens during a rendition?
- Queued: Waiting (depending on load – this time is variable) - why a queue? – because it is asynchronous from the upload event which is doing many other things in parallel. Unless there is a major migration going on, this time is usually a fraction of a second.
- Pre-Rendering: File undergoes a pre-screening to ensure it is valid for rendering. Different files have different attributes and rendering pre-requisites.
- Rendering: Depending on file type various rendering activities may occur this is covered in deeper details.The following situations may impact the rendering time: Large file, the longer it takes to convert to PDF. Complexity also adds time – more images, reference links, charts, graphs, alternating page settings. Complexity magnifies feature run time as well: More merge fields, more lookups, more insertions, more links – more scanning and replacing to add blue links, more headings & captions for bookmarks also increase the duration.
- Post Rendering: Optimizations, Text extraction for annotations and doc search (for valid text formats) and internal transformation process so that it can be seen in the viewer.
The following table lists Rendition related articles that help explain and resolve questions and issues. All articles reside in the Support Knowledge Base:
Rendition specification (link to KB article)
|Why Are Some Images Not Displaying in a Vault HTML Document?
|Vault Rendition Creation Limitation
|Why Does an Excel File Not Render in Vault?