Welcome to the Avid MediaCentral | Cloud UX Help > The File Info Tab (Asset Management) > Understanding Essences and Essence Packages

Understanding Essences and Essence Packages
The File Info tab provides information about video, audio, image, and text files. In Asset Management, such files are described as essences. The File Info tab shows in detail how the essence files that belong to the asset open in the tab are organized.
Essences
In Asset Management, essence refers to the pure media data of an asset without any descriptive metadata — for example, a video file. Essences are organized in essence packages. Essences are added to essence packages when they are ingested or imported.
Essence Packages
An essence package is a group of essences classified semantically. Each essence package contains a set of essences that represent the same content and share the same general purpose.
An asset can contain a number of essence packages and each essence package can contain an unlimited number of essences, but they should be of the same content; examples are movie, trailer, stills, script, and so on. The essences within a package can differ in technical features, such as resolution, quality (HiRes or Browse), format, bit rate, and more, but they still represent the same content. For example, the script for a movie should not be in the same essence package as the movie itself, even though they both belong to the same asset. The keyframes of a video are always stored in the same essence package as the video itself. They are considered a different representation of the same content.
Representative Essence Package
One essence package is defined as the representative essence package of the asset. The representative essence package contains the essences that represent the purpose of the asset. The essences in this package are opened by default when an essence or essence package is requested by an other component. The representative essence package can be changed manually or by workflow.
Timecode Handling in Essence Packages
The metadata of an essence package can contain information on the start of content (SOC), end of content (EOC), and the timecode master. This information is then used to handle requests for timecodes of the essences in the essence package.
SOC and EOC define the accessible area of the essences in the package. This indicates that SOC and EOC are the same for all essences of an essence package. If two essences of the same asset have different SOC and EOC, they must be stored in different essence packages.
A timecode master is the essence within an essence package that is used to determine timecodes, timecode leaps, and so on. This essence has been video-analyzed, or will be video-analyzed when the video analysis is triggered. Requests for or calculations of timecodes are answered by the timecodes of the timecode master essence.
Locations, Carriers, and Pools
The essences are managed in locations on carriers and pools. A carrier is a physical medium that stores essence files. Carriers can be disks, tapes, or even entire tape archive systems. The scope of a carrier depends on the granularity that is required to access an essence. A pool is a device or part of a device that holds one or more carriers.