Room
Touch panels
Displays
Sources on the Present card(s)
Ticking a source in a DM-NVX room adds an encoder carrying it under Video routing; unticking removes that encoder. Encoders can still be added, renamed or removed there by hand.Video routing
Encoders one source each - an NVX-363 has one HDMI input
Decoders one per display, then the codec / MediaSite ones - numbered after the encoders
A box with its MAC typed under Device setup gets a navy edge and the MAC under it; green once the scan has seen it on the network.
USB / keyboard-mouse over NVX
Direct wiring: pick the input each source lands on, per display, in the Displays list above.
Conferencing & pages
Compact single-display layout:
Video Conf. page:
Needs DM-NVX switching (Video routing above). With direct wiring the Share button is panel-local.
Needs DM-NVX switching (Video routing above).
MediaSite In 2 rows:
plus every source on the Present card
The In 2 rows route to it; Follow Display tracks the first Present card.
Needs DM-NVX switching (Video routing above). With direct wiring the In 2 rows are panel-local.
Needs DM-NVX switching (Video routing above).
Audio / DSP
Blocks in the Tesira design instance tag, then the channel - like the Crestron modules: "Level1" is channel 1, "Level1 2" is channel 2
Named controls in the Q-SYS design
TP_ default for that control · - = the program does not drive it.
Ceiling / table array mics
Cameras
USB cameras (Huddly, Logitech) are not controlled — no camera card on the panel. Q-SYS-controlled PTZ cameras get D-pad, zoom and presets throughTP_CamN… named controls. A camera whose video is on an NVX encoder gets that encoder added automatically (ENC-C1 …); selecting the camera streams it to the MediaSite In 1 / codec camera decoders set under Conferencing & pages.
Wireless mics (Mic Levels page)
Naming per the style guide: HH first, then LAV, numbered in sequence, Lectern last. Q-SYS names default toMic-N / Mic-N-Mute.
Power behaviour
Network & deploy
Site naming & addresses
CP-<site>-<room> .1 (CP4N), -TP .3, -IO1… .10 up (NVX, encoders first), DISP-… .80 up (displays), AUD-…-DSP .100, AUD-…-MICn .110 up. A blank field means that default is used; type over it to change one box. The IP table button on the right shows the result in the site's spreadsheet columns.
Device setup optional
How to use this page
- Set the room up first, but do not deploy it yet. Fill in the Room page (boxes, IP-IDs, the CP4N and panel addresses under Network & deploy) and press Create room folder (for a room that already has a folder the same button reads Save changes). The rows below come from that. Deploying comes after the boxes are configured.
- Be on the same network as the boxes. Plug this PC into the same switch or VLAN as the equipment, on the bench or in the rack. Finding boxes is a broadcast, so it does not cross a VPN or another subnet. Factory-fresh boxes on DHCP are fine; they are found by MAC, not by address.
- Type each box's MAC address from the label on the box. The dot next to it turns green as soon as a scan sees it (the page scans every 30 s; Scan network scans now).
- Say where each box should live: the subnet mask and gateway, an address per NVX box (the CP4N and panel take theirs from Network & deploy), and the login every box should have. Tick Use device setup for this room.
- Check devices is a dry run: it finds every box and lists what it would do, and sends no login, so it is safe to run as often as you like.
- Configure devices does the work, one box at a time: login (created on a factory-fresh box), hostname, IP table entry to the CP4N, clock from this PC, keyboard off on panels, then the static address and a reboot. The CP4N always goes last:
userpageauth, its LAN address from the site IT team and its control subnet, then its reboot, which takes the room network down for a minute. It does not wait for reboots; a rebooted box is checked at the end only when its new address is on a subnet this PC is on, otherwise the run just finishes. Run Check devices again afterwards and the dots go green at the new addresses. - Now deploy the room from the Room page (Create + build + deploy). The program sets each NVX box's mode and multicast address the first time it boots with it.
If a box refuses the login it is never retried, and two refusals in a row stop the run: a Crestron box blocks this PC for 24 hours after three bad logins. A box that never answers is usually on the wrong switch port or VLAN, or not powered. Passwords typed here go to that one run unless you tick save.
Network
CP4N network configured last
Login every box should have
Existing login (boxes set up before)
crestron, no password) and its create-account prompt is answered with the login above. The new login is then proved with a fresh session; an NVX drops SSH for a moment while it turns authentication on, and that wait is not counted as a refused login. Each box gets at most two login attempts (the login above, then the factory one), one short of the 24 h block. Passwords not saved are passed to that one run only.
Boxes in this room
Rows come from the Room page: the CP4N, the touch panel and every NVX box. CP4N and panel addresses are the ones under Network & deploy. Hostnames and NVX addresses default to the site's scheme (CP-<site>-<room>-IOn, .10 up - set under Network & deploy on the Room page); blank = that default. The dot next to each box: seen on the network (its current address is shown), not seen in the last scan, no MAC yet or not scanned. Scans send no login; the scan runs in the background every 15 s from the moment the builder opens.
Panel preview what the touch panel shows for this room
A demo panel driven by the same join map the program uses: it shows the pages, display cards, source rows, cameras and mic strips this room's config leaves visible, with the startup source selected. Change anything on the Room page (display layout, sources, cameras, mics, conferencing) and it updates here.