Migrating to Dynamic Delivery

Introduction

If you want to understand how Dynamic Delivery works and the advantages of using it, see the Overview of Dynamic Delivery. This topic covers some things you will need to do after switching to Dynamic Delivery, particularly around the using of Dynamic Ingest.

Retranscoding videos

Existing videos won't automatically be converted; contact your account manager for details on how to get your old videos moved over.

If you do have your existing videos converted, or retranscode them yourself to move them to Dynamic Delivery, note that the following metadata will for videos will change:

• The update_at date
• Paths to thumbnail and poster images (note that we recommend not hardcoding video asset URLs in your pages and apps generally)

DRM

If you protect your videos with DRM, one of the advantages of Dynamic Delivery is that you do not need custom profiles to apply DRM. Instead, all you need to do is contact Support and get your account configured for the DRM types you want to apply to your videos. After that, all videos that are ingested or retranscoded using a Dynamic Delivery profile will be automatically protected. See Ingesting content with DRM for more details.

Media Sharing

Be aware that billing works differently for media sharing in Dynamic Delivery. Costs associated with shared media are billed to the master account that the media is shared from, not the account the media is shared to.

Notifications

Notifications for Dynamic Delivery ingests are similar to ones for the legacy ingest but there are a few differences. If you have apps or integrations that depend on Dynamic Ingest notifications to trigger subsequent actions, you will probably need to modify them a little bit.

Below are sample notifications for successful rendition completion for Dynamic Delivery an non-Dynamic Delivery ingests to highlight the differences.

    {
        "status": "SUCCESS",
        "entity": "5123312711001",
        "entityType": "DYNAMIC_RENDITION",
        "version": "1",
        "action": "CREATE",
        "jobId": "48c3a283-40f9-4214-8c27-21e3a040ca6a",
        "videoId": "5123312711001",
        "dynamicRenditionId": "default/audio64",
        "accountId": "57838016001"
    }

    {
        "entityType": "ASSET",
        "status": "SUCCESS",
        "version": "1",
        "jobId": "93d40db1-df3f-4023-bab6-51459cdda470",
        "videoId": "5122632511001",
        "profileRefId": "mp2",
        "entity": "5122644754001",
        "action": "CREATE",
        "accountId": "57838016001"
    }

As you can see, the differences here are that the entity_type for Dynamic Delivery ingestion is DYNAMIC_RENDITION instead of ASSET, and you get a dynamicRenditionId instead of a profileRefId.

If you have an app or integration that depends on notifications, therefore, you will probably need to make some small adjustments in what you are looking for in the notifications.

Players

Good news - if you are using the standard player embed codes, or the native player SDKs, you will not need to make any changes to existing players for Dynamic Delivery. Your videos will continue to work as they did before.