Interplay MVE - Revision history

Sembiance: samples

2025-05-14T15:01:12Z

samples

← Older revision		Revision as of 08:01, 14 May 2025
Line 2:		Line 2:
	* Company: [[Interplay Entertainment]]		* Company: [[Interplay Entertainment]]
	* Samples: http://samples.mplayerhq.hu/game-formats/interplay-mve/		* Samples: http://samples.mplayerhq.hu/game-formats/interplay-mve/
			* Samples: {{DexvertSamples\|video/interplayMVE}}
	* Sample Parser: http://multimedia.cx/parse-ipmve.c		* Sample Parser: http://multimedia.cx/parse-ipmve.c

JianHouZi: Added Redneck Rampage Rides Again to list of PC games using MVE files.

2016-07-13T22:14:33Z

Added Redneck Rampage Rides Again to list of PC games using MVE files.

← Older revision		Revision as of 15:14, 13 July 2016
Line 345:		Line 345:
	* [http://www.mobygames.com/game/windows/fallout Fallout]		* [http://www.mobygames.com/game/windows/fallout Fallout]
	* [http://www.mobygames.com/game/windows/of-light-and-darkness-the-prophecy Of Light and Darkness: The Prophecy]		* [http://www.mobygames.com/game/windows/of-light-and-darkness-the-prophecy Of Light and Darkness: The Prophecy]
			* [http://www.mobygames.com/game/dos/redneck-rampage-rides-again Redneck Rampage Rides Again]
	* [http://www.mobygames.com/game/dos/stonekeep Stonekeep]		* [http://www.mobygames.com/game/dos/stonekeep Stonekeep]
	* [http://www.mobygames.com/game/windows/virtual-pool Virtual Pool]		* [http://www.mobygames.com/game/windows/virtual-pool Virtual Pool]

Multimedia Mike: link edits

2008-01-14T21:02:06Z

link edits

← Older revision		Revision as of 14:02, 14 January 2008
Line 1:		Line 1:
	* Extension: mve		* Extension: mve
	* Company: [[Interplay Entertainment]]		* Company: [[Interplay Entertainment]]
	* Samples: http://samples.mplayerhq.hu/game-formats/interplay-mve/]		* Samples: http://samples.mplayerhq.hu/game-formats/interplay-mve/
	* Sample Parser: [http://multimedia.cx/parse-ipmve.c ~~http://multimedia.cx/parse-ipmve.c]~~		* Sample Parser: http://multimedia.cx/parse-ipmve.c

	Interplay MVE is a full motion video format used in a number of PC games published by Interplay. It combines a custom [[Interplay Video\|video codec]] and either [[PCM]] or a [[Interplay DPCM\|custom DPCM]] coding scheme for audio.		Interplay MVE is a full motion video format used in a number of PC games published by Interplay. It combines a custom [[Interplay Video\|video codec]] and either [[PCM]] or a [[Interplay DPCM\|custom DPCM]] coding scheme for audio.

Avenger teambg at 12:53, 12 May 2007

2007-05-12T12:53:00Z

← Older revision		Revision as of 05:53, 12 May 2007
Line 127:		Line 127:
	'''(I think width and height are actually expressed as 8x8 pixel blocks. Need to verify. --[[User:Multimedia Mike\|Multimedia Mike]] 13:52, 5 February 2006 (EST))'''		'''(I think width and height are actually expressed as 8x8 pixel blocks. Need to verify. --[[User:Multimedia Mike\|Multimedia Mike]] 13:52, 5 February 2006 (EST))'''

	Width is the width of the buffer to allocate, and height is the height. Both are given in terms of pixels. Now, the count appears to be used to over-allocate the video buffer. To compute the size to allocate for the video buffer, they take 2 bytes per pixel, and multiply by the height and the width, and then multiply by the count. If scan-line doubling is enabled (which it is not in BG/BG2), it then divides this value by two, on the assumption that there is only enough data for half the resolution. Anyway, the over-allocation may be used to create a larger movie area and pan smoothly or something. I haven't seen a way to use the overallocation with the format details that I've discerned, but the video coding is particularly hairy, as the decoder relies on self-modifying x86 code to function. Yick. Anyway, I'm still in the process of looking for a file that uses over-allocation so that I can figure out exactly why it is used and what it is used for. (Again, this feature doesn't appear to be widely used in the sampling of BG/BG2 movies that I've examined.) Note that an alternate possibility for the usage of the over-allocated space is as scratch space. This ~~possbility~~ will be addressed in the (voluminous!) documentation for opcode 0x11.		Width is the width of the buffer to allocate, and height is the height. Both are given in terms of pixels. Now, the count appears to be used to over-allocate the video buffer. To compute the size to allocate for the video buffer, they take 2 bytes per pixel, and multiply by the height and the width, and then multiply by the count. If scan-line doubling is enabled (which it is not in BG/BG2), it then divides this value by two, on the assumption that there is only enough data for half the resolution. Anyway, the over-allocation may be used to create a larger movie area and pan smoothly or something. I haven't seen a way to use the overallocation with the format details that I've discerned, but the video coding is particularly hairy, as the decoder relies on self-modifying x86 code to function. Yick. Anyway, I'm still in the process of looking for a file that uses over-allocation so that I can figure out exactly why it is used and what it is used for. (Again, this feature doesn't appear to be widely used in the sampling of BG/BG2 movies that I've examined.) Note that an alternate possibility for the usage of the over-allocated space is as scratch space. This possibility will be addressed in the (voluminous!) documentation for opcode 0x11.

	==== Opcode 0x06: unknown ====		==== Opcode 0x06: unknown ====
Line 138:		Line 138:
	bytes unknown		bytes unknown

	I haven't seen this opcode used in any BG/BG2 movies; however, this may be used for the panning or some clever usage of the over-allocation ~~mentionedin~~ opcode 0x05. If "flip back buffer?" has bit 0 set, it will flip the two allocated buffers before it does whatever it is that it does.		I haven't seen this opcode used in any BG/BG2 movies; however, this may be used for the panning or some clever usage of the over-allocation mentioned in opcode 0x05. If "flip back buffer?" has bit 0 set, it will flip the two allocated buffers before it does whatever it is that it does.

	The "whatever it does" appears to be characterized by bulk memory moves, which makes it possible that it _is_ used in conjunction with the over-allocated video buffers.		The "whatever it does" appears to be characterized by bulk memory moves, which makes it possible that it _is_ used in conjunction with the over-allocated video buffers.

DonDiego: samples link fix

2006-10-28T09:04:08Z

samples link fix

← Older revision		Revision as of 02:04, 28 October 2006
Line 1:		Line 1:
	* Extension: mve		* Extension: mve
	* Company: [[Interplay Entertainment]]		* Company: [[Interplay Entertainment]]
	* Samples: [http:/~~/www.mplayerhq.hu/MPlayer~~/samples~~/game-formats/interplay-mve/ http://www~~.mplayerhq.hu~~/MPlayer/samples~~/game-formats/interplay-mve/]		* Samples: http://samples.mplayerhq.hu/game-formats/interplay-mve/]
	* Sample Parser: [http://multimedia.cx/parse-ipmve.c http://multimedia.cx/parse-ipmve.c]		* Sample Parser: [http://multimedia.cx/parse-ipmve.c http://multimedia.cx/parse-ipmve.c]

Multimedia Mike: revert spam/vandalism

2006-03-24T19:30:46Z

revert spam/vandalism

Show changes

61.23.149.68: "

2006-03-24T08:38:28Z

Show changes

Multimedia Mike: sample link

2006-03-15T04:23:44Z

sample link

← Older revision		Revision as of 21:23, 14 March 2006
Line 1:		Line 1:
	* Extension: mve		* Extension: mve
	* Company: [[Interplay Entertainment]]		* Company: [[Interplay Entertainment]]
			* Samples: [http://www.mplayerhq.hu/MPlayer/samples/game-formats/interplay-mve/ http://www.mplayerhq.hu/MPlayer/samples/game-formats/interplay-mve/]
	* Sample Parser: [http://multimedia.cx/parse-ipmve.c http://multimedia.cx/parse-ipmve.c]		* Sample Parser: [http://multimedia.cx/parse-ipmve.c http://multimedia.cx/parse-ipmve.c]

Multimedia Mike: /* Opcode 0x05: Initialize Video Buffer(s) */

2006-02-05T18:52:18Z

Opcode 0x05: Initialize Video Buffer(s)

← Older revision		Revision as of 11:52, 5 February 2006
Line 123:		Line 123:
	WORD ?count?		WORD ?count?
	WORD true-color		WORD true-color

			'''(I think width and height are actually expressed as 8x8 pixel blocks. Need to verify. --[[User:Multimedia Mike\|Multimedia Mike]] 13:52, 5 February 2006 (EST))'''

	Width is the width of the buffer to allocate, and height is the height. Both are given in terms of pixels. Now, the count appears to be used to over-allocate the video buffer. To compute the size to allocate for the video buffer, they take 2 bytes per pixel, and multiply by the height and the width, and then multiply by the count. If scan-line doubling is enabled (which it is not in BG/BG2), it then divides this value by two, on the assumption that there is only enough data for half the resolution. Anyway, the over-allocation may be used to create a larger movie area and pan smoothly or something. I haven't seen a way to use the overallocation with the format details that I've discerned, but the video coding is particularly hairy, as the decoder relies on self-modifying x86 code to function. Yick. Anyway, I'm still in the process of looking for a file that uses over-allocation so that I can figure out exactly why it is used and what it is used for. (Again, this feature doesn't appear to be widely used in the sampling of BG/BG2 movies that I've examined.) Note that an alternate possibility for the usage of the over-allocated space is as scratch space. This possbility will be addressed in the (voluminous!) documentation for opcode 0x11.		Width is the width of the buffer to allocate, and height is the height. Both are given in terms of pixels. Now, the count appears to be used to over-allocate the video buffer. To compute the size to allocate for the video buffer, they take 2 bytes per pixel, and multiply by the height and the width, and then multiply by the count. If scan-line doubling is enabled (which it is not in BG/BG2), it then divides this value by two, on the assumption that there is only enough data for half the resolution. Anyway, the over-allocation may be used to create a larger movie area and pan smoothly or something. I haven't seen a way to use the overallocation with the format details that I've discerned, but the video coding is particularly hairy, as the decoder relies on self-modifying x86 code to function. Yick. Anyway, I'm still in the process of looking for a file that uses over-allocation so that I can figure out exactly why it is used and what it is used for. (Again, this feature doesn't appear to be widely used in the sampling of BG/BG2 movies that I've examined.) Note that an alternate possibility for the usage of the over-allocated space is as scratch space. This possbility will be addressed in the (voluminous!) documentation for opcode 0x11.

Multimedia Mike: /* Opcode 0xc: Set Palette */

2006-02-05T18:39:54Z

Opcode 0xc: Set Palette

← Older revision		Revision as of 11:39, 5 February 2006
Line 212:		Line 212:
	* pal-count indicates the number of palette entries to fill		* pal-count indicates the number of palette entries to fill
	* pal-data is the palette data, 3 bytes per palette entry, packed as RGBRGBRGB		* pal-data is the palette data, 3 bytes per palette entry, packed as RGBRGBRGB

			Note that the palette components are 6-bit VGA palette values and only range from 0..63. The values must be shifted to display properly in higher resolution color formats where RGB components are generally 8 bits.

	==== Opcode 0xd: Set Palette Entries Compressed ====		==== Opcode 0xd: Set Palette Entries Compressed ====