getDASHStreamingSessionURL method
- DASHFragmentSelector? dASHFragmentSelector,
- DASHDisplayFragmentNumber? displayFragmentNumber,
- DASHDisplayFragmentTimestamp? displayFragmentTimestamp,
- int? expires,
- int? maxManifestFragmentResults,
- DASHPlaybackMode? playbackMode,
- String? streamARN,
- String? streamName,
Retrieves an MPEG Dynamic Adaptive Streaming over HTTP (DASH) URL for the stream. You can then open the URL in a media player to view the stream contents.
Both the StreamName
and the StreamARN
parameters
are optional, but you must specify either the StreamName
or
the StreamARN
when invoking this API operation.
An Amazon Kinesis video stream has the following requirements for providing data through MPEG-DASH:
-
The media must contain h.264 or h.265 encoded video and, optionally, AAC
or G.711 encoded audio. Specifically, the codec ID of track 1 should be
V_MPEG/ISO/AVC
(for h.264) or V_MPEGH/ISO/HEVC (for H.265). Optionally, the codec ID of track 2 should beA_AAC
(for AAC) or A_MS/ACM (for G.711). - Data retention must be greater than 0.
- The video track of each fragment must contain codec private data in the Advanced Video Coding (AVC) for H.264 format and HEVC for H.265 format. For more information, see MPEG-4 specification ISO/IEC 14496-15. For information about adapting stream data to a given format, see NAL Adaptation Flags.
- The audio track (if present) of each fragment must contain codec private data in the AAC format (AAC specification ISO/IEC 13818-7) or the MS Wave format.
-
Get an endpoint using GetDataEndpoint,
specifying
GET_DASH_STREAMING_SESSION_URL
for theAPIName
parameter. -
Retrieve the MPEG-DASH URL using
GetDASHStreamingSessionURL
. Kinesis Video Streams creates an MPEG-DASH streaming session to be used for accessing content in a stream using the MPEG-DASH protocol.GetDASHStreamingSessionURL
returns an authenticated URL (that includes an encrypted session token) for the session's MPEG-DASH manifest (the root resource needed for streaming with MPEG-DASH). The media that is made available through the manifest consists only of the requested stream, time range, and format. No other media data (such as frames outside the requested window or alternate bitrates) is made available. - Provide the URL (containing the encrypted session token) for the MPEG-DASH manifest to a media player that supports the MPEG-DASH protocol. Kinesis Video Streams makes the initialization fragment and media fragments available through the manifest URL. The initialization fragment contains the codec private data for the stream, and other data needed to set up the video or audio decoder and renderer. The media fragments contain encoded video frames or encoded audio samples.
-
The media player receives the authenticated URL and requests stream
metadata and media data normally. When the media player requests data, it
calls the following actions:
- GetDASHManifest: Retrieves an MPEG DASH manifest, which contains the metadata for the media that you want to playback.
-
GetMP4InitFragment: Retrieves the MP4 initialization fragment. The
media player typically loads the initialization fragment before loading
any media fragments. This fragment contains the "
fytp
" and "moov
" MP4 atoms, and the child atoms that are needed to initialize the media player decoder.The initialization fragment does not correspond to a fragment in a Kinesis video stream. It contains only the codec private data for the stream and respective track, which the media player needs to decode the media frames.
-
GetMP4MediaFragment: Retrieves MP4 media fragments. These fragments
contain the "
moof
" and "mdat
" MP4 atoms and their child atoms, containing the encoded fragment's media frames and their timestamps. Data retrieved with this action is billable. See Pricing for details.
GetMP4MediaFragment.OutgoingBytes
Amazon
CloudWatch metric. For information about using CloudWatch to monitor
Kinesis Video Streams, see Monitoring
Kinesis Video Streams. For pricing information, see Amazon
Kinesis Video Streams Pricing and AWS Pricing. Charges for both
HLS sessions and outgoing AWS data apply.
For more information about HLS, see HTTP Live Streaming on the Apple Developer site.
-
x-amz-ErrorType
HTTP header – contains a more specific error type in addition to what the HTTP status code provides. -
x-amz-RequestId
HTTP header – if you want to report an issue to AWS, the support team can better diagnose the problem if given the Request Id.
For more information, see the Errors section at the bottom of this topic, as well as Common Errors.
May throw ResourceNotFoundException. May throw InvalidArgumentException. May throw ClientLimitExceededException. May throw NotAuthorizedException. May throw UnsupportedStreamMediaTypeException. May throw NoDataRetentionException. May throw MissingCodecPrivateDataException. May throw InvalidCodecPrivateDataException.
Parameter dASHFragmentSelector
:
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.
Parameter displayFragmentNumber
:
Fragments are identified in the manifest file based on their sequence
number in the session. If DisplayFragmentNumber is set to
ALWAYS
, the Kinesis Video Streams fragment number is added to
each S element in the manifest file with the attribute name “kvs:fn”.
These fragment numbers can be used for logging or for use with other APIs
(e.g. GetMedia
and GetMediaForFragmentList
). A
custom MPEG-DASH media player is necessary to leverage these this custom
attribute.
The default value is NEVER
.
Parameter displayFragmentTimestamp
:
Per the MPEG-DASH specification, the wall-clock time of fragments in the
manifest file can be derived using attributes in the manifest itself.
However, typically, MPEG-DASH compatible media players do not properly
handle gaps in the media timeline. Kinesis Video Streams adjusts the media
timeline in the manifest file to enable playback of media with
discontinuities. Therefore, the wall-clock time derived from the manifest
file may be inaccurate. If DisplayFragmentTimestamp is set to
ALWAYS
, the accurate fragment timestamp is added to each S
element in the manifest file with the attribute name “kvs:ts”. A custom
MPEG-DASH media player is necessary to leverage this custom attribute.
The default value is NEVER
. When DASHFragmentSelector
is SERVER_TIMESTAMP
, the timestamps will be the server start
timestamps. Similarly, when DASHFragmentSelector is
PRODUCER_TIMESTAMP
, the timestamps will be the producer start
timestamps.
Parameter 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 GetDashManifest
,
GetMP4InitFragment
, or GetMP4MediaFragment
can
be made for that session.
The default is 300 (5 minutes).
Parameter maxManifestFragmentResults
:
The maximum number of fragments that are returned in the MPEG-DASH
manifest.
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 MPEG-DASH
manifest, 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 MPEG-DASH manifest 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 1,000 fragments corresponds to more than 16 minutes
of video on streams with 1-second fragments, and more than 2 1/2 hours of
video on streams with 10-second fragments.
Parameter 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 MPEG-DASH
manifest is continually updated with the latest fragments as they become
available. We recommend that the media player retrieve a new manifest 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.
-
LIVE_REPLAY
: For sessions of this type, the
MPEG-DASH manifest 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 manifest 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 MPEG-DASH
manifest contains all the fragments for the session, up to the number that
is specified in MaxMediaPlaylistFragmentResults
. The manifest
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 larger fragment number
(that is, the newer fragment) is included in the MPEG-DASH manifest. The
other fragments are not included. Fragments that have different timestamps
but have overlapping durations are still included in the MPEG-DASH
manifest. This can lead to unexpected behavior in the media player.
The default is LIVE
.
Parameter streamARN
:
The Amazon Resource Name (ARN) of the stream for which to retrieve the
MPEG-DASH manifest URL.
You must specify either the StreamName
or the
StreamARN
.
Parameter streamName
:
The name of the stream for which to retrieve the MPEG-DASH manifest URL.
You must specify either the StreamName
or the
StreamARN
.
Implementation
Future<GetDASHStreamingSessionURLOutput> getDASHStreamingSessionURL({
DASHFragmentSelector? dASHFragmentSelector,
DASHDisplayFragmentNumber? displayFragmentNumber,
DASHDisplayFragmentTimestamp? displayFragmentTimestamp,
int? expires,
int? maxManifestFragmentResults,
DASHPlaybackMode? playbackMode,
String? streamARN,
String? streamName,
}) async {
_s.validateNumRange(
'expires',
expires,
300,
43200,
);
_s.validateNumRange(
'maxManifestFragmentResults',
maxManifestFragmentResults,
1,
1000,
);
_s.validateStringLength(
'streamARN',
streamARN,
1,
1024,
);
_s.validateStringLength(
'streamName',
streamName,
1,
256,
);
final $payload = <String, dynamic>{
if (dASHFragmentSelector != null)
'DASHFragmentSelector': dASHFragmentSelector,
if (displayFragmentNumber != null)
'DisplayFragmentNumber': displayFragmentNumber.toValue(),
if (displayFragmentTimestamp != null)
'DisplayFragmentTimestamp': displayFragmentTimestamp.toValue(),
if (expires != null) 'Expires': expires,
if (maxManifestFragmentResults != null)
'MaxManifestFragmentResults': maxManifestFragmentResults,
if (playbackMode != null) 'PlaybackMode': playbackMode.toValue(),
if (streamARN != null) 'StreamARN': streamARN,
if (streamName != null) 'StreamName': streamName,
};
final response = await _protocol.send(
payload: $payload,
method: 'POST',
requestUri: '/getDASHStreamingSessionURL',
exceptionFnMap: _exceptionFns,
);
return GetDASHStreamingSessionURLOutput.fromJson(response);
}