Room control · Practical guide
Room control: survey, modes, and handover
Presenting from the table, hearing an audience question or preparing the room for the next meeting should be recognizable tasks. Compare room uses, available equipment and control options before selecting a platform.
Survey the room before choosing controls
Start with one task: “I want to present from the table without using three different remotes.” Note who performs it, how the room changes during the day, and what must remain available if the interface fails. An overview photo or simple sketch can start the conversation; the final design can follow.
Keep observations separate from open questions. A network connector does not establish IP control, and an installed app does not establish an integration license. Options include keeping separate remotes, adding a panel, or reviewing an existing controller against documented interfaces.
- List each device’s brand, exact model, known firmware, and role; mark missing information as “to be confirmed.”
- Describe sources and destinations: table laptop → main display; microphone → room speakers. Leave out private addresses and passwords.
- Use authorized photos of labels and accessible connections, without people, sensitive screens, or opening enclosures.
Meeting room: present, discuss, and finish
Consider three recognizable modes. Present can select the agreed source and retain enough light for notes; Discuss can remove the displayed image while leaving an active call alone; Finish can request the intended AV shutdown. Every action depends on the installed equipment and supported controls.
Write intention and confirmation separately: “display off requested” and “display reports off” are different states. Without documented feedback, confirmation is visual. Ending a presentation also does not necessarily end a video call or remove content from the computer.
- Define the display, source, audio, and lighting zones affected by each mode.
- Agree who confirms Finish and what happens when a meeting runs late.
- Keep the intended local control available; if a display responds slowly, avoid repeating the whole scene.
Paper review example: a meeting runs late and the laptop changes. What stays active, and what must the user select again?
Auditorium: room modes and attended operation
Talk, Projection, and Q&A describe room use, rather than a show cue list. For Talk, describe speech and presenter visibility; for Projection, the source and screen readability; for Q&A, who enables the audience microphone. Agree specific mixes and levels with the audio lead.
The room can retain a stable mode while an operator makes individual changes. If clips, music, or lights must follow a script, prepare a coordination document for show control and identify who authorizes the start. Do not assume the room panel knows the program position.
- Define which controls stay with the operator and which changes room users may make.
- Record the handover state: source, visible image, intended microphones, and affected zone.
- Plan a return to a simple talk without indiscriminately restoring every parameter.
Proposed acceptance criterion: switching from Projection to Q&A preserves the presenter’s speech and changes only the agreed destinations.
Divisible room: confirm zones before sharing signals
Draw a use matrix: independent A and B, combined A+B, and an overflow room receiving program only if needed. For each arrangement, identify which microphones reach which speakers, what source each display shows, and which panel has authority. Verify partition position and AV combination separately.
An audio room-combining component does not establish the physical wall position or automatically coordinate every display. If a sensor reports the division, document its meaning and the response to an unknown state. The AV proposal does not operate or modify partitions.
- Show zone names instead of an unexplained “all.”
- Request the existing logic and shared destinations before proposing changes.
- Keep meetings separate when the permitted room combination is unconfirmed.
Proposed review: with A independent, selecting a source in B should not change A’s image or audio; recording that result requires a later authorized test.
Hotel: hand the room to the next operator
A useful handover starts with the booked use, enabled zone, and current mode, rather than a password list. Prepare a short sheet for front desk, room staff, and the AV operator: how to recognize the selected source, where to adjust the permitted level, and whom to call if the state does not match.
Agree a known state for the next handover, such as a source without guest content and microphones matching the intended setup. Avoid calling it a factory reset: it must preserve the approved configuration. The designated person confirms that activity has ended, even when the booking has expired.
- Include a conceptual panel view or description and the changes permitted during daily use.
- Identify what carries between shifts and what session data must be removed under the hotel’s procedure.
- Provide a documented manual path and support contact without exposing administrator access.
Handover question: can someone who did not program the system identify the room, mode, and next step without guessing?
Reference documentation
These references support the stated functions; application depends on the actual model, version, and configuration.
- Q-SYS 9.13.2 — User Control Interface (UCI) Design Overview — Interfaces with controls and indicators; licensing depends on the Core.
- Q-SYS 9.13.2 — Snapshots — Saving and recalling selected control settings.
- Q-SYS 9.13.2 — Room Combiner — Audio combination across rooms; it does not verify the physical partition.