PTZ ComposerComposed presenter moves, and a frame that stays put.
Compose the moves a meeting room actually needs, and the people on the call get camerawork somebody decided on instead of a frame that keeps adjusting itself. A flight is an authored camera move, with a planned route, framing and pace from departure through landing.
A boardroom or a mid-size hybrid room with a table, a screen and a presenting position, and PTZ cameras already installed. A Teams or Zoom room system carries the call, and an AV or IT team owns this room and eleven more like it.
Three moments
A move from the table to the presenting position.
When somebody gets up to present, one press in the app or on a VISCA panel sends the frame from the table to the presenting position, where it settles. The route and the pace were composed for this room, so the people on the call see a deliberate change of shot rather than a scramble.
Stillness for as long as it takes.
A speaking person gets a frame that holds. Nothing creeps, nothing re-centers, nothing hunts for a better composition halfway through a sentence. The remote half of the room is looking at a shot, and it stays a shot.
A transition to the wide, and back.
When the discussion opens up, one press takes the coverage to the room framing your team composed. Another brings it back to the presenter. The same two moves work in every meeting this room hosts.
Who owns it
The AV or IT team owns this, and a meeting room is not a production. One person composes the room's moves once: the presenting position, the table, the screen side and the room wide. Compose one room properly and use its shot list as the pattern for the rooms built to the same drawing. Each room is composed on its own cameras, which is an afternoon rather than a design project. In the meeting itself nobody rides a camera. The host, or whoever chairs, presses a cue when the room wants a change of shot, and the frame holds otherwise. Your meeting platform carries the call exactly as it does today: the software drives the cameras and makes no claim on Teams, on Zoom or on the room system that runs them.
Compose the room once
Frame the presenting position, the table, the screen side and the room wide, then draw the routes between them. This is one session with the person who knows how the room is actually used.
Rehearse with real people in the seats
Run the moves during a working meeting and adjust the pace and the landings until the coverage reads as calm. A move that feels brisk in an empty room feels abrupt to somebody on a call.
Arrange the meeting's order
Put the prepared shots in a rundown in the order a meeting uses them, keep each flight one press away, then use that rundown as the pattern for the other rooms on your floor.
Perform it in the room
The meeting runs on the prepared coverage. The presenter presents, and the frame holds while people speak. The host cues a flight, from the app or from the joystick or the wheel on the controller they already use, when the room wants that control rather than leaving it alone.
Fits your room
Each row carries the state it is actually in today. Choose one to read what it does and what it does not do yet.
Cameras in this segment
- AVer
- Avonic
- BZBGEAR
- Cisco / Poly
- HuddleCamHD
- Lumens
- Minrray
- OBSBOT
- Panasonic
- PTZOptics
- QSC
- Sony
- Tenveo
- Vaddio (Legrand AV)
Manufacturer and product names belong to their owners. A name here describes what the software talks to, and states no endorsement or partnership.
Two answers, and we always say which one applies to you. Tested means a named model, firmware and control path we have flown; supported protocol means the camera speaks a control path we read, and the software measures it and tells you honestly whether it can fly it.
Proof
Film of real flights appears here when a Tested model has one on tape. Until then, here is what the software is doing for the shot.
Shape the whole moving shot.
Perform the move with the moment.
Motion planned around your camera.
Questions
Does this control Teams or Zoom?
No. Your meeting platform carries the call, the layout and the recording the way it does today. The software drives the cameras in the room and makes no promise about what the platform does with the picture it receives.
Our room already reframes by itself. What does this change?
It gives the room composed moves and a frame that stays still while somebody is speaking, because a person decided where each shot starts, where it lands and how fast it travels. We describe what our software does with the cameras it drives, and we make no claim about another vendor's framing behavior.
Who sets it up, and who runs it day to day?
Your AV or IT team sets it up in one session per room. Day to day nobody rides a camera. The host, or whoever chairs, can cue a prepared flight when the room wants a change of shot, and otherwise the frame holds.
We have twelve rooms. Do we compose all twelve?
Compose one room properly and use its shot list as the pattern for the rooms built to the same drawing. Each room is composed on its own cameras, which is an afternoon rather than a design project.
Our rooms have the camera that came with the room system. Will it work?
Tell us the make and model. Tested means a model and control path we have flown ourselves. Supported protocol means the camera speaks a control protocol we read, and we measure it and say plainly what it can do. A camera we cannot control is told to you before anything is bought.
What does IT have to approve?
It runs on a Mac or Windows computer on the camera control network and talks to the cameras over that network. Your program video never passes through it: the camera picture reaches your room system by the path it uses now. What the software itself stores and sends is described in its documentation, and we answer IT questionnaires at the setup check.
How is it licensed across a building, and can we try it in one room first?
Licensing is sold as a block of up to four cameras, and a block spans rooms and sites, so a floor of two-camera rooms is counted in blocks rather than room by room. The evaluation runs fourteen days from the day your setup is confirmed and no card is needed to start it. Pick a room with a real weekly meeting in it, then buy through your integrator or distributor when the team has seen it work.
Buying
Each plan covers a block of up to four cameras. A fifth camera needs a second block on the same plan. Blocks can span rooms and sites.
Put it through a real rehearsal and a real production first. Your evaluation runs fourteen days from the day your setup is confirmed. No card is needed to start.
Buy through a partner
Integrators, distributors and rental houses can sell and install this in your segment. Tell us your segment and region and we introduce one who works in your kind of room.
Take this to your AV and IT owners
- Three moves carry a hybrid meeting: a move to the presenting position, stillness while somebody speaks, and a transition to the room wide and back.
- Your AV or IT team owns it. One session composes a room, and nobody rides a camera during the meeting itself.
- One room's shot list is the pattern for the rooms built to the same drawing, so a floor of hybrid rooms behaves the same way.
- Your meeting platform carries the call as it does today. The software drives the cameras and makes no claim on Teams, on Zoom or on the room system.
- Runs on macOS and Windows. One license covers either.
- Licensing is sold as a block of up to four cameras, and a block spans rooms and sites, so a floor is counted in blocks rather than room by room.
- The evaluation runs fourteen days from the day your setup is confirmed, and no card is needed to start it.
- Buy through your integrator or distributor, on your usual purchase order.