Dynamic Ingest API FAQ

This topic addesses some frequently asked question about Dynamic Ingest


How do I start using Dynamic Ingest?

The New Studio uses Dynamic Ingest behind-the-scenes. Any upload will use the selected profile and have all the advantages Dynamic Ingest provides.

You can also use the Dynamic Ingest API. For more information about getting started please see our Quick Start Guide.

What is Dynamic Ingest?
Dynamic Ingest is a pull-based ingestion method that utilizes cloud transcoding for scalability and speed.
Where can I store my files for Dynamic Ingest?
Any publicly accessible HTTP or HTTPS URL or on an Amazon S3 bucket.
If I use S3 what should my bucket policy be?
See our recommended S3 Bucket Policy doc.
What are the advantages of using Dynamic Ingest over FTP Batch or Media API?
Dynamic Ingest allows for better scalability than the legacy ingestion system using FTP Batch and the Media API. It also allows for more flexible automation options as long as the best practices are followed.
What rendition can I expect to be created first using DI?
Dynamic Ingest doesn’t utilize the previous concept of a "Primary Rendition". Given the scalability of Dynamic Ingest, renditions will complete more closely in time to each other. Therefore, time-to-publish across devices will also improve.
How many renditions can I create for a video using DI?
The maximum number of renditions that you can define in an ingest profile is 25.
What are the Dynamic Ingest Best Practices?
  • Make fewer than 20 API Calls per Minute
  • Have fewer than 100 jobs processing simultaneously (including a callback url on your jobs can help facilitate this)
  • Ingest content smaller than 100GBs per file (if you need to ingest larger files please contact Account Manager)
  • If you are ingesting files in batches, limit batches to 100 and wait for the previous batch to complete processing before continuing
  • Validate profile changes before ingesting full batches
What type of Digital Rights Management does Dynamic Ingest offer?
  • Adobe Primetime Cloud DRM
  • Widevine Classic (for mobile devices)
  • DASH with Common Encryption (with Widevine Modular, Playready, and Marlin packages)
  • Smooth with Playready
What filetypes are allowed using Dynamic Ingest
See Supported File Formats.
What filesize limitations are there?
100 GBs per file (if you need to ingest larger files please contact Account Manager).
How many API calls can I make per minute?
20 API Calls per minute.
Can I retranscode using Dynamic Ingest?
Yes, see Dynamic Ingest API Overview.
Can I replace a current video file with a new one using Dynamic Ingest?
Yes, see Dynamic Ingest API Overview.
Can I configure metadata when I make a Dynamic Ingest call?
Yes, see the CMS API Reference.
What protocols are supported with Dynamic Ingest?
HTTP, HTTPS, S3. For other protocols contact your Account Manager.
What output settings will be used?
The Profile selected at the time of the ingest will be used. See the Default Profile Operations and the Ingest Profiles API Overview for details.
How can I tell if Dynamic Ingest is having an issue?
You can check our System Status page > Video Processing to see the current status.

Related Topics