As the list of features grows with each release of Cambria, we have been able to simplify our workflows that would have required many tools or functions. It can now be completed in a single transcoding step.
- Michael Moorfiled Global Broadcast Services Manager
Adstream provides a full suite of connected solutions for brands, creative agencies, production houses and media owners. It combines collaboration tools, digital asset management, a global distribution network and powerful analytics to provide smarter, more collaborative advertising workflows.
Provisioning the optimal amount of transcoding resources within a workflow is traditionally a tricky balancing act. Allocating too few resources risks SLA and missed airtime as demand exceeds available throughput and a queue backlog grows. Conversely, assign too many resources and costs increase, reducing revenues. Adstream has this balancing act down to a fine art.
Adstream has a transcoding presence in eight AWS regions, and when it seeks to replace or update transcoding technology, one of its major requirements is the ability to efficiently scale as demand requires.
Scalability was already available for the Adstream workflow engines controlling and orchestrating content, but the real challenge is finding transcoding technology to handle this content, which requires heavyweight toolsets beyond the limits of open-source solutions.
Using Capella Systems’ Cambria FTC and Cambria’s floating licence mechanism, Adstream manages transcoder demand with a tiered method that scales vertically and horizontally.
Cambria FTC’s efficient transcoding queue sizes and its ability to prioritise transcoding per individual job are the first step to dealing with peaks and managing bottlenecks.
Using the Cambria FTC API, workflow engines can set the number of concurrent transcode jobs to match the specifications of any situation, creating the right balance of throughput to avoid needless I/O bottlenecks.
By coupling queue optimization with per-job priority settings, Adstream ensures that JIT and SLA critical content can be transcoded ahead of lower-priority content.
Using the Cambria floating licence API, a licence can be attached to a job from a pool of available licences. Then, as a new job replaces a completed one, that licence is transferred to this new instance as the previous instance is terminated.
As the default Cambria licence model supports instances up to 64 cores, Adstream can continue to increase the instance size appropriately and without disruption to the BAU.
When demand reduces, the instance size can be decreased appropriately, or when no longer required, terminated completely, releasing the licence back into the pool.
While it is perfectly possible for content held in S3 storage in any of the AWS regions to be transcoded in any of the Adstream AWS regions, this cross-regional processing is not practical at scale.
Adstream clients’ regional peaks coincide with the path of the sun. A pool of floating licences available to all regions ensures that spikes in demand can be handled within the region to allow load balancing and further optimisation of the transcode queues.
Adstream’s automated deployment mechanisms protect against any misconfiguration or variances between regions. All the tools found in one AWS region need to be available in all other regions to provide a consistent product as part of DR strategies.
Capella has helped greatly in this respect by automating update installs and providing the ability to set features via an API. This reduces the complexity of evaluating new software releases and features in UAT environments before they’re deployed into live production.
Using Cambria FTC’s evolving toolset, Adstream has been able to reduce the number of subsystems required to meet the specifications and requirements for each broadcaster or playout provider.
Audio mapping and linear audio normalisation can be quite complex but are necessary steps, as are dynamically creating slates and providing custom head builds. Using the Cambria FTC API, Adstream does all this and transcode in a single step.
Not only has this consolidation optimized speed throughout the system, the lean and powerful infrastructure reduces the number of points where issues can arise, making support easier to manage.
Cambria FTC’s ability to transcode content directly from and to S3 buckets has also resulted in further efficiencies, especially around handling longform content and provisioning large amounts of temporary storage to stage source and target files.