Appnotes

Setting Up Lexi on Your EEG Encoder

Last Updated June 29, 2023

Lexi™ is a cloud-hosted automatic captioning service provided by EEG, offering multiple convenient ways to administer captioning jobs. EEG Cloud can be used to start, stop, and schedule Lexi, but depending on your workflow, you may prefer to administer Lexi directly through your EEG encoder. This appnote explains how to use the configuration portal of your encoder to configure Lexi.

An EEG Cloud account with an active Lexi subscription is required to run Lexi. If you do not have an EEG Cloud account or an active Lexi subscription and would like to activate Lexi on your EEG encoder, please contact the EEG sales team at sales@eegent.com or call 516-293-7472.

Lexi also requires iCap™ to be configured and running on your encoder; please see our iCap firewall configuration application note for details. Additionally, your network settings need to allow outbound connections to https://eegcloud.tv on port 443, and your encoder must have a valid DNS server configured under the Network tab on its web portal.

If your encoder's Lexi configuration page looks different from the screenshot below, it is likely that you have a different software version from the one featured. Please visit our Product Updates and Downloads page if you would like to request an update for your encoder.

Encoder Lexi management provides the option of using one of two modes: "Jobs" or "Instances". In Jobs mode, the Lexi settings are configured in the encoder's web configuration page as shown in Figure 1. In Instances mode, the Lexi settings are configured in an EEG Cloud "Lexi Instance", which is analogous to a profile. This mode provides the ability to create several different Instances in EEG Cloud. A use case example would be to select an Instance that has been configured with a Topic Model containing vocabulary applicable to specific content dialog,  A sample configuration using Instances mode is shown in Figure 2.

Figure 1: Lexi module accessed through the web interface of EEG encoders in "Jobs" configuration 

Figure 2: Lexi module accessed through the web interface of EEG encoders in "Instances" configuration

Login

EEG Cloud Username and Password: In order to link your encoder to your EEG Cloud account, you can enter your EEG Cloud login credentials here. Alternatively, if you have been provided with an API key generated by EEG, you can enter that in the EEG Cloud Password field, while using "api_key" as your username. The latter method is preferred, particularly for accounts with multiple encoders, as it allows users to more easily break down their Lexi usage reports by individual encoder.

Access Code: Enter the iCap Access Code associated with your EEG encoder - this tells Lexi where to send its captions. Please note that your Access Code must be shared with the iCap company EEGASR via the iCap Admin web site if this has not already been done via factory configuration.

 

Speech Recognition

Engine: This option allows you to choose the speech recognition engine that will be used to generate your Lexi captions.

Language: This will determine the language Lexi uses to generate captions; it must match the language of the dialog on the primary audio channel of your iCap Access Code. Note that the list of available languages may vary, depending on the engine chosen.

Topic Model: Through EEG Cloud, you can manage your Lexi account and create Topic Models to further improve accuracy for your unique application. This dropdown box will display all of the Topic Models available under your active EEG Cloud account, for the language you have chosen.

Safe Language Filter: Enabled by default, this option allows you to control whether to filter out profanity or potentially offensive word choices.

 

Caption Display

Caption Service: Choose from primary language (CC1/S1) and secondary language (CC3/S2) options.

Number of Rows: The number of rows per roll-up caption can range from 2 to 4.

Vertical Position: CTA-608 base row options range from 2 (top of the screen) to 15 (bottom of the screen).

Horizontal Position: Choose a left horizontal offset from 0 to 28 characters.

Force Capital Letters: When enabled, all captions will be written in upper-case.

Use Lexi Vision Positioning: Automatically position captions based on Lexi Vision's detection of on-screen text, faces, and other items that should not be covered with captions.

 

Lexi Status

Status: This will display the state of the Lexi job if one has been started, or else it will indicate that Lexi is not running on the selected Access Code.

Version: This field will display the current version of the Lexi software running on the encoder.

 

Lexi Client

Enable Lexi: The Lexi module must be enabled in order for the encoder to communicate with Lexi and receive captions from the cloud.

Monitor Service with GPO 2: When selected, GPO 2 will be active when Lexi is captioning to the selected Access Code, and will be inactive otherwise.

Require GPI-E: When checked, a Lexi captioning job will start when GPI-E is asserted and will run until GPI-E is de-asserted. When unchecked, a Lexi captioning job will be started immediately upon enabling the client module. Please note that if the Block on Serial Port or Block on Upstream options (below) are active, they may keep Lexi from running under the aforementioned circumstances.

Block on Upstream: Checking this will ensure that Lexi will not generate captions when upstream captions are present in your SDI video input. The timeout entered into the adjacent box determines how long upstream captions will have to be absent in order for Lexi to start up again.

Block on Serial Port: Checking this will ensure that Lexi will not generate captions when captions are present on one of the encoder's two serial port inputs; these are often used for teleprompter input. The timeout entered into the adjacent box determines how long serial port captions will have to be absent in order for Lexi to start up again.

Inactivity Timeout: If enabled, a Lexi job that runs for this amount of time without any dialog being transcribed will be terminated automatically by the server.

Auto-Restart: If the Inactivity Timeout is enabled, checking this box will cause Lexi to automatically start back up after being terminated, once sufficiently loud audio is present. The volume threshold at which Lexi will reactivate is determined by the adjacent dropdown box.