While Rio Broker presents a simple interface (See API section), some integration is required on the part of the client.
A detailed API description and integration guide is presented in the API section.
Spectra provides certification services for any client that wishes to be listed here and recommended by our sales force. Contact your local system architect to be considered for this service.
Clients that have been certified with Rio Broker (Details below):
- AVID “PAM”
- AVID “MAM”
- Arcastream (Rio?)
- Arvato VPMS
- Aveo NUE
- Axle.ai
- CatDV (DS3 only to Nearline Gateway)
- Dalet Galaxy
- Dalet Flex Ooyala
- eMAM (Rio?)
- Glookast (Rio?)
- Grass Valley
- Imagine (Rio?)
- IPV Curator
- Levels Beyond (Rio?)
- Marquis Postflux
- Marquis Project Parking
- Nuxeo
- Root6 Content Agent
- Suitcase TV (Rio?)
- Tedial aStorm
- Tiger (Rio?)
- TMD MediaFlex UMS (Rio?)
- VizRT (Rio?)
- VSN (Rio?)
¶ Avid PAM
| Avid Interplay PAM Version Tested |
Avid Shared Storage (Nexis) Version Tested |
BlackPearl Archive Plugin Version Tested |
BlackPearl Software Version Tested |
.NET Framework Version Tested |
| 2018.11 (Build: 4.2.0.10120) | 18.11.0.9 | 5.0.3 (uses RioBroker) | 5.2.1 | 4.8.03761 |
| 3.4-3.8; (2017.x-2020.x ok) |
4.7.x | 4.0.9 (uses RioBroker, recommened) 3.2.4 (without RioBroker) |
5.x (uses RioBroker) 4.1 (without RioBroker) |
4.5.2 |
| 3.6 and 3.8 (3.5-3.9 ok) | 4.7.10 | 3.2.4 | 3.5.x-4.1.x | 4.5.2 |
| 3.6 (3.5-3.7 ok) | 4.7.10 | 3.2.2 | 3.2.2 | 4.5.2 |
| 3.5 (3.4-3.6 ok) | 4.7.8 | 3.0.1 | 3.0.1 | 4.5 |
| 3.4 (3.3-3.5 ok) | 4.7.5 | 1.2.2 | 1.2.x | 4.5 |
* Versions in parenthesis were not tested but are expected to work.
Note: For customers using RioBroker, all future releases of Interplay PAM are supported.
¶ Avid MAM
| Asset Management Base Version |
Version Avid BlackPearl Connector |
Support for RioBroker | Support for BlackPearl Direct (max 250MB/s) |
| Media Central | Asset Management 2020.9 or higher* | 3.5.0 or higher | Yes, RioBroker 1.x-3.x | No |
| Media Central | Asset Management 2019.6-2020.4 | 3.2.0-3.4.0 | Yes, RioBroker 1.x | Yes for connector 3.2.0, not recommended for new installs -- use RioBroker |
| Media Central | Asset Management 2017.2-2018.11 | 2.1.0-3.1.0 | No | Yes |
| MAM 5.0-MAM 5.9 | 1.2.1.168 or higher | Yes | Yes |
| MAM 5.0-MAM 5.9 | 1.2.0 | No | Yes |
* For customers using RioBroker, all future releases of the MAM base version and connector version are supported with RioBroker 3.x.
¶ Dalet Ooyala
Certified May 27, 2021
Certification Documentation: /daletriocertificationtestplan_v2.pdf
¶ Grass Valley
Grass Valley has an integration with RioBroker that was first certified in May 2020. Here is some information and best practices that are specific to the Grass Valley integration with RioBroker.
¶ Grass Valley Integration Requires PFR Module
RioBroker includes an optional Partial File Restore (PFR) module that must be purchased by the customer to support time-based partial restores of files. Grass Valley supports the PFR module to support partial file restore of files in Grass Valley. Due to the nature of the way that RioBroker works with the FTP interface of Grass Valley, the PFR module must be included in all Grass Valley installations, even if the customer has no intention of using the partial file restore feature. This may change in the future. Be sure to include the PFR module on all Grass Valley opportunity quotes.
¶ Only MXF File Format is Supported
Grass Valley supports two "wrapper" file formats for archiving files - MXF and GXF. Currently only the MXF format is supported by the integration. This is due to a limitation in PFR. If an attempt is made to archive a GXF file, the archive action will fail.
¶ Temporary Disk Landing Space for Files
When you connect the PFR module to RioBroker, you fill out the form in the image below in the RioBroker interface (Settings/Gear Icon > Devices > Time-Based Partial Restore Devices > New). You must provide the path to the "Temporary Storage" where the file will be stored while it is indexed with PFR and then moved to BlackPearl.
The storage capacity of this temporary storage is important. The minimum required capacity is based partially on the number of threads allowed by the Grass Valley storage's FTP interface. Grass Valley customers pay/license the Grass Valley solution based partially on the number of parallel FTP connections allowed.
Therefore, the size of the temporary disk should be at least the customer's maximum file size multiplied by the number of FTP thread licensed by the customer. For example, if the customer's largest files in Grass Valley are 500GB, and they have licensed 5 FTP threads on the Grass Valley storage device, then the temporary disk landing space should be at least 500GB multiplied by 5, or 2,500GB.
¶ IPV Curator
As of 8 February 2023, IPV Curator is certified with RioBroker 3.3.0. We will run a smoke test vs 3.4.2 this week and update accordingly.
Recording of demo call is here: 2023_02_08_IPVCurator_Certified_with_RioBroker.mp4
Certification documentation: /riocertificationtestplanipvcurator.docx