|
DixShtix | |||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
Parsable |
Class Summary | |
ContainerChunk | |
Dump | Dump chunk information about a riff file. |
ExampleABCDE | Create a simple demo RIFF file. |
ExampleHello | The "hello world" program written using RIFFIO. |
FormChunk | |
FourByteConstant | RIFF Chunk-type identifiers. |
GenericChunk | |
InStream | InputStream with pushback facilities for implementing read of nested chunks. |
IOChunk | Low-level IO routines for manipulating RIFF Chunks. |
ListChunk | |
OutStream | Stack-based output for creation of RIFF file streams. |
Parser | Generic reader of RIFF files. |
ToXML | Dump chunk information about a riff file. |
This package is for the manipulation of Resource Interchange File Format (RIFF) Files.
In RIFF files, related data items are groups into "chunks," and related chunks can be combined into "lists." Chunks and lists include their own length within their structure. RIFF files are designed to be upwardly compatible, that is, amenable to future enhancement.
A RIFF file and each of its lists and chunks can be variable in length. A logical definition is required for each RIFF format, to identify which elements are required or optional at each level an the order in which the elements may appear.
RIFF is a binary format, but it is possible to describe a complete RIFF file with an ASCII representation. A structured notation system for representation RIFF files in ASCII is presented in the Microsoft Windows Multimedia Programmer's Reference.
Microsoft Press. "Microsoft Windows Multimedia Programmer's Reference," Redmond, WA, 1991. Telephone: 1-800-MSPRESS, ISBN#1-55615-389-9.
As an example of a proper RIFF file, we have a big-endian RIFX file avever1.nif.
Using Dump
we can obtain partial information
in an ASCII dump format.
avever1_dump.txt.
Using ToXML
we can obtain full information
in an XML dump format.
avever1.xml.
|
DixShtix | |||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |