RIFF Multimedia Movie - Revision history

Jsummers: /* Structure */

2024-05-09T15:07:46Z

‎Structure

Jsummers at 23:33, 28 April 2024

2024-04-28T23:33:04Z

Jsummers at 23:21, 28 April 2024

2024-04-28T23:21:10Z

Jsummers: Category->Animation

2024-04-25T19:55:01Z

Category->Animation

Sembiance: /* Software */

2024-04-17T02:21:55Z

‎Software

Jsummers at 15:09, 12 April 2024

2024-04-12T15:09:00Z

Sembiance: /* Sample files */

2024-02-16T03:35:43Z

‎Sample files

Sembiance: /* Sample files */

2022-03-07T19:22:50Z

‎Sample files

Sembiance: /* Sample files */

2020-07-26T20:31:35Z

‎Sample files

Sembiance: /* Sample files */

2020-05-26T21:11:33Z

‎Sample files

@@ Line 30: / Line 30: @@
 A single section's record in the file consists of:
-* [[FourCC|The 4-byte chunk/section type identifier, normal for RIFF.]] In RMPP, these are restricted to lowercase ASCII.
+* [[FourCC|The 4-byte chunk/section type identifier]], normal for RIFF.
 * A 4-byte integer recording the length of the chunk data, which, due to the next element in this list, amounts to the length of the section data in bytes plus four
 * A 4-byte "resource ID", whose use possibly depends on the chunk type.
 * In many cases the resource ID is followed by a "name" field in the form of a length-prefixed string, plus a padding byte if needed to make the field length an even number. This is usually just an empty string.
 * The section data itself
-* Possible a padding byte, if the next section would otherwise begin at an offset not divisible by two, unless the preceding section is the last in the file. This is normal for RIFF.
+* Possibly a padding byte, if the next section would otherwise begin at an offset not divisible by two, unless the preceding section is the last in the file. This is normal for RIFF.
 To summarize, RMMP "sections" are RIFF chunks with the first four bytes occupied by a "resource ID".
-The first section in an RMMP file is the table of contents, with type "cftc".
+The first section in an RMMP file is the table of contents, with type "cftc" or "CFTC".
 The individual sections that may appear in an RMMP file which have been at least partially decoded are listed below.
@@ Line 54: / Line 54: @@
 ==== "dib " ====
-This section holds a DIB-like (see [[BMP]]) image, preceded by 2 zero bytes. It is possible that the image may stored with its rows reversed in order, or this may just be an oddity of test data.
+This section holds a DIB-like (see [[BMP]]) image, preceded by 2 zero bytes. Bi-level images nostandard, though -- the row order is reversed, and the padding is different. The resource ID of dib sections starts at 1024 and increments by 1 for each subsequent dib section, or occasionally for non-dib sections.
 The resource ID of dib sections starts at 1024 and increments by 1 for each subsequent dib section, or occasionally for non-dib sections.
 The DIB lacks a color table, even though it has 8 or fewer bits per pixel (which would usually necessitate one).

@@ Line 26: / Line 26: @@
 As usual for the RIFF format, the RMMP file is organized into several "subchunks" of the RIFF chunk. However, unlike other RIFF types, there is no LIST chunk, and all chunks strictly follow a set of additions to the RIFF chunk definition here unofficially called "section" for clarity.
 A single section's record in the file consists of:
 * [[FourCC|The 4-byte chunk/section type identifier, normal for RIFF.]] In RMPP, these are restricted to lowercase ASCII.
 * A 4-byte integer recording the length of the chunk data, which, due to the next element in this list, amounts to the length of the section data in bytes plus four
-* A 4-byte value of unclear or possibly various use, here called the "sequence number"
+* A 4-byte "resource ID", whose use possibly depends on the chunk type.
 * The section data itself
 * Possible a padding byte, if the next section would otherwise begin at an offset not divisible by two, unless the preceding section is the last in the file. This is normal for RIFF.
-To summarize, RMMP "sections" are RIFF chunks with the first four bytes occupied by a "sequence number".
+To summarize, RMMP "sections" are RIFF chunks with the first four bytes occupied by a "resource ID".
 The first section in an RMMP file is the table of contents, with type "cftc".
@@ Line 45: / Line 48: @@
 * The section's typecode (4 bytes)
 * The section's length (4 bytes), with the same caveats as the length in the section itself
-* The section's sequence number (4 bytes)
+* The section's resource ID (4 bytes)
 * The section's absolute offset in the file (4 bytes)
 The RMMP table of contents always seems to be in the actual order of the sections in the file. It often seems to end in an area of zeroes, sized as if it held entries (i.e. its size is a multiple of 16 bytes).
-The cftc section seems to always have sequence number 0.
+The cftc section seems to always have resource ID 0.
 ==== "dib " ====
 This section holds a DIB-like (see [[BMP]]) image, preceded by 2 zero bytes. It is possible that the image may stored with its rows reversed in order, or this may just be an oddity of test data.
-The sequence number of dib sections starts at 1024 and increments by 1 for each subsequent dib section, or occasionally for non-dib sections.
+The resource ID of dib sections starts at 1024 and increments by 1 for each subsequent dib section, or occasionally for non-dib sections.
 The DIB lacks a color table, even though it has 8 or fewer bits per pixel (which would usually necessitate one).
 ==== "str " ====
-As the name indicates, this section type holds string data, specifically, what appears to a title. Its sequence number always appears to be 1024. Its data section consists of:
+As the name indicates, this section type holds string data, specifically, what appears to a title. Its resource ID always appears to be 1024. Its data section consists of:
 * A zero byte
 * A byte of uncertain purpose, always set to 0x54 (84) in the sample data
@@ Line 64: / Line 67: @@
 ==== "ver " ====
-This always seems to be the second section in the file. As the name indicates, probably holds file "version". Its data section consists of two bytes, the first of which is zero, and the second of which seems to vary between values that have no easily apparent meaning and zero, without a clear pattern. It seems more likely that the version of the file is stored in the sequence number, which is always 0x27 (39) in the Microsoft Works sample file linked from this page.
+This always seems to be the second section in the file. As the name indicates, probably holds file "version". Its data section consists of two bytes, the first of which is zero, and the second of which seems to vary between values that have no easily apparent meaning and zero, without a clear pattern. It seems more likely that the version of the file is stored in the resource ID, which is always 0x27 (39) in the Microsoft Works sample file linked from this page.
 ==== "vwac" ====
-This seems to hold text, possibly interface-related. Along with data of an unknown purpose, it contains scattered blocks of text, prefixed by 4-byte [[big endian]] lengths. It always appears to have the sequence number 1024.
+This seems to hold text, possibly interface-related. Along with data of an unknown purpose, it contains scattered blocks of text, prefixed by 4-byte [[big endian]] lengths. It always appears to have the resource ID 1024.
 == Sample files ==
@@ Line 87: / Line 90: @@
 [[Category:RIFF based file formats]]

@@ Line 10: / Line 10: @@
 RIFF RMMP is listed in the original RIFF specification, with the apparently-false claim that it will be described later in the document.
-"MMM" is sometimes said to stand for '''Microsoft Multimedia Movie''', be we could not confirm this.
+MMM is associated with software such as MacroMind Windows Player and Macromedia Director Player, ancestors of [[Shockwave (Director)|Adobe Director]]. It's not completely clear what MMM stands for, but one possibility is '''MacroMind Multimedia Movie'''.
-Many sources claim the format is associated with MacroMind Director 3.x (an ancestor of [[Shockwave (Director)|Adobe Director]]), and that "MMM" stands for '''MacroMind Multimedia Movie'''. Director did have an .MMM format, but we could not confirm that it is this one, and it would have to be reconciled with the reported release dates of MacroMind Director 3 (1989) and RIFF (1991). Note that these sources often misspell Director as "Directory".
+An MMM file is not a self-contained media format, but is a part of a multi-file application composed of a custom .EXE player app, one or more MMM files, and possibly other media files.
-Some sources imply there are two distinct "MMM" formats, though that isn't really consistent with those that say "RIFF RMMP" is a MacroMind format.
+MMM might have only been used on Windows, but some of the applications that use it also have a Mac version. The Mac counterpart to MMM is similar, but based on [[Macintosh resource file|Macintosh resource format]] instead of [[RIFF]].<ref>For example, see [https://archive.org/details/return-to-jurassic-ednovation this CD].
 == Identification ==
@@ Line 81: / Line 82: @@
 * [https://filext.com/file-extension/MMM filext.com .MMM page] - Lists two MMM formats
 * [[Wikipedia: MacroMind]]
 [[Category:RIFF based file formats]]

@@ Line 1: / Line 1: @@
 {{FormatInfo
 |formattype=electronic
-|subcat=Video
+|subcat=Animation
 |extensions={{ext|mmm}}
 |released=~1991

@@ Line 75: / Line 75: @@
 * {{CdTextfiles|cica/cica9308/WIN_NT/MULTIMED/SAMPLES/MMPF.ZIP|MMPF.ZIP}} - Source code (for Windows 3.x) to parse a file. See also the note in {{CdTextfiles|cica/cica9308/WIN_NT/MULTIMED/SAMPLES/DESCRIP.TXT|DESCRIP.TXT}}.
 * [[User:Effect2/readRMPP.c]]
 == Links ==

@@ Line 5: / Line 5: @@
 |released=~1991
 }}
-'''RIFF Multimedia Movie''' (also called '''RIFF RMMP''', '''MMM movie''', etc.) is a [[RIFF]]-based video/animation file format. It is perhaps a predecessor of [[AVI]].
+'''RIFF Multimedia Movie''' (also called '''RIFF RMMP''', '''MMM movie''', etc.) is a [[RIFF]]-based interactive media format, used mainly on Windows 3.x.
 == Discussion ==
@@ Line 73: / Line 73: @@
 == Software ==
 * [[User:Effect2/readRMPP.c]]

@@ Line 70: / Line 70: @@
 == Sample files ==
 * [https://archive.org/details/Microsoft_Works_-_Gateway_2000_Edition_Microsoft_1991 Microsoft Works - Gateway 2000 Edition (Microsoft) (1991)] (CD image from archive.org) → ISO image → *.MMM
-* https://telparia.com/fileFormatSamples/video/riffMultimediaMovie/
+* {{DexvertSamples|video/riffMultimediaMovie}}
 == Software ==