Channel Regionalization

Frame-accurate content replacement platform for TV Networks

What is STORM

Amagi STORM is an IBC Innovation Award-winning platform for regionalized content distribution. It can be deployed by TV networks and broadcasters to regionalize content in specific regions covered by a common satellite feed. By regionalizing specific content at an operator level, STORM platform eliminates the need to deploy additional satellite feeds to address local broadcast regulations, content rights obligations, or viewer preferences.

Amagi STORM is an intelligent IRD that supports a wide array of industry standard triggers such as SCTE35, Packet 31, DTMF Cue Tones, and Amagi’s patented ‘Watermark’ trigger for content replacement. When used with Amagi’s patented ‘Watermark’ triggers, STORM requires no changes to the existing broadcast workflow as the watermark signatures are completely inaudible, and invisible markers. Since STORM supports frame-accurate ad splicing, it can efficiently support requirements of sports or live event broadcasters. With support for multiple localization use cases, Amagi STORM is the most preferred regionalization platform available today.


  • Reduce CAPEX, eliminating the need for additional satellite feeds
  • Manage regulatory, viewer and advertiser requirements better
  • Centralized, web-based managed from any remote location

Application Areas

Regionalize content
Regionalize content

Insert local content in linguistically and culturally diverse markets such as Europe, South America, and Southeast Asia.

Geo-targeted advertising
Geo-targeted advertising

Splice ads in multiple regions offering better value for advertisers and maximizing ad inventory

Address broadcast regulations
Address broadcast regulations

Ensure compliance to specific broadcast regulations without setting up additional feeds.

Customize graphics at operator level
Customize graphics at operator level

Measure performance of campaigns at operator level by displaying different call-in graphic for each operator.

Manage content rights obligations
Manage content rights obligations

Replace non-licensed content with evergreen content without creating separate feeds



Interested in Amagi STORM? Talk to us today.

Technical Specifications

Input / Output


  • RF, HD/SD-SDI, IP, ASI input supported
  • DVB-S and DVB-S2 compatible
  • Conditional access support using DVB-CI
  • Suitable for both HD and SD channels
  • MPEG-2 or H.264 video with MPEG-2 or AC3 audio
  • Zixi output compatible


  • HD/SD-SDI, IP, ASI input supported
  • Zixi output compatible
  • MPEG-2 or H.264 video with MPEG-2 or AC3 audio

Localization features

  • Multisite workflows
  • Ability to do HD to SD down / up conversions in output
  • Multichannel playout with up to 2 HD/SD channels with simulcast support
  • Supports merging parent playlist (main channel playlist) with child playlist (local playlist)
  • Supports multiple playlist format from scheduling systems such as IBMS, BXF, ELG, XML, TXT, CSV formats
  • Evergreen rescue content
  • Customizable AsRun logs

Local content ingest formats

  • AES 128-bit encryption
  • Storage up to 3 TB in IRD
  • Media asset management, with third party integration (Omneon®, DIVA, Suitcase TV etc.)
  • Video: MOV, MXF, MPG, MPEG-2, MPEG-4, MPEG-TS etc.
  • Audio: Up to 16 tracks supported PCM, Dolby E, Dolby Digital
  • AC3, AAC, MP2
  • Graphics: TGA, MOV, Adobe After Effects (Dynamic)

Trigger support

  • Amagi Watermarking-based start and stop bumpers
  • Amagi Watermarking-based content / ads / promo replacement
  • SCTE 35-based insertions
  • DTMF-based insertions
  • Packet 31-based insertions


  • 10 hardware graphics layers & unlimited software layers
  • Dynamic graphics from media database, asset metadata and playlist data
  • Video squeeze capability
  • Static bugs/logos
  • Social media integration
  • Animated bugs/logos
  • Dynamic graphics
  • Tickers
  • Aston bands
  • L-bands


How is Amagi Watermark different than SCTE or DTMF?

Traditionally, replacement triggers such as DTMF, Packet 31, and SCTE 35 have been used to insert local ads on common feed. These triggers are not part of the content stream and are inserted as part of a separate workflow. Amagi Watermark is an inaudible and invisible audio signature that is embedded in the media assets, thus inserted as part of the stream.

How will deploying STORM change my existing workflow?

When using Amagi Watermark in combination with STORM, there would not be any changes to your workflow. Standard modifications may be required in case of DTMF and SCTE markers.

What makes STORM better than traditional localization platforms?

Unlike conventional ad triggers such as SCTE 35 and DTMF, STORM supports Amagi Watermark that eliminates the need to manually mark opt-in and opt-out points for commercials and ensures granular level of control on content/ad replacement.

How is the content to be replaced with sent to operator?

STORM can receive replacement content via cloud or even via satellite trickle bandwidth. Amagi has even created unique architectures that involve secured transfer of content directly from Ad partners to operators/affiliate headends.

How secure is STORM platform from malicious external threats?

STORM has been built to be an extremely secure system, with rigorous security policy governing all transmission of data.

How does STORM handle disaster recovery?

STORM has a built-in memory to store thousands of hours of video. Since every STORM IRD can be linked to cloud, content can be refreshed on a regular basis, ensuring that the IRDs keep playing out latest content in event of a catastrophe.

How do you provide 24x7 support? How do you ensure 365x24x7 uptime for my channel?

Amagi’s services are offered in ‘follow-the-sun’ model with a full-fledged monitoring facility located in Amagi’s operations center in Bangalore. Amagi’s web-based user interface enables operations team to provide 24x7 support remotely.

What support is included in your offering?

Amagi offers on-call and email L1, and L2 support, and L3 technical support for all customer deployments, and uses JIRA ticket management system for on-time resolution of all issues.

L1 Support is the first point of contact for any issues and is responsible for ticketing and monitoring.

L2 support team includes direct phone or email-based ticket resolution for all product/platform issues.

L3 support team works on issues that may require bug fixes or enhancement requests.

I don’t want to use public cloud? Can I use my private cloud?

Yes, Amagi’s platform can be configured for private or hybrid cloud deployments.