Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:CRI USM

From ReverseEngineering.wiki
Format
Developer CRI Middleware
Magic CRID (43 52 49 44)
Extensions .usm
Endianness big
License proprietary; reader: vgmstream
On this wiki Facts · Code · Notes · Topics

CRI's Sofdec2 video container (.usm): magic CRID, an @UTF header table named CRIUSF_DIR_STREAM and interleaved typed chunks @SFV (video: M2V, VP9, H.264), @SFA (audio: HCA or ADX), @SBT (subtitles), each chunk possibly partially encrypted.

Layout

CRID at 0, u16 header size at 0x08 (header table at that size + 8 = 0x20), then an Format:CRI UTF table named CRIUSF_DIR_STREAM with one row per stream (fields stmid four-character stream type, chno channel number, filename). The stream follows as chunks tagged by their four-character type: @SFV video, @SFA audio, @SBT subtitles; every chunk has a payload type (0 data, 1 header, 2 comment, 3 seek) and a channel number; header chunks carry their own @UTF table with codec, channels and sample rate. The payload is the plain elementary stream (MPEG-2 m2v, H.264, VP9 for video; HCA or ADX for audio). Chunks can be masked with a game key and the HCA inside can be keyed separately.

Audio is extracted by concatenating the data chunks of one @SFA channel. Keys are out of scope.

Related

Library:CRIWARE, Format:HCA, Format:Bink video (BIK, KB2).

Evidence & references

  • vgmstream commit db77f98f405a45ad08df98aa444cae3848f95e6c (ISC): src/meta/crid.c lines 10-80, crid_streamfile.h (comment on chunk types).