In some examples, the workflow may include automated computer-executed processes—e.g., applying effects to changed video, performing an audio mixing for changed audio content, etc. In some examples, the workflow may include preparing one or more users and/or teams with content useful for completing a task associated with the set of edits (e.g., data resources and/or directory structures associated with visual effects if a new scene has been inserted).

In some examples, the workflow may include a version control function. For example, by tokenizing the content of the media data objects (in terms of common and different contiguous subsequences between the media data objects), updated versions of a media asset may be represented in terms of changes applied to the media asset. Where two different teams make simultaneous modifications to a master media asset, the systems described herein may merge the identified changes from the two updated versions of the asset.

FIG. 3 is an illustration of two exemplary media assets processed such that a set of edits between the assets are identified. As shown in FIG. 3, a string 310 represents tokenized content of a first media data object and a string 330 represents tokenized content of a second media data object. Each token represents a contiguous subsequence of temporal content segments. A subsystem 302 analyzes strings 310 and 330 to determine a set of edits that describes the difference between strings 310 and 330. Thus, string 310, having tokens 312, 314, 316, 318, and 320, is modified with an insertion of a token 332, a substitution of a token 316 with a token 334, and a deletion 336 of token 320.