Emby Emby Emby Learn
  • Emby Home
  • Video
  • Audio
  • Media Files
    • Subtitles and captions
    • Photos and images
    • Metadata and discovery
    • Libraries and media collections
    • Playback and streaming
    • Media hardware acceleration
    • Displays and AV connections
    • Live TV and recording
  1. Emby Learn
  2. Media files and containers
  3. Common containers
  4. ASF
Search Results for

    Show / Hide Table of Contents

    ASF Container

    Advanced Systems Format stores synchronized audio, video, and metadata in an object-based container associated with Windows Media.

    The Windows Media file extensions WMV and WMA often sit above an ASF package. Advanced Systems Format stores descriptions, timed media packets, and optional navigation as identified objects.

    ASF objects begin with a GUID identifying their kind and a size indicating their extent. A reader can recognize the descriptions it implements and use the object size to navigate through the structure.

    Top-level object What the reader obtains
    Header File properties, stream descriptions, and optional metadata
    Data Encoded media in packets
    Index objects Time-based access to packet positions

    Initialize, then deliver packets

    The Header appears first and describes the source and its streams. The stream properties identify the media representations and setup needed to decode them. Global properties include information such as packet counts, size conventions, and duration.

    The Data object follows. Its packets have parsing information and payloads associated with one or more streams. Packet presentation timing helps organize their delivery. A reader routes the appropriate payloads to video or audio decoding rather than asking a decoder to consume ASF object headers.

    This separation explains a readable Windows Media file whose picture still needs conversion for an Emby app: the server can identify the ASF structure and its codec, while the receiving framework may need a different encoded representation or package.

    How a later position is found

    An index can map a requested time to a useful packet position. Without appropriate index information, finding that time can involve more reading or scanning. Sequential playback and fast random access consequently exercise different parts of the same package.

    A new mux can change the packet organization, timing description, and navigation while copying suitable encoded media. Descriptive tags require their own destination representation. The copied codec name describes the media branch, not every ASF object retained by the output.

    Recognized content and protected content

    ASF can also describe content-protection information. Recognition lets software explain what kind of resource it has encountered; obtaining usable media may additionally require an authorized decryption path. An object parser or a new filename does not supply that authorization.

    For an older collection, follow this sequence: Header interpretation, Data reading, source decoding, and the particular output needed. It places a failure at an actual boundary instead of attributing it broadly to “Windows Media.”

    See Also

    • Containers and Codecs
    • Packet Timestamps
    • Container Indexes and Seeking

    References

    • Microsoft: ASF file structure
    • Microsoft ASF Specification 1.20.06: archived download catalogue
    On this Page
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top