Device Configuration

Patrick: Welcome back.

Nate: All right, we've connected to our system and accessed Q-SYS RoomSuite Manager, so let's pick up where we left off.

Let's start on the menu item that's conveniently titled, "Get Started".

When we click on the Devices menu item, we'll see there are currently no paired devices here.

Let's fix that.

I'll just hit the Pair Devices button, and wow, that is nifty.

Patrick: As you can see, this page now shows a visual representation of each of the Ethernet ports on the RMP-100, and if you scroll down a little, those on the QIO-VEN4 as well.

Any port that has a peripheral attached to it shows the detail of that peripheral.

Port 1 on the RMP-100 correctly reports that it's connected to the QIO-VEN4,

Port 2 is connected to the network camera, Port 3 to the network soundbar, and so on.

And if we look at the QIO-VEN4, we can also see our touchscreen controller is connected to Port 1, and our NM-T1 is on Port 2.

Everything is already populated.

There's no need to add hardware manually or configure the network settings.

You probably already can see how much time we've saved here.

Nate: Now, before we go any further, we do need to define something that's pretty important.

What is the main use case for this room?

This particular room is set up for both a PC running a conferencing application of their choice in the credenza or for a laptop to connect here at the table.

So we're gonna leave this on Conferencing Compatibility Mode, which is the default setting.

That's for BYOD, or bring your own device.

However, if this room is primarily gonna be used as a capital R room for one of the UC providers,

like a Microsoft Teams room or a Zoom room, for example, which has its own compute device exclusively running one of those conferencing applications, you'll need to specify as such here in the RoomSuite Manager.

Patrick: Don't worry, this can always be switched if your needs change, but doing so has a number of ramifications that you'll need to consider.

In some cases, that may even include changing out some hardware.

Now, don't worry, we'll demonstrate those extra steps and configuration changes in another video, but for now, let's focus on that BYOD installation.

Nate: Okay, let's give these devices some friendly names so it's easy to tell them apart as we go along.

First, I'll name my QIO-VEN4 Table Extension, and then my camera Conferencing Camera.

You'll see that a number of default options are available, but I'm gonna go with my own custom monikers here as an expression of my individual style.

Patrick: However, when you have multiple devices of the same model, and you don't remember exactly which port you physically wired each one to, how do you know which one is which?

I can see them here on screen, but do I really need to start tracing those cable paths and cursing my forgetfulness?

Nate: Thankfully, no, uh, because just down here in the bottom right corner, you have an ID switch, and if you've used Q-SYS before, you know where we're going with this.

Just switch that ID button to on, and then the LED light on the device in question will actually flash, allowing you to easily identify it.

Patrick: Confirmed.

LED disco on the front left speaker.

Nate: Perfect.

I'll name this one front left speaker.

Oh, hey, look.

That's actually one of the default options.

Look how easy we're trying to make this for you.

Nice.

All right. Now, I'll repeat the process for the next loudspeaker, et cetera, as well as any of your other peripherals you're unsure about, including the ones connected to the QIO-VEN4.

Let's finish this off by also giving our various video inputs and outputs some friendly names, too.

I have both of the HDMI video outputs of my PC connected to the RMP-100, so let's link these and name the source as Room PC.

If these were two different HDMI sources,

I could leave them unlinked, name each one individually, and even specify which could be treated as the default meeting source.

I'll choose left display and right display as the names for the RMP-100's HDMI outputs.

Sadly, there's no ID button for this, so make sure you remember which is which.

Patrick: But frankly, if you don't plug your left display into port one and your right display into port two, I, I don't think that we can be friends anymore.

Nate: Oh, yeah.

No, you're dead to me, for sure.

Uh, all right.

Finally, we'll name the video inputs from the QIO-VEN4 table input.

With all of those devices, inputs, and outputs now named,

we can hit the Save button in the top right corner and see the fruits of our labors.

The most obvious result of all that naming can be found down here under the Room Controls menu item.

When we select the Touch Panel option here...

Patrick: Whoa.

That's a whole UCI.

Nate: Yeah, and look, I can navigate to the Meet section and choose between the video input on the RMP-100 that I designated as the meeting source Or the table input.

And if I navigate to the present section, I can choose video inputs.

The controls section offers me control of my camera, and I can even turn each of my displays on or off.

Patrick: For those of you that have designed Q-SYS system using Q-SYS Designer Software, it should be incredibly apparent how much time you just saved here.

Nate: Yeah.

Now, don't get us wrong, we all know that building a system using Q-SYS Designer Software can be easy, but it is intended for systems that might need a large degree of customization and third-party device integration.

Patrick: On the other hand, Q-SYS RoomSuite is for standardized, mass deployable rooms with not a lot of nuance in them.

So as you can see, all of the things like adding devices to the inventory and components that need to be wired and creating UCI's, all of that happens in a blink of an eye with minimal effort.

Nate: And at this point, we actually have a fully functional system.

This all works-

Patrick: Yeah

Nate: right now.

The cake is done.

All that's left is the icing.

Patrick: In the next video, it's icing time.

We'll talk about customizing your UCI and the overall experience.

We'll see you then.