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 xxxx xxxx all but one stream for each media type from previous version of Windows Media technologies.
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 packet sizes larger than 64 KB.
Readers affected. None of the implementations covered in this section are guaranteed to support non-consecutive ordering of payloads and media objects.
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. 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 xxxx xxxx the streams in all but one group (“record”) from previous versions of Windows Media technologies.
Readers affected. Bit rate mutual exclusion among video streams with different frame sizes is supported only by the components of Windows Media 9 Series. Following this guideline xxxx xxxx the mutual exclusion relationship as well as all but one of the streams from previous versions of Windows Media technologies.
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. 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.
