Sequence Size and Complexity

As you increase the complexity of your sequence, the demands on your MediaCentral Cloud UX server(s) might also increase. In some cases you can mitigate these demands by outfitting your server(s) with additional or more powerful resources – such as faster processors, faster solid-state drives, or more RAM. In other cases, you might create a sequence whose size or complexity strains the design of the MediaCentral Cloud UX system.

As user-load, media codecs, system resources, and other factors all contribute to the ability to load or save any individual sequence, Avid cannot provide you with exact performance values or define the point at which a sequence becomes too “complex”. However, you can use the following information to help you determine where complexity might be introduced and how large sequences might perform on your organization’s MediaCentral system:

• After you load a sequence for the first time, MediaCentral Cloud UX caches the sequence to the server’s storage. Assuming that this process completes successfully, subsequent loads of the same sequence are often much faster for all users. If the Asset Editor cannot load the sequence, the user interface might display a timeout error.

• Avoid creating, loading, or saving sequences that include more than 50 unique assets.

• Avoid creating or loading sequences with more than 100 segments. A segment is defined as a portion of a media asset that is cut into a sequence. When loading a sequence that contains a large number of segments, the user interface might display a timeout error. As long as the load process completes, this error can be ignored.

• Sequences with a large number of segments might fail to save. Although Avid has experienced this behavior with sequences that include 500 or more segments, your maximum segment count might vary. When saving a sequence of this size, you must be patient as the save process could take several minutes. During this time, the MediaCentral Cloud UX user interface might display timeout error while the back-end system continues to process the save request.

• When working with the assets from a particular MediaCentral module (Production Management, Asset Management, etc), note that system load on the module itself could affect operations related to those assets.

• The scale of your MediaCentral Cloud UX system could have an effect on the speed at which a sequence can be saved. If you have a large number of users, you might consider expanding to a clustered configuration, or add nodes to an existing cluster.

For additional information, see Playback of Simple and Complex Sequences. For more information on provisioning hardware resources and determining scale, see the Avid MediaCentral | Cloud UX Hardware Guide.