Readers affected Sample Clauses
The 'Readers affected' clause identifies which individuals or groups are impacted by the terms, obligations, or rights set out in the agreement. In practice, this clause may specify whether the contract applies to employees, contractors, customers, or other stakeholders, clarifying the scope of its reach. Its core function is to ensure clarity about who is bound by or benefits from the agreement, thereby preventing misunderstandings or disputes regarding the contract's applicability.
Readers affected. None of the implementations covered in this section support variable-size packets.
Readers affected. None of the implementations covered in this section are guaranteed to support non-consecutive ordering of payloads and media objects.
Readers affected. All of the Microsoft products covered in this section can play content whether or not this guideline is followed. However, unless the guideline is followed, editing the content’s metadata in products build on any versions of the Windows Media Format SDK before 9 Series will result in permanently corrupted content.
Readers affected. The presence of multiple independent audio or video streams is supported only by the components of Windows Media 9 Series. Following this guideline ▇▇▇▇ ▇▇▇▇ all but one stream for each media type from previous version of Windows Media technologies.
Readers affected. The ability to create and recognize mutually exclusive relationships between groups of streams is supported only by the components of Windows Media 9 Series. Following this guideline ▇▇▇▇ ▇▇▇▇ the streams in all but one group (“record”) from previous versions of Windows Media technologies.
Readers affected. As already mentioned, this guideline points out how ―unknown‖ stream IDs in the payloads affect the performance of Windows Media Services 4.1.
Readers affected. None of the implementations covered in this section are guaranteed to support packet sizes larger than 64 KB.
8.2.15 Padding length must be accurate
8.2.15.1 Guideline The Padding length field in the packet parsing section of an ASF packet shall accurately reflect the amount of padding at the end of the packet. However, as noted in section 5.2.2, ASF reader implementations should be prepared to handle cases when this value is zero and to infer the correct value from the size of the payloads.
8.2.15.2 ASF objects affected This guideline pertains to the packets in the Data Object.
8.2.15.3 Readers affected None of the implementations covered in this section are guaranteed to be able to handle inaccurate Padding length values for on-disk ASF content, and therefore ASF writer implementations should always set the Padding length field correctly. Windows Media Services is known to create and send packets with the Padding length equal to zero, and therefore ASF reader implementations should be able to parse such packets.
8.2.16 Ordering of payloads and media objects in packets
8.2.16.1 Guideline Presentation times in payloads of a single media object should be the same and presentation times of media objects should only increase. The associated object ids in payloads of a single media object should be the same and object ids of media objects should be incremental without gaps unless there is a discontinuity and/or object id wrap around.
8.2.16.2 ASF Objects affected This guideline pertains to the packets in the Data Object.
Readers affected. All implementations covered in this section prior to the components of Windows Media 9 Series recognize only the Simple Index Object. • Any content with any index objects besides the Simple Index Object(s) cannot be opened by Windows Media Services 4.1. It is also known that certain earlier ASF implementations on devices cannot handle index objects besides the Simple Index Object(s) (for more information, see section 8.2.11). • The Windows Media Format 7 SDK requires that the Index Objects be followed by at least one Simple Index Object.
Readers affected. All implementations covered in this section prior to the components of Windows Media 9 Series recognize only the Simple Index Object. Any content with any index objects besides the Simple Index Object(s) cannot be opened by Windows Media Services 4.1. It is also known that certain earlier ASF implementations on devices cannot handle index objects besides the Simple Index Object(s) (for more information, see section 8.2.11). The Windows Media Format 7 SDK requires that the Index Objects be followed by at least one Simple Index Object. The Windows Media Format 9 SDK and later require the presence of the NumberOfFrames attribute in addtion to a Frame Index Object to perform frame-based seeking in a specified piece of content.
Readers affected. None of the implementations covered in this section are guaranteed to support packet sizes larger than 64 KB.