Rhozet Carbon Server
Key Features |
|
 |
Scalable Operation |
| Carbon Server is designed to scale from a single user to an entire enterprise. Users can start with a single Carbon Coder node running under the control of Carbon Server, and then add more nodes as the transcoding load increases. The server software automatically recognizes new Carbon Coder nodes and adds them to the transcoding operation. If a node fails, transcoding is automatically routed to other nodes. |
| Click to enlarge |
 |
Web-Based Interaction |
| All control of the Carbon Server application is through an administrative Web interface that can be securely accessed from any machine on the network. This interface allows for the configuration of network watch folders, transcoding profiles, FTP transfers, etc. The “farm” can be fully automated, with specified priorities for jobs coming from certain network locations. Users can also submit jobs on an as-needed basis. |
Click to enlarge
Back to top |
 |
FTP Transfer Control |
| The “farm” managed by the Carbon Server application can access shared storage on the network or remote storage via FTP. As an example, Carbon Server can be set to watch an FTP location on a catch server, then automatically transcode arriving material into an editing format. The transcoded video can then be automatically transferred to an editing station. |
Click to enlarge
Back to top |
 |
XML-based Interface |
| 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. The same SDK controls both Carbon Coder and Carbon Server, so your work will scale from a single machine to an entire farm. |
Click to enlarge
Back to top |
|