UPDATE: It seems, at least for some "USM" containers, patching in a modified video file may be possible, however further experimentation and research into compression used (if any) by Criware in their "USM" containers (currently testing on the 2012 title "The Amazing Spider-man").
UPDATE 2: Patching in videos didn't work, however it seems it may be possible to decode the cue points from the .usm container as they are stored in plain text, however some values are difficult to translate, I'll update in a few days most likely.
Hi all,
Over the past few months I've been researching the "USM" file format, with the end-goal of successfully encoding the videos within such a file, as most from older titles ("Batman: Arkham City", "Batman: Arkham Knight" & "Mad Max") can be encoded with very little perceivable loss in quality to the naked eye, with the result of significantly reduced file size. However, "USM" containers with cue points will soft-lock the title upon completion of the video file, when attempting to execute an encoded "USM", requiring either the end-user restart the title and skip the video file, or, (and is my current solution), extend the video file to a given length, with a disclaimer informing the end-user they must skip the video.
This issue has been documented in passing
[1][2], however a solution hasn't yet been found (to my knowledge). If anyone has any insight into this file format, and extraction of cue points & subtitles, or might be able to point me in the right direction to sourcing the CRIWARE SDK and/or the AutoDesk Media & Entertainment Collection, I'd greatly appreciate it.
16-07-2021, 07:39
Threaded Mode