RIFX - Revision history

Jsummers: /* Links */

2016-10-05T20:18:32Z

‎Links

Jsummers at 17:57, 16 January 2016

2016-01-16T17:57:31Z

Jsummers at 17:44, 16 January 2016

2016-01-16T17:44:05Z

Jsummers: Categories

2016-01-13T20:40:54Z

Jsummers: Created page with "{{FormatInfo |formattype=electronic |subcat=Metaformats |released=1991 }} '''RIFX''' is a variant of RIFF that uses big-endian byte order. Note that the [[..."

2016-01-13T20:32:24Z

Created page with "{{FormatInfo |formattype=electronic |subcat=Metaformats |released=1991 }} '''RIFX''' is a variant of RIFF that uses big-endian byte order. Note that the [[..."

New page

{{FormatInfo
|formattype=electronic
|subcat=Metaformats
|released=1991
}}
'''RIFX''' is a variant of [[RIFF]] that uses big-endian [[Endianness|byte order]].

Note that the [[FourCC]] codes used for chunk names and other identifiers have the same order as in RIFF (left-to-right).

== XFIR ==
Evidently, there is also a little-endian variant of RIFX, whose files begin with "XFIR" ("RIFX" backwards). The difference between "XFIR" and RIFF is that in "XFIR", the [[FourCC]] codes are stored in reverse order (right-to-left).

== Identification ==
RIFX files begin with ASCII "{{magic|RIFX}}".

Files that use the "XFIR" variant begin with "{{magic|XFIR}}".

== Links ==
* [http://www.kk.iij4u.or.jp/~kondo/wave/mpidata.txt RIFF specification]
* [http://www.fileformat.info/format/riff/corion_rifx.htm The RIFX File Format] (from Corion.net, via FileFormat.info)

@@ Line 20: / Line 20: @@
 * [http://www.fileformat.info/format/riff/corion_rifx.htm The RIFX File Format] (from Corion.net, via FileFormat.info)
 [[Category:Microsoft]]
 [[Category:IBM]]

@@ Line 17: / Line 17: @@
 == Links ==
-* [http://www.kk.iij4u.or.jp/~kondo/wave/mpidata.txt RIFF specification]
+* Refer to [[RIFF#Specifications]].
 * [http://www.fileformat.info/format/riff/corion_rifx.htm The RIFX File Format] (from Corion.net, via FileFormat.info)

@@ Line 6: / Line 6: @@
 '''RIFX''' is a variant of [[RIFF]] that uses big-endian [[Endianness|byte order]].
-Note that the [[FourCC]] codes used for chunk names and other identifiers have the same order as in RIFF (left-to-right).
+Note that the [[FourCC]] codes used for chunk names and other identifiers, although they are often interpreted as 32-bit integers, are ''not'' reversed. They have the same order as in RIFF (left-to-right).
 == XFIR ==

@@ Line 9: / Line 9: @@
 == XFIR ==
-Evidently, there is also a little-endian variant of RIFX, whose files begin with "XFIR" ("RIFX" backwards). The difference between "XFIR" and RIFF is that in "XFIR", the [[FourCC]] codes are stored in reverse order (right-to-left).
+Evidently, there is also a little-endian variant of RIFX, whose files begin with "XFIR" ("RIFX" backwards). The difference between "XFIR" and RIFF is that in "XFIR", the FourCC codes are stored in reverse order (right-to-left).
 == Identification ==
@@ Line 19: / Line 19: @@
 * [http://www.kk.iij4u.or.jp/~kondo/wave/mpidata.txt RIFF specification]
 * [http://www.fileformat.info/format/riff/corion_rifx.htm The RIFX File Format] (from Corion.net, via FileFormat.info)