The section of this site describes the Low Level Transcoding and Archive API supported by yospaceCDS. Most customers however, will want to use the Media Item API which uses the higher level functions of yospaceCDS to support automatic transcoding, video access with device detection and a host of other workflow features. The Low Level API is only for developers wishing to encode and store video.
yospaceCDS Low Level API provides a way of storing and distributing media content (image, video, or audio). You put media content in, and can subsequently take it out in a wide range of formats perhaps with modifications such as added intros or logos. The API takes care of the format conversions, caching, and data management. The key feature is that you only need to provide the media content once.
yospaceCDS operates with a Web Services interface so it is easy to integrate into a wide range of applications. The full interface specification is available in WSDL. Content is uploaded and manipulated through HTTP(S) requests. yospaceCDS itself sends notifications to report the status of operations (typically confirming that content is now available for download). Ultimately the content itself, processed and stored in the media farm, is available for download or streaming using a simple URL.
You must explicitly indicate the conversions required to the content you upload (either you do this yourself, or you let the Device Targeting System (DTS) take care of it for you). Standard conversions include all the common media formats (so that a video submitted in one format is available in a range of others), but may also include filters such as thumbnailing, watermarking or splicing videos together. In addition to the standard conversions, yospaceCDS can also run third-party conversion scripts.
All content stored in yospaceCDS can be retrieved by a URL that uniquely identifies the content and the conversions that have been applied to it (for example, the format conversion).
Not everything in yospaceCDS is freely available for download or streaming. You can restrict any of the content so that it can only be accessed by authorised users. A typical example of this is content that is only available to a customer who has paid for it. For example, yospaceCDS can be configured to recognise an encrypted token, with a limited lifespan, which your purchasing mechanism can generate when the customer pays for the content.
The original, or canonical, data is never made available. This ensures, for example, that video that has been watermarked with the publisher’s logo cannot be downloaded without it.
The diagram shows the basic process of uploading media content, converting it, and making it available for download or streaming. See A Simple Example for a description of each stage of this process. The subsequent sections describe each stage in detail.