Quote:
Originally Posted by :( Sad8669
Yo man, you've been dealing with .usm files.
Can you explain a little about cue points in a simple manner?
|
Cue points are essentially a set of instructions executed at a given point (or duration) within the runtime of a given video file. These can, for example, include instructions when to end rendering and when to activate controller rumble features and at what intensity to do so.
Thankfully not all titles that utilises CRIWARE's container format include cue points, as some engines allow for such instructions to be executed in-engine. It can also be a developers choice to include/exclude the use of cue points, for reasons I'm not yet clear on. Deciphering these cue-points can be trivial (for titles such as "Batman: Arkham City"), but can also be trickier for other titles, as there is no universal set of instructions, and even formatting of the cue points can change from title to title. So far I've had success with each title I've attempted this with, however more testing is required to determine whether these methods can be applied universally (depending on how the ".usm" is loaded by a given title (not engine-specific) into memory, and a guide can be published, as some encoded videos will not terminate correctly, even if the methodology is identical to a working, encoded ".usm".
I'm also reluctant to release a guide just to spite some users over at the Xentax forums who were really unhelpful buggers, but were still expecting me to educate them should I be successful.