Hello and welcome to the QSC software feature licensing tutorial. My name is Patrick Heyn, and I'm
Nate Makaryk. In this course we're going to give you a baseline knowledge of QSC software licenses,
explain the advantages of the software licensing feature in the platform, and then finish off with
a series of practical demonstrations and use cases for QSC software licenses. For starters, let's talk
about what a software license is and what it's for. Think about all the apps on your phone.
When you pay for one of those apps and start using that software, you are licensing the right to use
that software. Buried deep in that software code are mechanisms to protect the intellectual property
of that software developer. And that's it. It's a legal instrument that governs the use of the software
for the licensee, and protects all the hard work of the designer. You may be most familiar with QSC
for its hardware, but in recent years software has played a really important role in so many of our new
products. Like CXD amplifiers, TouchMix, and probably the most obvious example, the Q-SYS platform.
As you probably know, Q-SYS pairs a real-time A/V and C software operating system with standard IT
technology to consolidate lots of audio, video, and control processors into one integrated solution.
We're taking that software model to the next level with Q-SYS, by licensing some of our features on the
Q-SYS platform rather than building new dedicated hardware to achieve the same functionality.
This concept may seem … a little new to some, but software has actually been a standard practice in the
IT industry for decades now. Things like Microsoft Office 360, Adobe Creative Cloud, SolarWinds,
salesforce.com - these are all licensed products, and the IT customer is already accustomed to licensing
features like these for their technology infrastructure. They also know that investing in a software-based
platform means that advancements and updates come at the software layer. Which means that their
capabilities and functionalities can expand with a simple firmware push, rather than adding additional
hardware. Let's go over the three separate features within Q-SYS that you'll be able to license.
The first one is the Multi-Track Audio Player upgrade in Q-SYS. That one is pretty straight forward.
It expands the audio track capacity of the Core's Multi-Track player. QSC has been licensing these for
years now, but now that licensing will take place in the new software licensing platform. The second
license feature is the Q-SYS UCI Editor, and more specifically, the ability to deploy custom user control
interfaces onto a Q-SYS touch-screen. This license lets you deploy UCI designs onto as many Q-SYS
touch-screens as you'd like on a given system. The third licensed feature is for the Q-SYS Scripting Engine,
which includes the use of plug-ins and the new text controller and block controller. Basically, the tools
that you use to script custom third-party devices. Keep in mind that designers will still be able to program
within Q-SYS UCI Editor and the Q-SYS Scripting Engine in emulation mode. We wouldn't dare take that
away from you! The license only comes into play when you need to deploy these features onto a
Q-SYS Core processor. A couple things to note … these feature licenses will be available for sale as
perpetual node-lock licenses, which is just a fancy way of saying that after you deploy it, the license does
not expire and the function that the license provides is a lock to a single device. In this case, the Core
processor. For our QSC sales partners, you'll be able to work with your sales directors on getting some
30-day demo licenses for your customer evaluation and sales calls - as well as a Not for Resale license,
which are 12-month licenses primarily used for demo systems and training gear. Now … before anyone
starts freaking out (I'm not freaking out), I want to be clear that all of the legacy Cores that are in the field right
now will not be required to license the UCI Editor deployment functionality or the Q-SYS Scripting Engine.
Maybe I should be freaking out, this sounds like something I should freak out about! No, those systems
are already grandfathered in automatically. We will also not be requiring licenses for the larger
enterprise Cores like the Core 5200. After the release of Q-SYS Designer Software 7.0 (I'm gonna freak
out about this) all of the new Q-SYS Core processors will ship with 7.0 firmware. Designers that want to
incorporate either UCI interfaces or the Scripting Engine into Designer (that use a 110 or 510 processor)
will be required to acquire a license, and deploy that license. So you're telling me that if someone has
a Core out there already, even if they upgrade to the new Q-SYS Designer 7.0 or higher, that they already
have the licenses built in and they don't have to worry? Yes! Yeah, I'm not going to freak out about that.
Here's how the basic channel structure works. In the U.S. a local rep firm will place an order with QSC,
who will then distribute those licenses to the integrators and installers via an online partner portal.
This integrator can then assign licenses to customers, manage those customer licenses, and activate
licenses on behalf of their customers. Outside the U.S., QSC distributors and partners will be expected
to carry a certain number of bulk licenses - and then be able to sell them to the integration customers.
So that's your introduction to QSC Feature Licensing. If you're a QSC rep or distributor and you'll need
access to tutorials on how to use the QSC Partner Portal, contact your local QSC rep for access.
If you need help actually deploying a feature license onto a Q-SYS Core, well we have a video for that too.
We'll see you next time.