Lines Matching full:container
76 and implementation of the Ogg container format. If you're new to Ogg
79 give distilled technical descriptions and references of the container
82 <h2>Container format design points</h2>
84 <p>Ogg is intended to be a simplest-possible container, concerned only
87 implementing a more complex, non-linear container (for example, see
91 <p>The Ogg container is not intended to be a monolithic
102 the Ogg container itself. Metadata is thus compartmentalized and
105 complete-enough metadata set should be. In this way, the container and
106 container implementation are isolated from unnecessary design flux.
110 <p>The Ogg container is primarily a streaming format,
117 no container feature requires nonlinear access of the bitstream.
125 optional or additional container features. There is no optimal
135 <p>Ogg is a byte-aligned container with no context-dependent, optional
265 duration, etc, do not appear in the Ogg container. The mux layer is,
271 the required metadata into the container itself, this strategy
272 increases container specification complexity, fragility, and rigidity.
275 container hasn't already provided for. New codecs are harder to
279 mechanism into the container layer to mark what frames to skip
291 <p>The Ogg container itself does not define a metadata system for
293 types in a muxed stream. That is, the Ogg container itself does not
296 is stored in the Ogg container rather than being built into the Ogg
297 container. Xiph specifies the 'Skeleton' metadata format for Ogg
298 streams, but this decoupling of container and stream structure
300 specification without altering the container itself, or without stream
