This guide describes how to obtain and install binary packages for the NVIDIA Riva Speech Synthesis (SS) plugin to the UniMRCP server on Red Hat-based Linux distributions. The document is intended for system administrators and developers.
Instructions provided in this guide are applicable to the following versions.
UniMRCP 1.7.0 and above
UniMRCP Riva SS Plugin 1.0.0 and above
The NVIDIA Riva Speech Skills platform must be installed separatelly. The implementation of the plugin is compatible with the following versions.
NVIDIA Riva Speech Skills 2.0.0 and above
UniMRCP RPMs are currently available for x86_64 (64-bit) architecture only.
|Operating System||Released||End of Support|
|Red Hat / Cent OS 7||April 2022||TBA|
|Red Hat / Cent OS 8||April 2022||TBA|
Packages for other distributions can be developed and made available in the scope of an annual maintenance agreement.
UniMRCP binary packages are available to authenticated users only. In order to register a free account with UniMRCP, please visit the following page.
A newly registered account needs to be verified by the user and then activated by the administrator prior further proceeding.
Account verification and activation.
The account credentials can be used to log in to the following websites.
Using the Yellowdog Updater, Modifier (yum), a command-line package management utility for Red Hat-based distributions, is recommended for installation of UniMRCP binary packages.
Configure a repository by creating a file /etc/yum.repos.d/unimrcp.repo with the following content.
[unimrcp] name=UniMRCP Packages for Red Hat / Cent OS-$releasever $basearch baseurl=https://username:email@example.com/repo/yum/main/rhel$releasever/$basearch/ enabled=1 sslverify=1 gpgcheck=1 gpgkey=https://unimrcp.org/keys/unimrcp-gpg-key.public [unimrcp-noarch] name=UniMRCP Packages for Red Hat / Cent OS-$releasever noarch baseurl=https://username:firstname.lastname@example.org/repo/yum/main/rhel$releasever/noarch/ enabled=1 sslverify=1 gpgcheck=1 gpgkey=https://unimrcp.org/keys/unimrcp-gpg-key.public
The username and password fields included in the HTTPS URI must be replaced with the corresponding account credentials.
In order to verify that yum can properly connect and access the UniMRCP repository, the following command can be used.
yum repolist unimrcp yum repolist unimrcp-noarch
where unimrcp and unimrcp-noarch are names of the sections set in the yum configuration file above.
In order to retrieve a list of packages the UniMRCP repository provides, the following command can be used.
yum --disablerepo="*" --enablerepo="unimrcp" list available yum --disablerepo="*" --enablerepo="unimrcp-noarch" list available
In order to install the Riva SS plugin, including all the dependencies, use the following command.
yum install unimrcp-riva-ss
In order to install the additional data files for the sample client application umc, the following command can be used.
yum install umc-addons
This package is optional and provides additional data which can be used for validation of basic setup.
UniMRCP RPM packages can be installed manually using the rpm utility. Note, however, that the system administrator should take care of package dependencies and install all the packages in appropriate order.
The RPM packages have the following naming convention:
The following is a list of UniMRCP RPM packages required for the installation of the Riva SS plugin.
|unimrcp-riva-ss||Riva SS plugin to the server.|
|uninvidiaapis||UniMRCP edition of the NVIDIA APIs library.|
|unigrpc||UniMRCP edition of the gRPC library.|
|umc-addons||Sample en-US data files used with umc. [Optional]|
|unilicnodegen||Node information retrieval tool, required for license deployment.|
|unimrcp-server||Shared library and application of the server.|
|unimrcp-client||Shared libraries and sample applications of the client. [Optional]|
|unimrcp-demo-plugins||Set of demo plugins to the server. [Optional]|
|unimrcp-common||Data common for the client and the server.|
|uniapr||UniMRCP edition of the Apache Portable Runtime (APR) library.|
|uniapr-util||UniMRCP edition of the Apache Portable Runtime Utility (APR-Util) library.|
|unisofia-sip||UniMRCP edition of the Sofia SIP library.|
Note that all the RPM packages provided by UniMRCP are signed by a GNU Privacy Guard (GPG) key. Before starting the installation, you may need to import the public key in order to allow the rpm utility to verify the packages.
rpm --import https://unimrcp.org/keys/unimrcp-gpg-key.public
Packages for the APR, APR-Util and Sofia-SIP libraries must be installed first.
rpm -ivh uniapr-$aprversion-$packageversion.el$rhelversion.$arch.rpm rpm -ivh uniapr-util-$apuversion-$packageversion.el$rhelversion.$arch.rpm rpm -ivh unisofia-sip-$sofiaversion-$packageversion.el$rhelversion.$arch.rpm
Then, a package containing common data for the client and the server, and a package for the server should follow.
rpm -ivh unimrcp-common-$universion-$packageversion.el$rhelversion.$arch.rpm rpm -ivh unimrcp-server-$universion-$packageversion.el$rhelversion.$arch.rpm
Next, a package containing the utility tool unilicnodegen, required for license deployment.
rpm -ivh unilicnodegen-$toolversion-$packageversion.el$rhelversion.$arch.rpm
Next, packages containing the gRPC-deps and gRPC libraries.
rpm -ivh unigrpc-deps-$grpcversion-$packageversion.el$rhelversion.$arch.rpm rpm -ivh unigrpc-$grpcversion-$packageversion.el$rhelversion.$arch.rpm
Next, a package containing the NVIDIA APIs library.
rpm -ivh uninvidiaapis-$apisversion-$packageversion.el$rhelversion.$arch.rpm
Finally, a package containing the Riva SS plugin should follow.
rpm -ivh unimrcp-riva-ss-$universion-$packageversion.el$rhelversion.noarch.rpm
The Riva SS plugin to the UniMRCP server is a licensed software.
In order to obtain a trial license, node information must be retrieved and submitted for license generation.
Use the installed tool unilicnodegen to retrieve the node information.
As a result, a text file uninode.info will be saved in the current directory.
Consider the following procedure to place an order.
- Navigate to https://unispeech.io/rivass.
- Under the section Obtain License, select
- License Variation: Trial
- License Term: 30-day
- License Type: Node-bound
- License Quantity: 2
Ther orders are normally processed within one business day. A license file will be provided as a result.
The license file needs to be placed into the directory /opt/unimrcp/data.
cp umsrivass_*.lic /opt/unimrcp/data
In order to load the plugin into the UniMRCP server, open the file unimrcpserver.xml, located in the directory /opt/unimrcp/conf, and add the following entry under the XML element <plugin-factory>. Disable other synthesizer plugins, if available. The demo plugins for other resources can also be disabled.
<!-- Factory of plugins (MRCP engines) --> <plugin-factory> <engine id="Demo-Synth-1" name="demosynth" enable="false"/> <engine id="Riva-SS-1" name="umsrivass" enable="true"/> </plugin-factory>
In order to enable log output from the plugin and set filtering rules, open the configuration file logger.xml, located in the directory /opt/unimrcp/conf, and add the following entry under the element <sources>.
<source name="RIVASS-PLUGIN" priority="INFO" masking="NONE"/>
Open the configuration file umsrivasr.xml, located in the directory /opt/unimrcp/conf, and specify a Riva service endpoint matching your deployment.
<streaming-recognition service-uri="127.0.0.1:50051" secure-transport="false" />
Validate your setup by using the sample UniMRCP client and server applications on the same host. The default configuration and data files should be sufficient for a basic test.
Launch the UniMRCP server application.
cd /opt/unimrcp/bin ./unimrcpserver
In the server log output, check whether the plugin is normally loaded.
[INFO] Load Plugin [Riva-SS-1] [/opt/unimrcp/plugin/umsrivass.so]
Next, check for the license information.
[NOTICE] UniMRCP Riva SS License -product name: umsrivass -product version: 1.0.0 -license owner: Name -license type: trial -issue date: 2022-03-07 -exp date: 2022-04-06 -channel count: 2 -feature set: 0
Note: the optional package umc-addons must be installed for this test to work.
Launch the sample UniMRCP client application umc.
cd /opt/unimrcp/bin ./umc
Run a typical speech synthesis scenario by issuing the command run bss1 from the console of the umc client application.
This command sends a SPEAK request to the server and then records synthesized stream into a PCM file stored in the directory /opt/unimrcp/var.
Visually inspect the log output for any possible warnings or errors.