MultimediaWiki - Recent changes [en]

Microsoft Camcorder Video

Suxen drol — Sun, 26 Apr 2026 03:14:59 GMT

+GDICOD97.DRV

← Older revision		Revision as of 20:14, 25 April 2026
(One intermediate revision by the same user not shown)
Line 2:		Line 2:
	* Company: [[Microsoft]]		* Company: [[Microsoft]]
	* Samples: http://samples.mplayerhq.hu/V-codecs/CGDI/		* Samples: http://samples.mplayerhq.hu/V-codecs/CGDI/
			* Reference decoder: GDICOD97.DRV
	* References: http://support.microsoft.com/support/office/content/office97/camcorder.asp		* References: http://support.microsoft.com/support/office/content/office97/camcorder.asp

Line 15:		Line 16:
	The internal state keeps a list of GDI objects in an internal array and references them by ID so that the command e.g. for drawing a rectangle sends as parameters rectangle coordinates (left, top, right, bottom) as well as the brush ID that will be selected before rectangle will be drawn. In general the commands that have brush, pen IDs or such send those IDs at the end of the list but before the variable-length part (e.g. points to draw polyline).		The internal state keeps a list of GDI objects in an internal array and references them by ID so that the command e.g. for drawing a rectangle sends as parameters rectangle coordinates (left, top, right, bottom) as well as the brush ID that will be selected before rectangle will be drawn. In general the commands that have brush, pen IDs or such send those IDs at the end of the list but before the variable-length part (e.g. points to draw polyline).

	Known opcodes are:		Known opcodes and command arguments are:
	* <code>0x00</code> -- fill region using region and brush IDs		* <code>0x00</code> -- fill region using region and brush IDs
	* <code>0x01</code> -- draw a border around region; parameters are region/brush IDs plus stroke width/height		* <code>0x01</code> -- draw a border around region; parameters are region/brush IDs plus stroke width/height
Line 76:		Line 77:
	* <code>0x46</code> -- create new bitmap using data from the stream		* <code>0x46</code> -- create new bitmap using data from the stream
	* <code>0x47</code> -- init some window parameters		* <code>0x47</code> -- init some window parameters
	* <code>0x48</code> -- set default parameters to the drawing system (usually the very first opcode in the first frame)		* <code>0x48</code> -- set default parameters to the drawing system (usually the very first opcode in the first frame) and blt 1280x1024px area with solid colorref brush
			** <code>COLORREF</code>
	* <code>0x49</code> -- clear drawing system from used objects		* <code>0x49</code> -- clear drawing system from used objects
	* <code>0x4A</code> -- set some flag, probably for custom window clipping		* <code>0x4A</code> -- set some flag, probably for custom window clipping
	* <code>0x4B</code> -- delete requested object		* <code>0x4B</code> -- delete requested object

			Data types:
			* <code>COLORREF</code> - 4 bytes - <https://learn.microsoft.com/en-us/windows/win32/gdi/colorref>

	[[Category:Video Codecs]]		[[Category:Video Codecs]]

SCM

Suxen drol — Fri, 24 Apr 2026 22:18:10 GMT

← Older revision		Revision as of 15:18, 24 April 2026
Line 8:		Line 8:
	[[Category:Container Formats]]		[[Category:Container Formats]]
	[[Category: Formats missing in FFmpeg]]		[[Category: Formats missing in FFmpeg]]
			[[Category:GDI Codecs]]

Microsoft Camcorder Video

Suxen drol — Fri, 24 Apr 2026 22:17:59 GMT

← Older revision		Revision as of 15:17, 24 April 2026
Line 84:		Line 84:
	[[Category:Screen Capture Video Codecs]]		[[Category:Screen Capture Video Codecs]]
	[[Category:Formats missing in MPlayer]]		[[Category:Formats missing in MPlayer]]
			[[Category:GDI Codecs]]

Windows Metafile

Suxen drol — Fri, 24 Apr 2026 22:17:47 GMT

← Older revision		Revision as of 15:17, 24 April 2026
Line 11:		Line 11:

	[[Category:Image Formats]]		[[Category:Image Formats]]
			[[Category:GDI Codecs]]

Category:GDI Codecs

Suxen drol — Fri, 24 Apr 2026 22:17:35 GMT

Created page with "Codecs that use the Microsoft Windows Graphics Device Interface (GDI) API to render pixels, shapes, text and textures."

New page

Codecs that use the Microsoft Windows Graphics Device Interface (GDI) API to render pixels, shapes, text and textures.

Factor 5 VID1

Kostya — Thu, 23 Apr 2026 16:29:02 GMT

keep updating

