Epiphan Pearl-2, Pearl Mini, and Pearl Nano SRT workflows
More live video workflow notes and product updates.
Production appliance decision hub
Pearl-2, Pearl Mini and Pearl Nano all support SRT, but they are not interchangeable sizes of one workflow. Pearl-2 is the higher-capacity production system, Mini is a compact multi-input switcher and recorder, and Nano targets a smaller single-channel contribution role. Choose from input count, layouts, recording and output needs before copying SRT fields.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct Epiphan Pearl-2, Pearl Mini, and Pearl Nano SRT workflows
| Path | Operational role | When to choose it |
|---|---|---|
| Pearl-2 | Higher-capacity production, switching, recording and SRT input/output workflows. | Choose when 4K, broader I/O, multiple layouts or more production headroom are required. |
| Pearl Mini | Compact multi-input HD production with local switching, recording and SRT output. | Choose for classrooms, events or studios that need several local sources without Pearl-2 scale. |
| Pearl Nano | Compact single-channel encoding, recording and SRT contribution or one network input. | Choose for a simpler remote feed and keep its source and stream limits in the design. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
Epiphan owns source capture, local layouts, hardware or software encoding, appliance recording, SRT input/output configuration and its local or cloud management surface.
Transport handoff
The handoff records model, firmware, active inputs, channel profile, codec, SRT mode, URL, source port, Stream ID, encryption, latency and available appliance capacity.
Callaba responsibility
Callaba owns the matching peer, receiver-side transport evidence, Multiview, cloud recording, routing, playback and automation after the Pearl output arrives.
Size the Pearl appliance before configuring SRT
- 1. List every local and network input, layout, encoded channel, recording and output. Select Nano, Mini or Pearl-2 from that workload rather than from the protocol checkbox alone.
- 2. Confirm firmware and whether the Pearl acts as SRT source or destination. Caller, listener and rendezvous must be paired with the opposite or matching mode described in the model guide.
- 3. Create the matching Callaba peer and align URL, port, Stream ID, latency and encryption. Check every firewall on the actual traffic path and keep security values out of public notes.
- 4. Run all intended layouts and recordings while streaming. Watch Pearl resource use because adding digital inputs, channels and processing can change stable capacity.
- 5. Verify Callaba video, audio and transport statistics, make a separate cloud recording and exercise the final route. A healthy Pearl preview is not proof of receiver or destination health.
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.
- Epiphan Pearl SRT support overview — Official family-level SRT support for Pearl-2, Mini and Nano.
- Pearl-2 SRT input guide — Official mode pairing, URL, port and Stream ID behavior.
- Pearl Mini product and specifications — Official compact production role, I/O, SRT and recording capabilities.
- Pearl Nano SRT guide — Official source, decoder and stream-capacity notes for Nano.
Frequently asked questions
Do Pearl-2, Pearl Mini and Pearl Nano all support SRT?
Epiphan documents SRT across all three. Their capacity, input mix and production role differ, so family support does not justify copying one model’s workload or menu limits onto another.
Which Pearl model is best for a single remote feed?
Pearl Nano is the compact single-channel starting point. Choose Mini or Pearl-2 when local source count, layouts, recording, 4K or simultaneous channel requirements exceed the Nano design.
Can a Pearl appliance receive and send SRT?
Supported Pearl workflows include SRT source and destination roles. Confirm the exact model’s input capacity and pair caller, listener or rendezvous correctly with the other endpoint.
Does Callaba replace Pearl recording?
No. The appliance can keep a local recording while Callaba records the received feed when independent copies are operationally justified. Validate and retain each artifact separately.
Why test resource use during the full layout?
Local inputs, network sources, layouts, encoding and recording share appliance capacity. A simple preview can pass while the complete production load is unstable, so preflight the exact show configuration.
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.
