DYNAMIC Workflow

The above image represents a workflow of the amagi DYNAMIC system. Here's a breakdown of the workflow:

Live Events Schedule:

The process begins with the live events schedule, which is presumably set up either manually or through a predefined schedule. live schedule can come via API, via UI (through API) and can also be dropped in a S3 bucket. the outcome is the same plalyist will be proessed by DYNAMIC and be converted into events where each of the event will have it's own schedule.

REST API:

• This is a common interface for any communication and user interaction regardless if the user is using a web-based UI or is interacting with DYNAMIC via a 3rd party system.
• This REST API can interact with both the UI (User Interface) and 3rd Party Platforms.
• The UI allows users to monitor, manage, and control the live events, while the 3rd party platforms could be systems integrated with DYNAMIC to provide additional services or data.

Orchestration API:

The REST API communicates with the orchestration API, which is responsible for the deployment and configuration of the software required for live playout operations. This API ensures that all elements of the system necessary for live playout are properly configured and integrated.

CLOUDPORT Live:

• The provisioned system for live playout can be then managed by user via CLOUDPORT LIVE UI.
• It manages the ingestion and preparation of live input feeds and media files for broadcast.
• CLOUDPORT Live ensures that the live stream is dynamically managed, pushing live feeds to the necessary delivery platforms.

Delivery Platforms:

• Finally, the output from CLOUDPORT LIVE is delivered to the various delivery platforms, which could include streaming services, broadcast channels, or other endpoints where the live event is viewed by the audience.