USM - Revision history

Reimar at 19:18, 3 September 2013

2013-09-03T19:18:55Z

← Older revision		Revision as of 12:18, 3 September 2013
Line 12:		Line 12:
	* 4 byte identifier string		* 4 byte identifier string
	* 4 byte length of data not including 8 bytes for identifier and length, big-endian		* 4 byte length of data not including 8 bytes for identifier and length, big-endian
	* 2 byte unknown		* 2 byte unknown (always 0 for @UTF, 0x18 otherwise?)
	* 2 byte padding bytes		* 2 byte padding bytes
	* 4 byte probably type 1 = header, 2 = metadata, 3 = index, 0 = data		* 4 byte probably type 1 = header, 2 = metadata, 3 = index, 0 = data
	* 4 byte timestamp		* 4 byte timestamp
	* 4 byte unknown		* 4 byte unknown
	* 8 byte unknown		* 8 byte unknown (always 0, padding?)

	The known indentifier strings are:		The known indentifier strings are:

Reimar at 16:35, 1 September 2013

2013-09-01T16:35:17Z

← Older revision		Revision as of 09:35, 1 September 2013
Line 11:		Line 11:
	The format of a chunk is		The format of a chunk is
	* 4 byte identifier string		* 4 byte identifier string
	* 4 byte length, big-endian		* 4 byte length of data not including 8 bytes for identifier and length, big-endian
	* 2 byte unknown		* 2 byte unknown
	* 2 byte padding bytes		* 2 byte padding bytes
Line 20:		Line 20:

	The known indentifier strings are:		The known indentifier strings are:
	* CRID ~~main~~ header		* CRID Main header, usually 512 bytes long
	* @UTF Used only as a sub-chunk, only 32 byte aligned. Header/meta data, consisting of first the (binary) real data, followed by a textual description of the fields.		* @UTF Used only as a sub-chunk, only 32 byte aligned. Header/meta data, consisting of first the (binary) real data, followed by a textual description of the fields.
	* @SFV Video stream. If type is "data", the actual data seems to start only at offset 0x60.		* @SFV Video stream. If type is "data", the actual data seems to start only at offset 0x60.

Reimar at 16:33, 1 September 2013

2013-09-01T16:33:17Z

← Older revision		Revision as of 09:33, 1 September 2013
Line 2:		Line 2:

	This format is used by e.g. "The Witcher 2".		This format is used by e.g. "The Witcher 2".

	It contains ordinary MPEG (probably MPEG-2) video, with the encoder string "TMPGEXE" being very obvious.		It contains ordinary MPEG (probably MPEG-2) video, with the encoder string "TMPGEXE" being very obvious.

	The file consists of (in the header nested) chunks.		The file consists of (in the header nested) chunks.

	Each main chunk is at least 64 byte aligned (though the design of the format should allow anything between including 0 and 64kB alignment if desired).		Each main chunk is at least 64 byte aligned (though the design of the format should allow anything between including 0 and 64kB alignment if desired).

	The format of a chunk is		The format of a chunk is
	4 byte identifier string		* 4 byte identifier string
	4 byte length, big-endian		* 4 byte length, big-endian
	2 byte unknown		* 2 byte unknown
	2 byte padding bytes		* 2 byte padding bytes
	4 byte probably type 1 = header, 2 = metadata, 3 = index, 0 = data		* 4 byte probably type 1 = header, 2 = metadata, 3 = index, 0 = data
	4 byte timestamp		* 4 byte timestamp
	4 byte unknown		* 4 byte unknown
	8 byte unknown		* 8 byte unknown

	The known indentifier strings are:		The known indentifier strings are:
	CRID main header		* CRID main header
	@UTF Used only as a sub-chunk, only 32 byte aligned. Header/meta data, consisting of first the (binary) real data, followed by a textual description of the fields.		* @UTF Used only as a sub-chunk, only 32 byte aligned. Header/meta data, consisting of first the (binary) real data, followed by a textual description of the fields.
	@SFV Video stream. If type is "data", the actual data seems to start only at offset 0x60.		* @SFV Video stream. If type is "data", the actual data seems to start only at offset 0x60.
	@SFA Audio stream. If type is "data", the actual data just like for metadata seems to start at offset 0x20.		* @SFA Audio stream. If type is "data", the actual data just like for metadata seems to start at offset 0x20.

	An index (called SEEKINFO) seems to only exist for video (it is placed into a @SFV tag), probably assuming the audio to be correct interleaved.		An index (called SEEKINFO) seems to only exist for video (it is placed into a @SFV tag), probably assuming the audio to be correct interleaved.

	[[Category:Container Formats]]		[[Category:Container Formats]]

Reimar at 16:32, 1 September 2013

2013-09-01T16:32:08Z

← Older revision		Revision as of 09:32, 1 September 2013
Line 21:		Line 21:
	@SFA Audio stream. If type is "data", the actual data just like for metadata seems to start at offset 0x20.		@SFA Audio stream. If type is "data", the actual data just like for metadata seems to start at offset 0x20.

	An index (~~calles~~ SEEKINFO) seems to only exist for video (it is placed into a @SFV tag), probably assuming the audio to be correct interleaved.		An index (called SEEKINFO) seems to only exist for video (it is placed into a @SFV tag), probably assuming the audio to be correct interleaved.

			[[Category:Container Formats]]

Reimar at 16:29, 1 September 2013

2013-09-01T16:29:57Z

New page

USM Container format

This format is used by e.g. "The Witcher 2".
It contains ordinary MPEG (probably MPEG-2) video, with the encoder string "TMPGEXE" being very obvious.
The file consists of (in the header nested) chunks.
Each main chunk is at least 64 byte aligned (though the design of the format should allow anything between including 0 and 64kB alignment if desired).
The format of a chunk is
4 byte identifier string
4 byte length, big-endian
2 byte unknown
2 byte padding bytes
4 byte probably type 1 = header, 2 = metadata, 3 = index, 0 = data
4 byte timestamp
4 byte unknown
8 byte unknown

The known indentifier strings are:
CRID main header
@UTF Used only as a sub-chunk, only 32 byte aligned. Header/meta data, consisting of first the (binary) real data, followed by a textual description of the fields.
@SFV Video stream. If type is "data", the actual data seems to start only at offset 0x60.
@SFA Audio stream. If type is "data", the actual data just like for metadata seems to start at offset 0x20.

An index (calles SEEKINFO) seems to only exist for video (it is placed into a @SFV tag), probably assuming the audio to be correct interleaved.