What each CMS platform supports on a Pearl device
Applies to: Pearl-2, Pearl Mini, Pearl Nano, Pearl Nexus.
Capability varies by CMS platform, not only by Pearl model. Check this table before assuming a procedure documented for one platform applies to another.
| CMS platform | Pearl registers as | Ad hoc events started from the Pearl device | Webcasting (live streaming) | Extend, pause, and resume |
|---|---|---|---|---|
| Panopto | Remote recorder | Supported | Supported | Supported |
| Kaltura | Resource | Supported | Supported, on a single channel only | Supported (pause and resume: firmware 4.24.6 or newer) |
| Opencast | Capture agent | Supported | Supported | Supported |
| YuJa | Third-party device | Not supported | Supported | Supported |
| EchoVideo (Echo360) | Room device | Supported (firmware 4.24.6 or newer) | Supported | Supported (pause and resume: firmware 4.24.6 or newer) |
YuJa does not support creating ad hoc events from a Pearl device. An impromptu event can be started from the YuJa web interface, but not from the Pearl device, the Pearl Admin panel, or third-party control such as a Q-SYS, Extron or Crestron panel or the REST API.
EchoVideo (Echo360) ad hoc events require firmware 4.24.6 or newer. They can be created from the Pearl device's touch screen (Pearl-2 and Pearl Mini), the Admin panel, or third-party control through the REST API; see "Create ad hoc events with EchoVideo" in the EchoVideo (Echo360) CMS integration guide. EchoVideo ad hoc events cannot be started with Delcom USB buttons. Epiphan Edge cannot start ad hoc events for any CMS platform, including EchoVideo; Edge can start scheduled EchoVideo events early. An impromptu event can also be started from the Echo360 web interface.
Kaltura supports webcasting on one channel only. Panopto, Opencast, YuJa and EchoVideo have no such single-channel restriction; consult the guide for your platform for its channel limits.
Where you choose which channels an event uses differs by platform:
Kaltura — select the channels in the CMS settings on the Pearl device.
Opencast — the CMS settings on the Pearl device set which channels are available for recording and streaming. When you schedule an event in Opencast, you choose which of those available channels the event uses. An ad hoc event uses whichever channels are marked as available on the Pearl device.
YuJa — channel selection is held in a profile configured on the Pearl device. You choose which profile an event uses when you schedule the event in YuJa.
Panopto — select the channels in the Panopto interface, not on the Pearl device.
EchoVideo (Echo360) — channel selection is held in a profile configured in the Echo360 interface, not on the Pearl device.
Device differences
- Pearl Nano: Pearl Nano cannot start ad hoc events from the device display, except for Panopto events when the Upload destination is the Default Folder and Enable user-customizable ad hoc events is disabled. Pearl Nano does not support EchoVideo (Echo360) at all.
- Pearl Nexus: Pearl Nexus is headless, so ad hoc events cannot be authenticated or created from a device screen. Use the Admin panel instead.