Overview

LEXI Pause feature is an alternative to the default behavior of the LEXI Controller, which offers some improvements in performance and workflow. Previously, the only available option was for LEXI jobs running on either EEG Cloud or LEXI Local to shut down every time captions were blocked. This happened whether blocking was by an alternate caption source, GPI-E activation, or SCTE-104 triggers, incurring short delays when stopping and starting the instance.

With LEXI Pause, the job continues running while captions are blocked, so pausing and resuming occurs much faster. There are some additional differences, which are discussed in this document.

LEXI Pause is compatible with EEG Cloud Scheduling, and can pause jobs run through any access code targeting a given encoder. Below is an overview of the differences between the pause and shutdown LEXI options:

Note: The Alta product also supports pausing/resuming Lexi via HTTP posts to an API endpoint. 

Benefits of LEXI Pause Mode

LEXI Pause has the following benefits compared to LEXI Pause:

• Less latency when transitioning between LEXI and other captioning sources.
• Ability to schedule LEXI jobs from EEG Cloud while still having LEXI not run upon detection of other caption sources. When Stopping LEXI, both cannot be done simultaneously.
• Won't run as many jobs, making it easier to review lists of jobs for debugging purposes.

Benefits of LEXI Shutdown Mode

LEXI Shutdown has these benefits compared to LEXI Pause:

• Users will not be billed when LEXI is shut down while blocked, but will continue to be billed while LEXI is paused. LEXI Pause does not currently work with the latest version of LEXI Local.
• Only LEXI Shutdown mode is currently supported with LEXI Local units. Support is coming soon for LEXI Local.

Enabling LEXI Pause

Note: LEXI Pause does not currently work with LEXI Local. Only LEXI mode works with the latest version of LEXI Local. Support for LEXI Local is coming soon.

1. On the encoder interface, navigate to the LEXI module.
2. At the top of the window, enable Instances mode. It is not necessary to select an instance for the pause feature to work. Any instance or access code that targets the encoder will be paused.
3. In the Lexi Client section, enable or disable LEXI:
   • If you are scheduling LEXI instances or jobs from EEG Cloud, deselect Enable Lexi.
     
   • If you are scheduling LEXI from the encoder, select Enable Lexi.
     
4. Select the check boxes of the fields for the signal types that you would like to cause LEXI to pause when it detects:
   • Block on Upstream
   • Block on Serial Port
   • Require GPI-E
   • Block on SCTE-104
5. Enter the number of seconds in the input field box for each type. This indicates the amount of time before LEXI to continues after no further detection of that selected signal.
   Note: For best performance, we recommend setting at least a 5-second delay upon blocking LEXI.
6. Block on SCTE-104 users: configure the system to send SCTE-104 messages via VANC in upstream video, in addition to marking the checkbox. If the following SCTE triggers are sent upstream, LEXI pauses or resumes respectively, or it stops and starts when Lexi Block Mode is set to Shutdown instead of Paused.
   Please note:
   
   • START NORMAL with a set Duration value and/or END NORMAL
   • Splice Start Immediate/Splice End Immediate
   • The following Segmentation Descriptor requests (start/end): Provider Ad, Distributor Ad, Provider Placement Opportunity, Distributor Placement Opportunity.
7. GPI-E users: activate that GPI when you would like LEXI to pause, and then deactivate it when you want LEXI to continue again.
   
8. From the Lexi Block Mode menu, select Pause.
9. Click Apply Settings to save your changes.