Amberfin announces new driver for transcoding farms
Significantly increases flexibility and versatility in a multi-node transcoding environment.
Amberfin has introduced new enterprise-class features for its ICR ingestion and transcoding system that will enable the creation of scalable transcoding farms from one to many nodes. With Amberfin ICR, media facilities of all sizes, scales and business models can increase their transcoding capabilities without the need for third-party elements.
The new functionality of the iCR transcoding farm controller enables large-scale multi-format transcoding. Significantly increases flexibility and versatility in a multi-node transcoding environment, improving resiliency and resilience while simultaneously realizing cost savings through more versatile network licensing capabilities.
In today's increasingly file-based media workflows, file transcoding operations have become critically important. Amberfin's approach allows for achieving an appropriate level of redundancy for a specific application and enables a combination of high performance and advanced system features.
The new ICR controller works by providing a single, reliable, and redundant interface to ICR transcoding capabilities. Jobs are sent to the ICR controller and in combination with the Amberfin network license it is possible to configure an even larger scale model of a pool of transcoding nodes that can dynamically float across the underlying server hardware and no longer require Fixed node-to-server relationships. This achieves higher levels of redundancy and operational efficiency across a large-scale transcoding network by efficiently using available hardware nodes.
AmberFin iCR also introduces sophisticated new tools to add and control custom metadata through your own configuration and without the need for expensive code customization. The ICR Metadata Plug-in Wizard allows users to configure the metadata they need for their organization so that ingestion and QA operators can automatically update and validate this information as part of an QA . This metadata can then be used to control segmentation workflows and different versions.
Did you like this article?
Subscribe to our RSS feed and you won't miss anything.