Fraps - Revision history

Compn: v3 was found and fixed , update

2008-12-13T19:46:03Z

v3 was found and fixed , update

← Older revision		Revision as of 12:46, 13 December 2008
Line 3:		Line 3:
	* Samples: [http://samples.mplayerhq.hu/V-codecs/FPS1/ http://samples.mplayerhq.hu/V-codecs/FPS1/]		* Samples: [http://samples.mplayerhq.hu/V-codecs/FPS1/ http://samples.mplayerhq.hu/V-codecs/FPS1/]

	The Fraps video codec is used to store in real-time data that is captured from high frame-rate computer games played on Windows PCs. There are 5 known versions of the codec: 0, 1, 2, 4, and 5~~; version 3 might exist but no samples have been seen in the wild~~. All versions occur with the same FourCC.		The Fraps video codec is used to store in real-time data that is captured from high frame-rate computer games played on Windows PCs. There are 6 known versions of the codec: 0, 1, 2, 3, 4, and 5. All versions occur with the same FourCC.

	== Header ==		== Header ==
Line 62:		Line 62:

	Lines are coded as the difference from the previous lines. For Y plane the line with index - 1 should contain all zeroes; for chroma planes - all 128.		Lines are coded as the difference from the previous lines. For Y plane the line with index - 1 should contain all zeroes; for chroma planes - all 128.

			== Version 3 ==
			Version 3 Fraps data, according to investigations, appears to be identical to v5 and can be decoded by the same algorithm.

	== Version 4 ==		== Version 4 ==

Kostya: /* Version 5 */ Now a bit more on version 5 is known

2008-08-10T18:12:58Z

Version 5: Now a bit more on version 5 is known

← Older revision		Revision as of 11:12, 10 August 2008
Line 68:		Line 68:
	== Version 5 ==		== Version 5 ==
	Version 5 Fraps data is the same as version 4, but encodes planar RGB24 upside-down.		Version 5 Fraps data is the same as version 4, but encodes planar RGB24 upside-down.
			For better compression ratio red and blue components are stored as a differences to the green component.

	[[Category:Video Codecs]]		[[Category:Video Codecs]]
	[[Category:Screen Capture Video Codecs]]		[[Category:Screen Capture Video Codecs]]

Multimedia Mike: remove the incomplete category since all known versions are supported

2008-03-09T16:39:28Z

remove the incomplete category since all known versions are supported

← Older revision		Revision as of 09:39, 9 March 2008
Line 70:		Line 70:

	[[Category:Video Codecs]]		[[Category:Video Codecs]]
	~~[[Category:Incomplete Video Codecs]]~~
	[[Category:Screen Capture Video Codecs]]		[[Category:Screen Capture Video Codecs]]

Kostya: /* Version 5 */ Now is it discovered

2008-03-09T08:32:32Z

Version 5: Now is it discovered

← Older revision		Revision as of 01:32, 9 March 2008
Line 67:		Line 67:

	== Version 5 ==		== Version 5 ==
	Version 5 Fraps data ~~uses an undetermined algorithm~~.		Version 5 Fraps data is the same as version 4, but encodes planar RGB24 upside-down.

	[[Category:Video Codecs]]		[[Category:Video Codecs]]
	[[Category:Incomplete Video Codecs]]		[[Category:Incomplete Video Codecs]]
	[[Category:Screen Capture Video Codecs]]		[[Category:Screen Capture Video Codecs]]

Multimedia Mike: /* Version 2 */ general edits

2008-03-09T04:50:13Z

Version 2: general edits

← Older revision		Revision as of 21:50, 8 March 2008
Line 40:		Line 40:

	All data is stored in 32-bit little-endian words.		All data is stored in 32-bit little-endian words.
	If frame size is 8 bytes long then repeat previous frame ~~otherwise~~ proceed to frame decoding.		If the total frame size is 8 bytes long then repeat the previous frame. Otherwise, proceed to frame decoding.

	=== Frame header ===		=== Frame header ===

	bytes 0- 7 - should be ignored		bytes 0- 7 should be ignored
	bytes 8-11 - 'FPSx'		bytes 8-11 'FPSx'
	bytes 12-15 - offset to the Y plane (minus 8), should be ~~always~~ 16		bytes 12-15 offset to the Y plane (minus 8), should always be 16
	bytes 16-19 - offset to the U plane (minus 8)		bytes 16-19 offset to the U plane (minus 8)
	bytes 20-23 - offset to the V plane (minus 8)		bytes 20-23 offset to the V plane (minus 8)

	=== Huffman tree construction ===		=== Huffman tree construction ===
	Huffman tree is built by canonical algorithm: sort symbols by their counts in ascending order, create node by joining two first nodes (or leaves)~~, and~~ place it just before the node with count greater than this new node.		The Huffman tree is built by the canonical algorithm:
			* sort symbols by their counts in ascending order
			* create node by joining two first nodes (or leaves)
			* place the node just before the node with a count greater than this new node.

	~~<b>~~WARNING~~</b>~~ If symbols have zero count they should also be included ~~into~~ the tree. So Huffman tree for this codec always has 256 leaves.		'''WARNING''' If symbols have a zero count they should also be included in the tree. The Huffman tree for this codec always has 256 leaves.

	=== Plane format ===		=== Plane format ===
	First 256 words (1 kB) of plane data are symbol frequencies used to construct Huffman tree. The rest of data represents bitstream packed into 32-bit words, MSB first.		First 256 words (4 byte each, 1 kB total) of plane data are symbol frequencies used to construct the Huffman tree. The rest of the data represents the bitstream packed into 32-bit words, MSB first.

	Lines are coded as difference to the previous lines. For Y plane the line with index -1 should contain all zeroes, for chroma planes - all 128.		Lines are coded as the difference from the previous lines. For Y plane the line with index - 1 should contain all zeroes; for chroma planes - all 128.

	== Version 4 ==		== Version 4 ==

Multimedia Mike: /* Version 2 */ quick intro

2008-03-09T04:45:23Z

Version 2: quick intro

← Older revision		Revision as of 21:45, 8 March 2008
Line 37:		Line 37:

	== Version 2 ==		== Version 2 ==
			Version 2 Fraps data stores YUV data with a [[Huffman]] scheme.

	All data is stored in 32-bit little-endian words.		All data is stored in 32-bit little-endian words.
	If frame size is 8 bytes long then repeat previous frame otherwise proceed to frame decoding.		If frame size is 8 bytes long then repeat previous frame otherwise proceed to frame decoding.

Multimedia Mike: /* Version 5 */

2008-03-09T04:43:54Z

Version 5

← Older revision		Revision as of 21:43, 8 March 2008
Line 62:		Line 62:

	== Version 5 ==		== Version 5 ==
			Version 5 Fraps data uses an undetermined algorithm.

	[[Category:Video Codecs]]		[[Category:Video Codecs]]
			[[Category:Incomplete Video Codecs]]
	[[Category:Screen Capture Video Codecs]]		[[Category:Screen Capture Video Codecs]]

Multimedia Mike: /* Version 4 */

2008-03-09T04:43:08Z

Version 4

← Older revision		Revision as of 21:43, 8 March 2008
Line 59:		Line 59:

	== Version 4 ==		== Version 4 ==
			Version 4 Fraps data, according to investigations, appears to be identical to v2 and can be decoded by the same algorithm.

	== Version 5 ==		== Version 5 ==

Multimedia Mike: /* Version 1 */

2008-03-09T04:41:22Z

Version 1

← Older revision		Revision as of 21:41, 8 March 2008
Line 34:		Line 34:

	== Version 1 ==		== Version 1 ==
			Version 1 Fraps data is 24-bit BGR data stored in an upside-down order, similar to the way that Microsoft [[BMP]] files store their data.

	== Version 2 ==		== Version 2 ==

Multimedia Mike: /* Version 0 */

2008-03-09T04:38:43Z

Version 0

@@ Line 17: / Line 17: @@
 == Version 0 ==
-Version 0 Fraps data is essentially reordered [[YUV 4:2:0]] planar video data.
+Version 0 Fraps data is planar [[YUV 4:2:0]] video data stored in an interleaved manner. The payload bytestream is formatted at:
 == Version 1 ==