← Older revision		Revision as of 09:29, 23 April 2026
Line 21:		Line 21:
	* 1 bit -- extended information present		* 1 bit -- extended information present
	* (extended information if present)		* (extended information if present)
	* 1 bit -- ?		* 1 bit -- rounding control
	* 3 bits -- DC quantiser threshold index (<code>intra_dc_vlc_thr</code>)		* 3 bits -- DC quantiser threshold index (<code>intra_dc_vlc_thr</code>)
	* 5 bits -- quantiser		* 5 bits -- quantiser
	* (non-I frames) 3 bits -- ~~something that seems to be used only in B-frames~~		* (non-I frames) 3 bits -- <code>vop_fcode_forward</code>
	* (B-frame only) 3 bits -- ?		* (B-frame only) 3 bits -- <code>vop_fcode_backward</code>
	* 32 bits -- timecode?		* 32 bits -- timecode
	* (frame ~~type 3~~ only) GMC/sprite information		* (S-frame only) GMC/sprite information
	* alignment to byte boundary		* alignment to byte boundary

	Extended information:		Extended information:
	* 1 bit -- ~~another extended bit~~		* 1 bit -- sprite information is present
	* (if ~~another extended bit~~ is ~~set~~) 2 bits -- ?~~, used in sprite information~~		* (if sprite information is present) 2 bits -- number of sprites?
	* (if ~~another extended bit~~ is ~~set~~) 2 bits -- ?		* (if sprite information is present) 2 bits -- sprite MV resolution?
	* 1 bit -- extended quantisation		* 1 bit -- extended quantisation
	* (if extended quantisation) 1 bit -- luma qmat present		* (if extended quantisation) 1 bit -- luma qmat present
Line 57:		Line 57:
	* (for MB type 1 only) 2 bits -- dquant		* (for MB type 1 only) 2 bits -- dquant
	* 1 or 4 motion vectors (with residual, just like ISO 14496-2)		* 1 or 4 motion vectors (with residual, just like ISO 14496-2)
			* block data

			B-frame macroblock layout:
			* 1 bit -- skip flag (if set, no further information is transmitted for the MB)
			* 1 bit -- coded MB
			* 1-4 bits -- macroblock type (as in table B-4 of ISO 14496-2)
			* (if MB is coded) 6 bits -- CBP
			* (if not direct MB and CBP is non-zero) 1-2 bits -- dbquant
			* (if applicable) forward/backward MV
	* block data		* block data

Factor 5 VID1

Kostya — Wed, 22 Apr 2026 17:12:10 GMT

start to fill some information

New page

* Company: Factor 5
* Extension: vid
* Game: [https://www.mobygames.com/game/9211/enter-the-matrix/ Enter the Matrix (Gamecube version)]
* demuxer code: [https://github.com/librempeg/librempeg/blob/master/libavformat/vid1.c librempeg]

This is a format used in at least one Gamecube game. VID1 format is not merely a container format but a proprietary video codec used in that container as well.

== Container format ==

This a typical chunked format starting with "VID1" header chunk, "HEAD" chunk containing stream headers, and "FRAM" chunks containing both video ("VIDD") and audio ("AUDD") data.

Audio codecs include PCM, variations of IMA ADPCM, or Vorbis.

== Video codec ==

VID1 video codec is a modification of MPEG-4 ASP.

Picture header:
* 16 bits -- ignored (sync marker?)
* 2 bits -- frame type (0 - I, 1 - P, 2 - B, 3 - S)
* 1 bit -- extended information present
* (extended information if present)
* 1 bit -- ?
* 3 bits -- DC quantiser threshold index (<code>intra_dc_vlc_thr</code>)
* 5 bits -- quantiser
* (non-I frames) 3 bits -- something that seems to be used only in B-frames
* (B-frame only) 3 bits -- ?
* 32 bits -- timecode?
* (frame type 3 only) GMC/sprite information
* alignment to byte boundary

Extended information:
* 1 bit -- another extended bit
* (if another extended bit is set) 2 bits -- ?, used in sprite information
* (if another extended bit is set) 2 bits -- ?
* 1 bit -- extended quantisation
* (if extended quantisation) 1 bit -- luma qmat present
* (if extended quantisation and luma qmat present) 8x8 bits -- luma qmat
* (if extended quantisation) 1 bit -- chroma qmat present
* (if extended quantisation and chroma qmat present) 8x8 bits -- chroma qmat
* 1 bit -- ignored
* 1 bit -- ignored

I-frames consists of macroblocks with the following layout:
* standard I MCBPC
* 1 bit -- AC prediction enabled
* I CBPY
* (if dquant is signalled) 2 bits -- dquant
* block data (likely just like ISO 14496-2 defines it)

P-frame macroblock layout:
* 1 bit -- skip flag (if set, no further information is transmitted for the MB)
* standard P MCBPC
* (for I-type MBs decoding is the same as in I-frames)
* 1 bit -- mcsel?
* P CBPY
* (for MB type 1 only) 2 bits -- dquant
* 1 or 4 motion vectors (with residual, just like ISO 14496-2)
* block data

Motion compensation is normal halfpel.

[[Category:Video Codecs]]
[[Category:Container Formats]]
[[Category:Game Formats]]

Adorage effects codec

Kostya — Fri, 17 Apr 2026 16:10:12 GMT

yet another simple codec

New page

* Company: proDAD
* FOURCC: pDAD

This is a codec used to store effects for proDAD Adorage video editor.

Each frame actually consists of two images, actual picture and its alpha mask. Usually it is JPEG image with PNG alpha mask but JPEG image with JPEG mask samples are also known and other combinations are theoretically possible.

Frame format:
* 4 bytes -- header size (12 bytes)
* 2 bytes -- image part type (<code>JP</code> for JPEG, <code>PG</code> for PNG)
* 2 bytes -- alpha mask type (in the same format)
* 4 bytes -- unknown, usually zero
* 4 bytes -- image part size
* 4 bytes -- alpha part size
* N bytes -- image picture
* M bytes -- alpha picture

[[Category:Video Codecs]]

MoviePak

Kostya — Fri, 17 Apr 2026 15:59:54 GMT

add description

New page

* Company: RasterOps

This is a simple [[JPEG]]-based video codec for Classic Mac QuickTime.

Frame format:
* 2 bytes -- frame width
* 2 bytes -- frame height
* 4 bytes -- first field size (or whole frame for non-interlaced files)
* 4 bytes -- second field size (0 for non-interlaced files)
* 64 bytes -- luma quantisation matrix
* 64 bytes -- chroma quantisation matrix
* N bytes -- first field data
* M bytes -- second field data (if present)

Field data is raw (non-escaped) JPEG data for 4:2:2 subsampling.

[[Category:Video Codecs]]

PDQ2

Kostya — Fri, 17 Apr 2026 15:54:31 GMT

add description

New page

* FOURCC: PDQ2
* Game: [https://www.mobygames.com/game/6145/the-incredible-hulk-the-pantheon-saga/ The Incredible Hulk: The Pantheon Saga]

This is a codec used in DOS and Saturn versions of one game and there's not much known about it (not even the proper name). From compression point of view the codec operates on 4x4 tiles that can be either coded raw or copied from some other place in the frame. DOS version allows additional LZ compression of frame data. Also while Saturn version encodes 16-bit pixels, DOS version works on 8-bit paletted format.

Frame structure (all multi-byte values endianness is native to the platform i.e. LE for DOS and BE for Saturn):
* 1 byte -- frame type (0 - DOS normal frame, 1 - DOS packed frame, 0x80 - Saturn frame)
* 2 bytes -- if zero frame should be cleared
* 2 bytes -- size of opcodes part
* 2 bytes -- size of motion vectors part
* 2 bytes -- unknown data part
* N bytes -- opcodes
* X bytes -- unknown data
* M bytes -- MV data
* P bytes -- colour data

Decoding goes as following: while not all tiles are processed read opcode, depending on it read motion vector or colour data, paint/copy tile (or several, if the opcode signals it).

Known opcodes:
* <code>0x85</code> -- motion tile, motion vector is coded as two signed 16-bit ints
* <code>0x86</code> -- invalid opcode
* <code>0x87</code> -- modifier; read next opcode, its top bit tells if it's a tile run or a tile skip minus one
* <code>0x88</code> -- motion tile, motion vector is coded as two bytes, unsigned for X component and signed for Y component
* <code>0x89</code> -- raw tile, read 16 pixel values from colour data for it
* <code>0x8A</code> -- motion tile, motion vector is coded as two bytes, X is in -256..-1 range, Y is in -128..127 range
* all other opcodes are for motion tiles, coding MV as signed nibbles e.g. <code>0xC4</code> corresponds to <code>(4,-4)</code>

[[Category:Game Formats]]
[[Category:Video Codecs]]
[[Category:Video FourCCs]]

STJ

Dun4d — Thu, 16 Apr 2026 20:17:16 GMT

← Older revision		Revision as of 13:17, 16 April 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	STJ is a file format created by STMicroelectronics around 2004. It is a format to store video based around the STV0674 chip.		STJ is a file format created by STMicroelectronics around 2004 - 2006. It is a format to store video based around the STV0674 chip.

	~~The file format~~ is ~~not designed to be played back~~, ~~rather to store a series of JPEG'S and uncompressed 8bit audio at~~ 8~~, 11.5 or 21khz~~.		Audio is always 512 bytes in length, with the first two bytes being FF FF. After that, pure unsigned 8 bit.

	The ~~original STJ2MOV (Mac)~~ and ~~AVICREATE (Windows) software to decode~~ is ~~no longer around~~, ~~though an open~~-~~source decoder is here~~.		Audio can interrupt video, so JPG frame may be started with FF FF interrupting.
	~~https~~://~~github~~.com/~~dun4d~~/~~demuxstj~~
			FourCC is STAV followed by 01, indicating there may be one version of this.

			Video is either 15fps at 320x240, or 640x480 at 30fps.

			The file format is not designed to be played back, rather to store. It's a series of JPGs and audio is uncompressed 8bit audio at 8, 11.5 or 21khz.

			Review of device.
			http://www.dansdata.com/edvr.htm

			Spec sheet of the chip.
			http://pdf.dzsc.com/74-/STV0674-100TQFP_1134827.pdf

			Archive of STV0674 download page.
			http://web.archive.org/web/*/http://www.st.com/stonline/products/applications/consumer/cmos_imaging/processors/674_nms_sw.htm