Epiphan Pearl-2, Pearl Mini, and Pearl Nano SRT workflows
More live video workflow notes and product updates.
Epiphan Pearl production boundary
Prove the program inside Pearl, then prove what Callaba actually received
Pearl-2, Pearl Mini and Pearl Nano combine capture, encoding, streaming and recording in different capacity envelopes. Epiphan documents SRT across the family, including source and destination workflows, but that does not make the appliances interchangeable.
Select the Pearl from the complete production workload. Then keep two independent acceptance views: the local Pearl program and the remote Callaba result.
Choose the Pearl from sources, layouts and simultaneous jobs
Pearl-2
Start here when broader I/O, multiple sources, layouts, encoded channels and simultaneous recording or streaming need more headroom. Test the intended workload rather than quoting a family maximum.
Pearl-2 SRT guidePearl Mini
Use Mini when a classroom, event or studio needs several local sources, switching and recording without the Pearl-2 envelope. Include every intended channel and recording in capacity rehearsal.
Pearl Mini SRT guidePearl Nano
Use Nano for a smaller single-program role whose input, encoding, recording and network requirements fit the unit. Do not copy Pearl-2 limits or screens.
Pearl Nano SRT guideWatch the two proofs side by side
Proof A: Pearl local program
Confirm source lock, layout, graphics, motion, complete audio, encode profile and the intended appliance recording. This proves what Pearl is trying to send.
Proof B: Callaba remote result
Confirm the SRT session, sustained bitrate, RTT, packet loss, decoded picture, audio, sync and a separate recording. This proves what crossed the network.
If the Pearl program is correct while Callaba fails, keep the investigation on transport and receive-side settings. If both are wrong, return to the source, layout or encoding job. This simple separation prevents teams from reopening every part of the system at once.
Pair the SRT modes deliberately
Caller + Listener
One peer initiates and the other accepts. For a Pearl sending from a private venue network, Pearl as Caller toward a public Callaba Listener is often the cleanest first test.
Listener + Caller
Use the reverse only when Callaba can reach the Pearl-side address and port. Document firewall and NAT ownership before deployment.
Rendezvous
Use only when the model guide and network design call for matching Rendezvous peers and ports. Do not mix it with a Caller/Listener example.
Align URL or address, source and destination ports, Stream ID, latency, recovery overhead and AES passphrase at both peers. Keep security values out of screenshots and public runbooks.
Size the appliance before configuring transport
Count the local work
List every physical and network input, layout, encoded channel, local recording, confidence output and operator view. Adding a network input or another recording can change the stable workload.
Count the remote work
List the single accepted contribution first, then any Multiview tile, Callaba recording, web playback, onward SRT peer or recovery route. Expand only after the first path passes.
Run the full acceptance sequence
- Record the exact Pearl model, firmware and intended source or destination role.
- Build the real local program and prove every source, layout and audio channel on Pearl.
- Create the matching Callaba peer and align mode, ports, Stream ID, encryption, latency and expected media profile.
- Stream and record under the complete planned Pearl workload while observing resource and network behavior.
- Verify Callaba transport statistics, decoded motion and audio; make and play back the independent Callaba recording.
- Interrupt the real network path, measure reconnect, then test any downstream route or failover as a separate operation.
Choose the Callaba location from the receive boundary
An AWS deployment provides a public receiving point for distributed contributors. Self-hosted Callaba keeps the server inside a facility or private Linux network. In both cases, the operational value is the same: a browser view of accepted Pearl feeds, receiver-side evidence, recording and controlled routing after the handoff is proved.
Official Epiphan references
Review Epiphan’s SRT support overview for Pearl, the Pearl-2 SRT input guidance, the Pearl Mini Caller/Listener guide, and the Pearl Nano SRT guide. Match the guide release to the installed firmware and confirm model-specific capacity.
