PTZ system guide
Planning a complete PTZ camera setup
Ask GLMedia about a PTZ system for conferences and events: camera, control, power, signal path, and operation for your required shots.
Plan the system as well as the camera
With the date, location, and intended use, we can review which equipment and combination can be offered. You can inquire before measurements, drawings, or the final schedule are ready.
A PTZ plan needs more than a camera. It must connect the required shot to a destination, allow the intended control, provide compatible power, and support the camera in a suitable position.
We can compare configurations from the room layout and desired coverage before every model is settled. Tell us whether you need a lectern shot, stage movement, a panel, or remote participation.
Picture, control, and power
- Picture
- Identify camera output, format, transport, switcher, and destination. Confirm simultaneous output conditions on the exact model.
- Control
- Match camera and controller protocols and versions. Network discovery or a moving camera does not verify the video path.
- Power
- Check the exact supply or PoE requirement, compatible equipment, and the complete power plan. A network connector alone does not establish power compatibility.
What to share
Share room photos or a sketch, stage dimensions, speaker movement, and intended camera positions. We can compare coverage before a final plan is ready.
Tell us the production format and destinations: screens, stream, recording, or conferencing. Include audio and any return or tally needed by the operators.
List equipment already available, cable paths, control location, and setup time. We can identify what is required and which functions remain optional.
If the event feeds screens, streaming, and recording, identify all three destinations and what each should receive. A simple diagram helps separate program video, returns, and signals to retain.
Preparing the comparison
- Define shots and operator tasks before choosing positions. Review sightlines and obstructions with representative speaker movement.
- Identify exact camera, controller, firmware, supply, and support. Confirm mounting with the system documentation and qualified personnel.
- Prepare the signal and control paths separately. Check selected output format and the destination’s supported input.
- Test camera movement and picture independently. For Canon CR-N300, selecting UHD HDMI disables SDI output; do not assume all ports remain active in every mode.
- Rehearse framing, focus, exposure, white balance, and presets under planned lighting. Check what happens when the presenter moves away from the lectern.
- Review the complete production path, audio, recording, and source changes. Preserve working settings and agree who monitors each part.
- Prepare a shot list with the speaker stationary, walking, and in front of the screen. Rehearse on-air transitions and agree on recovering a useful shot if automation loses the subject.
- Keep a diagram of each camera’s output and format, destination input, and control path. When comparing proposals, distinguish included functions from those requiring additional software, accessories, or personnel.
Technical questions and show decisions
The controller moves the camera, so why is there no picture?
Trace the video route independently: camera output, format, cable or transport, selected input, and destination. Control confirms only part of the setup.
Compare a known supported direct video path, then add intermediate stages one at a time outside the live program. Record where the result changes.
Will any PoE switch power any PTZ camera?
Confirm the camera’s documented standard and required supply together with the switch or injector and available power budget. Do not select by connector alone.
Send model labels and the proposed topology. We can review the documented combination before planning cable routing and operation.
Can presets or tracking replace an operator?
Define the required shots and movements, then check which functions the exact model, software, and version support. A feature name does not establish successful coverage.
Rehearse representative movement and a manual recovery method. We can compare an operated plan with supported automation based on the observed results.
Should the show use PTZ, locally operated cameras, or a combination?
Start with required shots: lectern, panel, speaker movement, performance, or details. Compare positions, obstacles, light, framing, and changes during the program. PTZ allows remote framing, but placement and movement range must cover the scene; presets or tracking alone do not establish that every required shot is covered.
We can prepare PTZ, locally operated camera, or combined options, defining who controls each shot and how it reaches production. The proposal considers camera, control, power, mounting, and the path to screens, streaming, or recording. Photos and approximate movement let us start; representative content and changes are rehearsed before confirming configuration.
Checks to guide decisions
| Symptom | Check | What it helps distinguish |
|---|---|---|
| Control works, no picture | Output format and video route. | Control versus image path. |
| Camera unavailable | Documented power and connections. | Supply or communication. |
| Preset misses the shot | Position, scene, and recalled settings. | Framing and operation. |
| Image changes during movement | Focus, exposure, and scene. | Settings requiring a rehearsal. |
Installation and limits
Use the exact camera and support documentation for mounting and power. Keep equipment and cables clear of movement and access routes.
Preserve working configurations. Do not reset or update firmware as a generic first step for a routing problem.
Test optional protocols, tracking, tally, and returns only in the documented combination. Record any function that still needs verification before the event.
Sources and context
- Canon: CR-N300 specifications and output conditions
- Canon: documented settings guide, model and version specific
- Panasonic: original AW-UE150 specifications
Research reused from records consulted October 22, 2026. Model examples illustrate compatibility checks; they do not identify the event equipment or transfer functions to other PTZ cameras.
Help us improve this guide
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.