A divisible ballroom works best when AV routing, audio zoning, and lighting scenes all reference a single combined/split room state, rather than requiring staff to reconfigure each system separately. The underlying architecture — one system per sub-room that can also recombine into one — comes from how Crestron documents divisible-space design for its Automate VX conferencing platform, and the same principle of independent-sections-that-recombine applies to how a ballroom's AV, camera, and lighting infrastructure should be planned. Getting the per-section hardware count and network topology right is a decision for the design phase, before walls close, not something to work out the week of an event.
How does a divisible room's AV architecture handle open and closed configurations?
Crestron's own documentation on divisible spaces describes exactly this two-state problem: a very large room that sections off into two or more rooms, often with folding walls or sliding doors, where "one Automate VX system should be used for each room within the divisible space" (Room Design | IV-SAM-VX and IV-SAM-VX2 Series Manual). Each half of the space needs enough of its own cameras and microphones to function as a standalone room, and the hardware and network architecture then needs a separate mechanism to recombine when the wall is collapsed. For a ballroom or banquet hall, the equivalent design question for your AV contractor is how partition state gets communicated to the AV system at all — whether that's a sensor on the track, a staff panel press, or some other trigger — since Crestron's documentation describes the resulting system architecture rather than prescribing how state detection itself should work.
How do microphone and camera coverage combine when sections open into one room?
Crestron's worked divisible-room example splits a space into two functionally similar halves, each built around a presentation area, and recommends four intelligent ceiling array microphones total — two placed in each half — so that both the seating and presentation areas in each section are properly covered on their own (Room Design Examples | IV-SAM-VX and IV-SAM-VX2 Series Manual). For cameras, the same example recommends Crestron NDI-enabled cameras specifically because they can connect to multiple Automate VX systems independently, and then "when the spaces are combined into a single room, the cameras can be connected to a single Automate VX2 Pro system." One of the two Automate VX2 Pro systems in the example is designated to operate as the primary system once the halves are joined. The two network switches serving each half are also connected to each other, which the documentation says "provides the ability to combine the microphones and cameras of each room when the divisible wall is collapsed." The practical takeaway for a banquet space: whatever platform handles video conferencing or speaker tracking needs enough independent hardware per section to run alone, plus a network link between sections that lets that hardware recombine without a re-cable.
How should video routing and displays change between split and combined configurations?
Crestron's example assigns one of the two per-section systems to act as the primary once the sections are joined, rather than re-patching hardware by hand. For a ballroom's display and source routing more broadly — including whether a presentation, event signage, or shared feed needs to reach every screen across a combined space — the right topology depends on how many sub-rooms the ballroom divides into and how many displays each one serves. That's a specific design question to put to your AV contractor, since Crestron's divisible-room documentation addresses its Automate VX conferencing architecture and does not detail video-distribution matrix sizing for ballroom AV.
How should lighting and shading follow the room's physical layout?
Lighting and shading should ideally track the same combined/split distinction the AV system uses, so that a single scene recall changes shade position and lighting together rather than needing separate adjustments per sub-room. Cave Group designs guest-facing and event-space lighting on Lutron as part of its hospitality integration work; ask your lighting programmer how your property's scene list should map to the room's physical configurations. For general guidance on hospitality lighting, AV, and PMS-driven systems, see Cave Group's hospitality page.
What should banquet staff be able to change without a technician?
Crestron's divisible-room guidance treats the split and combined configurations as two defined operating states for the AV and conferencing hardware, each with its own set of independently functioning equipment. Translating that into a small, clearly labeled set of staff-facing presets — rather than a raw matrix of inputs and outputs — is a sensible design goal to raise with your integrator, matched to however your property signals a configuration change.
What should architects and AV planners lock before rough-in?
Before walls close, Crestron's divisible-space example points to several things worth locking in the drawing set: microphone and camera placement sized so each sub-room performs as a standalone space; a network switch topology that links each section's gear so hardware can recombine without re-cabling; and camera selection (NDI-enabled, per Crestron's recommendation) if cameras need to serve both split and combined configurations. A standardized architectural symbol set helps keep a multi-section ballroom drawing set consistent — AVIXA publishes a free standard with floor-plan and reflected-ceiling-plan symbols for audio, video, and control systems, including associated environmental and network elements (AV & Control Architectural Drawing Symbols | AVIXA). Floor box placement, input plate locations, and how partition state itself gets detected or triggered are property-specific decisions to confirm directly with your AV contractor before rough-in.
Frequently asked questions
Does the partition wall need a sensor to trigger the system?
Crestron's divisible-room documentation describes the resulting AV architecture — independent per-section systems that recombine — but does not specify how partition state should be detected. Ask your integrator whether a sensor, a staff panel trigger, or another method fits the hardware being proposed.
How many microphones does each ballroom section need?
It depends on the room, but Crestron's own divisible-room example uses four intelligent ceiling array microphones split evenly across two sections, two per half, sized so each half can function as a standalone space.
Can the same cameras serve both split and combined configurations?
Yes, if they're NDI-enabled. Crestron's documentation recommends NDI cameras for divisible spaces specifically because they can connect to multiple Automate VX systems and be reassigned to a single combined system when the dividing wall collapses.
Should the network linking each section be planned before rough-in?
Yes. In Crestron's divisible-room example, the network switches serving each section are connected to each other specifically so microphones and cameras can be combined when the wall collapses — a topology decision that belongs in the design phase, not after construction.
Where should lighting scene logic for a divisible ballroom be decided?
Lighting scenes should ideally be mapped to the same combined/split states the AV system tracks, worked out during design with your lighting programmer before rough-in; Cave Group designs guest-facing and event-space lighting on Lutron as part of its hospitality services.