Lumens VC-A61P, VC-A71P, and PN model SRT boundaries
More live video workflow notes and product updates.
PTZ suffix and transport decision hub
A final letter changes this workflow. Lumens manuals distinguish VC-A61P from VC-A61PN and VC-A71P from VC-A71PN, and the documented feature tables mark SRT unavailable for the PN variants covered there. A shared setup that ignores the suffix can send an operator searching for controls the camera does not expose.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct Lumens VC-A61P, VC-A71P, and PN model SRT boundaries
| Path | Operational role | When to choose it |
|---|---|---|
| VC-A61P | 4K PTZ camera with documented SRT configuration on the P variant. | Choose when the exact label is A61P and the firmware exposes the manual’s multicast and SRT fields. |
| VC-A71P | 4K PTZ camera path with documented SRT settings on the P variant. | Choose when the exact label is A71P and the intended codec and output profile are supported. |
| VC-A71PN or A61PN | NDI-oriented suffix whose referenced manuals mark the direct SRT setting unavailable. | Choose a corrected bridge design; do not present the P-model web menu as a native PN feature. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
Lumens owns PTZ acquisition, camera audio, image profiles, encoding, NDI capability where licensed and every model-specific network control in the camera web interface.
Transport handoff
For a supported P model the handoff records codec, raster, bitrate, multicast state, SRT destination, port and delay. For PN, the handoff must name the external bridge that performs conversion.
Callaba responsibility
Callaba owns the reachable receiver, live statistics, Multiview, recording, routing and playback after a supported SRT camera output or an explicit bridge reaches it.
Prevent P and PN configuration drift before an event
- 1. Photograph the full product label and record the firmware revision. Treat P and PN as separate products even when their chassis, lens and basic camera menus look similar.
- 2. Open the official manual for that suffix and confirm the feature table. If it marks SRT unsupported, stop the direct-camera plan and select an external NDI or baseband bridge.
- 3. For a supported P model, configure the documented stream profile, multicast prerequisite, destination, port and delay. Avoid ports reserved by the camera as listed in its manual.
- 4. Create the matching Callaba receiving endpoint and verify firewall direction. Store security values outside public screenshots and do not reuse a production Stream ID in editorial examples.
- 5. Test PTZ response, video, audio and full-scene network load, then verify Callaba telemetry, recording and the downstream route. Keep the suffix visible in every runbook heading.
After preflight, use the SRT Gateway hub for architecture choices, the SRT Server guide for receiver concepts, Multiview for browser operations, and the SRT API documentation for automation. These shared resources do not replace the model-specific guide linked in the decision table.
Official references reviewed
Capabilities and menu fields can change with hardware revisions, firmware and account entitlements. Recheck the exact model before a production event.
- Lumens VC-A61P/A61PN English manual — Official model feature matrix, multicast prerequisite and SRT settings.
- Lumens VC-A71P/A71PN manual — Official P-versus-PN SRT support boundary and port guidance.
- Lumens VC-A61P downloads — Official location for current installation material and revisions.
Frequently asked questions
Does the Lumens VC-A61PN support the same SRT setup as VC-A61P?
No assumption is safe. The current A61P/A61PN manual marks the referenced SRT setting available for the P path and unavailable for PN. Use an external bridge for PN unless newer exact-model documentation says otherwise.
Does VC-A71PN expose the VC-A71P SRT menu?
The referenced A71P/A71PN manual marks SRT unsupported for the PN variant. Do not copy screenshots or ports from A71P. Confirm the suffix and design an explicit bridge when the source is PN.
Why does the model suffix matter so much?
The suffix changes network transport capability, not merely color or region. A procedure that omits it can be technically plausible yet impossible to execute on the installed camera.
Can a Lumens NDI camera still reach Callaba?
Yes, through a clearly owned NDI-to-SRT or other compatible bridge when direct SRT is not documented. Test discovery, conversion, codec, audio and the receiving path as separate boundaries.
What should the Callaba acceptance test include?
Verify the exact camera identity, stable video and audio, PTZ operation under load, receiver statistics, a short recording and the final route. For bridged PN workflows, monitor both the NDI side and the converted transport.
Move from device choice to a tested receiving path
Open the exact-model guide, validate one contribution feed in Callaba, then add recording, monitoring and downstream routes only after the ingest contract is stable.
