Designer Basics

Video Transcript

0:08
Welcome back. Now that we know the basics of video, let’s take a look at wiring the NV-32-H in
0:13
the Q-SYS Designer software.
0:15
As always, we recommend you follow along as you watch, even if you don’t have any
0:19
hardware. So, come with me if you want to live. 
0:26
We’ll start by going to the Inventory panel and selecting the Video tab. You’ll find the NV-32-H
0:32
near the top, and let’s click twice to add two of them to our design. We’re going to simulate a basic
0:38
setup in which we have three HDMI sources in one room, and we’ll deliver those to a single HDMI
0:44
display in another room. These sources and displays are represented by these items: “Generic HDMI
0:50
Display” and “Generic HDMI Source” in the software, so let’s add those to our design too. We don’t care
0:57
what manufacturer or model these devices are, we just need something in the Schematic to represent
1:03
those devices.
1:04
However, a nice benefit to having these devices in your inventory is that their statuses can be
1:10
delivered to the Q-SYS Reflect Enterprise Manager, so you can get all the information on these sources and
1:15
displays from your cloud-based monitoring system. Pretty neat, right?
1:20
Like any Q-SYS networked peripheral, you’d want to make sure you give this inventory item the
1:25
same name as an actual device that’s connected to your network. If you’re emulating this without
1:30
hardware then obviously you can’t do this right now, but I’ll use the Q-SYS Configurator to find my
1:35
devices on the network and name them appropriately in my inventory properties. And don’t forget to do
1:42
your good housekeeping and give all your items a Location name, and particularly for your HDMI
1:48
components you may want to label them so you know what they represent. Mine will represent a
1:54
Rackmount PC, a Laptop, and a BluRay Player for the sources, and a Projector for the display.
2:07
Once everything is named and organized, you have a very important task for your NV-32-Hs. By default
2:14
they start as encoders, so be sure to look at the properties and change the “Device Type” to “Decoder”
2:20
for any devices you’re using in this manner. For me, I have one encoder and one decoder. Now, let’s
2:27
drag the most pertinent components of each item into our design so we can wire them together. Your
2:33
Generic HDMI devices only have a single Status/Control block, so we’ll grab each of these. The NV-32-Hs
2:42
have an “HDMI I/O Encoder” or “HDMI I/O Decoder” component, so drag these into your schematic as well.
2:50
You’ll notice some new pin types you might not have seen before. The HDMI pin obviously represents a
2:57
local HDMI port, while this other pin represents the encoded stream that goes across the network
3:04
between two endpoints. We’ll call this an AV port, since it contains both the audio and video in the
3:11
stream, and because the icon kind of looks like an A and a V that got fused together at their corners.
3:16
However, rest assured that the HDMI pins also carry both video and audio. You’ll notice that the
3:23
Decoders have an HDMI pin as well as audio pins, but these audio pins can be sent to the Core for
3:30
routing and processing, especially if you’re using local reinforcement. These audio pins automatically
3:36
follow the selected video, so there’s no need to write any extra control logic for that. But if you’re not
3:43
reinforcing this audio with other loudspeakers, you don’t need to wire these pins to your display
3:47
component at all. We’ll talk more about breaking audio away from the HDMI streams in a later video.
3:53
Before you wire anything together, I want to point out that if you open these components’
3:58
control panels right now, there is very little inside. In fact, the Decoder will even tell you that it’s useless
4:05
because no display is wired to it.
4:08
So, let’s wire them up! Wire your three HDMI sources to your encoder’s local HDMI inputs…
4:17
Don’t forget that these generic objects in the designer are just “dummy” blocks. If you
4:21
physically wire the BluRay Player into Port 1 but you label it a PC here in the software, you could get
4:28
very confused later when you try to troubleshoot.
4:31
To make the connection between the encoder and the decoder, you could wire these AV pins to
4:36
each other, but I’m going to recommend that you use signal tags for this.
4:41
It’s important to note as you do this, that on the Encoder side there is a direct one-to-one correlation of
4:48
the HDMI inputs to the AV streams. HDMI Input 1 will always go to AV output stream 1, HDMI input 2
4:57
will always go to AV output stream 2, and HDMI Input 3 will always go to AV output stream 3. However,
5:04
once they’re encoded on the network, you can deliver them to a decoder in any order you like.
5:09
Also, note that the Decoder has a default of three AV inputs, which in my small example is perfect. But if
5:16
you have lots of video streams on the network, don’t worry—you’re not limited to only three options.
5:21
Simply select the decoder and look at its properties, and adjust the “AV Input Count” field. This lets you
5:28
add a lot more options for your encoded AV sources to select from for your Decoder’s outputs.
5:34
Finally, wire your Decoder's HDMI outputs to your HDMI Display.
5:40
Once this is wired up, the last and most important controls you’ll want to know about are here inside
5:45
the Decoder’s control panel. These are the routing options for your displays. Most installers will simply
5:52
drag and drop these buttons into your UCI to give the user the ability to do simple switching. That’s
5:58
definitely the easiest route, however you can get pretty crafty here if you know a little Q-SYS Scripting.
6:04
By the way, you probably noticed that there are more input options than you probably expected. The
6:10
first three options, labeled Graphics 1-3, will display one of three static images you can upload using the
6:18
Core Manager, which are useful for displaying color test patterns, business logos, or standby screens.
6:25
You can also select any of the three local non-encoded HDMI sources of the Decoder unit, if you have
6:32
any sources located near this device. Finally, your encoded AV streams are listed at the end. If you’re
6:39
curious why they’re listed last even though they seem like the most commonly used buttons, I’ll tell you.
6:44
The graphics and local HDMI sources are fixed at three each, but you can customize the number of AV
6:51
streams. This means you can add new AV streams later without breaking any logic you’ve built for
6:56
activating the graphics or HDMI sources.
6:59
If you were following along with real hardware, congratulations—you currently have a
7:04
functioning design! Your media enters Q-SYS through an HDMI port on the encoder, and you can select
7:11
to display that content across the network with the decoder.
7:15
However, this was a very simple scenario. In the next videos we’ll get more complicated and show
7:21
multiple displays, different source types, and breaking away the audio out from your HDMI streams.
7:26
One final awesome feature I wanted to show you is you might have noticed a label called
7:30
“USB Bridging” in the NV-32-H’s properties panel.
7:34
In addition to managing HDMI video stream, NV Series doubles as an bridge for Q-SYS conference
7:40
camera video and audio for use with soft codec conferencing application like Microsoft Team, Zoom, GotoMeeting, etc.
7:49
This eliminates the need for an additional Q-SYS bridging endpoint device that needs to live at
7:53
the table … less cost and less hardware. 
7:57
If you want to learn more about how to do USB Audio and Camera video bridging, we have a
8:00
different tutorial for that. Alright! So take a quick break and move on whenever you’re ready.