Duck IVF: Difference between revisions
Jump to navigation
Jump to search
(found a Shantae game that uses this format) |
(fix incorrect offset) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 12: | Line 12: | ||
bytes 12-13 width in pixels | bytes 12-13 width in pixels | ||
bytes 14-15 height in pixels | bytes 14-15 height in pixels | ||
bytes 16- | bytes 16-19 time base denominator | ||
bytes 20-23 time base numerator | bytes 20-23 time base numerator | ||
bytes 24-27 number of frames in file | bytes 24-27 number of frames in file | ||
Line 23: | Line 23: | ||
bytes 12.. frame data | bytes 12.. frame data | ||
== PC games using | == PC games using IVF files == | ||
* [https://www.mobygames.com/game/rogue-trooper-redux Rogue Trooper Redux] | * [https://www.mobygames.com/game/rogue-trooper-redux Rogue Trooper Redux] |
Latest revision as of 18:01, 27 December 2022
- Extension: ivf
- Samples: The test-vectors-* archives available here: https://chromium.googlesource.com/webm/vp8-test-vectors
IVF is a simple file format that transports raw VP8 data.
Multi-byte numbers of little-endian. An IVF file begins with a 32-byte header:
bytes 0-3 signature: 'DKIF' bytes 4-5 version (should be 0) bytes 6-7 length of header in bytes bytes 8-11 codec FourCC (e.g., 'VP80') bytes 12-13 width in pixels bytes 14-15 height in pixels bytes 16-19 time base denominator bytes 20-23 time base numerator bytes 24-27 number of frames in file bytes 28-31 unused
The header is followed by a series of frames. Each frame consists of a 12-byte header followed by data:
bytes 0-3 size of frame in bytes (not including the 12-byte header) bytes 4-11 64-bit presentation timestamp bytes 12.. frame data