Last Updated: August 2004
The XMF Meta File Format depends on MMA management of certain ID numbers. This page displays the current state of all MMA-managed IDs in XMF. Developers are encouraged to check this page when planning extensions or new XMF-based format proposals. Developers should refer to the MMA published XMF specifications for all other XMF implementation details.
XMF Meta File Format Version IDs
In all XMF files, the FileHeader structure begins with the 4 1-byte characters "XMF_" followed by the version of the XMF Meta File Format to which the file conforms, also expressed as 4 1-byte characters. To date, the following XMF Meta File Format versions have been defined:
|XMF Meta File Format Version IDs|
|Version ID||Version Name||Defined in RP#||Used in XMF File Types|
|'1.00'||1.00||RP-030||0 & 1 (original)|
|'1.01'||1.01||RP-039||0 & 1 (as revised)|
|'2.00'||2.00||RP-043||2 (Mobile XMF)|
XMF File Type IDs
Most non-proprietary XMF files conform to a particular MMA defined XMF File Type specification, for example "Mobile XMF" or "XMF Type 0" . Every MMA defined XMF File Type specification has a unique File Type ID, including the file Type number and a Revision level within that Type. In the XMF Meta File Format version 1, the XMF FIle Type must appear in a MetaDatItem attached to the RootNode, using the Standard meta-data field "XMF File Type" (FieldID 0). In the XMF Meta File Format version 2, the XMF File Type appears in new fields in the FileHeader structure, immediately following the 4-character XmfMetaFileFormatVersion. To date, the following XMF File Type IDs have been defined:
|XMF File Type IDs|
|File Type ID||Revision Level||File Type Name||Defined in RP|
|0||XMF Type 0||RP-031|
|0||1||XMF Type 0||RP-039|
|1||0||XMF Type 1||RP-031|
|1||1||XMF Type 1||RP-039|
|3||1||Mobile XMF w/Audio Clips||RP-045|
XMF ResourceFormat IDs
In XMF files, every FileNode must include in its NodeMetaData one MetaDataItem indicating the data format of the resource (e.g. SMF, DLS, WAV, etc.), using the Standard meta-data field "Resource Format" (FieldID 3). There are four types of resource format IDs, however only two of them are MMA-administered and shown here: Standard and Registered.
|Standard Resource Format IDs|
|For standard resource formats required by XMF File Type specifications (such as XMF Type 0 & 1, or Mobile XMF), the following set of Standard ResourceFormatIDs have been defined to date. Note that some XMF File Types may not support some or all Standard ResourceFormatIDs.|
|Resource Format ID||Format Name||Defined in RP for XMF File Type|
|Standard MIDI File (SMF) Type 0||0 and 1|
|1||Standard MIDI File (SMF) Type 1||1|
|2||Downloadable Sounds (DLS) v1||0 and 1|
|3*||Downloadable Sounds (DLS) v2||0 and 1|
|4*||Downloadable Sounds (DLS) v2.1||0 and 1|
|5||Mobile DLS||2 (Mobile XMF)|
|* NOTE: XMF players and tools should treat ResourceFormatIDs 3 (DLS 2) and 4 (DLS 2.1) the same, because the only difference between the DLS 2.0 and DLS 2.1 specs is a few error corrections.|
|Registered Resource Format IDs|
To date, no Registered ResourceFormatIDs have been assigned. To apply for one, click here .
In XMF files, any Node may be encoded, such that the use of one or more 'unpacker' operations is required to decode the resource into a playable unencoded format. This information appears in the NodeUnpackers structure. There are four types of unpacker IDs, however only two of them are MMA-administered and shown here: Standard and Registered.
|Standard Unpacker IDs|
|For standard resource formats required by XMF File Type specifications (such as XMF Type 0 & 1, or Mobile XMF), the following set of Standard ResourceFormatIDs have been defined.|
|UnpackerIDs||Unpacker Name||Algorithm Reference|
|1||zlib Decompressor||AMEI/MMA RP-040|
|Registered Unpacker IDs|
To date, no Registered UnpackerIDs have been assigned. To apply for one, click here .