Dynamic Media OpenAPI does not support direct delivery of progressive MP4 renditions
This article explains that Adobe Experience Manager Dynamic Media with OpenAPI does not provide out-of-the-box support for direct delivery of individual progressive MP4 renditions for video assets, and clarifies available options.
Description description
Environment
- Adobe Experience Manager Assets as a Cloud Service
- Dynamic Media with OpenAPI enabled
Issue/Symptoms
You need each automatically generated adaptive video representation as a complete progressive MP4 file at a stable, documented delivery URL. The required characteristics are:
- Content type:
video/mp4. - HTTP byte-range support.
- A stable delivery URL.
- Correct width and height metadata.
- No dependency on HLS/DASH manifests or adaptive-streaming players.
Example target outputs include:
940 × 1180desktop MP4.768 × 964tablet MP4.640 × 804smaller desktop/mobile MP4.576 × 724mobile MP4.
The consuming application must fetch the complete MP4 directly, without using the /play endpoint or adaptive-streaming technologies.
Cause
Dynamic Media OpenAPI is designed to deliver video assets primarily through adaptive streaming (HLS/DASH) and does not natively expose individual encodes as progressive MP4 renditions via direct URLs.
Resolution resolution
Use the delivery option that matches your playback requirement:
- If your consuming application supports adaptive streaming, use the HLS or DASH playback manifest with a compatible player. This delivers the adaptive video set; it doesn’t provide a separate progressive MP4 URL for each encode.
- If your application needs one progressive file rather than each adaptive encode, use the original uploaded video through the documented original-binary API, or use an existing pre-generated rendition through the documented rendition API. These APIs deliver the original file or a stored rendition; they don’t expose the automatically generated adaptive encodes individually.
- If your application requires every automatically generated adaptive encode as a separate progressive MP4 with a stable URL, HTTP byte-range support, and the corresponding width and height metadata, build a custom solution outside the standard Dynamic Media with OpenAPI functionality. Your development or consulting team must design, implement, and maintain that solution. Adobe Support assists with documented product features; it doesn’t design, implement, or support custom solutions.