This page contains a Flash digital edition of a book.
post production feature Once ingested and bound together,


the client’s worldwide sales staff can access all the content to browse for what they need through a custom, branded portal. When someone finds something they want the source file for, the user interface allows them to make a request for either the entire asset or a partial version in the codec/format they desire. This sends a request to a server via XML that the local system is set to poll at regular intervals. Using file acceleration software, a new deliverable is created and a link is emailed to the address on file for the requesting user. Once the email link is clicked, delivery of the requested content is initiated - and the link automatically expires after download is successfully completed. With this workflow, Client A has


been able to control the costs of offering a cloud service, while still providing a global distribution system and secure access to all media materials worldwide.


SAN in the cloud


Client B demonstrates a far more complex integration. This client is a major Internet media news property


which wanted to mirror its SAN on the cloud in proxy form so that at any given time, assets on its SAN are searchable from anywhere in the world. This would effectively create a PAM (Production Asset Management) system designed to track work in progress, something very much needed in a news environment. On top of that, it wanted access to multiple versions that would be hosted on its own system, rather than the cloud service provider’s - in order to ensure control of access. To serve this need, the integrator


for Client B used MediaSilo’s API to develop a server appliance and write an application platform that constantly monitors its SAN directories. As changes are made to the SAN, this application makes corresponding calls into the cloud platform that mirror these changes, which might include a new folder or subfolder being created, new assets being added, or content being moved to a new location or deleted. While not in real time, this sync updates on a fixed schedule multiple times per day. Utilising a concept called ‘external asset create’, a proxy version along with other deliverables can now exist on the cloud storage platform of the client’s


Client B.


choice (or any other HTTP-accessible storage location with its own RTMP streaming server to control access and cost) - while the source content remains its SAN. Through this set-up, multiple versions of each asset are available via download links which are inserted into the metadata of the record so that they can be accessed by those with appropriate credential and downloaded with a single-click. In both these cases, Clients A and B


have leveraged existing local systems and have been able to maintain existing workflows by automating the process behind the scenes. Instead of taking the time and expense of trying to host and build their own solutions, their integrators were able to leverage the benefits of a platform as a service (PaaS) that offers the flexibility and user-friendly interface needed to securely and easily get their content out to end users anywhere in the world. This means that their content is no longer locked away, but instead democratised across the entire organisation - ultimately saving individual time and organisational money. More than that, this process transforms previously unused and inaccessible content into valuable, dynamic assets.


www.ibeweb.com l september/october 2012 l ibe l 65


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84