Carbon Server

Workgroup Transcoding – Small to Medium Farms

Multiple Carbon Coder nodes can be configured as a transcoding farm, controlled by one or more Carbon Servers. Carbon Server allows for automated processing of high-volume transcoding tasks, server-controlled failover of Carbon Coder nodes, as well as managing job distribution, job prioritization, load balancing, FTP transfer, status monitoring, and job notification.

Interaction with the server software is through an administrative application that runs on the Carbon Server machine, or via an XML-based API that is included with the product. The same API controls both Carbon Coder and Carbon Server. A web interface that can be accessed from remote machines is also available.

Carbon Server is well suited for simple transcoding managing a couple of Carbon Coder nodes. For more complex transcoding environments requiring; high volume, tighter 3rd party integration or sophisticated workflows, we recommend the Rhozet Workflow System (WFS).

Key Features

Scalable Transcoding

For large transcoding tasks, multiple Carbon Coders can be configured as a transcoding farm, under the control of Carbon Server or the Rhozet Workflow System software. Carbon Server and WFS manage job distribution, prioritization, load balancing, FTP transfers, status monitoring and job notification. All interaction with the server software is through an administrative Web interface that can be accessed remotely, from across the office or around the world.

Automated Operation

Carbon Coder can be run in a fully automated mode. Watch folders and FTP transfers can be configured to automatically transcode any files that are moved to specified locations, and then the results can be placed into designated locations. For example, a single Carbon Coder workstation can service a group of editors, taking completed projects and converting them into the appropriate format for a playout server.

Transcoder Failover

When deployed as part of a transcoding farm, Carbon Server can detect the malfunctioning of a Carbon Coder machine, and automatically re-route existing transcoding jobs that were assigned to that machine to a different Carbon Coder. When the malfunctioning machine is restored Carbon Server will add it to the farm again, and resume sending it new transcoding jobs.

XML-based SDK

Carbon Coder and Carbon Server can be controlled directly via an XML-based SDK provided with the software. Every aspect of the transcoding process can be controlled by the SDK, including source/target destinations, transcoding parameters, filtering, compositing, ad insertion, titling, notifications, etc.