Axia iQs Overview


  • Console capability without the physical surface
  • Distributed / remote workforce
  • Temporary studio anywhere (nontraditional studio space)
  • Studios lacking physical space
  • Multiple users who need concurrent collaboration on a single mix
  • Telos Alliance® was there for you when you made the leap to IP, and now we’re here to help you on the journey to virtualization, wherever you are on that path. Our goal is to give you broadcasting options that are familiar while creating new ways of working that deliver on virtualization's promise of added scalability, adaptability, cost efficiency, simple deployment, and reliability. And that’s just what we’ve done with our new Axia iQs AES67 Mixing Console Software.

    More than a decade ago, Telos Alliance created the Axia iQ AoIP console, now known for its ability to deliver a powerful and flexible mixing experience. Rather than pay for unwanted extras and faders, iQ allowed broadcasters to work smarter, offering the ‘just right’ functionality to mix content how they wanted, without sacrificing features.

    Then we took the iQ philosophy and upgraded its underlying technology to create the Axia iQx AES67 console, the first AES67 AoIP console to combine the mix engine and console into one chassis. iQx lets you plug right into your AoIP network —with complete AES67 / SMPTE ST-2110-30 compliance— and enjoy the same capable, easy-to-use experience of the iQ.

    Now, the Axia iQ family takes a bold step into the virtual AoIP future with iQs, the software version of iQx that does not require a physical surface. iQs is the first soft console controlled by a full HTML-5 interface, allowing you to not only control a mix from anywhere, but on any device—Mac, Windows, tablet, laptop, even your phone! It’s available in two ways to suit your needs and comfort level.

    The Benefits of Virtualization

    Non-Proprietary Hardware

    You have more options when it comes to designing your system, including commercial off-the-shelf (COTS) options from the IT world.


    The virtual broadcast studio is customizable, because functionality is not hard-coded to a specific physical attribute on a piece of hardware, like a physical surface.


    You can run multiple instances of software concurrently, allowing you to scale up for demanding production requirements and scale back down accordingly, only paying for what you need.

    Reliable Virtual software and cloud computing are tested, tried, and true. Broadcasters need not worry about reliability compared with hardware options.


    Requires less maintenance, hardware, real estate, conditioned power, HVAC, and associated costs with flexible subscription models to meet OPEX business requirements.

    Easier Upgrades

    Easier to update software remotely over the Internet or en masse in a centralized data center, eliminating site visits.

    2 Ways to Deploy iQs AES67 Virtual Console Mixing Software

    iQs + AE-1000 for Easy Virtualization

    Telos Alliance understands that virtualizing studio operations can be an overwhelming prospect. That’s why we are eliminating some of the legwork by pre-installing the iQs AES67 Mixing Console Software on a 1RU Telos Alliance AE-1000 Application Engine—our new line of universal servers—to help you ease into the virtual studio and prepare for the future. You can centralize the AE-1000 at the studio, yet give board operators the flexibility to control the iQs mix from a bedroom, a coffee shop, a makeshift studio...anywhere with an Internet connection.

    iQs Container for the Data Center

    iQs is available as a Docker container. Docker is a set of platform-as-a-service products that uses OS-level virtualization to deliver software in packages called containers. Containers are isolated from one another and bundle their own software, libraries and configuration files; they can communicate through well-defined channels. Docker is an integral part of the IT future.

    Because iQs is available as a Docker container, it allows broadcasters to deploy it in a server farm or the cloud, delivering the added benefits of true virtualization, such as easier facility-wide upgrades, concurrent instances, and more, without site visits. Perfect for large installations of iQs console software instances.

    iQs in a Docker container lets you realize your all-virtual future now because it’s available as a subscription-based model in addition to singular instances. A subscription allows you to be even more nimble—growing or shrinking the size of your system dynamically as your needs change. You only pay for the functionality you need, and you aren’t locked into any particular console configuration, large or small, for the ultimate in facility flexibility.


    Interoperable, easy to use

  • Browser-based (HTML-5) and therefore accessible from any device (Windows, Mac, Tablet, Smartphone
  • Assign any AoIP source to any channel, like having more than 16 million patch points!
  • Familiar console interface in a software format allows users to get up and running fast, on any HTML-5 device!
  • Smooth handoff from one operator to the next, even in remote locations
  • Use iQs with Axia Pathfinder (not included) to easily route, monitor, and control AoIP sources
  • AoIP Features

    • 3 dedicated stereo Program busses, plus a stereo Utility bus that can be used for phone calls, off-air recording, or as a fourth Program bus
    • Automatic mix-minus on each fader, plus talkback functions
    • Automix automatically balances levels of on-air-microphones when more than one mic is open at a time in a studio
    • Off-Air Record Mode Trigger
    • Studio and Control Room monitor controls
    • 24 built-in stereo three-band EQs
    • Channel-input confidence meters assure the operator of audio presence before taking sources to air
    • Profile context-sensitive Soft key can be used to activate talkback, start delivery system events, or perform other special functions
    • Stereo PFL (“cue”) functions for every fader with a unique interlock system for the fast cueing of multiple sources
    • Reconfigurable CR monitor section with direct selection of 4 program busses and re-assignable buttons that allow instant monitoring of external sources
    • Additional monitor section provides separate monitor volume, source selection, and talkback controls for an associated studio
    • Flexible built-in mix-minus and talkback system lets operators talk to phone/codec sources, each with an associated, automatically created backfeed mix-minus
    • Precision event timer can be operated manually or triggered by starting preselected sources
    • Unlimited Source Profiles with four quick-recall snapshots (show profiles)
    • Auxiliary “V-Mix” remotely controllable 5-input virtual mixer, for whatever extra audio needs you may have



    • Four main stereo program bus outputs, plus bus outputs for Record, Phone, CR Monitor, CR Monitor Direct, CR Headphones, Preview, Talkback to CR, Talkback to External, Studio Guest HP, Studio Monitor, Studio Talent HP.
    • Automatic mix-minus provided for any source input.
    • 5 stereo input to 1 stereo output, auxiliary “V-Mix” mixer.

    Minimum Requirements for iQs Docker Deployment

    • Server-class multi-core CPU(s), 2.0Ghz minimum
    • Memory: 1GB of RAM per each iQs, minimum
    • Docker hosting platform: Docker Engine on Linux (Ubuntu 18.04 LTS) server.
    • For smaller iQs instances with up to 12 faders, two iQs instances can be run per each reserved core.

      Virtualization Platforms

    • The iQs is delivered as a Docker container. The Docker host (Docker Engine) can be run either on a bare metal server or inside of a virtual machine (when running in the cloud, Docker is always run inside a cloud-hosted VM).
    • When Docker is run inside of a VM, there are performance requirements on the virtualization platform in order not to introduce latencies and throughput bottlenecks underneath Docker, which would affect the real-time audio.
    • If Virtualization is used, a type 1 Virtualization host capable of: Exclusive allocation (i.e., pinning) of CPU cores to virtual machines Allocation of CPU resources to network I/O traffic Note: The number of server CPU cores required is the same as listed above in the Docker Deployment section.