Merge pull request #85095 from johndeu/master

Small edits to timed metadata spec

Author: PRMerger8

articles/media-services/media-services-specifications-live-timed-metadata.md

@@ -143,9 +143,9 @@ Enabling this feature in the RTMP Group will pass SCTE-35 signals to the Adobe R
 The "onCuePoint" message type is defined in [Adobe-Flash-AS] and has the following payload structure when sent from the Elemental Live RTMP output.
 
 
-|Property  |Description  |
+| Property  |Description  |
 |---------|---------|
-|name     | The name SHOULD be '**scte35**' by Elemental Live. |
+|  name     | The name SHOULD be '**scte35**' by Elemental Live. |
 |time     |  The time in seconds at which the cue point occurred in the video file during timeline |
 | type     | The type of cue point SHOULD be set to "**event**". |
 | parameters | A associative array of name/value pair strings containing the information from the SCTE-35 message, including Id and duration. These values are parsed out by Azure Media Services and included in the manifest decoration tag.  |
@@ -164,7 +164,11 @@ received at least four seconds prior to the presentation time will be acted upon
 
 ## 2.2 Fragmented MP4 Ingest (Smooth Streaming)
 
-Refer to [MS-SSTR-Ingest] for requirements on live stream ingest. The following sections provide details regarding ingest of timed presentation metadata.  Timed presentation metadata is ingested as a sparse track, which is defined in both the Live Server Manifest Box (see MS-SSTR) and the Movie Box (‘moov’).  Each sparse fragment consists of a Movie Fragment Box (‘moof’) and Media Data Box (‘mdat’), where the ‘mdat’ box is the binary message.
+Refer to [MS-SSTR-Ingest] for requirements on live stream ingest. The following sections provide details regarding ingest of timed presentation metadata.  Timed presentation metadata is ingested as a sparse track, which is defined in both the Live Server Manifest Box (see MS-SSTR) and the Movie Box (‘moov’).  
+
+Each sparse fragment consists of a Movie Fragment Box (‘moof’) and Media Data Box (‘mdat’), where the ‘mdat’ box is the binary message.
+
+In order to achieve frame-accurate insertion of ads, the encoder MUST split the fragment at the presentation time where the cue is required to be inserted.  A new fragment MUST be created that begins with a newly created IDR frame, or Stream Access Points (SAP) of type 1 or 2, as defined in [ISO-14496-12] Annex I. This allows the Azure Media Packager to properly generate an HLS manifest and a DASH multi-period manifest where the new Period begins at the frame-accurate splice conditioned presentation time.
 
 ### 2.2.1 Live Server Manifest Box
 
@@ -213,6 +217,12 @@ The ‘stsd’ box **SHOULD** contain a MetaDataSampleEntry box with a coding na
 Sparse track fragments consist of a Movie Fragment Box (‘moof’) and a Media Data
 Box (‘mdat’).
 
+> [!NOTE]
+> In order to achieve frame-accurate insertion of ads, the encoder MUST split the fragment at the presentation time where the cue is
+> required to be inserted.  A new fragment MUST be created that begins with a newly created IDR frame, or Stream Access Points (SAP) of
+> type 1 or 2, as defined in [ISO-14496-12] Annex I
+> 
+
 The MovieFragmentBox (‘moof’) box **MUST** contain a
 **TrackFragmentExtendedHeaderBox (‘uuid’)** box as defined in [MS-SSTR] with the
 following fields: