![]() Scenario one has no start or end time and users are unable to seek within the The variables T1 and T2 are used to represent the timestamp on theĬaution: Scenarios 3 and 4 are not officially supported, but playback is See Adding Program Guide Data for how to configureīelow are descriptions and screenshots of the scenarios supported by the LiveĪPI. Users are allowed to seek within the live stream's seekable window.There are eight possible types of scenarios for live streaming, each of whichĪre configured by setting three core settings: Live stream scenarios Caution: Scenarios 1, 7 & 8 are officially supported. For a live stream this will happen when the player detects the manifest is removing earlier segments. Triggered when the seekable range of a live stream changes from a fixed window to a moving window, or vice versa. At this point the end value in the LiveSeekableRange will stop updating users will still be able to view content within the live seekable range. Note: You cannot update values in an event, for more details see Object, which contains the current live seekable range. Two events, LIVE_ENDED and LIVE_IS_MOVING_WINDOW_CHANGED, are included in Guide for details about how to disable media commands for voice. Removing the supported media command for SEEK signals to sender applicationsĪnd touch displays to disable seeking, but doesn't disable voice commands suchĪs ‘Ok google, seek backwards 30 seconds.’ See the PlayerManager.removeSupportedMediaCommands(.SEEK, true) To disable seeking within a stream, you need to remove the seek functionalityįrom the supported media commands on the Web Receiver: // disable seeking in the LOAD messageInterceptor Restart playback at the live edge of the stream. ![]() Of the live seekable window, or if seeking is disabled entirely, the stream will Note: If the user pauses a stream long enough that their play head falls outside Is 10 seconds, the start and end times will be updated about every 10 seconds as Thus if the typical length of a segment for your stream It is important to note the start andĮnd times in the seekable range are updated based on the time it takes to * This interceptor is called before your content is loaded by a Cast deviceĬ.LOAD, Responsible for calculating it when the content is LIVE. MediaInformation.duration should be -1 as the player instances are ![]() Indicate a load request is for a live stream, simply set the Object that contains all the important metadata about a load request. using a sender-side or receiver-side generated load request.using the LOAD message interceptor in your Web Receiver application.There are two ways to configure the Web Receiver SDK to use the Live API for Play Head - A UI timestamp for the current playback position.Live Edge - The newest part of a live stream available to the player.Seekable Window - The range of a live stream that users can seek within.The following terms are used throughout the guide: Supports typical live stream configurations for the Additionally, to run the code samples you will need access to a live ![]() Web Receiver is required before reviewing this Prerequisitesįamiliarity with the basics of implementing a Warning: Use of the Live API is currently not Screenshots demonstrating what each scenario looks like. This guide demonstrates how to configure a stream to the Live APIs, includingĬode and metadata samples for configuring core Live scenarios, along with Start and end times, program metadata, DVR controls, and seekable windows. Live experiences with just a few lines of code. This includes aįlexible, out-of-box UI, coupled with APIs that allow developers to create rich The Cast SDK includes built-in APIs for supporting live content.
0 Comments
Leave a Reply. |