Free online USM to TRP converter

USM files usually contain CRI Sofdec game video, while TRP is an MPEG transport stream used by some televisions, DVRs, and playback tools. Conversion is needed when extracted game footage must be opened by hardware or software that accepts MPEG-TS rather than the proprietary USM container.

What the USM format is

USM is a video container created by CRI Middleware's Sofdec system and commonly used for game cutscenes, opening movies, menus, and other bundled video assets. The files are produced by CRI authoring tools and encountered inside PC, console, and arcade game installations.

A USM file can contain different video and audio combinations, including MPEG-1, MPEG-2, H.264, ADX, and HCA streams. Some releases also encrypt or obfuscate the contents, so the filename extension alone does not identify the codecs or guarantee that a general media player can read the file.

What the TRP format is

TRP is generally an MPEG transport stream, similar to an .ts file. It can carry several audio and video codecs in timestamped packets and is used by some digital television receivers, DVRs, set-top boxes, and device-specific playback software.

TRP does not require one universal codec combination. A target device may expect MPEG-2 video with MP2 audio, H.264 with AAC, or a particular resolution, frame rate, bitrate, and audio channel layout. Renaming a USM file to .trp does not perform a conversion.

How to actually convert USM to TRP

The reliable desktop workflow is to extract the streams from USM first, then mux or transcode them into an MPEG transport stream.

1. Make a backup of the original USM file. If it came from a game, extraction may be affected by encryption, proprietary audio, or an unusual Sofdec variant.
2. Open the file with a CRI USM-capable extractor, such as the relevant USM functionality in VGMToolbox or a compatible CRI USM extraction utility. Extract the video and audio streams rather than simply changing the extension. The result may be files such as .h264, .m2v, .adx, or .hca.
3. Inspect the extracted streams with FFmpeg's ffprobe. For example:

ffprobe video.h264

If the extracted video and audio codecs are accepted by the destination device, mux them without re-encoding:

ffmpeg -i video.h264 -i audio.aac -map 0:v:0 -map 1:a:0 -c copy -f mpegts output.trp

Replace the input names and codec assumptions with the files actually produced by the extractor. If the audio is ADX or HCA, decode it with a compatible CRI audio tool first; FFmpeg cannot decode every proprietary CRI audio variant in every build.

For broad hardware compatibility, transcode to MPEG-2 video and MP2 audio:

ffmpeg -i extracted_video.mkv -map 0:v:0 -map 0:a:0 -c:v mpeg2video -b:v 6M -c:a mp2 -b:a 192k -f mpegts output.trp

Use an intermediate container such as extracted_video.mkv only if the extractor or a prior muxing step provides one. The -f mpegts option creates the transport-stream format; .trp is the output filename convention.

You can also use the free converter on 101convert.com without installing software, provided its USM parser supports that particular CRI variant and the resulting TRP matches the requirements of your playback device.

Quality, compatibility, and limitations

Stream copying with -c copy preserves the extracted quality and avoids another generation of loss, but it may produce a TRP that a particular DVR or television cannot decode. Transcoding improves compatibility at the cost of quality and processing time.

Check the device's required video codec, audio codec, frame rate, resolution, maximum bitrate, packet format, and file-size limit before choosing settings. Use ffprobe output.trp to verify that the output contains the intended streams. If the USM is encrypted, damaged, or built with an unsupported Sofdec variant, it may need a release-specific extractor; a generic converter cannot recover unavailable or proprietary stream data.