Live Captioning - Managing reserved instances (Beta)

3Play's Live caption service requires that you send a video (RTMP) stream from your encoder or meeting platform in order to produce captions. 3Play produces a Stream Target (by provisioning a transcoder) to which you stream for each Live event. 

3Play will provide you with the Stream Target (transcoder) described by an Input Stream RTMP URL address and Input Stream Key to the stream target on the confirmation page of your 3Play captioning ordering workflow. By default, the RTMP URL and Key will be unique for every event, and you'll enter this information into your encoder stream settings in preparation for each event.

mceclip0.png

3Play also offers a Reserved Stream Target, with which the Input Stream RTMP URL address and Input Stream Key will remain static for any Live events scheduled to use one. This article outlines the process for requesting a reserved stream target, as well as the process for utilizing a reserved stream target for your live captioning events.

 

Requesting a Reserved Stream Target

Please reach out to your account manager or 3Play support to request a Reserved Stream Target. In your request, please specify your 3Play account and project name as well as the number of reserved stream targets that you would like.

You should request as many Reserved Stream Targets as the maximum number of live events you anticipate needing to caption in that 3Play project. Each Reserved Stream Target will require and be associated with its own Folder in your 3Play project.

3Play will then create the reserved stream targets, using the naming convention Channel-1, Channel-2, and so on. Each reserved stream target is associated with a folder in your 3Play account system.

Once reserved stream targets are provisioned within a given project, you will no longer be able to use the real-time provisioned stream targets for your Live Events, and reserved stream targets (or your own transcoder) must be used.

 

Live Captioning Ordering with Reserved Stream Targets

Each Reserved Stream Target is associated with a Folder in the 3Play system. To use a reserved stream target, the Live Captioning event must be associated with the Folder corresponding to the desired Reserved Stream Target (eg, "Channel-1") when scheduling your event. You can select the folder in 2 ways:

  1. Project Setting: Set a default folder for your Live Captioning events in the 3Play Project Settings. This will associate the SAME folder for all your Live events by default.
    1. 3Play_Media___Account__.png
  2. Per Event: Choose the reserved instance used for your Live Captioning event when ordering. You'll select which Reserved Stream Target associated Folder (eg, "Channel-1") you want to use within the Advanced Settings under "Where would you like to store this file upon completion" when scheduling each event in 3Play. The streaming information for the selected instance will pre-populate on the confirmation screen. 
    1. Mouse_Highlight_Overlay_and_3Play_Media___Account___Live_Auto_Captioning___New_Event__1__png.png
    2. Search_results_-_slaing_3playmedia_com_-_3playmedia_com_Mail.png

Stream Recovery & Maximum Stream Time

If there is a disconnection between your encoder and 3Play, this will cause the event in 3Play to end. In order to begin the stream again, you will need to schedule a new event in 3Play. 

If you are using a 3Play-provisioned reserved transcoder: please ensure the recovery event is scheduled at least 5 minutes in the future to ensure the transcoder has enough time to reset prior to re-initiating your stream, OR select a different transcoder.

Once you disconnect, the reserved instance will spin down on its own in a few minutes. If you don't stop streaming to the instance, then the instance will spin itself down after the Max Stream time duration has been reached (as defined in the advanced settings of the event). The Max Stream duration starts at the Stream Start time you select in the ordering workflow. You can also select "end event" on the Live dashboard page, which will also cause the instance to spin down.
NOTE: do not schedule overlapping events using the same reserved stream targets, this will cause the later event to fail. 
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk