Service Description
With deliver.media engine., you can easily connect and manage the tools and services that deliver your content, automating workflows so that you save time and money. Deployed on-premises, deliver.media engine. enables you to unify your existing broadcast and media applications, whatever they are and wherever they run, and easily add new features. The platform allows you to seamlessly interconnect the third-party applications and services you already use with a range of tailored media modules available within the deliver.media ecosystem. Enjoy efficient and automated workflows for video file handling, audio conversion, metadata enrichment, content monitoring, and automated archiving. Even legacy scripts and systems can be integrated in deliver.media’s connected world. Your teams can access the platform through our web-based portal providing authentication and access control for all services.
Components
deliver.media engine. consists of the following components:
Instance(s)
A deliver.media application instance consists of one or more workflows and tasks in a graphical user interface (GUI) or a service instance. All the associated files, including configurations, are contained within an application instance container (folder). This makes it easy to copy, back up, restore, and move instances on the same machine (e.g. Windows PC or Server).
Workflow(s)
Task(s)
A task is a sub-element of a deliver.media engine. workflow. Each task can have one or two outcomes (on-success or on-failure) which can lead to another tasks (subtask). Every task is started by a trigger that uses data inputs and outputs and connectors. It is possible that external applications or workflow systems act as triggers (pull) or are triggered (push). Furthermore, deliver.media engine. workflow allows users to modify and translate inputs and outputs, as well as process multiple and combined inputs and outputs for both simple and complex metadata tasks with audio and video processing.
Trigger(s)
A trigger is an element or signal that starts a deliver.media workflow (task). Multiple types of triggers are available:
- A watch folder is a directory that is monitored for incoming files that are used to trigger a workflow. Watch folder triggers are useful for tasks that need to be triggered by the presence of a file in a specific directory. For example, you can use watch folder triggers to trigger a workflow when a file is uploaded to a certain directory, or when a certain file is modified. With deliver.media engine., you can easily set up watch folder triggers for your workflows, allowing you to automate tasks based on the presence of specific files.
- An interval trigger is a type of workflow trigger that is set to a specific time interval and runs the workflow every time the interval elapses. Interval triggers are useful for tasks that need to be run on a regular schedule, such as daily backups or weekly reports. With deliver.media engine., you can easily set up interval triggers for your workflows, ensuring that your tasks are completed on time and with minimal manual effort.
- A timed trigger is a type of workflow trigger that is set to a specific time and runs the workflow only once when the time is reached. Timed triggers are useful for tasks that need to be run only once, such as sending out a notification or an email. With deliver.media engine., you can easily set up timed triggers for your workflows, ensuring that your tasks are completed on schedule.
- A REST API trigger is a type of workflow trigger that is triggered by an external application or service via a REST API call. REST API triggers are useful for tasks that need to be triggered in response to an external request, such as triggering a workflow when an order is placed or when a customer service request is received. With deliver.media engine., you can easily set up REST API triggers for your workflows, allowing you to automate tasks based on external requests.
Data Inputs and Outputs
Data inputs and outputs are essential elements of deliver.media engine. Data inputs are the sources of data that are used to trigger a workflow, such as files, webhooks, and REST API calls. Data outputs are the data that is produced by the workflow, such as the output of each task, the final output of the workflow, and any errors that may have occurred. With deliver.media engine., you can easily read, transform, translate, and export metadata with audio and video files. The engine can read data and files from various sources, referred to as data inputs, and after processing, output the results.
Currently, supported formats for input data:
- Text (Plain text .txt)
- Spreadsheet: Microsoft Excel 2003 or earlier (.xls). Microsoft Excel 2007 or newer (.xlsx)
- XML
- SQL (Microsoft SQL 2012 or newer)
- Audio Files: Common formats (see VLC) [1]
including- ID3 Tags
- Apple iTunes metadata
- MPN (audio, metadata, artwork)
- Video Files: Common formats (see VLC) [1]
- And custom connectors or APIs
Currently, supported formats for output data:
- Text (Plain text .txt)
- Rich Text Format (.RTF)
- Spreadsheet: Microsoft Excel 2003 or earlier (.xls). Microsoft Excel 2007 or newer (.xlsx)
- XML
- SQL (Microsoft SQL 2012 or newer)
- Audio Files: Common formats (see VLC) [1]
- Video Files: Common formats (see VLC) [1]
- And custom connectors or APIs
Currently, the following standard connectors are available (alphabetical order):
- AWS S3 file storage or compatible
- Azure storage (blob and azure files)
- Exoscale storage
- IBM Storage
- SFTP / FTP
Custom Connector(s)
In alphabetical order:
- Adremes
- CreateCTRL API
- DABiS (Standard and Premium)
- DigiMedia
- HTTP JSON REST
- Kaltura
- MusicMaster Standard and API
- OmniPlayer (Version 2)
- PluxBox
- radio.cloud
- WDSL for SAP
Annotations
[1] Since we are continuously adding support to more formats and some formats might contain errors, we recommend getting the file approved by our data team or run a PoC on your system.
Comments
0 comments
Please sign in to leave a comment.