@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class GetHLSStreamingSessionURLRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP| Constructor and Description |
|---|
GetHLSStreamingSessionURLRequest() |
| Modifier and Type | Method and Description |
|---|---|
GetHLSStreamingSessionURLRequest |
clone() |
boolean |
equals(Object obj) |
String |
getContainerFormat()
Specifies which format should be used for packaging the media.
|
String |
getDiscontinuityMode()
Specifies when flags marking discontinuities between fragments are added to the media playlists.
|
String |
getDisplayFragmentTimestamp()
Specifies when the fragment start timestamps should be included in the HLS media playlist.
|
Integer |
getExpires()
The time in seconds until the requested session expires.
|
HLSFragmentSelector |
getHLSFragmentSelector()
The time range of the requested fragment and the source of the timestamps.
|
Long |
getMaxMediaPlaylistFragmentResults()
The maximum number of fragments that are returned in the HLS media playlists.
|
String |
getPlaybackMode()
Whether to retrieve live, live replay, or archived, on-demand data.
|
String |
getStreamARN()
The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
|
String |
getStreamName()
The name of the stream for which to retrieve the HLS master playlist URL.
|
int |
hashCode() |
void |
setContainerFormat(String containerFormat)
Specifies which format should be used for packaging the media.
|
void |
setDiscontinuityMode(String discontinuityMode)
Specifies when flags marking discontinuities between fragments are added to the media playlists.
|
void |
setDisplayFragmentTimestamp(String displayFragmentTimestamp)
Specifies when the fragment start timestamps should be included in the HLS media playlist.
|
void |
setExpires(Integer expires)
The time in seconds until the requested session expires.
|
void |
setHLSFragmentSelector(HLSFragmentSelector hLSFragmentSelector)
The time range of the requested fragment and the source of the timestamps.
|
void |
setMaxMediaPlaylistFragmentResults(Long maxMediaPlaylistFragmentResults)
The maximum number of fragments that are returned in the HLS media playlists.
|
void |
setPlaybackMode(String playbackMode)
Whether to retrieve live, live replay, or archived, on-demand data.
|
void |
setStreamARN(String streamARN)
The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
|
void |
setStreamName(String streamName)
The name of the stream for which to retrieve the HLS master playlist URL.
|
String |
toString()
Returns a string representation of this object.
|
GetHLSStreamingSessionURLRequest |
withContainerFormat(ContainerFormat containerFormat)
Specifies which format should be used for packaging the media.
|
GetHLSStreamingSessionURLRequest |
withContainerFormat(String containerFormat)
Specifies which format should be used for packaging the media.
|
GetHLSStreamingSessionURLRequest |
withDiscontinuityMode(HLSDiscontinuityMode discontinuityMode)
Specifies when flags marking discontinuities between fragments are added to the media playlists.
|
GetHLSStreamingSessionURLRequest |
withDiscontinuityMode(String discontinuityMode)
Specifies when flags marking discontinuities between fragments are added to the media playlists.
|
GetHLSStreamingSessionURLRequest |
withDisplayFragmentTimestamp(HLSDisplayFragmentTimestamp displayFragmentTimestamp)
Specifies when the fragment start timestamps should be included in the HLS media playlist.
|
GetHLSStreamingSessionURLRequest |
withDisplayFragmentTimestamp(String displayFragmentTimestamp)
Specifies when the fragment start timestamps should be included in the HLS media playlist.
|
GetHLSStreamingSessionURLRequest |
withExpires(Integer expires)
The time in seconds until the requested session expires.
|
GetHLSStreamingSessionURLRequest |
withHLSFragmentSelector(HLSFragmentSelector hLSFragmentSelector)
The time range of the requested fragment and the source of the timestamps.
|
GetHLSStreamingSessionURLRequest |
withMaxMediaPlaylistFragmentResults(Long maxMediaPlaylistFragmentResults)
The maximum number of fragments that are returned in the HLS media playlists.
|
GetHLSStreamingSessionURLRequest |
withPlaybackMode(HLSPlaybackMode playbackMode)
Whether to retrieve live, live replay, or archived, on-demand data.
|
GetHLSStreamingSessionURLRequest |
withPlaybackMode(String playbackMode)
Whether to retrieve live, live replay, or archived, on-demand data.
|
GetHLSStreamingSessionURLRequest |
withStreamARN(String streamARN)
The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
|
GetHLSStreamingSessionURLRequest |
withStreamName(String streamName)
The name of the stream for which to retrieve the HLS master playlist URL.
|
addHandlerContext, copyBaseTo, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic void setStreamName(String streamName)
The name of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
streamName - The name of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
public String getStreamName()
The name of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
You must specify either the StreamName or the StreamARN.
public GetHLSStreamingSessionURLRequest withStreamName(String streamName)
The name of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
streamName - The name of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
public void setStreamARN(String streamARN)
The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
streamARN - The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
public String getStreamARN()
The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
You must specify either the StreamName or the StreamARN.
public GetHLSStreamingSessionURLRequest withStreamARN(String streamARN)
The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
streamARN - The Amazon Resource Name (ARN) of the stream for which to retrieve the HLS master playlist URL.
You must specify either the StreamName or the StreamARN.
public void setPlaybackMode(String playbackMode)
Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with the
latest fragments as they become available. We recommend that the media player retrieve a new playlist on a
one-second interval. When this type of session is played in a media player, the user interface typically displays
a "live" notification, with no scrubber control for choosing the position in the playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if there is
a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media player to halt
or cause a jump in playback. In this mode, fragments are not added to the HLS media playlist if they are older
than the newest fragment in the playlist. If the missing fragment becomes available after a subsequent fragment
is added to the playlist, the older fragment is not added, and the gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly to how
it is updated for LIVE mode except that it starts by including fragments from a given start time.
Instead of fragments being added as they are ingested, fragments are added as the duration of the next fragment
elapses. For example, if the fragments in the session are two seconds long, then a new fragment is added to the
media playlist every two seconds. This mode is useful to be able to start playback from when an event is detected
and continue live streaming media that has not yet been ingested as of the time of the session creation. This
mode is also useful to stream previously archived media without being limited by the 1,000 fragment limit in the
ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the fragments for
the session, up to the number that is specified in MaxMediaPlaylistFragmentResults. The playlist
must be retrieved only once for each session. When this type of session is played in a media player, the user
interface typically displays a scrubber control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if there are
multiple fragments with the same start timestamp, the fragment that has the largest fragment number (that is, the
newest fragment) is included in the HLS media playlist. The other fragments are not included. Fragments that have
different timestamps but have overlapping durations are still included in the HLS media playlist. This can lead
to unexpected behavior in the media player.
The default is LIVE.
playbackMode - Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with
the latest fragments as they become available. We recommend that the media player retrieve a new playlist
on a one-second interval. When this type of session is played in a media player, the user interface
typically displays a "live" notification, with no scrubber control for choosing the position in the
playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if
there is a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media
player to halt or cause a jump in playback. In this mode, fragments are not added to the HLS media
playlist if they are older than the newest fragment in the playlist. If the missing fragment becomes
available after a subsequent fragment is added to the playlist, the older fragment is not added, and the
gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly
to how it is updated for LIVE mode except that it starts by including fragments from a given
start time. Instead of fragments being added as they are ingested, fragments are added as the duration of
the next fragment elapses. For example, if the fragments in the session are two seconds long, then a new
fragment is added to the media playlist every two seconds. This mode is useful to be able to start
playback from when an event is detected and continue live streaming media that has not yet been ingested
as of the time of the session creation. This mode is also useful to stream previously archived media
without being limited by the 1,000 fragment limit in the ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the
fragments for the session, up to the number that is specified in
MaxMediaPlaylistFragmentResults. The playlist must be retrieved only once for each session.
When this type of session is played in a media player, the user interface typically displays a scrubber
control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if
there are multiple fragments with the same start timestamp, the fragment that has the largest fragment
number (that is, the newest fragment) is included in the HLS media playlist. The other fragments are not
included. Fragments that have different timestamps but have overlapping durations are still included in
the HLS media playlist. This can lead to unexpected behavior in the media player.
The default is LIVE.
HLSPlaybackModepublic String getPlaybackMode()
Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with the
latest fragments as they become available. We recommend that the media player retrieve a new playlist on a
one-second interval. When this type of session is played in a media player, the user interface typically displays
a "live" notification, with no scrubber control for choosing the position in the playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if there is
a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media player to halt
or cause a jump in playback. In this mode, fragments are not added to the HLS media playlist if they are older
than the newest fragment in the playlist. If the missing fragment becomes available after a subsequent fragment
is added to the playlist, the older fragment is not added, and the gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly to how
it is updated for LIVE mode except that it starts by including fragments from a given start time.
Instead of fragments being added as they are ingested, fragments are added as the duration of the next fragment
elapses. For example, if the fragments in the session are two seconds long, then a new fragment is added to the
media playlist every two seconds. This mode is useful to be able to start playback from when an event is detected
and continue live streaming media that has not yet been ingested as of the time of the session creation. This
mode is also useful to stream previously archived media without being limited by the 1,000 fragment limit in the
ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the fragments for
the session, up to the number that is specified in MaxMediaPlaylistFragmentResults. The playlist
must be retrieved only once for each session. When this type of session is played in a media player, the user
interface typically displays a scrubber control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if there are
multiple fragments with the same start timestamp, the fragment that has the largest fragment number (that is, the
newest fragment) is included in the HLS media playlist. The other fragments are not included. Fragments that have
different timestamps but have overlapping durations are still included in the HLS media playlist. This can lead
to unexpected behavior in the media player.
The default is LIVE.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with
the latest fragments as they become available. We recommend that the media player retrieve a new playlist
on a one-second interval. When this type of session is played in a media player, the user interface
typically displays a "live" notification, with no scrubber control for choosing the position in the
playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if
there is a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media
player to halt or cause a jump in playback. In this mode, fragments are not added to the HLS media
playlist if they are older than the newest fragment in the playlist. If the missing fragment becomes
available after a subsequent fragment is added to the playlist, the older fragment is not added, and the
gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly
to how it is updated for LIVE mode except that it starts by including fragments from a given
start time. Instead of fragments being added as they are ingested, fragments are added as the duration of
the next fragment elapses. For example, if the fragments in the session are two seconds long, then a new
fragment is added to the media playlist every two seconds. This mode is useful to be able to start
playback from when an event is detected and continue live streaming media that has not yet been ingested
as of the time of the session creation. This mode is also useful to stream previously archived media
without being limited by the 1,000 fragment limit in the ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the
fragments for the session, up to the number that is specified in
MaxMediaPlaylistFragmentResults. The playlist must be retrieved only once for each session.
When this type of session is played in a media player, the user interface typically displays a scrubber
control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if
there are multiple fragments with the same start timestamp, the fragment that has the largest fragment
number (that is, the newest fragment) is included in the HLS media playlist. The other fragments are not
included. Fragments that have different timestamps but have overlapping durations are still included in
the HLS media playlist. This can lead to unexpected behavior in the media player.
The default is LIVE.
HLSPlaybackModepublic GetHLSStreamingSessionURLRequest withPlaybackMode(String playbackMode)
Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with the
latest fragments as they become available. We recommend that the media player retrieve a new playlist on a
one-second interval. When this type of session is played in a media player, the user interface typically displays
a "live" notification, with no scrubber control for choosing the position in the playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if there is
a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media player to halt
or cause a jump in playback. In this mode, fragments are not added to the HLS media playlist if they are older
than the newest fragment in the playlist. If the missing fragment becomes available after a subsequent fragment
is added to the playlist, the older fragment is not added, and the gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly to how
it is updated for LIVE mode except that it starts by including fragments from a given start time.
Instead of fragments being added as they are ingested, fragments are added as the duration of the next fragment
elapses. For example, if the fragments in the session are two seconds long, then a new fragment is added to the
media playlist every two seconds. This mode is useful to be able to start playback from when an event is detected
and continue live streaming media that has not yet been ingested as of the time of the session creation. This
mode is also useful to stream previously archived media without being limited by the 1,000 fragment limit in the
ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the fragments for
the session, up to the number that is specified in MaxMediaPlaylistFragmentResults. The playlist
must be retrieved only once for each session. When this type of session is played in a media player, the user
interface typically displays a scrubber control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if there are
multiple fragments with the same start timestamp, the fragment that has the largest fragment number (that is, the
newest fragment) is included in the HLS media playlist. The other fragments are not included. Fragments that have
different timestamps but have overlapping durations are still included in the HLS media playlist. This can lead
to unexpected behavior in the media player.
The default is LIVE.
playbackMode - Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with
the latest fragments as they become available. We recommend that the media player retrieve a new playlist
on a one-second interval. When this type of session is played in a media player, the user interface
typically displays a "live" notification, with no scrubber control for choosing the position in the
playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if
there is a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media
player to halt or cause a jump in playback. In this mode, fragments are not added to the HLS media
playlist if they are older than the newest fragment in the playlist. If the missing fragment becomes
available after a subsequent fragment is added to the playlist, the older fragment is not added, and the
gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly
to how it is updated for LIVE mode except that it starts by including fragments from a given
start time. Instead of fragments being added as they are ingested, fragments are added as the duration of
the next fragment elapses. For example, if the fragments in the session are two seconds long, then a new
fragment is added to the media playlist every two seconds. This mode is useful to be able to start
playback from when an event is detected and continue live streaming media that has not yet been ingested
as of the time of the session creation. This mode is also useful to stream previously archived media
without being limited by the 1,000 fragment limit in the ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the
fragments for the session, up to the number that is specified in
MaxMediaPlaylistFragmentResults. The playlist must be retrieved only once for each session.
When this type of session is played in a media player, the user interface typically displays a scrubber
control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if
there are multiple fragments with the same start timestamp, the fragment that has the largest fragment
number (that is, the newest fragment) is included in the HLS media playlist. The other fragments are not
included. Fragments that have different timestamps but have overlapping durations are still included in
the HLS media playlist. This can lead to unexpected behavior in the media player.
The default is LIVE.
HLSPlaybackModepublic GetHLSStreamingSessionURLRequest withPlaybackMode(HLSPlaybackMode playbackMode)
Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with the
latest fragments as they become available. We recommend that the media player retrieve a new playlist on a
one-second interval. When this type of session is played in a media player, the user interface typically displays
a "live" notification, with no scrubber control for choosing the position in the playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if there is
a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media player to halt
or cause a jump in playback. In this mode, fragments are not added to the HLS media playlist if they are older
than the newest fragment in the playlist. If the missing fragment becomes available after a subsequent fragment
is added to the playlist, the older fragment is not added, and the gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly to how
it is updated for LIVE mode except that it starts by including fragments from a given start time.
Instead of fragments being added as they are ingested, fragments are added as the duration of the next fragment
elapses. For example, if the fragments in the session are two seconds long, then a new fragment is added to the
media playlist every two seconds. This mode is useful to be able to start playback from when an event is detected
and continue live streaming media that has not yet been ingested as of the time of the session creation. This
mode is also useful to stream previously archived media without being limited by the 1,000 fragment limit in the
ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the fragments for
the session, up to the number that is specified in MaxMediaPlaylistFragmentResults. The playlist
must be retrieved only once for each session. When this type of session is played in a media player, the user
interface typically displays a scrubber control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if there are
multiple fragments with the same start timestamp, the fragment that has the largest fragment number (that is, the
newest fragment) is included in the HLS media playlist. The other fragments are not included. Fragments that have
different timestamps but have overlapping durations are still included in the HLS media playlist. This can lead
to unexpected behavior in the media player.
The default is LIVE.
playbackMode - Whether to retrieve live, live replay, or archived, on-demand data.
Features of the three types of sessions include the following:
LIVE : For sessions of this type, the HLS media playlist is continually updated with
the latest fragments as they become available. We recommend that the media player retrieve a new playlist
on a one-second interval. When this type of session is played in a media player, the user interface
typically displays a "live" notification, with no scrubber control for choosing the position in the
playback window to display.
In LIVE mode, the newest available fragments are included in an HLS media playlist, even if
there is a gap between fragments (that is, if a fragment is missing). A gap like this might cause a media
player to halt or cause a jump in playback. In this mode, fragments are not added to the HLS media
playlist if they are older than the newest fragment in the playlist. If the missing fragment becomes
available after a subsequent fragment is added to the playlist, the older fragment is not added, and the
gap is not filled.
LIVE_REPLAY : For sessions of this type, the HLS media playlist is updated similarly
to how it is updated for LIVE mode except that it starts by including fragments from a given
start time. Instead of fragments being added as they are ingested, fragments are added as the duration of
the next fragment elapses. For example, if the fragments in the session are two seconds long, then a new
fragment is added to the media playlist every two seconds. This mode is useful to be able to start
playback from when an event is detected and continue live streaming media that has not yet been ingested
as of the time of the session creation. This mode is also useful to stream previously archived media
without being limited by the 1,000 fragment limit in the ON_DEMAND mode.
ON_DEMAND : For sessions of this type, the HLS media playlist contains all the
fragments for the session, up to the number that is specified in
MaxMediaPlaylistFragmentResults. The playlist must be retrieved only once for each session.
When this type of session is played in a media player, the user interface typically displays a scrubber
control for choosing the position in the playback window to display.
In all playback modes, if FragmentSelectorType is PRODUCER_TIMESTAMP, and if
there are multiple fragments with the same start timestamp, the fragment that has the largest fragment
number (that is, the newest fragment) is included in the HLS media playlist. The other fragments are not
included. Fragments that have different timestamps but have overlapping durations are still included in
the HLS media playlist. This can lead to unexpected behavior in the media player.
The default is LIVE.
HLSPlaybackModepublic void setHLSFragmentSelector(HLSFragmentSelector hLSFragmentSelector)
The time range of the requested fragment and the source of the timestamps.
This parameter is required if PlaybackMode is ON_DEMAND or LIVE_REPLAY.
This parameter is optional if PlaybackMode is LIVE. If PlaybackMode is
LIVE, the FragmentSelectorType can be set, but the TimestampRange should
not be set. If PlaybackMode is ON_DEMAND or LIVE_REPLAY, both
FragmentSelectorType and TimestampRange must be set.
hLSFragmentSelector - The time range of the requested fragment and the source of the timestamps.
This parameter is required if PlaybackMode is ON_DEMAND or
LIVE_REPLAY. This parameter is optional if PlaybackMode is LIVE. If
PlaybackMode is LIVE, the FragmentSelectorType can be set, but the
TimestampRange should not be set. If PlaybackMode is ON_DEMAND or
LIVE_REPLAY, both FragmentSelectorType and TimestampRange must be
set.
public HLSFragmentSelector getHLSFragmentSelector()
The time range of the requested fragment and the source of the timestamps.
This parameter is required if PlaybackMode is ON_DEMAND or LIVE_REPLAY.
This parameter is optional if PlaybackMode is LIVE. If PlaybackMode is
LIVE, the FragmentSelectorType can be set, but the TimestampRange should
not be set. If PlaybackMode is ON_DEMAND or LIVE_REPLAY, both
FragmentSelectorType and TimestampRange must be set.
This parameter is required if PlaybackMode is ON_DEMAND or
LIVE_REPLAY. This parameter is optional if PlaybackMode is LIVE. If
PlaybackMode is LIVE, the FragmentSelectorType can be set, but the
TimestampRange should not be set. If PlaybackMode is ON_DEMAND or
LIVE_REPLAY, both FragmentSelectorType and TimestampRange must be
set.
public GetHLSStreamingSessionURLRequest withHLSFragmentSelector(HLSFragmentSelector hLSFragmentSelector)
The time range of the requested fragment and the source of the timestamps.
This parameter is required if PlaybackMode is ON_DEMAND or LIVE_REPLAY.
This parameter is optional if PlaybackMode is LIVE. If PlaybackMode is
LIVE, the FragmentSelectorType can be set, but the TimestampRange should
not be set. If PlaybackMode is ON_DEMAND or LIVE_REPLAY, both
FragmentSelectorType and TimestampRange must be set.
hLSFragmentSelector - The time range of the requested fragment and the source of the timestamps.
This parameter is required if PlaybackMode is ON_DEMAND or
LIVE_REPLAY. This parameter is optional if PlaybackMode is LIVE. If
PlaybackMode is LIVE, the FragmentSelectorType can be set, but the
TimestampRange should not be set. If PlaybackMode is ON_DEMAND or
LIVE_REPLAY, both FragmentSelectorType and TimestampRange must be
set.
public void setContainerFormat(String containerFormat)
Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging because
there is minimal packaging overhead. The other container format option is MPEG_TS. HLS has supported
MPEG TS chunks since it was released and is sometimes the only supported packaging on older HLS players. MPEG TS
typically has a 5-25 percent packaging overhead. This means MPEG TS typically requires 5-25 percent more
bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
containerFormat - Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging
because there is minimal packaging overhead. The other container format option is MPEG_TS.
HLS has supported MPEG TS chunks since it was released and is sometimes the only supported packaging on
older HLS players. MPEG TS typically has a 5-25 percent packaging overhead. This means MPEG TS typically
requires 5-25 percent more bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
ContainerFormatpublic String getContainerFormat()
Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging because
there is minimal packaging overhead. The other container format option is MPEG_TS. HLS has supported
MPEG TS chunks since it was released and is sometimes the only supported packaging on older HLS players. MPEG TS
typically has a 5-25 percent packaging overhead. This means MPEG TS typically requires 5-25 percent more
bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging
because there is minimal packaging overhead. The other container format option is MPEG_TS.
HLS has supported MPEG TS chunks since it was released and is sometimes the only supported packaging on
older HLS players. MPEG TS typically has a 5-25 percent packaging overhead. This means MPEG TS typically
requires 5-25 percent more bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
ContainerFormatpublic GetHLSStreamingSessionURLRequest withContainerFormat(String containerFormat)
Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging because
there is minimal packaging overhead. The other container format option is MPEG_TS. HLS has supported
MPEG TS chunks since it was released and is sometimes the only supported packaging on older HLS players. MPEG TS
typically has a 5-25 percent packaging overhead. This means MPEG TS typically requires 5-25 percent more
bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
containerFormat - Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging
because there is minimal packaging overhead. The other container format option is MPEG_TS.
HLS has supported MPEG TS chunks since it was released and is sometimes the only supported packaging on
older HLS players. MPEG TS typically has a 5-25 percent packaging overhead. This means MPEG TS typically
requires 5-25 percent more bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
ContainerFormatpublic GetHLSStreamingSessionURLRequest withContainerFormat(ContainerFormat containerFormat)
Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging because
there is minimal packaging overhead. The other container format option is MPEG_TS. HLS has supported
MPEG TS chunks since it was released and is sometimes the only supported packaging on older HLS players. MPEG TS
typically has a 5-25 percent packaging overhead. This means MPEG TS typically requires 5-25 percent more
bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
containerFormat - Specifies which format should be used for packaging the media. Specifying the FRAGMENTED_MP4
container format packages the media into MP4 fragments (fMP4 or CMAF). This is the recommended packaging
because there is minimal packaging overhead. The other container format option is MPEG_TS.
HLS has supported MPEG TS chunks since it was released and is sometimes the only supported packaging on
older HLS players. MPEG TS typically has a 5-25 percent packaging overhead. This means MPEG TS typically
requires 5-25 percent more bandwidth and cost than fMP4.
The default is FRAGMENTED_MP4.
ContainerFormatpublic void setDiscontinuityMode(String discontinuityMode)
Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each fragment. This
means that if there is any overlap or gap between fragments (as is typical if HLSFragmentSelector is set
to SERVER_TIMESTAMP), the media player timeline will also have small gaps between fragments in some
places, and will overwrite frames in other places. Gaps in the media player timeline can cause playback to stall
and overlaps can cause playback to be jittery. When there are discontinuity flags between fragments, the media
player is expected to reset the timeline, resulting in the next fragment being played immediately after the
previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It is
recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or overlap of
more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant issue
with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP, and
NEVER when it is set to PRODUCER_TIMESTAMP.
discontinuityMode - Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each
fragment. This means that if there is any overlap or gap between fragments (as is typical if
HLSFragmentSelector is set to SERVER_TIMESTAMP), the media player timeline will also
have small gaps between fragments in some places, and will overwrite frames in other places. Gaps in the
media player timeline can cause playback to stall and overlaps can cause playback to be jittery. When
there are discontinuity flags between fragments, the media player is expected to reset the timeline,
resulting in the next fragment being played immediately after the previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It
is recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or
overlap of more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant
issue with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP
, and NEVER when it is set to PRODUCER_TIMESTAMP.
HLSDiscontinuityModepublic String getDiscontinuityMode()
Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each fragment. This
means that if there is any overlap or gap between fragments (as is typical if HLSFragmentSelector is set
to SERVER_TIMESTAMP), the media player timeline will also have small gaps between fragments in some
places, and will overwrite frames in other places. Gaps in the media player timeline can cause playback to stall
and overlaps can cause playback to be jittery. When there are discontinuity flags between fragments, the media
player is expected to reset the timeline, resulting in the next fragment being played immediately after the
previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It is
recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or overlap of
more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant issue
with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP, and
NEVER when it is set to PRODUCER_TIMESTAMP.
Media players typically build a timeline of media content to play, based on the timestamps of each
fragment. This means that if there is any overlap or gap between fragments (as is typical if
HLSFragmentSelector is set to SERVER_TIMESTAMP), the media player timeline will also
have small gaps between fragments in some places, and will overwrite frames in other places. Gaps in the
media player timeline can cause playback to stall and overlaps can cause playback to be jittery. When
there are discontinuity flags between fragments, the media player is expected to reset the timeline,
resulting in the next fragment being played immediately after the previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist.
It is recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or
overlap of more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant
issue with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to
SERVER_TIMESTAMP, and NEVER when it is set to PRODUCER_TIMESTAMP.
HLSDiscontinuityModepublic GetHLSStreamingSessionURLRequest withDiscontinuityMode(String discontinuityMode)
Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each fragment. This
means that if there is any overlap or gap between fragments (as is typical if HLSFragmentSelector is set
to SERVER_TIMESTAMP), the media player timeline will also have small gaps between fragments in some
places, and will overwrite frames in other places. Gaps in the media player timeline can cause playback to stall
and overlaps can cause playback to be jittery. When there are discontinuity flags between fragments, the media
player is expected to reset the timeline, resulting in the next fragment being played immediately after the
previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It is
recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or overlap of
more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant issue
with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP, and
NEVER when it is set to PRODUCER_TIMESTAMP.
discontinuityMode - Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each
fragment. This means that if there is any overlap or gap between fragments (as is typical if
HLSFragmentSelector is set to SERVER_TIMESTAMP), the media player timeline will also
have small gaps between fragments in some places, and will overwrite frames in other places. Gaps in the
media player timeline can cause playback to stall and overlaps can cause playback to be jittery. When
there are discontinuity flags between fragments, the media player is expected to reset the timeline,
resulting in the next fragment being played immediately after the previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It
is recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or
overlap of more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant
issue with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP
, and NEVER when it is set to PRODUCER_TIMESTAMP.
HLSDiscontinuityModepublic GetHLSStreamingSessionURLRequest withDiscontinuityMode(HLSDiscontinuityMode discontinuityMode)
Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each fragment. This
means that if there is any overlap or gap between fragments (as is typical if HLSFragmentSelector is set
to SERVER_TIMESTAMP), the media player timeline will also have small gaps between fragments in some
places, and will overwrite frames in other places. Gaps in the media player timeline can cause playback to stall
and overlaps can cause playback to be jittery. When there are discontinuity flags between fragments, the media
player is expected to reset the timeline, resulting in the next fragment being played immediately after the
previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It is
recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or overlap of
more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant issue
with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP, and
NEVER when it is set to PRODUCER_TIMESTAMP.
discontinuityMode - Specifies when flags marking discontinuities between fragments are added to the media playlists.
Media players typically build a timeline of media content to play, based on the timestamps of each
fragment. This means that if there is any overlap or gap between fragments (as is typical if
HLSFragmentSelector is set to SERVER_TIMESTAMP), the media player timeline will also
have small gaps between fragments in some places, and will overwrite frames in other places. Gaps in the
media player timeline can cause playback to stall and overlaps can cause playback to be jittery. When
there are discontinuity flags between fragments, the media player is expected to reset the timeline,
resulting in the next fragment being played immediately after the previous fragment.
The following modes are supported:
ALWAYS: a discontinuity marker is placed between every fragment in the HLS media playlist. It
is recommended to use a value of ALWAYS if the fragment timestamps are not accurate.
NEVER: no discontinuity markers are placed anywhere. It is recommended to use a value of
NEVER to ensure the media player timeline most accurately maps to the producer timestamps.
ON_DISCONTINUITY: a discontinuity marker is placed between fragments that have a gap or
overlap of more than 50 milliseconds. For most playback scenarios, it is recommended to use a value of
ON_DISCONTINUITY so that the media player timeline is only reset when there is a significant
issue with the media timeline (e.g. a missing fragment).
The default is ALWAYS when HLSFragmentSelector is set to SERVER_TIMESTAMP
, and NEVER when it is set to PRODUCER_TIMESTAMP.
HLSDiscontinuityModepublic void setDisplayFragmentTimestamp(String displayFragmentTimestamp)
Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically, media players report the playhead position as a time relative to the start of the first fragment in the playback session. However, when the start timestamps are included in the HLS media playlist, some media players might report the current playhead as an absolute time based on the fragment timestamps. This can be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
displayFragmentTimestamp - Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically,
media players report the playhead position as a time relative to the start of the first fragment in the
playback session. However, when the start timestamps are included in the HLS media playlist, some media
players might report the current playhead as an absolute time based on the fragment timestamps. This can
be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
HLSDisplayFragmentTimestamppublic String getDisplayFragmentTimestamp()
Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically, media players report the playhead position as a time relative to the start of the first fragment in the playback session. However, when the start timestamps are included in the HLS media playlist, some media players might report the current playhead as an absolute time based on the fragment timestamps. This can be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
HLSDisplayFragmentTimestamppublic GetHLSStreamingSessionURLRequest withDisplayFragmentTimestamp(String displayFragmentTimestamp)
Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically, media players report the playhead position as a time relative to the start of the first fragment in the playback session. However, when the start timestamps are included in the HLS media playlist, some media players might report the current playhead as an absolute time based on the fragment timestamps. This can be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
displayFragmentTimestamp - Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically,
media players report the playhead position as a time relative to the start of the first fragment in the
playback session. However, when the start timestamps are included in the HLS media playlist, some media
players might report the current playhead as an absolute time based on the fragment timestamps. This can
be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
HLSDisplayFragmentTimestamppublic GetHLSStreamingSessionURLRequest withDisplayFragmentTimestamp(HLSDisplayFragmentTimestamp displayFragmentTimestamp)
Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically, media players report the playhead position as a time relative to the start of the first fragment in the playback session. However, when the start timestamps are included in the HLS media playlist, some media players might report the current playhead as an absolute time based on the fragment timestamps. This can be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
displayFragmentTimestamp - Specifies when the fragment start timestamps should be included in the HLS media playlist. Typically,
media players report the playhead position as a time relative to the start of the first fragment in the
playback session. However, when the start timestamps are included in the HLS media playlist, some media
players might report the current playhead as an absolute time based on the fragment timestamps. This can
be useful for creating a playback experience that shows viewers the wall-clock time of the media.
The default is NEVER. When HLSFragmentSelector is SERVER_TIMESTAMP, the
timestamps will be the server start timestamps. Similarly, when HLSFragmentSelector is
PRODUCER_TIMESTAMP, the timestamps will be the producer start timestamps.
HLSDisplayFragmentTimestamppublic void setExpires(Integer expires)
The time in seconds until the requested session expires. This value can be between 300 (5 minutes) and 43200 (12 hours).
When a session expires, no new calls to GetHLSMasterPlaylist, GetHLSMediaPlaylist,
GetMP4InitFragment, GetMP4MediaFragment, or GetTSFragment can be made for
that session.
The default is 300 (5 minutes).
expires - The time in seconds until the requested session expires. This value can be between 300 (5 minutes) and
43200 (12 hours).
When a session expires, no new calls to GetHLSMasterPlaylist,
GetHLSMediaPlaylist, GetMP4InitFragment, GetMP4MediaFragment, or
GetTSFragment can be made for that session.
The default is 300 (5 minutes).
public Integer getExpires()
The time in seconds until the requested session expires. This value can be between 300 (5 minutes) and 43200 (12 hours).
When a session expires, no new calls to GetHLSMasterPlaylist, GetHLSMediaPlaylist,
GetMP4InitFragment, GetMP4MediaFragment, or GetTSFragment can be made for
that session.
The default is 300 (5 minutes).
When a session expires, no new calls to GetHLSMasterPlaylist,
GetHLSMediaPlaylist, GetMP4InitFragment, GetMP4MediaFragment, or
GetTSFragment can be made for that session.
The default is 300 (5 minutes).
public GetHLSStreamingSessionURLRequest withExpires(Integer expires)
The time in seconds until the requested session expires. This value can be between 300 (5 minutes) and 43200 (12 hours).
When a session expires, no new calls to GetHLSMasterPlaylist, GetHLSMediaPlaylist,
GetMP4InitFragment, GetMP4MediaFragment, or GetTSFragment can be made for
that session.
The default is 300 (5 minutes).
expires - The time in seconds until the requested session expires. This value can be between 300 (5 minutes) and
43200 (12 hours).
When a session expires, no new calls to GetHLSMasterPlaylist,
GetHLSMediaPlaylist, GetMP4InitFragment, GetMP4MediaFragment, or
GetTSFragment can be made for that session.
The default is 300 (5 minutes).
public void setMaxMediaPlaylistFragmentResults(Long maxMediaPlaylistFragmentResults)
The maximum number of fragments that are returned in the HLS media playlists.
When the PlaybackMode is LIVE, the most recent fragments are returned up to this value.
When the PlaybackMode is ON_DEMAND, the oldest fragments are returned, up to this
maximum number.
When there are a higher number of fragments available in a live HLS media playlist, video players often buffer content before starting playback. Increasing the buffer size increases the playback latency, but it decreases the likelihood that rebuffering will occur during playback. We recommend that a live HLS media playlist have a minimum of 3 fragments and a maximum of 10 fragments.
The default is 5 fragments if PlaybackMode is LIVE or LIVE_REPLAY, and
1,000 if PlaybackMode is ON_DEMAND.
The maximum value of 5,000 fragments corresponds to more than 80 minutes of video on streams with 1-second fragments, and more than 13 hours of video on streams with 10-second fragments.
maxMediaPlaylistFragmentResults - The maximum number of fragments that are returned in the HLS media playlists.
When the PlaybackMode is LIVE, the most recent fragments are returned up to this
value. When the PlaybackMode is ON_DEMAND, the oldest fragments are returned, up
to this maximum number.
When there are a higher number of fragments available in a live HLS media playlist, video players often buffer content before starting playback. Increasing the buffer size increases the playback latency, but it decreases the likelihood that rebuffering will occur during playback. We recommend that a live HLS media playlist have a minimum of 3 fragments and a maximum of 10 fragments.
The default is 5 fragments if PlaybackMode is LIVE or LIVE_REPLAY,
and 1,000 if PlaybackMode is ON_DEMAND.
The maximum value of 5,000 fragments corresponds to more than 80 minutes of video on streams with 1-second fragments, and more than 13 hours of video on streams with 10-second fragments.
public Long getMaxMediaPlaylistFragmentResults()
The maximum number of fragments that are returned in the HLS media playlists.
When the PlaybackMode is LIVE, the most recent fragments are returned up to this value.
When the PlaybackMode is ON_DEMAND, the oldest fragments are returned, up to this
maximum number.
When there are a higher number of fragments available in a live HLS media playlist, video players often buffer content before starting playback. Increasing the buffer size increases the playback latency, but it decreases the likelihood that rebuffering will occur during playback. We recommend that a live HLS media playlist have a minimum of 3 fragments and a maximum of 10 fragments.
The default is 5 fragments if PlaybackMode is LIVE or LIVE_REPLAY, and
1,000 if PlaybackMode is ON_DEMAND.
The maximum value of 5,000 fragments corresponds to more than 80 minutes of video on streams with 1-second fragments, and more than 13 hours of video on streams with 10-second fragments.
When the PlaybackMode is LIVE, the most recent fragments are returned up to
this value. When the PlaybackMode is ON_DEMAND, the oldest fragments are
returned, up to this maximum number.
When there are a higher number of fragments available in a live HLS media playlist, video players often buffer content before starting playback. Increasing the buffer size increases the playback latency, but it decreases the likelihood that rebuffering will occur during playback. We recommend that a live HLS media playlist have a minimum of 3 fragments and a maximum of 10 fragments.
The default is 5 fragments if PlaybackMode is LIVE or LIVE_REPLAY,
and 1,000 if PlaybackMode is ON_DEMAND.
The maximum value of 5,000 fragments corresponds to more than 80 minutes of video on streams with 1-second fragments, and more than 13 hours of video on streams with 10-second fragments.
public GetHLSStreamingSessionURLRequest withMaxMediaPlaylistFragmentResults(Long maxMediaPlaylistFragmentResults)
The maximum number of fragments that are returned in the HLS media playlists.
When the PlaybackMode is LIVE, the most recent fragments are returned up to this value.
When the PlaybackMode is ON_DEMAND, the oldest fragments are returned, up to this
maximum number.
When there are a higher number of fragments available in a live HLS media playlist, video players often buffer content before starting playback. Increasing the buffer size increases the playback latency, but it decreases the likelihood that rebuffering will occur during playback. We recommend that a live HLS media playlist have a minimum of 3 fragments and a maximum of 10 fragments.
The default is 5 fragments if PlaybackMode is LIVE or LIVE_REPLAY, and
1,000 if PlaybackMode is ON_DEMAND.
The maximum value of 5,000 fragments corresponds to more than 80 minutes of video on streams with 1-second fragments, and more than 13 hours of video on streams with 10-second fragments.
maxMediaPlaylistFragmentResults - The maximum number of fragments that are returned in the HLS media playlists.
When the PlaybackMode is LIVE, the most recent fragments are returned up to this
value. When the PlaybackMode is ON_DEMAND, the oldest fragments are returned, up
to this maximum number.
When there are a higher number of fragments available in a live HLS media playlist, video players often buffer content before starting playback. Increasing the buffer size increases the playback latency, but it decreases the likelihood that rebuffering will occur during playback. We recommend that a live HLS media playlist have a minimum of 3 fragments and a maximum of 10 fragments.
The default is 5 fragments if PlaybackMode is LIVE or LIVE_REPLAY,
and 1,000 if PlaybackMode is ON_DEMAND.
The maximum value of 5,000 fragments corresponds to more than 80 minutes of video on streams with 1-second fragments, and more than 13 hours of video on streams with 10-second fragments.
public String toString()
toString in class ObjectObject.toString()public GetHLSStreamingSessionURLRequest clone()
clone in class AmazonWebServiceRequestCopyright © 2021. All rights reserved.