Sony camera SRT setup hub: BRC-X400, FR7, and PXW-Z280
More live video workflow notes and product updates.
Camera-model selection hub
BRC-X400, FR7 and PXW-Z280 belong to different production roles. A PTZ camera in a fixed venue, a cinema-line PTZ system and a field camcorder should not share one copied setup narrative. Choose the model first, then use its own firmware and streaming controls.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct BRC-X400, FR7, and PXW-Z280
| Path | Operational role | When to choose it |
|---|---|---|
| BRC-X400 | Remote PTZ contribution for studios, venues, education and houses of worship. | Use the BRC guide for firmware prerequisites, camera web controls and PTZ-oriented preflight. |
| FR7 | Cinema-style PTZ production with documented caller and listener streaming modes. | Use the FR7 guide for stream profiles, role selection and model-specific limitations. |
| PXW-Z280 | Field camcorder contribution with firmware and RTMPS fallback checks. | Use the Z280 guide for mobile production settings; do not copy FR7 menu locations. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
The Sony camera owns acquisition, image profile, camera audio, hardware encoding and model-specific streaming controls.
Transport handoff
The handoff contract includes firmware, codec, resolution, frame rate, bitrate, SRT role, port, latency, Stream ID and encryption support.
Callaba responsibility
Callaba owns the receiving endpoint, live statistics, shared browser monitoring, recording, routing, playback and downstream automation.
Route settings questions to the exact Sony model
- 1. Confirm the full model name and installed firmware before opening a setup guide. Sony menu names and enabled transports differ across these cameras.
- 2. Choose the model guide and configure its documented stream profile. BRC-X400 SRT support requires the appropriate firmware; FR7 has explicit caller/listener controls.
- 3. Create the matching Callaba endpoint and align the connection role, UDP port and security fields. Never reuse a live Stream ID in public screenshots.
- 4. Test the intended resolution, frame rate, codec and camera audio. A picture in a browser does not prove that production audio or every output profile is correct.
- 5. Exercise PTZ operation or field movement while monitoring packet loss, recovery and bitrate. Preserve the final model-specific values in the event runbook.
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.
- Sony BRC-X400 SRT technical guide — Official BRC-X400 SRT procedures and firmware context.
- Sony FR7 streaming settings — Official caller/listener, codec and stream-setting controls.
- Sony FR7 start and stop guide — Official operational difference between caller and listener modes.
Frequently asked questions
Which guide should I use for PTZ, cinema production or field contribution?
Use BRC-X400 for a fixed PTZ workflow, FR7 for cinema-style PTZ production, and PXW-Z280 for a field-camcorder path. The role determines the guide; similar Sony branding does not make the menus interchangeable.
Where are the SRT caller settings on each camera?
Open the exact model guide. FR7 documents caller and listener settings in its Stream menu, while BRC-X400 and PXW-Z280 use their own firmware-dependent web or network controls.
Do all three models expose the same security fields?
No. Stream ID, passphrase, encryption and certificate-related controls vary by model and firmware. Use the official manual for the installed version and test the exact values against Callaba.
What bitrate and latency should I start with?
Start from the official model profile and a value supported by the complete network and decoder path. Measure packet loss, RTT and glass-to-glass delay; do not copy one universal number across venue PTZ and mobile field workflows.
How do I verify video and audio after arrival?
Use Callaba preview and transport statistics, listen to every required audio channel, make a short recording, inspect the file and test the real downstream route. Connection state by itself is insufficient.
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.
