Sundog media toolkit c4 id Use Cases. Project Cloud QTR meeting Disney/ABC
•Descargar como PPTX, PDF•
0 recomendaciones•1,167 vistas
A major feature is the playlist mastering and versioning capability for DCP and IMF (note - IMF is not general availability yet). The platform includes a playlist aware asset management feature. This manages content within a customer’s storage to ingest, validate then organise the assets in a dedicated repository. C4ID is used to ensure unique asset identification within the Sundog system and the customer’s asset repository and at the same time provide external reference capability. Additionally C4ID is used to ensure no duplication of assets within the repository.
Recomendados
Recomendados
Más contenido relacionado
Más de ETCenter
Más de ETCenter (20)
Último
Último (20)
Sundog media toolkit c4 id Use Cases. Project Cloud QTR meeting Disney/ABC
- 1. C4 ID for mastering asset management in Sundog Media Toolkit Ingest Point Source media Asset Repository Validate assets Package MD5 hash check C4ID hashing function (single function) Create Asset Object Metadata Rename object with C4ID C4ID ObjectsMXF tracks XML Playlists Metadata Key data DB De-duplicate using C4 ID
- 2. C4 ID for mastering asset management in Sundog Media Toolkit Asset Repository Verify asset match and validate via C4ID hashing function C4ID Objects PackageMetadata Distro Repository Client Cloud Working Repository 3rd Party Distribution Platform C4ID Objects DB C4 ID list Identify Package C4ID group Package request
- 3. C4 ID for mastering asset management in Sundog Media Toolkit Asset Repository C4ID hashing function Call Assets via Object Metadata Rename object with original name C4ID Objects MXF tracks XML Playlists Metadata Customer Archive Client Cloud Working Repository Long Term Archive No database interaction required
Notas del editor
- Sundog Media Toolkit is a cloud platform for post production processes. A major feature is the playlist mastering and versioning capability for DCP and IMF (note - IMF is not general availability yet). The platform includes a playlist aware asset management feature. This manages content within a customer’s storage to ingest, validate then organise the assets in a dedicated repository. C4ID is used to ensure unique asset identification within the Sundog system and the customer’s asset repository and at the same time provide external reference capability. Additionally C4ID is used to ensure no duplication of assets within the repository. File naming issues are common, particularly in the versioning environment. C4ID removes any ambiguity in this respect and helps to flag assets that are the same but differently named, or share a name but are different. In the Sundog platform, where assets are passed through this process the C4ID is also attached as part of the mastering metadata which is attached to the cloud object. C4ID is also stored in the asset database alongside other key relational data.
- C4ID allows a more robust exchange of assets with distribution platforms whereby the recipient may or may not receive C4ID named object, but can use C4ID to verify the uncorrupted and correct delivery of assets. Although the hashing process is not as fast as an MD5 checksum normally used in this type of asset exchange, it gives the same level of confidence assets are uncorrupted while also ensuring the delivery is of the correct assets.
- In asset exchange between storage clouds, the C4ID is not required to be exchanged to be useful. In this scenario the assets are to be moved from a customers working repository to an archive repository in a different domain. The assets to be exchanged can be identified either via the C4ID and database, or directly via the metadata. Sundog attached mastering metadata is descriptive enough to preclude the requirement for database interaction. Effectively a validated and authenticated secure “shopping list” can be used to identify assets. When moving assets out of the repository, they can be renamed with original or new human friendly filenames as part of the transfer. This can happen at either end, but it is preferential to do so at the receive point, at the same time as performing the C4ID hash to check for file integrity.